Solved 4.37 fails to start
-
@Predator-23rd and all, thank you.
After uninstalling and re installing the problem went away. -
well, actually it isn’t fixed. After reinstalling I managed to get the launcher started, and could do a few flights both in VR and 2D. Then I closed the launcher, and upon trying to start it again I get the same error.
@Predator-23rd can you still open the launcher?
With the legacy launcher I get a weird message on startup (file access denied) then the launcher starts but all buttons are disabled except for “close” and “documentation”. I am using an administrator account.
the VR help section did not help, I don’t think this has anything to do with VR.
-
@bonfor What directory do you have BMS installed in?
I hear a lot of people having weird file/directory permission problems, installing it under the Steam folders… BMS really wants to be in its own top-level folder, eg. ‘C:\Falcon BMS 4.37’ or near to that. (Not under C:\Users or C:\ProgramFiles anywhere.)
-
@bonfor for me everything is working as it should be.
I have all my game files on a dedicated M.2 card. D:\Falcon BMS 4.36 and D:\Falcon BMS 4.37. The launcher handles this without a problem.
-
@Predator-23rd and @airtex2019 , ok thanks. I’ll try that. I have it under C:\Program Files\Falcon… I’ll try moving it back up to C:\ and report back.
-
that was it! It didn’t like it being installed under program files, it needs to be under C:/
How do I mark this as solved? -
-
Hi,
Having similar problem and log file as bonfor did have.
Tried to uninstall, fix registers, reinstall.
No success.Cannot start 4.37 via the AL and neither via the 4.37 launcher itself.
Even can not enter AL.
AL is only working when I do remove 4.37 and go on with 4.36My install folder does look like:
Any ideas what I can do next?
Thanks
Al -
-
@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