Solved 4.37 fails to start
-
@Sparks it was solved for the poster…
If your issue is different, then new thread…
-
-
@Sparks very hard to say what’s going wrong… my earlier solution was a wildass guess so sorry that’s all I’ve got
do you have a lot invested in keybd/hotas bindings yet? if not, you can try uninstall reinstall.
if so, backup everything in your User/Config subfolder and try it. lame advice, but that’s what I’d try.
If that still fails, I’d do as Max suggests and open a new thread, for the launcher devs to take a fresh look.
-
Well one step further now.
I can run 4.37 fromD:\FALCOM BMS 4.37\Bin\x86\Hub.exe
Sytem specs:
Intel I7-4790 CPU @3.6 Ghz
RAM 16 Gb
W10 PRO 64 bit
NVIDIA GeForce GTX970Regards
Al -
How is your Error Log.txt like?
-
@chihirobelmo ok now I am getting this failure!
I have VS 2022 and am more than willing and able to help debug WPF code. Let me know if there’s any particular suspect I should look for, Chihiro… or if you’d like me to zip up my config, if you’d like to take a look.
-
@airtex2019 Window_Loaded() seems finished but it crashed with some kind of windows library and really hard to track what is that caused by the error message. If you can try debug them it would help a lot, also please zip and send me User/Config
-
@chihirobelmo cool will do – I meant to ask, is the v2.2.0 tag on GitHub the right source for 4.37?
-
@Sparks there may be more doing on, but in my case at least, it seemed to be due to missing ‘BMS - Auto.key’ file.
I made a copy of ‘BMS - Basic.key’, renamed it ‘BMS - Auto.key’, and was able to start the New Launcher successfully.
The error message and logs in this case, are very weird tho … still investigating.
-
@airtex2019 said in 4.37 fails to start:
@Sparks there may be more doing on, but in my case at least, it seemed to be due to missing ‘BMS - Auto.key’ file.
I made a copy of ‘BMS - Basic.key’, renamed it ‘BMS - Auto.key’, and was able to start the New Launcher successfully.
The error message and logs in this case, are very weird tho … still investigating.
Hi,
Didn’t work for me
Regards
Al -
Problem solved thanks to airtex in other treat.
I have chenged the securuty setting of the total 4.37 folder to full permissions.
Thanks
-
I had a problem with launching after installing 4.37:
the problem was wrong usage rights on created folder and some files,solved by reassigned them to All users permission to allow reading/writing/etc as it was in 4.36
-
thanks
-
Started encountering this today after previously having no issues.
Posted solutions dont seem to work.
Edit: Not definitive, but I’ve reinstalled BMS completely and then restored my User/Config dir and the AL works again - so if I had to guess I’d suggest not an issue with anything within that dir.
-
I just get the start up splash screen then a CTD. Full permissions enabled. Happened after the ITO theater install.
-
@Mower this thread was more about AL not starting
if BMS proper is crashing, I recommend opening a new thread, and paste or link to your crash log file
-
@Mower said in 4.37 fails to start:
I just get the start up splash screen then a CTD. Full permissions enabled. Happened after the ITO theater install.
It seems you’ve exceeded limit of leaving/going back to Falcon/BMS
In seriousness, if it happen after installing ITO, i’d start with uninstall ITO, try or do clean install without ITO and confirm if it still CTDs.
If yes, then report back if no, check with vAiCon. -
Installing this theater started the problem of BMS CTD-ing after the initial splash screen.