Solved BMS 4.37 Startup error: Could not create device on adapter
-
@felix557 delete
\Falcon BMS 4.37\User\Config\d3d11.dsp
and run with ‘debug’ (=-mono
) enabled in the launcher.Then zip all the debug files and share them. Details see here https://forum.falcon-bms.com/topic/20866/
-
I don’t see the d3d11.dsp in the said folder. I tried searching the entire BMS Folder for the said file, but it does not exist.
I did the steps in creating a debug registry key for BMS.exe
I ran BMS from the alternative launcher in debug mode, then this guy appeared before the game actually launched.
Then the splash screen appeared, then the same error appeared.
When the error appeared, I opened the task manager, and right-clicked on Falcon BMS, but the “Create Dump File” is grayed out.
-
@felix557 is this Windows 11, 22H2?
There have been widespread reports of problems with Nvidia drivers, reporting they’re in “debug mode”.
https://windowsreport.com/windows-11-22h2-nvidia-issue/
I think already fixed in latest drivers… try updating?
-
@felix557 - Same issue here on an AMD 6900XT. Through testing I have found it is definitely the G2 initialising with windows mixed reality that is causing the problem.
-
Drivers are already updated. I also tried reinstalling them.
Did you unplug your G2 before running BMS? What workaround did you do?
-
@felix557 - I rebooted with the G2 unplugged and I can launch BMS in 2D. As soon as I have initialised and run Windows Mixed Reality neither VR or 2D mode will work for that boot.
-
@Boffin3212 I can confirm this works. Rebooted my PC with the Reverb G2 unplugged. And it worked.
-
I’m also running a G2 and having this issue. I didn’t start Windows Mixed Reality just had the headset powered on.
Windows 11 and Nvidia drivers are all up to date. -
I tried plugging in my G2 after successfully starting BMS in 2D (booted my PC with the G2 unplugged). The error came back.
-
Debug log looks very similar to yours - looks like the hits with the “Please run without a graphics debugger attached.” line.
-
@airtex2019 said in BMS 4.37 Startup error: Could not create device on adapter:
@felix557 is this Windows 11, 22H2?
There have been widespread reports of problems with Nvidia drivers, reporting they’re in “debug mode”.
https://windowsreport.com/windows-11-22h2-nvidia-issue/
I think already fixed in latest drivers… try updating?
@Boffin3212 so I guess this hasn’t been fully fixed as it still affects some programs?
-
@felix557 Im AMD so not much I can do about Nvidia drivers - but my AMD set is up to date. Can confirm I am on 22H2 though.
Curious - do you use any other tools for DCS VR? I am wondering about OpenComposite/OpenXR Developer tools. Shouldnt have an impact since not open XR though.
-
@Boffin3212 missed that part. My bad. I am on the same windows version tho.
For DCS I use OpenComposite/OpenXR toolkit without any problem.
-
Posting my debug output as well.
-
@felix557 - Just tried rolling out of Steam VR betas/OpenXR runtime etc. Nothing seems to change anything and I have checked that 2D wont work from the moment of plugging in the headset (not just having run Windows Mixed Reality). Don’t think there is much else to try.
-
Debug logs from 4.35 which runs without issue for comparison
-
@Boffin3212 Can confirm I have a same issue with Reverb G1 on Windows 11 22H2. My GFX card is RTX 2070 and I am using the latest Nvidia Driver and the latest Geforce Experience.
-
I read in another thread that some of them rolled back to Windows 11 21H1.
How come my windows recovery panel doesn’t have the option to rollback to previous versions? -
@felix557 did you do a disk clean up since then? You might have removed them. Unfortunately the only way to put 21H2 back on that I know of is the reinstall Windows.
-
@felix557 said in BMS 4.37 Startup error: Could not create device on adapter:
I downloaded Falcon BMS 4.37 today and installed it normally using the installer. When I first ran the game (non-VR) thru the alternative launcher, I got the “Could not create device on adapter” error.
I looked up the error on the internet and tried the suggestions (Although those I read were for 4.35 and 4.36) such as reinstalling the drivers and Nvidia physx, but I still get the error both in VR and non-VR.
My PC specs:
i9-9900k
MSI Gaming X Trio 3090 Ti
32GB 3200MHZ DDR4 RAM
ROG Maximus XI Hero WiFi MoBo
HP Reverb G2 VR HeadsetWow, that is the error I used to get in 4.36 when I tried running it with my G2 turned on. Could never figure it out, just had to make sure it was powered off before starting BMS… Hope this gets sorted, just installing 4.37 now. I am absolutely NOT rolling back the OS…