Neyjour opened this issue on Jan 21, 2006 ยท 27 posts
acanthis posted Sat, 21 January 2006 at 1:29 PM
Poser 6 SR2 still crashes, but it isn't as bad as all of the prior versions and service releases since 5.0. The problem continues to be bad memory management, but at least 90% of the time P6 SR2 gives you a warning that it's about to trash your work with the "Poser has encountered a problem while rendering" message. In my experience, you should never EVER save your scene after a render has crashed. Get out of poser double quick time and go back to your last saved version, otherwise you WILL lose your work. Also, avoid using the e-Frontier-recommended "Texture Filtering" setting in Firefly, especially if you are using hi-res textures. This checkbox should really be renamed "Cause the rendering engine to crash" As for the abomination known as External Binary Morph files, all I can say is that I turned that off in P6 a long long time ago, and I have never even bothered to check whether SR2 fixed it or not. After three experiences of ruined scenes and corrupted figures that had had their morph channels detached due to the unforgiveable bug in the original PMD handler, I will never trust that feature again. However, all of that said, on the whole Poser 6 SR2 works reasonably well and is acceptably reliable. It is, hoever, a VERY long way from something that you could regard as stable to use in a production environment. The only remedy that I know of is to save your scenes at least every ten minutes while working with ascending version numbers in the filename, then at least you can go back WHEN Poser trashes your work for you. (Note that - WHEN not IF)