Does "-dx11" In Command Prompt Still Work Under Windows 7?

[Broth of Crom]

Would typing "-dx11" in the command line make the game work under Windows 7? Anyone know that had first-hand experience? (Don't want to install the game for nothing.)

[Bedna]

There was a big discussion about this earlier on the forum.
Neither Microsoft nor Steam supports win7.

It is higly insecure for you to use such an old operating system (unless completely disconnected from the internet at ALL times).

Please consider switching operating system.
If hardware limitations exist, consider learning how to use a linux distribution.
Satisfactory plays perfectly on linux, I know, because I do it. :)

[Phoenix Cat]

Steam does not support windows 7. It's been 10 and higher since January 2024. If you look at the requirements it says Windows 10. It's people like you that cause security issues and breaches. Windows 11 is now going to be standard. Get with the times...

[Broth of Crom]

Originally posted by Phoenix Cat:

Steam does not support windows 7. It's been 10 and higher since January 2024. If you look at the requirements it says Windows 10. It's people like you that cause security issues and breaches. Windows 11 is now going to be standard. Get with the times...

So, you don't know and failed to understand the question. Got it. You also have no hands-on experience (speaking of "requirements").

Furthermore, you also accused me of causing security issues and breaches. You will refrain from further misinformation and attempts at correspondence.

Back to the here-and-now: If anyone's tested -dx11 on a Windows 7 machine, did it work as of v1.0? No more useless flamer(s), thanks!

[Broth of Crom]

Originally posted by Bedna:

There was a big discussion about this earlier on the forum.
Neither Microsoft nor Steam supports win7.

It is higly insecure for you to use such an old operating system (unless completely disconnected from the internet at ALL times).

Please consider switching operating system.
If hardware limitations exist, consider learning how to use a linux distribution.
Satisfactory plays perfectly on linux, I know, because I do it. :)

Perhaps; however, presently I am wondering about the simple Windows 7 workaround.

[H5N1]

I just tried -dx11 on my Win11 PC and yes it ran in DX11 mode so I would guess it works however getting it to work may be more challenging because of Steams requirements these days.

[Goblin]

The issue with running the game on Windows 7 isn't only related to DX12, it's DLLs and functions in the engine no longer looking for certain files and API functions that are on Win7 and got replaced by others in later versions.
For earlier builds you had to hex edit one DLL to change a call to the CreateFile2 function into CreateFileW instead. This is generally a case of code previously having a branch "if windows 7 or older use A, else B", and as support gets dropped for the older OS said code gets cleaned up over time. And from what I can tell more stuff is broken now than before. Could very well not even be something CSS did, but got changed in the newer UE5 version they upgraded to.
It might be possible to track down everything new that got this treatment and get it running again, but it might also just be unrecoverable at this point. Honestly, at this point it's probably easier - and safer - to learn to use Linux than to figure out how to fix issues like these.

[Bedna]

Originally posted by Broth of Crom:

So, you don't know and failed to understand the question. Got it. You also have no hands-on experience (speaking of "requirements").

No, you got the correct answer, but that was not the answer you wanted to hear.

Nobody cares if the option works or not because:
1. It is not supported
2. NOBODY SHOULD USE WIN7

Furthermore, you also accused me of causing security issues and breaches. You will refrain from further misinformation and attempts at correspondence.

Back to the here-and-now: If anyone's tested -dx11 on a Windows 7 machine, did it work as of v1.0? No more useless flamer(s), thanks!

Again, no, nobody accused you of anything, What was said was YOU put YOURSELF in a very dangerous situation.
But since you framed it that way, depending on your situation, you might put others at risk too. People using the same network as you for example. Family members on the same connection. Or phishing is extremely popular towards win7 users acquaintances, because they can fake send things that looks like they come from you super easy, hence putting others in danger too.

But since YOU only flame and act like an idiot towards people TRYING TO HELP YOU, I will not interact more with you, and for sanity reasons, I recommend others to do the same.

[HardXcoreXdave]

some people just shouldn't use a computer lol

[Broth of Crom]

Originally posted by Bedna:

Originally posted by Broth of Crom:

So, you don't know and failed to understand the question. Got it. You also have no hands-on experience (speaking of "requirements").

No, you got the correct answer, but that was not the answer you wanted to hear.

Nobody cares if the option works or not because:
1. It is not supported
2. NOBODY SHOULD USE WIN7

Furthermore, you also accused me of causing security issues and breaches. You will refrain from further misinformation and attempts at correspondence.

