Tweet
Hi,
I started noticing that every time I work with any scene that has PhoenixFD in it, 3ds Max exit will end up in a crash, instead of regular exit. It happens in 3ds Max 2016 with SP3, but probably in other versions too.
I remember seeing this bug in some other 3ds Max plugins too, such as Corona Renderer, iToo ForestPack or Multiscatter. It seems like a problem that's commonly ran into, and developers have to patch it around. So I think Vlado has likely ran into it too and should know how to get rid of it.
Basically, everytime I exit 3ds Max, 3dsmax.exe process remains hanging in the task manager for a while, and then I get window saying 3dsmax.exe has stopped working. Occasionally, I will get also one more error message saying something like "3ds max runtime error r6025 pure virtual function call".
This happens only when I interacted with scene that has any PhoenixFD in it. When I do not work with any PhoenixFD scenes, 3ds Max always exits fine.
I started noticing that every time I work with any scene that has PhoenixFD in it, 3ds Max exit will end up in a crash, instead of regular exit. It happens in 3ds Max 2016 with SP3, but probably in other versions too.
I remember seeing this bug in some other 3ds Max plugins too, such as Corona Renderer, iToo ForestPack or Multiscatter. It seems like a problem that's commonly ran into, and developers have to patch it around. So I think Vlado has likely ran into it too and should know how to get rid of it.
Basically, everytime I exit 3ds Max, 3dsmax.exe process remains hanging in the task manager for a while, and then I get window saying 3dsmax.exe has stopped working. Occasionally, I will get also one more error message saying something like "3ds max runtime error r6025 pure virtual function call".
This happens only when I interacted with scene that has any PhoenixFD in it. When I do not work with any PhoenixFD scenes, 3ds Max always exits fine.
Comment