Rooty Tooty Posted January 31, 2024 Posted January 31, 2024 Okay so, I updated a bunch of mods, I'm running 1.6.640 and recently upon trying to start a new game right after loading in and such, it just randomly CTDS every single time, I believe it involves FSMP so I attached my crash log in the hopes someone more informed on how to decipher these, can see the potential issue I'm having. crash-2024-01-31-03-07-35.log
traison Posted January 31, 2024 Posted January 31, 2024 (edited) Definitely a crash caused by hdtSMP64.dll yes. Conveniently, the crash logger dumped a bunch of additional information for you: XmlReader ReadBom I'm going to say your issue is in one of the xml config files. More specifically, it may be in the BOM which traditionally stands for byte order mark. I doubt its actually looking for the BOM, it is most likely expecting a specific text encoding and since it can't find it it attempts to guess by looking for the BOM. So, go through all xml files with a tool like Notepad++ and normalize the text encodings in all of them. UTF-8 without BOM seems to work, as that's what I have here. If you specifically find one with a BOM, remove it, as it may be a somewhat dead concept and tends to confuse more apps than it helps. Edit: Guess I missed the obvious, the RSI register literally contains a pointer to "not a boolean" and RSP+F0 is a pointer to "enableNPCFaceParts". So your issue is in SMP's configs.xml. Edited January 31, 2024 by traison 2
Rooty Tooty Posted January 31, 2024 Author Posted January 31, 2024 (edited) 7 hours ago, traison said: Definitely a crash caused by hdtSMP64.dll yes. Conveniently, the crash logger dumped a bunch of additional information for you: XmlReader ReadBom I'm going to say your issue is in one of the xml config files. More specifically, it may be in the BOM which traditionally stands for byte order mark. I doubt its actually looking for the BOM, it is most likely expecting a specific text encoding and since it can't find it it attempts to guess by looking for the BOM. So, go through all xml files with a tool like Notepad++ and normalize the text encodings in all of them. UTF-8 without BOM seems to work, as that's what I have here. If you specifically find one with a BOM, remove it, as it may be a somewhat dead concept and tends to confuse more apps than it helps. Edit: Guess I missed the obvious, the RSI register literally contains a pointer to "not a boolean" and RSP+F0 is a pointer to "enableNPCFaceParts". So your issue is in SMP's configs.xml. I'm now having some other issue, so I realized my FSMPM was accidentally being overwritten by FSMP, which it says it shouldn't so I swapped that up, and now hdtSMP64.dll is having a fatal error upon startup and now I'm at a loss. Also I checked the configs.xml and I didn't notice anything weird in it, but I'm also not super knowledgeable on that stuff. Edited January 31, 2024 by Rooty Tooty
Rooty Tooty Posted January 31, 2024 Author Posted January 31, 2024 14 minutes ago, Rooty Tooty said: I'm now having some other issue, so I realized my FSMPM was accidentally being overwritten by FSMP, which it says it shouldn't so I swapped that up, and now hdtSMP64.dll is having a fatal error upon startup and now I'm at a loss. Also I checked the configs.xml and I didn't notice anything weird in it, but I'm also not super knowledgeable on that stuff. Okay I figured it all out, weirdest issue but it was being caused by FSMPM making empty configs.xml's upon loading up the game, which when it would try to reference it made it crash or something along those lines. So a full reinstall of FSMPM fixed my issue, both the .dll error and the CTD's. Thanks a ton for your help Traison.
traison Posted January 31, 2024 Posted January 31, 2024 The inner text (as its called) of most of those elements is an empty string. This is not considered a valid boolean by the parser, which makes sense. For instance, change... <enabled></enabled> ..to: <enabled>true</enabled> ...and repeat that for all fields and your crashing issue will be fixed. Obviously not all fields are booleans however, which should be obvious: windStrength etc. Seems you got it sorted regardless. Just figured I'd post this for future Googling people.
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