[VALKAMA]

The same exact thing has been happening to my Mac machines on renders that go over night. Not only does it mess up when you stop, it also will appear to hang at level 4 or 5, then when i stop, it jumps to level 13, where is should be and then crashes.

[VALKAMA]

Nextlimit sent me a beta patch but it ended up doing the same thing. For the last 2 weeks i have not been able to produce one usable image from maxwell because of these lines.. And forget multilight becuase it will hang and not allow you to change light settings. This went from a slow but good rendering engine to something completely useless via one patch.

[Q2]

Same happens to me too with the simball szene which comes with Maxwell. Rendersize was 3500x3500 px.

Q2

[Patrick_Hoenig]

Hi everybody
Same thing here. It happens when the rendering process is stopped manually: The lines appear, an output is written, but the console never says "render successfully finished", as it should. Also, the problem seems not to be dependent on the size of the image: mine was only 800/500 px. The sampling level seems to have an influence, though: at low levels there is no problem. Furthermore I checked CPU-load during the stopping process: It seems, as if the rendering process continues after stopping forever, because all 8 CPU's are completely used up all times, and maxwell does not respond to the refresh button. To me it seems as if it were possible to press the stop button at a such an unfortunate time, that the command "falls" between two processes and impedes finishing that process, wich writes the final layers to the image. That would explain, why sometimes there is no problem (chatch the right time to press) and sometimes there is one.

Patrick

Octo Mac 2.8 GHz, 4 G RAM, OS X 10.5.8, C4D 11.0, Maxwell 2.02

[micheloupatrick]

It would be nice to hear something from NL about this issue, even if it's only "we're looking into it".

Don't get me wrong, I think that NL is doing a great job updating Maxwell Render (already 2 Maya Plug-In and render engine updates, lots of bugs corrected), but this issue is nasty, and I hope a patch will be available soon.

[zdeno]

http://www.youtube.com/watch?v=qfResyFrqlM

but seriously

It is not NL's line to get involve into discusion.

You can:
1. put in wishlist
2. contact with customer tech support.
3. pray

ever discusion leads to engin wars flame

but realy seriously

if there is no word , they know what is going on and are working on that.
If they wouldn,t know someone would ask questions or ask for sending corrupt files.
there is only patience left.

[micheloupatrick]

but seriously... but realy seriously...

I am pretty serious...

It is not NL's line to get involve into discusion.

You can:
1. put in wishlist
2. contact with customer tech support.
3. pray

Correcting a bug has nothing to do with a wishlist, and I hope nothing to do with faith.

I respect your opinion, but I stand by what I wrote : a bit of communication can't harm.

[Mattia Sullini]

I agree it could be a RAM related problem. One of my macs has a malfunctioning RAM module, and either this occurs quite often with big mxi's.
It's not a merging matter since i was running maxwell on only one single machine.

[tom]

The bug is boiling at the top of our priority list since it's discovered and we can't wait to distribute a cure ASAP. These silent moments happen when we're making sure it won't happen again or at least we don't want to make an unsuccessful patch about it. Do never forget we always read every single line here. Thanks for your patience!

[micheloupatrick]

Great to hear that. Thank you!

[zdeno]

Correcting a bug has nothing to do with a wishlist, and I hope nothing to do with faith.

Oh it is misunderstanding;)

I was personal (make a hint?) in Tom's direction. As You can see it worked .
BTW thanks Tom for quick and professional answer. It is how customer-factory relations should looks like.

[micheloupatrick]

I was personal (make a hint?) in Tom's direction. As You can see it worked .

Indeed!

[tom]

Thanks! You know, it's easy to question a few guys like us but, in our shoes it's not always easy to reply thousands.