Since a certain point in 2022, I now am unable to play the game continuously on my hardware once I reach the point in a game where I would build/spawn my CV. In the presence of that CV, the same one that I've used for a very long time, the game's framerate over the first five minutes of the game steadily declines from a solid 60 FPS to 10-15 FPS and then remains there. Exiting and reloading the same saved game doesn't restore the framerate; what does restore it - for another few minutes - is fully exiting the game and restarting it. This behavior is highly specific and perfectly repeatable. Even spawning a medium-sized SV cuts the framerate in half and leads to obvious sluggishness when panning the worldspace, even when not piloting the ship and just being inside or in proximity to it. This probably also goes for structures. It's all about the blocks and the significantly larger performance burden that they impose on the game since about 1.8.8. If I'm out walking in a playfield at least a few hundred meters from structures, my framerate is a perfect 60 FPS. Not even quartering my display's default 3840x1600 resolution to 1920x800 changes this sorry dynamic: even at that fuzzy resolution the presence of even my SV will reduce the framerate by half. I can't play the game when I have to fully quit every five minutes or less or endure a framerate that doesn't allow smooth movement. This seems to be directly related to the reflections and post-processing additions made to the game this year. The burden imposed by the simple existence of blocks is now more severe than at any other time. Those additions were not desired by me, and the effect of them on my ability to play the game past early stages has been catastrophic. I have used the few added Options to limit the effect as much as possible, but it seems that the mere framework itself is responsible, as I'm unable to restore the solid framerate I once enjoyed throughout the game at all stages. The pain of this post-processing is also felt when trying to work with glass blocks: retrieving or changing the transparency of them now takes a full literal agonizing second for each one, whereas early in 2022 and before it was virtually instantaneous. Given that extreme measures have been taken in the past attempting to preserve performance, was there not one person on the staff who said "this is too much" when post-processing was proposed? What am I supposed to do?
