thank you very much for fixing this, this was really problematic in using the asset

In T164087#2328485, @Lexx2k wrote:

Well, I have adapted our screen to that on the vanilla Marshall now to keep consistency. Guess if this is a controversial change, it should be discussed in the ticket for the A3 base game first (or the forum thread). That said, after playing with the new FOV for a while, I find it to be much more intuitive to use than with the mirrored image.

In T164087#2327752, @Lexx2k wrote:

I have to reverse on this one. See this thread here and my sample images. It appears the Marshall reverse camera image is actually correct, it's just a bit weird / confusing because it's not in center screen but to the left of the drivers view.

The image is also correct on the vanilla Marshall, and the only change on current dev-branch is that the FOV has been tweaked.

In T164087#2302080, @Lexx2k wrote:

Fixed in the next update. Sadly we can't fix this in the vanilla variants. It's better if you make a new ticket about it in the main game tracker.

visual reference for the bug

what makes this bug - that is only a typo oversight - more confusing is that the external mirror pips (reflections?) are correct.. making a backup when turning in even more confusing.

Thank you for the reply nonetheless!

additional note (pointing out the source issue even more):
a "steerable parachute" is also categorized as a "vehicle", responding only to the analog bindings for steering - making the confused state of the TRACKED VEHICLES not responding at all to the bindings even more noticeable.

Addendum.
BOATS also do NOT accept the granular left/right controls and only work in granularity forward/back by coindicence (keyinbind "fast forward" on throttle, "car back" and "car forward" on left stick).

that is **correct**,
I just tried, and it loaded "Drawdown 2035" or "State Scarlet" or any selected campaign or unlocked mission.
So v8 seems to have fixed that already.
But please be advized that I switched to the standard build in-between, so if there was a lingering outlier bug, it might have been cleaned up by the switch "profiling->standard->profiling", and whatever caused it, can now not be reproduced (also not logs available aso)

👍

Addendum for clarity: