Jump to content

Recommended Posts

Posted

A certain other person here will have far more knowledge about this. Some quick and obvious pointers i can give:

 

1. Crashlogger tends to provide more useful crashlogs than Trainwreck. You might want to reproduce the crash with Crashlogger, to see if it provides data Trainwreck doesn't show (Don't run both at the same time however. Use a modmanager to have either Trainwreck or Crashlogger enabled, not both).

 

2. OAR and animation processing is near the top of the stack. Could be some bugged animations (which would explain why it doesn't always happen). Or could be an incompatibility between OAR and Ostim. Just for testing i would try to disable OAR and see if it still happens. If not, then you know it's either an OAR animation, or OAR being incompatible with OStim.

 

3. OStim doesn't even seem to appear in the report. But this being Trainwreck, that doesn't mean much. Try reproducing with Crashlogger and see where in the callstack OStim is.

Posted (edited)

It tried to dereference rdx, which was 0x0 at the time of the crash. This is a null pointer. The issue is animation related. I would start by disabling OAR. If the problem doesn't go away, start cutting animations from your behavior files, and obviously make sure there's no errors or warnings being printed from the utility you use to generate these.

Edited by traison

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...