Solved BMS 4.37 Startup error: Could not create device on adapter
-
@LockeyNoS7even said in BMS 4.37 Startup error: Could not create device on adapter:
This cannot just be down to windows since 4.35 runs on my machine while 4.36 and 4.37 both crash at start.
I just tried it for the 1st time in VR. Turned on my G2 power, started SteamVR, and hit the 4.37 exe… no error, started right up! The cockpit was off a few degrees left and my feet are in my chest, but other than that it worked flawlessly in 10 minutes of Instant Action! I’m going to guess that “SIM: VR Camera Rotation Reset” is the VR recenter key and will try it again soon to see if that centers my view, have set the “OTW: VR Zoom” and “OTW: VR Zoom Toggle” jeys up also to see what they do. All in all they did a damn good job for first release! I have the latest Nvidea drivers (NVCleanstall - No Bloat) and the latest Win11 release.
-
@MaxWaldorf I have and I am facing this issue too.
-
@MaxWaldorf affirm, I’ve also tried uninstalling and re-installing 4.37
-
As 22H2 seems to be broken for you guys anyways, could you try installing KB5020044? it should fix some issues for VR
It addresses an issue that affects the performance of some games and applications. This issue is related to GPU performance debugging features.
-
@Tumbler31 - Thanks for the ideas mate. Sadly I already have that one installed (my windows is fully up to date to KB5021255.)
Also for completeness I have tried rolling back AMD drivers a few versions and have the same issue.
-
@Tumbler31 I also already have that update
-
KB5020044 is a preview update, so doesnt come standard. Your update history shows this update installed?
-
@Tumbler31 Yes, my machine took the original W11 22H2 update which introduced a performance issue for a number of games. I installed this update as soon as it was available for my machine.
-
@LockeyNoS7even thanks for checking, quite a pity it didnt solve the issue
-
@Tumbler31 I know! Particularly annoying that the
createDeviceOnAdapter
call works for the 4.35 install I have.
Is the direct x installer available separately anywhere? Just wondering if the silent install is failing somehow and not logging anything.
-
Nevermind. Assuming I’ve got the right one: https://www.microsoft.com/en-gb/download/details.aspx?id=8109
Installing from this didn’t resolve the issue either. -
@Tumbler31 my Windows 11 is already up to date with KB5021255. I am also running on Nvidia Game Ready Driver 527.56. I also tried reinstalling my directX runtime, but to no avail. I still get the same error.
-
Same issue, i’m on W11 22H2 with the newest AMD drivers. Installed DirectX. Windows is up to date, including KB5020044 and KB502155.
-
@rubbereend said in BMS 4.37 Startup error: Could not create device on adapter:
Same issue, i’m on W11 22H2 with the newest AMD drivers. Installed DirectX. Windows is up to date, including KB5020044 and KB502155.
I’m running Win11 Pro 22H2 build 22623.1037 and Nvidia 527.56. I also run (from framerate issues a ways back in VR on IL-2/DCS) a Holoshell shut down batch file that may not even be necessary anymore, and my Nvidia drivers are “naked”, installed by running Display Driver Uninstaller and then running NVCleanstall and only installing the Drivers (and PhysX and Sound if you use them, if not, ONLY the drivers. No Telemetry, No GeForce Experience bloatware. Other than that I have done nothing special to get this working, good luck!
-
I can confirm that when I unplug my Reverb G2 and reboot the game runs fine. I can then plug in my Quest 2 via Link cable and the game runs in VR just fine. When I unplug the Quest 2 and plugin the Reverb G2 the game no longer works. So, I am definitely leaning towards a windows update issue that has broken this game with WMR. I am currently running Windows 11 22H2 and cannot roll back. I am in the insider programs beta branch so I guess it’s a waiting game or maybe there is something in Falcon BMS 4.37 that can be adjusted for it to work. I guess I’ll have to wait for smarter people to come up with something or Microsoft to fix Windows 11 again.
-
I was never impressed by HP hardware…
Don’t know what they did with their headset to be so different from the others…
-
I found a fix for windows 11:
I’ve updated to the latest beta version of windows 11 with a bat file that you can find here: https://github.com/abbodi1406/offlineinsiderenroll/releases
then, I’ve stopped the holographic shell with a bat file that you can find here:
https://forums.flightsimulator.com/t/win-11-update-causing-stutters/543631/127(if you are completely new to bat files, copy the code: "
@echo off
logman stop HolographicShell -ets
" without the 2 “” and paste it in a .txt file. Then rename it to yourfilename.bat) -
@vps_zen I can confirm this works without installing beta. I’ve ran the bat file and then game launches correctly.
-
for clearer copy/pasta:
@echo off logman stop HolographicShell -ets
this is great news, if this works for everyone
-
@johnnyj71 again, if you are on the Windows Insider Beta release section you should be running 22H2 22623.1037, that is not the issue as i’m in the WI program also. Try the Holoshell fix shown above, if it works you can set it as a Task to run at every start up…
-