ok, so you ARE saying the HDAccess impact on render times is resource-fetching, not with writing the actual output file.

Given that....i wonder if Poser is smart enough to load more into RAM if it sees a lot of RAM, or does it make assumptions, and above a certain point starts swapping to virtual REGARDLESS and causing HD access. [SIDE NOTE: the new G5s can map out up to 8GIG of RAM! Many PC motherboards can go to 4GB. In an extreme situation, would Poser, I wonder, even see that RAM and use it to load full textures, etc.]

So, if one has a lot of RAM, I guess the first approach to avoid disk access is strategy/settings to force Poser to load as much as possible into memory. Are there any?

Next...what about putting Poser.exe and the runtime folder (with the textures, obviously) on a RAM disk?

::::: Opera :::::

Message edited on: 12/22/2004 11:57