Have you actually checked your graphics settings & made sure they haven't changed. Remember that programs such as Nvidia's GeForce Experience can & will "optimise" games on update.running with steam on win10, after the last update to the game with no changes to settings, the graphics for the ships and planets look like they are half made of static. is there a way to fix or we waiting for the next bug fix?
no changes, before the update it ran smooth on Ultra in game. everything is the same settingsHave you actually checked your graphics settings & made sure they haven't changed. Remember that programs such as Nvidia's GeForce Experience can & will "optimise" games on update.
approaching planets is where i see most of the graphics issues. its like it cant decide how to visualize the planet, its static mixed with smooth patches around the surface.The only new graphics issue I've seen so far is occasional micro stutters and hitching when loading/swapping mipmap/LoD textures (e.g. approaching a planet or station) which was smooth and pretty much unnoticeable prior to the last update.
pretty sure the cache gets deleted everytime i close the game, only because when I start it the 1st load screen shows the shaders and terrain being loaded. sometimes it only takes a moment and other times it takes about a minute for each. ill delete it though and see what it doesScreenshots might help identify the issue.
In the meantime, try clearing the game, driver, and OS shader caches:
- If you have an NVIDIA GPU navigate to "%LocalAppData%\NVIDIA\DXCache" and delete the contents of that folder. Some files will be in use by Windows, but you can just skip those; as long as the game isn't running the game's files will be able to be deleted.
- Find the game's main product directory, i.e whichever folders have EliteDangerous64.exe in them, and delete the GPUWorkTable.xml files you find.
- Run Windows' Disk Cleanup and make sure the "DirectX Shader Cache" box is checked before having it clean files.
Once that's all done, restart the game and let it rewarm shaders and rebuild the terrain timing tables, then check to see if you experience the same issue.