There seems to be a total lack of posts recently about P6 problems, now is that because there isn't any now or just that people are fed up complaining about it not doing stuff. I tried a render today in P6 with 1 V3, 2 M3's, the DAZ SFCS and 6 lights, I also set up Firefly how CL said to with textures set to 2000 and bucket size at 30 and guess what, "out of memory" bull s**t again. Is it just me or are you other P6 users still having problems after SR1? Not a rant against CL, just trying to see if an SR2 is needed or coming and yes I am going to tell CL about it! thefixer, poser coord.

yes im still having probs with p6 after sr1

it's infinately better than before but it still has some bugs to shake out before it goes prime time. Oh, wait...nevermind.

I hope they're working on an SR2 ... would have hate spend money on a version in it's current state. Oh, wait...nevermind.

Message edited on: 07/22/2005 16:09

Its better than it was before SR1 but still i cannot stop all this memory rubbish... I hope they are working on a real fix for this issue... and for the Artifact problem in AO IBL renders that seam to effect me..... Or have they all gone on holiday after releasing SR1???? Come on EF give us some news...

thefixer, I think your settings could use some adjustment. In my trials, I have found that the best bucket size is by 4's. I haven't gone as low as 16 (that may be too small.) The lowest I have done is 32, but I have found that 64 is the best for me. Keep in mind, the higher this number, the more that can be processed at the same time. My suggestion would be to only use less than 64 if you are very low on RAM, or you need to frequently stop renders (in which case, you may want to use the Area Render feature.) On the texture subject, per EF, you should not use a texture size greater than the resolution of the scene. Using larger textures does not improve the final render after the resolution of the scene has been passed. You have a lot going on in your scene, including the lights, especially if you are using any extras like raytraced shadows, AO, etc. For a good idea of what your scene is trying to render, try the attached script. You need to change the file extension to .py You can also use the settings (see the instructions in the top header) to split your renders into shadow only, and color only, so you can composite the images later. This uses less total resources for each render (at the expense of longer total time to render the two, and compositing them, but hey, it's something.) Hope this helps!

destro75, I appreciate your helpful tips but the main problem is that P5 would have done this scene easily. In this particular scene I haven't used any of the new P6 attributes like AO or raytracing. In the end I had to delete a wall prop and 1 of the M3 figures to make it render the scene. As for bucket size, the smaller the better for resource, using a larger bucket size increases the memory usage. Thanx for the info and I will certainly look into what you have said. Regards, thefixer, poser coord.

Well, I didn't say P6 doesn't still have problems ;-) I know, it's frustrating. The tips I gave you were to help you out until we can get a new update. Who knows when that is coming, so we may as well make do for now. As far as the bucket size, yes, it does increase resources the higher the number. It is actually a 1:1 ratio with MB of RAM. The reason I suggest upping your bucket is this. By increasing the bucket size, you allow a larger area of the image to be rendered during the same operation. So if you have a scene with many shadows, or lots of detail, etc. the engine can make less total calculations, as opposed to doing each one a little bit faster. I am actually trying an experiment with a size of 256 right now. I will post my results when it's done. Hope this helps!

Ah yes I see where you're coming from now, I'd be interested to learn how that works out, be sure to keep me informed please! thefixer, poser coord.

Funny. I just rendered a scene in P6 SR1 that refused to render in P5 SR4. One M3, one V3, one Microcosm, two spotlights, hires dynamic hair on V3, hires textures on both M3 and V3. H8ad to reduce bucket size to 8 and texture resolution to 1024, but P6 did render to completion, with AO turned on. P5 flatly refused to render the scene, even without the terrain and with only one light.

After I install SR1 some of my file icons disappeared and somehow I cannot save files, so I reinstalled Poser 6 and am still using the unupdated version ever since. It is fine now and I don't want to risk another "incident" like that again until it absolutely needs fix.

I actually began a new thread to show the results of my test on this subject. I figured other people might be interested in the results and this thread is already buried deep on page 2.