Solved Alternative launcher crashing
-
@airtex2019 a day of no bms launches is a good amount of reproducing of the problem haha
-
@airtex2019 is this the same bug i posted yesterday?
-
@headcase Quite possibly. Did you continue to have problems after re-installing everything?
-
@airtex2019 no not currently another 6-7 hours in log, no problems
-
-
@okayasugf thanks – and can you confirm that baseDir is correct? is your main BMS exe at
D:\Falcon BMS 4.37\Bin\x64\Falcon BMS.exe
? -
@airtex2019 oh, i just added an NVMe to my laptop, it somehow made the D drive for itself and changed D drive to E drive
-
@okayasugf lol ok … “there’s your problem”. I’ll leave you to sort that out…
thanks for nudging me into fixing a couple of problems in AL startup code, and improving the diagnostic logging – I’ll try to make sure a better error msg appears, for this case.
-
@airtex2019 any idea how i fix it tho
do i have to change the registry? -
Option A: backup any user cfg or data files you care about, and re-install BMS.
Option B: just edit the registry to point to E:\Falcon BMS 4.37 or wherever you shifted things to
Option C : use DiskMgmt.msc to re-assign drive letters back to the way they were … if that was your original intention or expectation
-
@airtex2019 option b worked, thanks, you’re a legend
-
-
@okayasugf great – if you search your entire registry for “D:\Falcon” you might find a few other hits. these may or may not be important to you… just things to be aware of
- firewall port rules for BMS (for multiplayer)
- antivirus exclusion rules, if you configured that
- the list of “prefer high-performance” apps
- Windows appcompat flags (current BMS doesn’t really need any… just dpi-aware, but that will get recreated automatically)