Hi, during all my years working with PiXYZ, it has not been known to be the most stable software. Crashes are common, and in our experience most usually some step of the guided import of a STEP-file will lead to problems, crashes or freezing. However, lately in 2025, I’m experiencing crashes more frequently and not easily reproducable. It can be something as simple as deleting a part of the hierarchy, merging parts, pruning or raking the tree. One object that causes the crash in one session can work fine the next, depending on what I’ve done before or if it’s the first command in the sessions. I’m keeping tabs on memory usage but am only consuming 50% of my 64GB, so should not be the issue.
Currently on 2025.1.1.2 but same issue with the release before.
Log file always just states
[2025/03/14 9:59:08] Terminated due to native crash
Any clues on to what’s going on or what I can do to troubleshoot?
Regards, Björn
Had chatgpt o3 have a look at the dump file:
Not sure if that helps in your investigation
Interesting because I also had the feeling that recently, models were working in one session but sometimes not the other. Also using scripts which should result in the same behaviour every time.
I 100% agree. I’ve been using Studio for several years to process large models and in my opinion the SDK-based versions of Studio are unusable. I’ve tried v 2024.1 (Beta), 2025.1.0.5, and 2025.1.1.2. Performance is extremely poor but the unpredictability of the crashes is what really sent me back to version 2022.1.2.7. I work at a location where I am not able to share models with Unity due to the information security restrictions on the data so I can’t be part of the solution but I really hope someone figures out both the crash and performance issues.
I just upgraded to the newest version of Pixyz yesterday and have already had so many more crashes than I did in the older version. In older versions usually a crash would occur when I would have a long-running script doing something complicated, but in this version I’ll be doing fairly innocuous stuff like undoing/redoing, deleting parts/models, etc. A few more of these and I think I’ll revert.
Dear Pixyz Studio Community,
Thank you for taking the time to share your feedback regarding the stability and performance issues in Pixyz Studio 2025. We want to acknowledge your concerns and assure you that the entire team is fully committed to resolving these challenges as quickly as possible. As you know, Pixyz Studio has been entirely rebuilt on top of Pixyz SDK the past years, and we are now in a stabilization phase.
Your insights and detailed reproduction cases have been incredibly valuable in helping us identify and address specific issues. Please continue to share them, as they play a crucial role in improving the software for everyone. We deeply appreciate your collaboration and patience during this process.
If you’re facing situations involving confidential data or would like to discuss specific topics in greater detail, please don’t hesitate to reach out to us directly. We’re here to listen and work with you to find solutions.
Thank you for your continued support and trust in Pixyz Studio, we’re dedicated to delivering the performance and reliability you expect from us.
@bjornsyse a possible workaround for your specific problem with STEP files is to use the alternative importers which can be found in the preferences to Studio.
We’ve found the alternative importer for STEP files to be both more stable and produce better material representation.
