I’ve been extremely frustrated with this bug and have so far only determined roughly where in the code the source is. But I have no fix and I’d like some help.
When a player touches a pain causing volume, the game crashes, from within a PhysX dll. Of which I have no access to, and simply get told in VS “Frame Not Loaded”. As in, the debugger is of no use in fixing this. If there’s a way I can get debugging data and symbols for PhysX that would be a great start.
I don’t know a lot about this bug as it’s so elusive. It happens rarely in the editor, and happens about 50% of the time when playing the game in “Development” and “Debug” Configuration. It also happens in a shipped build, although not reliably.
Here’s crash log I got once from the editor, but most often I’m told the stack isn’t available or something of the like.
https://dl.dropboxusercontent.com/u/53792213/PhysXCrash.txt
Any help is appreciated,
Thanks
Hello Constan7ine,
It seems like the error that stands out here is the following:
LoadErrors:Error: Error ActiveClassRedirects contains a collision with multiple redirectors for old class named AnimNode_SkeletalControlBase
There are a few of those for different classes. This seems like something that could make use of the Fix Up Redirectors operation from right-clicking on your folders in the Content Browser. Could you give that a try and see if it may fix your issue?
I did this and unfortunately it didn’t prevent the crash. I then noticed afterward that the fixup redirects command had actually had no effect on those warnings. They still persisted, and so does the crash.
On other research into the problem I noticed an occasionally occurring error complaining of NaN in the FastInverse function, as it’s being called from the dynamic shadows system. Could this be related? At one point I had the crash not occurring, and these NaN matrix errors occurring instead, as players hit the pain causing volume.
I’ve also found this problem occurs much more regularly in a game build than it does in the editor. In fact it hardly ever happens in the editor. Is there some reason why?
Oh I also did a map check and found nothing to be a problem.
What are the collision settings on your character and your pain causing volume? Also, have you attempted reproducing this problem, possibly only with the character and the pain causing volume in a new map or in a new project? If it seems to only be happening in your project, it would be helpful to have a copy of it, if possible. If not, repro steps to set it up in a new project would suffice.
I can reproduce this without issue on a new map, unfortunately the project is large and complicated and simply sending it over isn’t really possible.
I created a new third person template and put a pain causing volume in the level. Walking into it didn’t cause a crash. However it’s a completely different Pawn and Controller, so all it’s done is rule this out as an engine bug. I am still stuck with it in our project.
Is there a way I can get PhysX pdb files? Better yet source code? That way I could properly debug this and trace the crash back to my code
If you’d like to get the PhysX source code, Nvidia released it themselves last year on Github. You’ll need to register for their programs and create a Github account to be able to see it, as it is private and only for registered users. You can find more information about that here: PhysX SDK: Latest Features & Libraries | NVIDIA Developer
Hello Constan7ine,
It seems like that was all you needed so I converted my last comment into an answer. If this is incorrect, let me know and the question will reopen.
It was certainly helpful, but the bug was actually found to be something else, I just forgot to come back and put it here. I commented out lines of code executed after entering a pain causing volume until the crash stopped. There was a line copying an (invalid) bone name in the damage event. When the line was commented out the code no longer crashed.