Solved BMS 4.36 CTD when trying to connect to servers
-
Before I go into deep detail of my current system and setup. I am going to attach the links to my crash log and pray someone can help. I recently installed BMS 4.36 with the hotfix and everything works fine until I try to connect to someone’s server. At first, the connection is established, but there’s no name or host listed under the online tab for tactical engagement and campaign missions. Once I go back to the comms menu and disconnect from the server and try to reconnect it CTD (crashes to desktop) every time after a few seconds. I have no issues flying single player mission. Its only crashing during multiplayer server connecting. My 4.35 works just fine still. No issues there. Can someone please take a look at my crash log files and I will be happy to answer any questions and brainstorm on how to fix this. Thank you.
https://drive.google.com/file/d/1xnoxr4OxnTW-ZjnAfZRutknhLEz-sO6s/view?usp=sharing
https://drive.google.com/file/d/15NyaZSvHViVWWQ3Lyw8U0B-im1PsjFdD/view?usp=sharing
-
@Starkes So my connection issues was due to editing the hot fix with Excel instead of notepad, which caused my falcon BMS CFG file to get corrupted with random Quotation marks all throughout random lines in my BMS CFG file. I basically copied and pasted a new CFG file from a friend and then correctly placed and edited the hot fix and then everything worked fine.
-
Open your configuration file and paste here your
g_sNonCompatibleChanges
line.It should be like
set g_sNonCompatibleChanges "all-DURANDAL-DEAGGED_LOADOUT"
Seems to me you have several non compatible changes disabled.
-
@Starkes please check.
-
@Seifer I replaced the parenthesis “” part with the hot fix. I can easily revert it back to the default line and see if that works
-
@Starkes and make sure there is no such line in the user file, which overrides this setting.
-
-
@Seifer Ok. Checking now
-
@Starkes said in BMS 4.36 CTD when trying to connect to servers:
NC_CHANGE_DEAGGED_LOADOUT
Watch out, you are using UTF8 quotes. Copy paste from here, avoid any quote conversion.
-
@Seifer Ok. I reverted that line back to its default status. It now reads.
set g_sNonCompatibleChanges “all-DURANDAL-DEAGGED_LOADOUT” // Dev Setting -
@Starkes Could you please post what the line above it should read? The setg_sCompatibleChanges one please.
-
@Starkes set g_sCompatibleChanges “all-C_CHANGE_DYNAMIC_SMART_SCALING-C_CHANGE_CHANGE_STORE_DAMAGE” // Dev Setting
I also changed this line to what the hotfix had listed. That may have caused my connection issues.
-
The hotfix lines are correct. I think the problem is coming from your UTF8 quotes in the config file.
Also, did you bring any change from the 4.35 file?
-
@Seifer Only things brought from 4.35 was my phonebook file, logbook file, and key file. That’s all.
-
@Starkes What are UTF8 quotes??
-
They are curved quotes… notice the difference between (UTF8):
set g_sCompatibleChanges “all-C_CHANGE_DYNAMIC_SMART_SCALING-C_CHANGE_CHANGE_STORE_DAMAGE”
and non UTF8:
set g_sCompatibleChanges "all-C_CHANGE_DYNAMIC_SMART_SCALING-C_CHANGE_CHANGE_STORE_DAMAGE"
-
@Seifer I notice the color difference of the line
-
@Starkes Both my lines look like this now.
set g_sCompatibleChanges “all-C_CHANGE_DYNAMIC_SMART_SCALING-C_CHANGE_CHANGE_STORE_DAMAGE” // Dev Setting
set g_sNonCompatibleChanges “all-DURANDAL-NC_CHANGE_DEAGGED_LOADOUT” // Dev Setting
-
@Starkes Not sure how to make them non (UTF8)
-
@Starkes just copy my non UTF8 line to your config file. Use notepad to edit the config file, not word (because word converts quotes to UTF8 quotes).
-
@Seifer Ok. I just did that now