Attached Link: http://www.meddo3d.com

Did some got that message when rendering Firefly with Final setting, My System is P4 2.8 G with 2Gig RAm and a ATI Radeon 9800 Pro 256 Meg.

Meddo
www.meddo3d.com
www.endless-studios.com

Yes, I get that all the time. Even if I have only one figure in the scene. Then it nukes the file. :-(

Same here. Hope curious labs finds a way to fix this.

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=2201426

You've been bitten by the infamous P6 Memory Bug.

We've already had a couple of dozen or so threads about it.

Here's a link to one of them.

Hopefully, the first service release will repair the problem.

Otherwise, Poser 6 is severely handicapped in what it can do.

Here's another thread on the subject:

http://www.renderosity.com/messages.ez?Form.ShowMessage=2202759

Something To Do At 3:00AM 

I got that a couple times as well. Running a process killer (like EndItAll) helped a good bit, but that's because you're having more memory to start out with, and has nothing to do with acctually fixing (avoiding) the bug, it just delays it. In my case it delays it until the render is over, but I'm sure if I made some really big complicated renders I'd still run into it.

I get this, usually when the FireFly engine is set to its top quality settings. I have found that regularly defragging and optimising my hard drives, and making sure that nothing else is running, minimises the occasions when this happens. But it still happens...

---

Windows 10 x64 Pro - Intel Xeon E5450 @ 3.00GHz (x2)

PoserPro 11 - Units: Metres

Adobe CC 2017

I've found that setting the bucket size down to 8 seems to help most of the time - I've had several scenes which generated the above message, then rendered just fine when the bucket size was cranked down that far.

I render with a bucketsize of 64 with no problems. It has to do with lights.

Attached Link: http://www.meddo3d.com

I send the bug to Curiouslabs they reply with several question (normal) , and all the information was pass to the engineers and they are working on it.

Meddo

maybe a service pack.

www.meddo3d.com
www.endless-studios.com

Hi all, please understand that there is a distinction between the general case of the FireFly renderer running out of memory and the particular problem of a scene file getting corrupted on saving that some people report. The settings labeled as final are very aggressive in terms of resource needs. It is possible that at such render settings, a complex scene consumes more memory than an application can use on a 32 bit Windows system (2 gigabytes). That's why there is a memory check during rendering and that's why there is a message that suggests lowering those settings. This is all normal operation of the application. Please also consult the FireFly rendering tutorial in the Poser 6 Tutorial manual PDF for details on this matter. If you experience that lowering the render settings doesn't help, if your scene is not complex (100,000 polygons or less, no 4k by 4k textures) or if you are affected by Poser writing a corrupted scene file, then that is not normal and considered a bug. In that case, Curious Labs tech support would like to talk to you. Please make contact through http://www.curiouslabs.com/article/articleview/18?sbss=435. Thanks a lot, Uli