Solved CTD on opening 2D setup
-
<p>So my BMS CTDs when I click the 2D setup button.<br />dmp.7z file: <a href=“https://we.tl/t-8G9FEqSUda” target=“_blank”>https://we.tl/t-8G9FEqSUda</a> <br />It happens on a fresh install once I copy back my /user/config.<br />After some search in here, it turns out that might comes from a corrupted key file, I’m using Alternative Launcher 1.6 for my bindings, how can I track the culprit, corrupted line? I can try to redo the bindings from scratch (I have a <strong><em>lot</em></strong> of those), but even then I’m not sure if I’ll not corrupted it again, not knowing where the problem came from in the first place…</p>
-
<p>@Jetsun be on lookout for any UTF-8 or extended ascii characters … eg. in the description text field. I don’t know if BMS has a problem with those, but I suspect AL doesn’t so it might be a point of incompatibility…</p>
-
<p>@Jetsun <br />I once had this happen … my fault, for hand-editing the key file. and I didn’t have any recent backup of that work, to diff it back against. but I just couldn’t see the problem with my own eyes. <br /><br />How savvy are you with regular expressions? I ended up doing a lot of ‘grep -v’ to filter out all lines that adhered to the expected syntax… that eventually allowed me to see the problem. (turns out I’d somehow bumped the keyboard, or mistakenly inserted a ‘comma’ in one of the dx bindings)<br /><br /></p>
-
<p>@airtex2019 used some grep in my younger days, so might google to educate myself back, but first I’d like to be sure that my problem comes from the keyfile, can’t decipher the .dmp myself, which after some thinking would be kinda weird as it is auto generated by alt launcher, so at least no typo.<br /><br />Edit: <br />Tried the following, same CTDs:</p><ul><li>alt lauching bms without alt launcher setup override </li><li>creating a new pilot in the logbook</li></ul><p><br /></p>
-
<p>@Jetsun Try deleting your
d3d11.dsp
file in the config folder.</p> -
<p>@CriticalMass oh yes, sorry, forgot to mention I did try that too first time I got the problem.</p>
-
<p>May be someone is able to tell me from the .dmp which user file is triggering the crash?</p>
-
<p>@Jetsun Some things to try, to maybe narrow it down…<br /><br />1. Fresh install (or using fresh-install copy of User/Config folder) including Viper.pop and all the stock key files and ini files…<br />2. Launch BMS exe directly (\Falcon BMS 4.35\Bin\x64\Falcon BMS.exe) not through the launcher, or alt launcher…<br /><br />That should work ok. Then…<br /><br />3. Change the keyfile … load your custom key file. <br />4. Quit and restart… then see what happens.<br /><br /><br /></p>
-
<p>@airtex2019 Right on, thanks, so it is my BMS - full.key that is corrupted, the one generated by Alternative launcher, gonna look closer. </p>
-
<p>@Jetsun be on lookout for any UTF-8 or extended ascii characters … eg. in the description text field. I don’t know if BMS has a problem with those, but I suspect AL doesn’t so it might be a point of incompatibility…</p>
-
<p>@airtex2019 great, that was precisely that! easy to track down with the notepad++ compare (pluggin) between original BMS - full.key and mine. Big thank you for your time and guidance.</p>
-
<p><img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=1g16vn91q2r” alt=“” class=“not-responsive emoji emoji-android emoji–+1” /> </p>
-