@Frank240374
I think we’re looking at this from different perspectives. The point is that Asobo changed the behavior, not us.
If camera panning was smooth before SU4 with exactly the same hardware, add-ons, and settings, and the stuttering only appeared after SU4, then it’s Asobo’s responsibility to fix the regression - not ours to come up with workarounds.
I strongly disagree with the idea that users should lower their settings to compensate for something that previously worked perfectly. Now, to reduce the stuttering, people are told to lower settings such as Terrain LOD to 50 or make other compromises. Before Asobo introduced this regression, many of us could pan the camera smoothly with Terrain LOD at 200 without any issues. Now the experience is dramatically worse.
Of course, complex add-ons can increase the workload, but that doesn’t change the fact that the underlying behavior changed after SU4. The responsibility for fixing that lies with Asobo and I want to make this point very clear.
EDIT
I agree that this issue may never be officially bug-logged but not because the test team cannot reproduce it.
The reason, in my opinion, is that it is currently considered “by design”. Asobo intentionally took a step backwards to address the VRAM issue first and the cost of that decision was increased stuttering during camera panning.
That is why it may not be logged as a bug - because from their perspective this behavior is now expected, rather than an unintended issue.
I just hope the fixes will come sooner rather than later, because this is a noticeable regression compared to how the simulator behaved before.