[chedda]

I have seen this before and i am quite concerned considering i have lost about 60 hours of rendering ! When i resume the render at the next update i get bright horizontal stripes or bands in the render nothing seems to help ! I am using the latest version on osx 10.6, has anyone else seen this or have a fix ? I am using sketchup to model but this time it went through studio as well so i can't see this being the problem. It looks like the render file has become corrupted i/m very peeved as the image was rendered for an architectural competition and had reached sl 23+ PLEASE HELP

[Bubbaloo]

Nothing can help unless you have a saved copy or backup of the original MXI before you resumed it. Most likely it was a problem during the over-writing of the file which caused it to corrupt. A little late now for advice but it's a good idea to back up any file you plan to over-write with new data.

If the manager is still open, you may be able to snag a pre-merged version.

[chedda]

Thanks for the reply Bubbaloo, so nobody has any idea how this is caused and how it can be avoided ?

[JamesColeman]

Was it like this http://www.maxwellrender.com/forum/view ... 13&t=36253? That was due to intersecting SSS geometry.

[chedda]

Yes James it looked very similar, i am at a loss though as to the cause because the model was very tidy and did not include any sss materials. If ss geometry was to blame surely this error would have been immediate ? It has happened to me before the common theme being pause & resume rendering especially at high SL levels. I just hope the developers can re-produce & fix this bug because it really shafted me.

[flower]

I've had this occur too. I can understand your frustration, so annoying. Most recently it happened on a render that had been rendering for a long time, I had stopped and resumed several times, each time there had been no problem, and then suddenly it hangs on the writing to disk and the Update box says Waiting...

This was a single machine render, no SSS or funny geometry, saving to local hard drive.

Personally, I think it happens when the machine is trying to do something else, maybe writing to disk or some memory related task, at the exact same moment that an update is being written to disk. It's like there is a hiccup and some parts of the file get their values multiplied.

Luckily every time I stop a render I back up the mxi file before I resume.

Sorry I dont have any answers, but I can only share your frustration.

Region render the affected parts to the same SL, is the only sure way to 'fix' the problem areas. Region renders go through surprisingly quickly.

Cheers,
Bim

[chedda]

Thanks for the help guys, i will try to remember to back up before resuming next time. I agree with you flower it seems like a conflict with something else the machine is doing running a maintenance script or something. Is this error mac specific or are you guys using windows ? Lets track down this problem and fix it ! Nextlimit can you reproduce this ?

[flower]

I'm on Mac

2008 2.8 Dual Quad Core (Octo) , 10 Gb Ram, running OS X 10.6.8 Snow Leopard

Whilst MXCL was running, I was doing email Mail, bit of web browsing Safari and Firefox, iCal, Address Book.. and that's all, not really heavy.

It would be good to track this down.

Cheers,
Bim

[chedda]

Okay so it's mac specific then, i believe during the twilight hours mac defrag etc perhaps it is related ?

[flower]

Mine last incident happened between 10pm and 11pm. Not sure what hidden operations its up to.

[Bubbaloo]

I have had it happen on Windows, but it hasn't happened in a very long time.

[chedda]

Perhaps the windows version was fixed, i really love maxwell but something as tragic as this really puts me off.I just cannot excuse 60 hours of lost rendering time. I didn't know about the render region feature is this in studio ? Perhaps someone could point me in the direction of a tutorial.