Janrith Posted May 4, 2019 Posted May 4, 2019 (originaly posted in the General Discussion thread -- my bad; didn't see this one). I took a demorecord of our SG base on Torchbearer, but when I went to play it back (via score -demoplay), I simply get a CTD. Dropping into a VS debug session, it looks like an AV in score.exe: Unhandled exception at 0x008513DC in score.exe: 0xC0000005: Access violation writing location 0x00000000. I don't have symbols for the score.exe executable (looking for Resurgence.pdb), so I can't provide a stack. Anyone else having an issue trying to play back demorecord files, and/or have a fix/workaround? Thanks. -=Janrith
Janrith Posted May 9, 2019 Author Posted May 9, 2019 Has no one else tried to take a DEMORECORD and then play it back using score.exe? I've tested it with the 5/6/2019 version of score.exe; no change. Thanks. -=Janrith
Piledriver Posted May 10, 2019 Posted May 10, 2019 I wasn't getting a CTD, but some stuff wasn't showing up, among other issues. Adding -patchdir score to the command before -demoplay fixed that. It might work for the CTD if new stuff in the base is the cause. It looks like different private servers can define different "patch directories," but the contents are probably identical at this point.
Janrith Posted July 4, 2019 Author Posted July 4, 2019 I wasn't getting a CTD, but some stuff wasn't showing up, among other issues. Adding -patchdir score to the command before -demoplay fixed that. It might work for the CTD if new stuff in the base is the cause. It looks like different private servers can define different "patch directories," but the contents are probably identical at this point. That did the trick! Thanks so much. Take care.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now