Please consider this: a real GNS 530 Screen is 320x234 pixels. If the GNS 530 Screen is covering about 1/10 of the FOV width when looking at the panel, this means you need 3200 pixels wide to represent each individual GNS screen pixels properly (actually you need at least 1.5 times more).
In other words, it takes at least a Reverb G2 panel to be able reading the EFIS screens from the pilot seat position. Any lower panel resolution will invariably lead to fuzzy EFIS screens.
With analogue gauges it is different for two reasons at least:
Gauge lettering is usually bigger and needles are wider than their virtual representations on an EFIS screen.
FS2020 is rendering analogue gauges at the displayed resolution (Post-Process res in the fps window) whereas it is rendering EFIS screens at the rendering resolution (Render Scale res.)*
*actually it is rendering everything at the rendering resolution but enlarging pixels representing 3D features (buttons, knobs, needles) is less prone to aliasing than pixels representing dots on an EFIS screen.
Right well with a Vive I canât even read the buttons or anything smaller than the aircraft registration, even with VR Focus zoomed in, and physically leaning in even farther, so, there must be a better solution than this.
My only suggestion would be to look for some magnifier overlay⊠OVR toolkit might have a way for you to toggle the windows magnifier overlay, which might make it possible to zoom in on the desktop view in such a way that if you supersample and make the desktop 4k, you can get better visibility. Once itâs set up you could be able to say âzoomâ and have voice attack toggle the zoom. Yes, this is ridiculous but the truth is the headset screen just doesnât allow for what you want
Edit: this is 100% possible, itâs not a âmaybeâ
