Maxwell Render | Official public forum

It gets to SL 1.00 And just stalls. The time keeps running as if its still calculating but The Next Sl and Update says Waiting . Also The percentage of the rendering increases but no new SL. What could be causing this?

Well, it means exactly what it sais.... Can't go more than SL 1.0 so there is probably something wrong.... Since the calculation and the rendering time is running MXCL is working.... try to examine the scene especially displacement materials.... How long did you wait before you decide there is something wrong?

gadzooks,
can you copy the text in Maxwell Render Console and paste it in this thread?

You know - the text saying something like this:

Is it writing a huge mxi file (high resolution or many emitter multilight)? It will say "waiting" while it is writing the file. If you are writing to a network drive, it will take even longer.

JTB What should i look for in Displacement Materials?



KurtS Here is what it says:

===================== New session opened at 05/February/2002 05:03:37 =====

Maxwell Render® 1.7.0 - win32
(C) 2004-2007. Next Limit Technologies

C:\Program Files\Next Limit\Maxwell\mxcl.exe -d -p:low
--------------------------------------------------------------------------

WARNING: - Low Priority Enabled

[05/February/2002 05:03:56] Reading MXS:F:/2007/0756-AIS Science Building/KennyImages/Ais_1.MXS
[05/February/2002 05:04:24] MXS file read successfully

Geometry:
- Num Meshes: 737
- Num Triangles: 2188630
- Num Vertexes: 1113556
- Num Normals: 1066115
Render settings:

- render core : RS1
- render version : Maxwell Render® 1.7.0 - win32
- desired rendering time : 16h00s
- desired sampling level : 30.000
- render resolution : 3000 x 1667
- using 0 threads
- illumination layers:
. . direct layer: true
. . indirect layer: true
. . direct caustic reflection layer: true
. . direct caustic refraction layer: true
. . indirect caustic reflection layer: true
. . indirect caustic refraction layer: true

[05/February/2002 05:06:49] Checking Data
[05/February/2002 05:06:49] Loading Bitmaps & Preprocessing Data
[05/February/2002 05:07:29] Start Voxelization

Have you tried lowering the resolution and trying to render? Depending on your computer and the complexity of the file it might take a long time calculating at higher resolutions.

For example- I render jewellery and was trying to render a scene with a lot of emitters at a high resolution similar to yours. I actually had the scene crash with insufficient memory. I streamlined my emitters and lowered the resolution a little and it rendered normally.

I may be off but it is worth a shot while you are waiting for the experts to weigh in

Good luck and let us know what works!!

post some more... this isnt all.

I've experienced mxcl not allowing any more instances to render and therefore stopping after sl 1.0.

This would be noted in the console though and there is no sign of it in your post.

If there is anymore info after reaching sl 1.0 I'd post that.
Otherwise I've heard many people here solving problems with 1.6 and 1.7 by reinstalling it.

Perhaps give it a try if nothing else helps.

Joris

CaryJames I did lower the resolution and as well lowering the precision of the displacement maps. And so far their rendering past SL 1.0.
I'm not sure which one corrected the problem, but seems to be working so far. Thanks to all of you who helped me with this. Gadzooks

Are you sure you're not running out of memory and MXCL starts using the scratch disk?

Hey Gadzooks- cool login name by the way . Glad that it is rendering past SL1 now. My computer is 32 bit and as such can only access 3gigs of RAM even though I have 4 gigs on hand. I fooled around with my scenes until I found the maximum resolution that my computer could handle and I use that as a benchmark when starting renders. I have to upgrade to XP64 and buy some more RAM but making my scenes efficient has helped a lot. Hope you solved it !

Mihai- No I was not aware of that. Will have our IT Guys look at that.

CaryJames _ do you have the three gig switch installed on your computer.? That should allow windows to access more ram. If not you might try it. Thanks Gadzooks