[6.0] Black screen after changing graphics settings - Fix in HF2.
Moderator: Moderators for English X Forum
-
- Moderator (English)
- Posts: 30429
- Joined: Fri, 16. Apr 04, 19:21
Re: [5.10 HF3] Black screen after changing graphics settings
I have a Samsung SSD 970 EVO Plus 1TB as my OS/drivers/boot drive and a Samsung SSD 870 QVO 1TB as my applications drive where Steam is. X4 is absolutely fine. I suspect therefore that the issue is perhaps with the newer Samsung 990 Pro SSDs and their set-ups, options and drivers.
Please check that these newer SSDs do not have any encryption, compression or extra caching set by default, whether built in or as an additional Samsung application option.
Please check that these newer SSDs do not have any encryption, compression or extra caching set by default, whether built in or as an additional Samsung application option.
A dog has a master; a cat has domestic staff.
Re: [5.10 HF3] Black screen after changing graphics settings
yes, I think so. My previous system had 980 and 970 evo and I had no issues.Alan Phipps wrote: ↑Fri, 20. Jan 23, 19:54I have a Samsung SSD 970 EVO Plus 1TB as my OS/drivers/boot drive and a Samsung SSD 870 QVO 1TB as my applications drive where Steam is. X4 is absolutely fine. I suspect therefore that the issue is perhaps with the newer Samsung 990 Pro SSDs and their set-ups, options and drivers.
Re: [5.10 HF3] Black screen after changing graphics settings
how do I check if those are off or on?Alan Phipps wrote: ↑Fri, 20. Jan 23, 19:54Please check that these newer SSDs do not have any encryption, compression or extra caching set by default, whether built in or as an additional Samsung application option.
-
- Moderator (English)
- Posts: 30429
- Joined: Fri, 16. Apr 04, 19:21
Re: [5.10 HF3] Black screen after changing graphics settings
I would guess to look in the supplied Samsung SSD supporting literature, support software, in Samsung applications, or by online research.
A dog has a master; a cat has domestic staff.
Re: [5.10 HF3] Black screen after changing graphics settings
Haven't found any info. Tried disabling W11 encryption and compression - but no change it takes 3-4 launches to bypass the black screen and be able to playAlan Phipps wrote: ↑Fri, 20. Jan 23, 20:03I would guess to look in the supplied Samsung SSD supporting literature, support software, in Samsung applications, or by online research.
-
- Moderator (English)
- Posts: 30429
- Joined: Fri, 16. Apr 04, 19:21
Re: [5.10 HF3] Black screen after changing graphics settings
At a further guess, all the Samsung support apps, and possibly any support information, would be in the folder where the Samsung Magician app that you uninstalled would have been.
I'm pretty sure the culprit will be a Samsung app or setting and not so much a W11 one.
On the off chance, see if it's mentioned at all in the ASUS support areas, or possibly look under devices and settings in ASUS's Armoury Crate if you have that app installed.
I'm pretty sure the culprit will be a Samsung app or setting and not so much a W11 one.
On the off chance, see if it's mentioned at all in the ASUS support areas, or possibly look under devices and settings in ASUS's Armoury Crate if you have that app installed.
A dog has a master; a cat has domestic staff.
-
- Moderator (English)
- Posts: 4764
- Joined: Fri, 21. Dec 18, 18:23
Re: [5.10 HF3] Black screen after changing graphics settings
Please try the 6.00 beta to confirm this was not fixed by the massive engine changes.
Re: [5.10 HF3] Black screen after changing graphics settings
Tried it. Its a bit worse because with 5.1 90% of the time I can get into main menu on first attempt, while in 6.0 it takes several attempts.Imperial Good wrote: ↑Sat, 21. Jan 23, 03:32Please try the 6.00 beta to confirm this was not fixed by the massive engine changes.
(example for 6.0 beta: I launch the game see the first logo - then it freezes, I lat tab and end process. Then on the next launch I get to the intro and it freezes after the intro - I alt tab again, end process. Then on third attempt it usually reaches main menu.)
And both builds act the same if I try to change graphics settings.
-
- Moderator (English)
- Posts: 4764
- Joined: Fri, 21. Dec 18, 18:23
Re: [5.10 HF3] Black screen after changing graphics settings
Freezes might be due to some obscure race condition that only can occurs on extremely fast SSDs with very highly parallel processors.
I wonder if reducing CPU core count could make a difference. Another approach would be to run a CPU stress test while X4 loads which would simulate a much slower CPU.
X4 uses non-cached IO to read data files. This is very different from most other games that use cached IO. It could be a bug with the Samsung NVMe drivers and those drives when it comes to what non-cached reads are permitted.
I wonder if reducing CPU core count could make a difference. Another approach would be to run a CPU stress test while X4 loads which would simulate a much slower CPU.
X4 uses non-cached IO to read data files. This is very different from most other games that use cached IO. It could be a bug with the Samsung NVMe drivers and those drives when it comes to what non-cached reads are permitted.
Re: [5.10 HF3] Black screen after changing graphics settings
Hey,Mr.Freud wrote: ↑Sat, 21. Jan 23, 03:57Tried it. Its a bit worse because with 5.1 90% of the time I can get into main menu on first attempt, while in 6.0 it takes several attempts.Imperial Good wrote: ↑Sat, 21. Jan 23, 03:32Please try the 6.00 beta to confirm this was not fixed by the massive engine changes.
(example for 6.0 beta: I launch the game see the first logo - then it freezes, I lat tab and end process. Then on the next launch I get to the intro and it freezes after the intro - I alt tab again, end process. Then on third attempt it usually reaches main menu.)
And both builds act the same if I try to change graphics settings.
I interfere here once again.
Sorry, I know I'm repeating myself but yes I can confirm that as well
6.00 Beta is significantly worse than stable.
Stable: Most of the time the game loads normally, but the big problem is the graphics settings. Sometimes the game start takes a few seconds longer with black screen at start.
But this is rather the exception.
6.00: The start often takes several minutes or ends in nothing.
So exactly as you have also described.
The problem with the graphics settings is unchanged in 6.00.
47 75 74 65 6e 20 50 72 6f 66 69 74
Re: [5.10 HF3] Black screen after changing graphics settings
tried disabling E-cores, Hyperthreading - no luck.Imperial Good wrote: ↑Sat, 21. Jan 23, 04:43Freezes might be due to some obscure race condition that only can occurs on extremely fast SSDs with very highly parallel processors.
I wonder if reducing CPU core count could make a difference. Another approach would be to run a CPU stress test while X4 loads which would simulate a much slower CPU.
X4 uses non-cached IO to read data files. This is very different from most other games that use cached IO. It could be a bug with the Samsung NVMe drivers and those drives when it comes to what non-cached reads are permitted.
-
- Posts: 4
- Joined: Fri, 6. Feb 04, 13:00
Re: [5.10 HF3] Black screen after changing graphics settings
I had the same issue on my PC.
After moving the X4 game folder from the Samsung 990 PRO to a WD HDD the issue was resolved.
After moving the X4 game folder from the Samsung 990 PRO to a WD HDD the issue was resolved.
-
- Posts: 1
- Joined: Thu, 13. Apr 23, 13:43
Re: [5.10 HF3] Black screen after changing graphics settings
Same exact issue using the 2TB Samsung 990 Pro.
Made a steam post here https://steamcommunity.com/app/392160/d ... 317789208/ with a link to this forum as well.
Troubleshooting:
- Ran all updates for Windows
- Updated graphic card driver to 531.41
- Disabled steam overlay
- Checked Vulkan install via vulkaninfo console command
- Verified game files
- Disabled AV (MS Defender)
- File compression is disabled
- No other screen overlay is enabled
- Deleted the Egosoft folder from Documents folder
- Rebooted the PC several times
Specs:
- Windows 11 Pro 64-bit
- Intel i9-13900KS
- Gigabyte Z790 Aorus Master
- 32GB Corsair DDR5-7200
- 2TB Samsung 990 Pro NVMe
- NVIDIA GeForce RTX 4090 24GB
Looking at the disk usage while on the black screen shows it consistently maxing out the read speed. Drive encryption is off and the firmware is the latest version. This is the only game it happens with.
Made a steam post here https://steamcommunity.com/app/392160/d ... 317789208/ with a link to this forum as well.
Troubleshooting:
- Ran all updates for Windows
- Updated graphic card driver to 531.41
- Disabled steam overlay
- Checked Vulkan install via vulkaninfo console command
- Verified game files
- Disabled AV (MS Defender)
- File compression is disabled
- No other screen overlay is enabled
- Deleted the Egosoft folder from Documents folder
- Rebooted the PC several times
Specs:
- Windows 11 Pro 64-bit
- Intel i9-13900KS
- Gigabyte Z790 Aorus Master
- 32GB Corsair DDR5-7200
- 2TB Samsung 990 Pro NVMe
- NVIDIA GeForce RTX 4090 24GB
Looking at the disk usage while on the black screen shows it consistently maxing out the read speed. Drive encryption is off and the firmware is the latest version. This is the only game it happens with.
Re: [5.10 HF3] Black screen after changing graphics settings
Bought the Boron DLC, now I can\t start the game at all. In beta at least it would start every few launches.
Can Devs look into it? No other game/app has such problems with the nvme.
Can Devs look into it? No other game/app has such problems with the nvme.
Re: [5.10 HF3] Black screen after changing graphics settings
As already stated, we're aware of the issue and are investigating. In the meantime, the workaround is to install the game on a different drive.
Re: [6.0] Black screen after changing graphics settings
Hello everyone
I'm facing same issues. Also with 2TB Samsung 990 Pro NVMe.
Please push topic
Cant play my favorite game anymore
I'm facing same issues. Also with 2TB Samsung 990 Pro NVMe.
Please push topic
Cant play my favorite game anymore
Re: [6.0] Black screen after changing graphics settings
We've just released a hotfix which should hopeful solve this.