All variants of the upgraded BADGER / MARSHALL IFVs/ ICVs have (as has the base version) a mirror reversed backup camera on the driver station.
The PiP is not showing the actual camera perspective of the backup camera, but a left-right reversed mirror version, making the backup camera confusing as the pictuer is the wrong way round"
use MARSHALL / BADGER (any variant)
enter driver position
reverse and look at backup camera
notice backup camera being mirrored (aka left-right reversed)
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.
This bug should be easy to resolve, without any noticeable ressource necessary.
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.
very nice, thank you - so basically, create a ticket for the "vanilla badger" in the main game tracker, no problem
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.
and as stated in this very thread, this bizarre option does neither ergonomically apply to backup cameras displayed on MFDs in random locations nor in the context of a PC game.
This niche option - while feasible for some, and some only - if a camera image happens to be displayed pip-style in a mirror or placed in "mirror location" does not qualify as being "correct", when it is completely unintuitive, unergonomic and outright confusing to the wider majority of the userbase.
Highlighting this as "correct" when it is not only a bug in genesis but also does not apply to the vast majority of backup camera pip-displays in the A3 suite in really not contributive.
The only, the ONLY suitable application would be an option toggle - somewhere. Which would we a waste of precious ressouces if seen from the potential usage rate.
So please do no "unfix" a fix for an actual bug, that also has the genesis of a typo-bug.
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.
BHI has a backlog of oversight bugs and a very bad trackrecord of debugging.
Taking a manifested bug as a normalized state for a follow-up expansion asset ist not "conistency", it is more of a copypasta oversight acceptance.
As you typed yourself - it is much more intuitive in the, well, plain normal, intended state of a "camera feed on an MFD" (which is btw.. also the realiter state of most systems mounted as far as they are in widely available frames.
From a CDLC perspective fixing the bug (that has the genesis of a bug, not an intended design state) can only help solidify the products' USP and maybe even encourage the franchise holder to do an arbitrary fix an a random bug in a pool of many (as they focus on other things).
So again, I would implore to keep the bugFIX, well FIXED.
Please, in earnest.
Do not REbug.debug
