luciusDXL
First frame of firing weapon after load game.
I was actually investigating something related, but there is this behavior on my reference system that complicates it.
To verify good vsync and framerate I had this test case with firing weapon at key 6, with the four barrels and green plasma. Bad Vsync/framerate often prevents the first frame of firing from being visible. The plasma becomes visible only further from the barrel and higher up the screen. This weapon 6 is the most obvious example of that.
But now I noticed that when I start a new mission there is no issue with that, But when I load a saved game the issue is always visible. Start a new game again: no issue.
Can anyone replicate?
Verified to behave as described on the following systems:
Laptop intel i5-8250U with windows 10 x64, integrated intel graphics Laptop intel i3-2310M with windows 7 x64, integrated intel graphics Desktop intel i5-3550 with windows 7 x64, nVidia Geforce GT 710 Desktop intel i5-3550 with windows 7 x64, Radeon HD 7750
With official Windows x64 binary v1.09.521. Changing rendering settings has no effect on the issue.
Edit: So this weapon 6 is actually called "Jeron Fusion Cutter"
How far away is far away? When continuously alt-firing weapon 6, the distance of the first rendered frame to the weapon sprite seems to "cycle" between 3 positions (closest, next, next-next). it's not noticeably far away.
Basically, the barrel of the Fusion Cutter weapon (No6) should initially overlap/intersect the fired round/plasma bolt. When you start a new game it does that. See attached screenshot. When you load a game it never does that. There is always a gap of background visible in between. The composition of the screenshot is skipped.
Sorry for going through this so late.
It is interesting that there is a difference between a new game and loading a saved game. It sounds like some state is not being captured properly. So I will look into it as a bug and take a look in the near future.
Sorry for going through this so late.
It is interesting that there is a difference between a new game and loading a saved game. It sounds like some state is not being captured properly. So I will look into it as a bug and take a look in the near future.
Take your time. Since posting this issue, I haven't got any new insights to report.