A thing I noticed already in my first longer flight in MSFS and then again today:
The cockpit and world scale looked just right to me in the G2. But with the Aero, the world (houses, cars…) looks too small to look right 
When I move the world scale slider in MSFS to 120%, the world looked OKish but the cockpit seemed too large.
Anyone seeing the same issue when coming from the G2 to the Aero?
Any ideas what-to-how-to?
I have not checked yet in DCS or Il-2.
How is your IPD set up? Do you have it set to scan every time or on pre-set?
Scanning each time at first and then I switched to pre-set.
Edit: IPD setting moves the lenses, not the displays, doesn’t it?
Yes, just the lenses. If the IPD is off, the scale will look wrong.
I haven’t used my VR play computer in quite a while, so I don’t remember the setup and how this can be adjusted. I know DCS has its own IPD adjustment, that basically alters the scale of the environment.
I understand that if the distance of the two viewpoints in the sim is set differently to my RL IPD, then the world scale would look different.
I need to check also the other sims. It is weird.
Yes, the ‘tech stack’ for all this is getting deep…nature of the beast? 
My understanding, now, is that the Aero has DFR built in for games that support it. DCS either does not or does not support the kind of DFR (Quad-View DFR) that the mbucchia tool does.
I dipped my toes into the docs mbucchia recommends we read along with some bits about QVFR and from what I could tell while skimming it all: QVFR is ‘better’ but, it seems, it’ll make your CPU work harder?
I did see an improvement, so far, in clarity and performance. Note I’ve not had time to run the patch that dropped today.
Yeah, we keep on adding layer after layer of complexity.
That’s how I understand it as well. DCS supports the quad view of the professional Varjos, that has a display in the center of each display. This means DCS puts out 4 video feeds, but we need mbucchias tool to use all 4 feeds in the Aero and differentiate the resolution in them.
I’m hip.
I haven’t turned on ‘turbo’ mode with the mbucchia tool, or reinstalled OXRTK to use its version of turbo mode (you must chose one or the other, not both) but I was getting a clearer image and better performance (performance about what I had in 2.8 after a LOT of tweaking) as is. When I get time I’ll try the turbo thing again - but I swear I saw that it was On in the mbucicha config already? Then a YT said is wasn’t supported == me confused. Maybe this evening I’ll have time.
I have noticed a strange thing when using the Aero with IL-2.
Varjo software locks IL-2 files so it’s not possible to edit keymapping while ingame in VR.
DCS has not this problem, so it is something the Base software does with IL-2 files.
Anyone else noticed this behaviour?
Yes, I’ve noticed this.
I can’t map joystick bindings, for instance…
Works in 2D, but not in VR.
I haven’t tried it myself, but I read a post on the IL-2 forum that switching the Aero to another Display port fixes the issue…
How strange is that a move to another DP should solve locking files.
Well I will try and see what happens.
Here’s another thread on the subject
And here is the first thread. I see that switching ports doesn’t help everybody.
Strange bug, indeed.
I hve this issue, switching the port didn’t work for me. I just make the change in 2D.
Unfortunately mapping in 2D won’t work for me since I don’t have a monitor in front of me in the sim-rig. All VR for me
Did you try the advice in the thread above?
Run as admin and unlock the data folder?
Yes, no joy.
But the suggestion You linked me to worked, moving around the display ports solved the problem for now anyways. Very odd that what DP in use would cause this anomaly. And only in IL-2 
I can map the controls in VR again. Lets se what strange things pop up next
Heads up with Nvidia driver issue. A friend got this from Varjo support:
“Thank you for confirming that, I noticed from your logs you are running a 4090 GPU.
Our developers have found a bug in the latest NVIDIA driver family that affects Varjo users that have RTX 40-series GPU (mainly we have gotten reports from people using 4090).
The bug can present itself in various ways, most often with different types of connection issues.
The issue should be gone if you downgrade driver to 532.03 or before.
You can confirm if this is the case with you too by testing out that driver.
Please let us know if this resolves your issue.
Best Regards, Laurice Varjo Support”
Thanks for the info!
Oh the wonderful world of computers… 
staring at my 17" laptop screen …
I know it’s not a laptop, but it’s a cool gif.
And it shows that 2D can have depth too…