This is what I have. Just trying of a removing added xref scene via user XRef Files Dialog causes immediate crash of MAX 2016 sp4
MAX 2012 doesn’t crash. (I don’t have another versions at my hands now)
If i remove a xref scene via MXS it “works”. But any attempt to load another file after that causes a crash.
Can anyone confirm or refute this fact?
I don’t have the same problem.
What i did:
- References – XRef Scene – Add… – pick a max file and it is loaded properly
- References- XRef Scene – Remove – the same scena and everything works.
Then I have added and removed several other xref scenes without any problems
Here is an update.
I’ve found the source of the crash. It’s the PhysX plugin! I don’t know yet what part of the plugin causes the problem yet. As soon as I will know I will update the post…
Without the PhysX plugin installed the MAX 2016 works correct with deleting XREF scenes
PhysX/MassFX in Max installs a lot of scene loading callbacks. AFAIK those are all installed by one “init” script. Maybe you could find a way to quickly unhook those callbacks prior your Xref operation and rehook after them ? This would spare you from removing the plugins completely , which in case of MassFX is shipping with 3ds Max
Thanks, Josef.
That’s exactly my plan. I will post a solution as soon as I find it
the problem was solved… i’m disabling all scene reference messages before a xref scene deleting … it works. i don’t care… it’s my xref scene. i can do what i want. i want to load i load, i want to delete i delete it
BTW… i’ve wrote anyway the methods to collect all custom added callback events, and can temporary disable them, and enable them back…