[Solved] Medieval Engineers broke Space Engineers D: DX11/Adapter issue

[Corvus]

[Solution]

setting launch options to force DX9 appears to reset a variable that got stuck, causing the DX11 check to fall. After launching, closing, removing dx9 launch option - the game is running fine again. No clue about ME, I'm scared to test it... I just want to play SE.

*Right click Space Engineers in Library
*Properties
*Set Launch Options: -force-d3d9
*Launch game (may have to load a game... I'm not sure at this point)
*Close game
*Remove launch option
*Launch game

Worked for me.

_________________________________________________________

[Original Post]

I hope I'm just dumb and missing something. 2 days trying to get this game working again...

It's been a few years, but I've been playing SE the past few weeks. Been having a really good time and enjoying all the updates. Decided I wanted to see what had changed in Medieval Engineers, so I closed SE and downloaded and launched ME:

"Update Windows or your video drivers" (or something like that) and game closes.

Hm... ok - so I check drivers (GTX 780 ti), they're good. Same message appears. So I said screw it, I'll just go back to SE.

I launch SE (less than an hour after I stopped playing it) and now splash screen freezes and I get the message:

"The current version of the game requires a Dx11 card. \n For more information please see:
http://blog.marekrosa.org/2016/02/space-engineers-news-full-source-code_26.html "
(the link is dead)


I've been through the whole list of routine fixes and can't seem to figure out what the problem is. The only other game I seem to be having problems with is Empyrion - but I'm not sure that's related. All other DX11 games are working.

I saw in the SE DX11 log file that it checked the wrong video adapter (integrated card) - so updateRequired was set to TRUE, I assume THIS the ultimate cause. I've done everything to ensure it's checking the correct adapter, but it doesn't even generate the log file now so I can't verify. All settings look good though.

PLEASE let me know if you have any solutions :(

I think the initial error with ME occurred because it launched on my second monitor, which is connected to my integrated graphics card. Not sure why it did this, the main monitor was in focus and no other applications were open. I don't know why this would also affect SE - seems to be a shared setting of some sort?

I've checked all settings I know of and they are defaulted to the correct adapter.



Here's what I've done:

Windows up to date
Clean install of Nvidia drivers
Verified integrity of files
Deleted cfg/shader files/folder
Deleted entire AppData SE folder content
Deleted ALL files (appdata/steamCommon)
Uninstalled/Reinstalled
power options (Windows and nvidia CP)
Disabled integrated video adapter


Specs:
i7-3770K 3.5
16gb
GTX780ti


Again, SE has been working fine until I launched ME. :'(

[Annonymous]

Run Dxdiag, and post the abbreviated results.

Although I've noted several posts about DX11 issues, lately. Odd....

[Corvus]

------------------
System Information
------------------
Operating System: Windows 10 Home 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
System Model: To Be Filled By O.E.M.
BIOS: BIOS Date: 03/08/12 19:58:28 Ver: 04.06.05 (type: BIOS)
Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16278MB RAM
Page File: 3921MB used, 17476MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 104 DPI (108 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.17763.0001 64bit Unicode

---------------
Display Devices
---------------
Card name: NVIDIA GeForce GTX 780 Ti
Manufacturer: NVIDIA
Chip type: GeForce GTX 780 Ti
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_100A&SUBSYS_28813842&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 11168 MB
Dedicated Memory: 3029 MB
Shared Memory: 8139 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Internal
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.632813,0.339844), Green(0.320313,0.622070), Blue(0.155273,0.041992), White Point(0.312500,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: SMS23A350H
Monitor Id: SAM07D4
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9c0cfd0baad9a756\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9c0cfd0baad9a756\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9c0cfd0baad9a756\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9c0cfd0baad9a756\nvldumdx.dll
Driver File Version: 25.21.0014.1935 (English)
Driver Version: 25.21.14.1935
DDI Version: 12
Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.5
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported by Graphics driver
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:False
Driver Attributes: Final Retail
Driver Date/Size: 2/28/2019 6:00:00 PM, 957824 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-534A-11CF-7D5C-8F081BC2D435}
Vendor ID: 0x10DE
Device ID: 0x100A
SubSys ID: 0x28813842
Revision ID: 0x00A1
Driver Strong Name: oem17.inf:0f066de3182b453d:Section008:25.21.14.1935:pci\ven_10de&dev_100a
Rank Of Driver: 00D12001
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported

---------------
Diagnostics
---------------
Windows Error Reporting:
+++ WER0 +++:
Fault bucket 1524662434367910590, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Empyrion.exe
P2: 2017.1.2.34239
P3: 10.0.17763.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

[Corvus]

Found someone with the same problem...

https://steamcommunity.com/app/244850/discussions/6/1480982338963689221/?ctp=1


Easy fix... just reinstall windows!

[Corvus]

setting launch options to force DX9 works

right click Space Engineers in Library
Properties
Set Launch Options
-force-d3d9

works - looks the same - runs the same.

Not sure if this is a long term solution.

[Annonymous]

I'm hoping someone more knowledgeable than me can take a look at what you've posted and point out a solution. Me.... I can't honestly see anything wrong. To me, you've the appropriate hardware and software..

Best of luck!

[Corvus]

Thanks for taking a look - I appreciate your time!

[Ydyp]

Try to reinstall a clean copy of SE as well as repair your directX installment, guides can be found online. As it seems while trying to run ME it either messed up a shared setting with the engine, but more likely because of the work around did corrupt your DirectX installement.

[Corvus]

Which work around caused corruption? Only work around I'm aware of was my 'solution' of DX9 which was the last step I took, so had nothing to do with the problem.

I did clean install. DirectX repairs/installations are managed through Windows updates, as far as I could find.

[Ydyp]

Originally posted by Corvus:

Which work around caused corruption? Only work around I'm aware of was my 'solution' of DX9 which was the last step I took, so had nothing to do with the problem.

I did clean install. DirectX repairs/installations are managed through Windows updates, as far as I could find.

I think you misunderstood or I was not clear enough, it was not the workaround that did corrupt your installment of Direct X. But your work around to force dx9 is just an indicator that your dx11 is most like corrupted by ME when you tried to run it.

But if none of the repairs and reinstalling worked, I fear that the problem is nested deeper in your pc or either you hit a bug in SE that conflicts with the later dx versions and only Keen can help you any further to figure out what and where it goes wrong.

[Manwith Noname]

Originally posted by Corvus:

-force-d3d9

This looks suspiciously like a Unity command and I'm not convinced it is actually doing anything. Does anyone have a list of VRAGE launch commands? My google fu seems lacking on this.

[Corvus]

The game won't run without it in launch options, so it's doing something. It might still be running 11, but I can't tell.

Is there a way to check what version is being utilized once the game is running.

[Corvus]

Thanks ydp, I get what you mean. it must be specific to keen games, as other direct x games continue to function properly.

[Dan2D3D]

I have both games and that never happened to me =

+

Games will always use the Graphic card DirectX

Yours is NVIDIA GeForce GTX 780 Ti = DirectX 12.0 (11_1) = OK

so it should run no problems!

Make sure Windows updates are completed.

And do not force DX9 cause there is already a DX9 game version we can install in the BETA tab of the game properties.


DX9 = No Planets

[Corvus]

Lol Dan, while I appreciate the response, did you read?

Game is running fine with dx9. Saved game loads with planets, no problem. Maybe other poster is correct that the launch command is not actually affecting direct x, but it changes something during launch, because it allows me to play.

Yes, I'm aware my card is fine. I've been playing for a bit until ME messed stuff up.

Obviously, there is a problem.

Windows is completely updated, per original post. Again, no problems until ME launch.

I don't want to install a beta, I shouldn't have to. Forcing dx9 is the ONLY way I can play.

[Dan2D3D]

That is why it's a weird problem cause No planets on DX9