BMS 4.33 U1 - Cannot proceed past Mission Schedule screen to 3D world in Windows 10
-
I’ve read the few other posts regarding BMS not running in Windows 10. However my issue seems similar but unique. I can launch BMS (both 4.33 and 4.33 U1 64 bits), and get as far as the Mission Schedule screen, right before hitting “Takeoff”. As soon as I hit the takeoff button, the cursor changes to the parachute man, then disappears, and then…nothing. It just hangs up at that screen. No further progress.
Here are my system specs:
HP Envy
Windows 10 Home 64 bit version 1511
OS Build 10586.545
Processor: Intel i7-5500U 2.40GHz
RAM: 16GB (x2 8GB Hynix/Hyundai 1600MHz)
NVIDIA GeForce GTX 950M
Intel HD Graphics 5500I’ve tried running in windowed mode and I have the same problem. Also tried running as Windows 7 compatibility and no success.
I’m forced to enter Task Manager, at which point a message pops up saying, “BMS has stopped working” or something to that effect.
Any suggestions?
-
You are on notebook. Have you set power settings to maximum performance from control panel?
Also in gfx settings which vga is selected?Sent from TapaTalk
-
BMS is running off the NVIDIA card; only option I have in game. And my settings are set for max performance. This laptop came with Windows 8.1 BMS ran fine on that OS. I’ve had Windows 10 for several months. Can’t remember if I ever ran BMS under Windows 10 or only before upgrading. It’s been a while since I’ve tried to fly.
-
I have the same problem than Bluebombers_84. The game stalls when I hit the takeoff button. I also run on Windows 10. I guess we have the same issue (and we are probably not the only ones).
Help would be greatly appreciated.
-
Same here. BMS 4.33 cannot run on some Windows 10. No fix. So I moved over to DCS.
Update: Selecting GeForce Graphics card under NVidia Control Panel>Manage 3D plus changing the Falcon BMS exe properties to run in Win 7 Compatibility made it work for me, although only in 32bit mode. I couldn’t get it to work in 64bit mode -> after ‘Commit’, parachute man appears then disappears and it never gets to the F-16 loading screen. (I have 64bit Win10.)
-
Guys, did BMS never work on 10 or did it use to work and suddenly stopped?
In the latter case, did you by chance received the Windows 10 Anniversary Update? -
Guys, did BMS never work on 10 or did it use to work and suddenly stopped?
In the latter case, did you by chance received the Windows 10 Anniversary Update?Really wish I could help but I’ve never had issues with Win 10 and BMS 4.32 or 4.33U1
Win10 Pro 64
Version 1607
Build 14393.51
Hardware in sig -
Really wish I could help but I’ve never had issues with Win 10 and BMS 4.32 or 4.33U1
Same here, just trying to understand if it could be a “side effect” of the Anniversary Update…
-
Same here, just trying to understand if it could be a “side effect” of the Anniversary Update…
Do you have yours in a standalone directory or /Program Files etc?
I’ve read/heard of issues with installing games into /Program Files on the OS drive or other drives.
I have a SSD that is my F drive that I keep all games on, and install them all in their own directory so there’s no permission issues.
I run it native without admin rights and with no compatibility settings.
Maybe if we can find some common ground some progress can be made, questions apply to those with issues also. -
Good point, indeed.
I also have it out of Program Files, in my case I have my games installed in a subdirectory of (each in its own folder) but I think this makes no difference.
I run them with my user, without admin privileges and with no compatibility setting, too.
Hope this helps.Inviato dal mio Nexus 6 utilizzando Tapatalk
-
Currently loaded into C:\Program Files (x86)\Falcon BMS 4.33 U1
I ran BMS 4.33 out of the same C:\Program Files (x86)\ directory without issue - but again I can’t recall if that was running Windows 10 or 8.1
Thanks for the help everyone. I’m hoping a solution can be found.
-
I run BMS 4.33 U1 on Win10 x64 Anniversary update just fine without any compatibility settings. However, I have installed it on other disk than C:/.
-
Thanks for the help everyone. I’m hoping a solution can be found.
Well, considering also the last reply from gravite, you could try to uninstall and reinstall BMS being careful to NOT make it end into “Program Files”… if it starts working, it would be a quasi-ultimate proof of the isssue and a solution.
Try for instance to change the installation folder path to “C:\Games\Falcon BMS 4.33 U1” (mine is as such). -
Hmm…interesting thoughts. I’ll try uninstalling and re-installing into a new directory. My hard drive is partitioned into several smaller directories, so I’ll throw it onto something other than C:\ and report back when I’ve done that.
-
Hmm…interesting thoughts. I’ll try uninstalling and re-installing into a new directory. My hard drive is partitioned into several smaller directories, so I’ll throw it onto something other than C:\ and report back when I’ve done that.
Let us know, one weird thing but I don’t know if it would affect it, the C:\Program Files (x86)\ is for 32 bit programs. http://www.computerhope.com/issues/ch001266.htm
-
Sadly no change. Re-installed to a new directory and having the same issues.
-
Sad to hear this, I really hoped it to work.
Have you got any crash log in your User folder? -
I dont have a solution but maybe i can narrow the focus. I have bms 4.33.u1 on Win10 installed to (C:\Falcon BMS 4.33 U1)
so may be the issue isn’t ten. be advised its an older win ten that never goes online so i dont know about updates (breaking) the sim -
Sadly no change. Re-installed to a new directory and having the same issues.
Well crap hoped that would help. Just to be sure, your callsign in BMS is less than 12 characters correct?
Also. now that you have it in a new directory, delete the dx9display.dsp in x:\Falcon BMS 4.33 U1\User\Config and restart to see if that might help. -
Sadly no change. Re-installed to a new directory and having the same issues.
Have you tried downloading a new BMS exe in case of corruption?
You tried changing driver version or are you stuck with an OEM driver?
What about installing DX libraries again?
Am on the latest Win 10 64 update but actually still running an older NVIDIA driver 353.62 to run some older games.