Sun, Jan 12, 7:35 AM CST

Renderosity Forums / Poser 11 / Poser Pro 11 OFFICIAL Technical



Welcome to the Poser 11 / Poser Pro 11 OFFICIAL Technical Forum

Forum Moderators: nerd

Poser 11 / Poser Pro 11 OFFICIAL Technical F.A.Q (Last Updated: 2025 Jan 12 6:19 am)

banner

Welcome to the Poser Forums! Need help with these versions, advice on upgrading? Etc...you've arrived at the right place!


Looking for Poser Tutorials? Find those HERE



Subject: Poser 11 Pro Mac crashes when loading pre-assembled scenes


gerberc ( ) posted Sun, 05 December 2021 at 7:25 AM · edited Thu, 19 December 2024 at 3:06 PM

Hi everybody

I have the issue Poser 11 Pro Mac crashes when I want to load older and complex prefab scenes from the character or prop libraries.

The problem typically occurs with prop or character sets built of multiple objects. For example, I can load each individual prop of the Planet Iridia set by Petipet but not the character file with the whole, pre-assembled setting. It's not a problem specific to this product, the same happens with other sets, too. However, not all oder pre-assembled prop sets crash. There are examples like Greek&Jungle ruins that load just fine. Interestingly there is no issue with loading PZ3 files with many characters and props, both old and new ones. It just happens with some older cr2 and pz2 files from the library.

If that helps I run Poser 11 Pro on a MacBook Air with a 1.2 GHz Intel Core i7 and 16 GB RAM. However, I'm sure the problem is not related to the hardware as I had the same issue on my old MacBook Pro ...

For the time being I assemble all scenes by manually loading each prop or character individually. However it would be nice to uses pre-assembled scenes form the prop and character libraries too!

Thank you very much for any hint, Christoph



nerd ( ) posted Sat, 11 December 2021 at 3:59 PM
Forum Moderator

Could you open a support ticket for this. https://support.posersoftware.com/ and attach one of the scenes affected.Or if the scene's a commercial product link it. I don't have a clue but this should be investigated.


gerberc ( ) posted Sun, 09 January 2022 at 10:51 AM

Found a simple solution not involving updating to MacOS Monterey: Just set the USE_OPENGL to 0 (was 1) and everything is fine. 


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.