Page 1 of 2
C++ runtime error
Posted: Wed Jan 18, 2006 10:47 am
by hdesbois
...when loading materials from a texture-heavy scene. Just stops at 75% with this message. Anyone else having the same problem?
2 GB ram, so this should not be an issue
HD
Re: C++ runtime error
Posted: Wed Jan 18, 2006 3:01 pm
by mane162
hdesbois wrote:...when loading materials from a texture-heavy scene. Just stops at 75% with this message. Anyone else having the same problem?
2 GB ram, so this should not be an issue
HD
It´s a RAM memory amount used in the prosess. Press ALT+CTRL+SUPR and see how many RAM have reached your mxcl, maybe 1.400 at least is consummed in this process. this problems appear to me when:
1. I use high polys scenes (more than 3.0 millions)
2. When you use so high resolution textures
mane162
Posted: Wed Jan 18, 2006 3:17 pm
by hdesbois
memory use was huge, more that 2gb and a good deal of swapping, I think. But this scene renders ok with beta, or LW (native or fprime). So, obviously, RC5 is not ready for complex scenes (and this one was just using middle to moderately high rez textures, nothing unreasonable).
HD
Re: C++ runtime error
Posted: Wed Jan 18, 2006 3:19 pm
by AndreD
hdesbois wrote:...when loading materials from a texture-heavy scene. Just stops at 75% with this message. Anyone else having the same problem?
2 GB ram, so this should not be an issue
HD
imho, 2GB is the maximum amount for windows 32 bit..
(2GB app/2GB kernl)
Re: C++ runtime error
Posted: Wed Jan 18, 2006 3:21 pm
by mane162
AndreD wrote:hdesbois wrote:...when loading materials from a texture-heavy scene. Just stops at 75% with this message. Anyone else having the same problem?
2 GB ram, so this should not be an issue
HD
imho, 2GB is the maximum amount for windows..
(2GB app/2GB kernl)
for windows 32 bits sure
mane162
Re: C++ runtime error
Posted: Wed Jan 18, 2006 3:22 pm
by AndreD
mane162 wrote:AndreD wrote:hdesbois wrote:...when loading materials from a texture-heavy scene. Just stops at 75% with this message. Anyone else having the same problem?
2 GB ram, so this should not be an issue
HD
imho, 2GB is the maximum amount for windows..
(2GB app/2GB kernl)
for windows 32 bits sure
mane162
thank you for making it clearer, same time, by the way
2006 1:21 pm;
Posted: Wed Jan 18, 2006 3:42 pm
by Hervé
This is a real drag..... all scnens that render fine before now crash... I have a dual AMD with 2GB ram like Henri, and this is just not acceptable... I don't even try a 3 million polys scene... 1 million is enough... high rez textures... well the biggest I have in that scene are 2000x1200 pix... so ....
we need a new LW plugin..... I just cannot believe they have not tested this one AT ALL before releasing... insane...
Posted: Wed Jan 18, 2006 6:38 pm
by Mihai
Hervé, what is the procedure exactly? You save out a mxs from LW, then try and import it into Studio?
It could be that certain translated materials from the plugin make Studio crash. Try exporting your geometry with a default maxwell material (with a bitmap applied in the color slot to make sure uv info is also translated), then make all your materials from scratch in Studio. It is a bad idea anyway to start making your Maxwell materials in LW or any host app.
Posted: Wed Jan 18, 2006 9:18 pm
by hdesbois
Ok, this not only a plugin issue : I had a scene loaded in studio, and 3D viewport set to render mode. Got the very same error message when hitting render button. After reloading the same scene but with simple shaded preview, hitting render was ok.
HD
Posted: Wed Jan 18, 2006 9:29 pm
by Mihai
It could be a plugin issue because it doesn't translate materials properly, giving problems with Studio.
Posted: Wed Jan 18, 2006 9:38 pm
by Hervé
hello Mihai....mmm yes indee it looks like a plugin issue... so what you advise is to make a basic (at least) surface in LW with just the color texture in Slot channel... that might work..... but look here what Henri found...
http://www.maxwellrender.com/forum/view ... hp?t=11100
Thankx a lot Mihai...
Posted: Wed Jan 18, 2006 9:43 pm
by Hervé
I am thinking also the plugin because of this... whenever I hit the preview little yellow arrows...
Posted: Wed Jan 18, 2006 9:43 pm
by Mihai
Well, doesn't matter......new plugins will come out, but I would still make and apply materials in Studio. Makes no sense to start tweaking them in LW, when the best material editor including preview and render region is in Studio....
Posted: Wed Jan 18, 2006 9:46 pm
by Mihai
Hervé, you need to apply a maxwell mat, WITH a bitmap to the color channel so that the uv info is translated into the mxs. You get that error when there is no uv info in the object, because the uv's weren't transferred to the mxs when you exported from LW....because you didn't apply a material WITH a bitmap
Posted: Wed Jan 18, 2006 10:16 pm
by Hervé
Mihai Iliuta wrote:Hervé, you need to apply a maxwell mat, WITH a bitmap to the color channel so that the uv info is translated into the mxs. You get that error when there is no uv info in the object, because the uv's weren't transferred to the mxs when you exported from LW....because you didn't apply a material WITH a bitmap
no no I swear, I applied a texture in color slot, and with a UV... no problem... I am thinking it comes from the fact (as you said) that I'd better texture in studio, you're right... maybe it is because I applied also some texure in the spec channel in LW... and when I save the MXS from LW, I get some erroe messages "spec strentgh error...
I'll try with just the color Bitmap (for UV transfer into MXS) and do the rest in Studio...
BTW, I've already asked you in another thread (so feel free totell me go to hell...)... -- do we absolutlely need UV maps from LW, or do planar or cubic also work...?
Thanks a looooottt