Forum Moderators: nerd, RedPhantom
(Last Updated: 2025 May 17 9:54 pm)
I suggest that you open a ticket on the support, here: https://support.posersoftware.com/index.php
It looks like Mac's world seem to show errors only when they're relevant to a developper.
𝒫𝒽𝓎𝓁
(っ◔◡◔)っ
👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gaming, Asus Tuf Gaming RTX 4070 OC Edition, 1+2 TB SSD's, 6+4TB HD
👿 Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️
Thanks, Phyl for the quick feedback.
In the past week searching the forum here didn't seem to turn up any thread with a similar complaint but I was hoping that the new release might have been created with other Mac users having already opening support tickets on this issue.
I've read here that this is the final version for Mac so I'm not sure what that would mean for any new Mac tickets.
This is my first Apple silicon machine so there is the possibility that the issue may be the Mac being overprotective. ???
And yet, I have rendered many files old and new on this machine without issue.
What works is loading figures, loading material poses (without issue), loading figure poses, props, sets, etc.
Going to the Material room, loading a material can work but change a second material: KABOOM!
So, thanks I will open a ticket but this first draft is here just in case someone else is having this problem and searches the forum.
If I get a real solution to this I will post it here.
dB
I am a Windows user, since V1. But I also have a Mac Mini M2 since I am learning Bass. So that I've launched a few timers the same scene on both Poser 13 version (Win & Mac) without encountering any error.Thanks, Phyl for the quick feedback.
In the past week searching the forum here didn't seem to turn up any thread with a similar complaint but I was hoping that the new release might have been created with other Mac users having already opening support tickets on this issue.
I've read here that this is the final version for Mac so I'm not sure what that would mean for any new Mac tickets.
This is my first Apple silicon machine so there is the possibility that the issue may be the Mac being overprotective. ???
And yet, I have rendered many files old and new on this machine without issue.
What works is loading figures, loading material poses (without issue), loading figure poses, props, sets, etc.
Going to the Material room, loading a material can work but change a second material: KABOOM!
So, thanks I will open a ticket but this first draft is here just in case someone else is having this problem and searches the forum.
If I get a real solution to this I will post it here.
dB
𝒫𝒽𝓎𝓁
(っ◔◡◔)っ
👿 Win11 on i9-13900K@5GHz, 64GB, RoG Strix B760F Gaming, Asus Tuf Gaming RTX 4070 OC Edition, 1+2 TB SSD's, 6+4TB HD
👿 Mac Mini M2, Sequoia 15.2, 16GB, 500GB SSD
👿 Nas 10TB
👿 Poser 13 and soon 14 ❤️
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.
Load: Poser13/prop/Primitives/Ball Hi-Res
Open Material Room, Go to Materials library, load: basic material
Generally this works.
Pick another basic material and load it: Instant CRASH.
Even when I restart the process described above and choose the material that crashed Poser, the material will load but when I then try to load the material that worked before it crashes Poser.
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Poser13.3.1041
Mac M3 Max
128G memory
I've been using Poser since P3, have never seen this problem before.
Any ideas as to the cause of this?
Thanks in advance for any feedback