Back to the here-and-now: If anyone's tested -dx11 on a Windows 7 machine, did it work as of v1.0? No more useless flamer(s), thanks!

Again, no, nobody accused you of anything, What was said was YOU put YOURSELF in a very dangerous situation.
But since you framed it that way, depending on your situation, you might put others at risk too. People using the same network as you for example. Family members on the same connection. Or phishing is extremely popular towards win7 users acquaintances, because they can fake send things that looks like they come from you super easy, hence putting others in danger too.

But since YOU only flame and act like an idiot towards people TRYING TO HELP YOU, I will not interact more with you, and for sanity reasons, I recommend others to do the same.

Um, are you friends with the flamer? Everything you responded to (quoted) was not even directed to you and not true. Did you read it? Now I'm not sure if I would take advice from you if you can't differentiate that, let alone start to unnecessarily attack me. You seemed as if you were genuinely trying to help earlier; however, evidently, looks can be deceiving and your true colors came out. Makes me lose hope for humanity.

Don't derail the topic any further.

[Broth of Crom]

Originally posted by Goblin:

The issue with running the game on Windows 7 isn't only related to DX12, it's DLLs and functions in the engine no longer looking for certain files and API functions that are on Win7 and got replaced by others in later versions.
For earlier builds you had to hex edit one DLL to change a call to the CreateFile2 function into CreateFileW instead. This is generally a case of code previously having a branch "if windows 7 or older use A, else B", and as support gets dropped for the older OS said code gets cleaned up over time. And from what I can tell more stuff is broken now than before. Could very well not even be something CSS did, but got changed in the newer UE5 version they upgraded to.
It might be possible to track down everything new that got this treatment and get it running again, but it might also just be unrecoverable at this point. Honestly, at this point it's probably easier - and safer - to learn to use Linux than to figure out how to fix issues like these.

You're right that it probably won't work if you even did try. And trying would be a lot of work to even see if it will run. I'll probably get kernal32.dll errors and whatnot. And Unity changes definitely made it harder for things to work together in that respect. Thanks for the insight. I was just curious if someone tried -dx11 and saw this post and what happened, that's all. Helpful to hear that it probably won't work with that simple fix in the end like it did in the past, and like in other games. Other games I got it to work with it, or changing or renaming .dlls, but most likely not going to work with this game.

[Alrethe]

Broth of Crom you seem a bit hostile. Breath my friend. :) Quick 10 second google searching. Seems since Satisfatory Update 5 they switched to an updated Unreal engine which dropped support Win7 with DX11. Looks like a few have hacked things to get it to work on the older version of Satisfactory. But as the game and Steam and well pretty much everything doesn't support Win7. Then the answer to your question of "Does '-dx11' In Command Prompt Still Work Under Windows 7?" is ... sorry nope. But you might find hacks via google. I wasn't very lucky when doing light research.

[GI Ged]

The game ist based on Unreal Engine 5 ->>> Requirements:
Operating System Windows 10 64-bit version 1909 revision .1350 or higher, or versions 2004 and 20H2 revision .789 or higher
Processor Quad-core Intel or AMD, 2.5 GHz or faster
Video RAM 8 GB RAM
Graphics Card DirectX 11 or 12 compatible graphics card with the latest drivers

you can make what i did; Windows 7 to Linux years ago, its free and Steam works

[КрендельФигов]

1) At the moment, on my Windows 7, when running directly (Windows 7 compatibility mode or running as administrator do not help) FactoryGameSteam-Win64-Shipping.exe
Error C0000005 occurs when loading the second DLL FactoryGameSteam-BuildSettings-Win64-Shipping.dll
(after the first loading FactoryGameSteam-Core-Win64-Shipping.dll)
That is, at the moment, the problem is in this DLL. The situation does not even reach the initialization of 3DRender (any API).
I can not get the logs, they simply do not exist, as a result, I can not understand anything either.

2) Windows 7 on Update 8 on Unreal 5 worked perfectly for hours continuously without any problems in DX11 mode.
3) I do not see any situations with problems like CreateFile2 or GetOverlappedResultEx (there are no calls to these procedures at all, it seems that the developers deliberately removed them).
4) Dxvk will not help because it does not even get to the initialization of 3DEngine.
5) I also tried deleting the directory with the settings in Appdata.

UPD In this case, only the developers can fix the possible problem (if they want); at the moment it is with FactoryGameSteam-BuildSettings-Win64-Shipping.dll
Considering everything and my understanding of this issue, so far there are no signs of this being impossible. Unreal 5 works fine on Windows 7 (because it is a reworked Unreal 4 and nothing more)