I know the subject must bore you to death by now, but still I dare to bring it up. After installing the service release 1 pack, I thought that renderproblems would be over ( they seamed to be a common issue ) but even now poser ( 6 ) as a problem with the render memory. The pic I'm trying to render features Jessi and Jessi hair ( an included dynamic hair set ) I tried to render the face camera view at 40cm x 30 cm at 28 pixels per cm ( that's the default setting ) This does't look to be such a big task ( I did a lot more heavy renders in P5 ) but it simply won't go. Now maybe it's because I still have P5 installed aswell (????) my curious labs directory includes poser 5 and 6 ( yes I know, stupid, but that's what happens if you ask someone else to buy it for you, you get the full version instead of the upgrade ) Poser 5 also runs on the firefly renderengine. So would the problems concerning the renders in P6 finaly disappear if I uninstall P5? Let me now asap please not being able to render is NOT funny Thanks a lot Peevee

Yeah, your not the only one getting the memory bug after installing SR1. I was working away on a piece yesterday, just V3, Daz Moffat hair, 'Shandi' texture only over 'Women of power' body morph. I did 4 renders at highest quality in Firefly just fine, then on 5th render I got the 'Texture is missing or cannot be found' and 'Out of memory' message. I could only render this piece again after turning Poser off, then on again. I also appear to have lost all the V3 'Head' morphs? Here we go again!

Same problem here - it's better than it was before the patch, but after a while I do still get "out of memory" errors and textures being lost. Normally that seems to be body textures - they are there in the material room, but when you render the character comes out plain white. Restarting Poser seems to be the only solution. At least the saved files don't seem to get trashed now.

Because it seems to happen after I've been working for a while, I suspect there's bad memory management at work - Poser "locking up" memory and not giving it back. So as you render a few times in your session you are gradually eating up available memory, until eventually there isn't enough left to work with. Even when I've closed Poser I notice Windows swapping to disk a lot until I reboot the PC, so I think that memory stays locked up even after you exit Poser.

It does seem to be better than it was though - at least now I can actually render on production quality. Prior to the patch the best I could do was about half way up the scale with Firefly. :/ Oh - and there doesn't seem to actually be an "upgrade" version of Poser6. When you buy the upgrade you are just paying less for the full version of Poser6. It installs into a new directory anyway. I just shared my Poser5 runtime into Poser6 and kept Poser5 in case I wanted to go back, but to be honest I may as well just get rid of the old version - haven't touched it for over a month now.

Message edited on: 06/06/2005 09:46

'Not really a satisfactory situation though is it? Such a pity, Poser6 could be a GREAT piece of kit if it just worked properly...will it EVER i wonder?

Yep, I know: In Poser 5 a lot of things work just fine. When I try to open them on Poser 6, I get these boring "please locate " pop-ups. Strangely a couple of things that made Poser 5 fail, run great in Poser 6 ( do you guys still get messages that there isn't a disk in drive "X" ( I get drive C ) because I don't in Poser 6 Anyway, glad to know that I'm not alone, but how do these guys in the marketplace fix it? There's some high resolution renders in there for P6 exclusive goods, so their P6 must be working fine then or what?

'Seam's like it's down to individual system's as to how P6 perform's? I'd still bet that at the end of the day it will all come down to software conflict's! I have a friend who has an identical PC to mine, exactly the same hardware made by the same person and his P6 run's just fine 'difference is that he has completely different software interests to me and that's what makes me so certain....Yep, all down to what other software resides on the same drive as P6!!!

Hi all, I have posted some information recently regarding what some of you call 'the memory bug': http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2275282&Reply=2276129#35 http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=2275282&Reply=2277618#66 Why can you spot high resolution renders in many locations? It might be that the artist was considerate regarding the scene setup (hires textures only when needed, lores figures in the background, etc.) or that the artist adjusted render settings according to the complexity of the scene. You don't have to use the most extreme settings to get good quality renders. Often enough you can't tell the difference between a render with middle-of-the-road settings and one with killer settings. Naladae, what you describe sounds like trouble with virtual memory. Especially the fact that Windows is swapping even after closing Poser hints that Poser was using a lot of virtual memory and/or many other applications have been swapped out (i.e. the data has been written to a swap file on disk) during its session. I can pretty much guarantee that with SR1 applied, Poser 6 frees every possible chunk of memory after a render and also tries to reduce memory fragmentation before and after every render. However, once virtual memory is used extensively, the Windows memory manager decides whether it holds on to data it stored previously or frees it and grants more memory to an application requesting it. That unfortunately yields less predictable results than you'd desire. Uli

But WHY did we not have this problem AT ALL with P5???