I had this issue a few months ago when running DX12, so I reverted to DX11, which seemed to resolve the issue, but it’s come back and when using DX11. Not sure if it’s the same issue, but I noticed this in DX12 when moving in and out of the simulation fitting window, maybe while a session change is taking place. It’s fairly random and doesn’t happen all the time and is generally fixed by closing and reopening the client. Love an intermittent issue!
1 Like
I ran dx12 and had a lot of issues went to DX11 problems went away , and had another one creep up a few days ago
I restarted the game.
That fixed it.
TODAY I got YET ANOTHER PROBLEM, game was telling me to reinstall it completely due to GAME not being able to READ GAME FILE.
In YOUR words- “it is problem with your PC, not with our game, server or lack of developer knowledge of how our own game works”…
SO NO, I will not be sending you anything. You are always hiding behind “it is you, not me” excuse, so deal with it yourself.
I thought I was immune to this bug, as so far I hadn’t experienced it.
1 Like
DX12, 2080TI, windowed mode, graphics on full, incl. raytracing, etc, one client, no overlay, everything vanilla. first tooltips became semi-transparent with a blue circle around, then the tooltips transformed into the icon of the drone relics that I was hacking in a drone relic site. after jumping a system, that went away, but my relic analyzer transformed into an armor membrane.
1 Like
Just had it happen on a kill mail.
Did a report: EBR-57126
1 Like
It also affects the hacking minigame on relic sites (perhaps data sites too, not done one recently. I created a bug report but since I was in a wormhole at the time, I wasn’t able to take a screenshot with the in game tool, so here is the screenshot (linked bug report is ID EBR-57131):
On Sunday 2026-03-01, after warping to a fractured moon grid, I saw corrupted moon asteroid text names in the overview (screenshot below). It could be a separate thing, or it could be a different symptom of the same data corruption issue.
Ore names in other places (targets, info window, brackets) were OK.
Few minutes later I also observed the corrupted “V”→”Q” thing in the Neocom menu:
I play on Linux via Steam, DX11, RTX 3070 (550.163.01).
Issues were visible in just one of two clients I was running at that time.
Very bizarre.
I’m having none of these issues right now.
DX11 isn’t the answer. I use it and still have the issue. My gf used DX 12, and it does seem more common with it than 11. I swapped her PC to 11 and she still gets problems with it. I will try clearing our catches and see if the problems happen again…
DirectX 11, after cache reset, while running abyssals still caused the problem to arise for me. Gf hasn’t had the issue happen again (yet)…