Following the patch on 26 February we’ve seen an increase in icons being erroneously swapped throughout the game. This can be in the item hangar, fitting screen, on the HUD, etc. Our engineers are actively looking into this issue and would appreciate any additional information that you can provide for those who have experienced this. This includes information like:
Any reproduction steps
Number of clients you have running
How you are swapping between them (alt tab, EVE-O preview, other)
Hardware you’re running
Specifically this seems to be affecting NVidia cards, so any other data points would be very helpful to know.
Any third party overlays that may be running, such as Discord, GeForce Now, OBS, etc
And lastly: screenshots / recordings of it happening - ideally when it triggers.
Bug reports can be submitted in-game by hitting F12 and selecting “report a bug”, and while that’s the preferred way any data you’d like to share in this thread will able be processed as well.
As we get closer to a resolution we’ll update this thread with any information.
Thanks for helping us better understand this issue, and fly safe!
Thank you for the update on that issue.
From what I know and heard from others, this only seems to happen when running the client in dx12. If you use dx11 everything seems fine, at least for me.
I had to submit a big report today as well… character sheet opens at every session change. Jumping, docking, undocking, logging in…. the character sheet opens. Cleared cache files… no change.
Any reproduction steps
I’ve dragged a R.A.M. item from my ship cargo to an assembled container inside an NPC station. Many icons now have a R.A.M. icon on top of their own.
Number of clients you have running
One.
Hardware you’re running
Nvidia 3080, 12GB, driver 591.86. The settings are stock, Nvidia default.
Any third party overlays that may be running, such as Discord, GeForce Now, OBS, etc
Nvidia overlay running in background, not shown on screen.
Discord running, but overlay turned off.
And lastly: screenshots / recordings of it happening - ideally when it triggers.
Edit: Closing the client and opening it again fixed the issue. I’ve started LogLite and tried to reproduce it, but without luck. I’ll keep LogLite running for a while and see if I can catch it.