Gordy

Thanks, Don, for all your contributions to making everyone's experience here better. May you inspire others to do the same.

I now have a single pair of 2x 32 GB DDR5-6600

not better for me, maybe marginally worse, but not definitively. My fps is generally 80-90 fps in VR anyway though 13900k, 4090, 64 GB of DDR5-6600, varjo aero. A second set of DIMMs may force your motherboard to run them all at a lower speed - check that. I was really disappointed when I figured that out. Downgrading back to a single bank of 32 GB of ram improved my performance, because I was able to run them at the rated speed.

@plott1964Try the zoom in/zoom out controls (generally Rshift-numpad* and Rshift-numpad/), though those seem to be aircraft specific, so may vary. I replay VR tracks in 2d/pancake all the time, it's fine. Just don't change views, if you want to play back the head movements. Or if you want, you can take control of head movements yourself and look around with TrackIR or whatever during the replay - I'll do this sometimes if I'm playing back to record the flight, to make sure the right things are visible and the movement is smooth. The VR head movements can be too jerky.

@obious - I noticed a definite performance improvement in DCS when I increased the speed of my RAM, both on an intel 12900-KS and a 13900KS system, but I can't say for certain that it will improve your microstuttering. I'm running 32 GB DDR5 @ 6600 MHz, but if your bottleneck is elsewhere (cpu? gpu?), the faster memory may not help you. The easiest way to check is if you can tune your memory performance up and down in the bios, but that only helps you if you already have the fast memory. I think I saw a 20% boost in frames when I tuned my memory properly. I think I saw a 25% boost in frames when I moved from a 12900ks to a 13900k (same motherboard!) Try running in steamvr with fpsview and see where your bottleneck seems to be. If you seem to be cpu-bound, but you don't have cores that are 100% utilized, your memory might be holding you back. Your issue of stutters/fps drops as you pan past high detail scenery sounds similar to what I was experiencing.

Known and acknowledged ED bug, linking existing ED bug report:

echoing @phtate0830 - I can consistently reproduce this in the mi-24 border campaign (missions 2 and 3 at least), and it only affects me when running Multi-threaded and in VR in this campaign. It does not affect me when running multithreaded VR in multiplayer, instant action, etc.

Tested this in different modes, and this only affects Multithreaded/VR sessions for me: English cockpit is not honored mi-24 moving map in cockpit is broken mi-24 mirrors are broken But since these all work fine in Multithreaded/2D, Single-threaded/2D and Single-threaded/VR, it must be an ED bug, and not a problem with the mission or campaign. Weird that I don't have this issue when flying the mi-24 in other single or multiplayer environments, though.

This workaround (ask ground crew to change skins) didn't work for me - no other skins are available? I am flying in VR/multithreaded, but I fly the Mi-24 in VR/multithreaded all the time, so it's not just that.

I have some notes from the Radar mission (#2), when playing in English - There's a typo - one of the instructions to change the radio says to tune the R-862 to a certain channel, should be the R-863. I spent a long time looking for a R-862 dial. There's a message, "start descent" after I land at the hospital, which is either late, or mistranslated. The bearing given back to the base for RTB is incorrect - it seems to be the bearing to the hospital from the radar (head 163, 960 Khz). That is confusing, with respect to where you are intended to land. Which leads to... There is no information in the briefing that warns you that you will instant-fail the mission if you cross the border on the south. ...so if the player follows the given heading to look for a different base for landing, they fail the mission. I also have the Cyrillic cockpit issue, but will try the workaround from the other thread. The labels on the F10 map are also in Cyrillic when playing in English. Happy to assist with English translations if you like

@dureiken : https://github.com/mbucchia/Varjo-Foveated https://github.com/mbucchia/Varjo-Foveated/wiki

@dburneI just rolled back to Varjo Foveated from QVFR - eye tracking was inconsistent, leading to what looked like only getting the peripheral resolution half the time, though it could just be me. Everything looks sharper to me in Varjo Foveated... which is what had me digging into the eye tracking in the first place. Performance seems comparable, but that's hard to judge when I'm not sure I was getting my focus area properly. https://discord.com/channels/933220354401398785/947051902913376318/1141605552418455592 YMMV

Has anyone worked out the optimal resolution settings/multipliers? Surely there's a value that matches the native resolution of the headset, for the focus area, so there's little point in going over that, because you'd just be giving up frames for no reason. I could just do the math if I knew what fraction of the display area the focus region occupied, but I haven't seen that anywhere. Overall native resolution of the whole display (per eye) is 2880x2720, right? Right now I'm running on high, because that gives me the resolution I want for the peripheral area at x1.0, and a focus area multiplier (x1.11525) that brings it up to where it defaults at 'highest', 1200x1200. That seems pretty good, I haven't noticed any big improvements if I jack it up higher. Also, the focus area does appear to be overlaid over the peripheral area; if you dial the peripheral area resolution down enough, you can see some ghosting/smudging underneath the focus area display. I noticed it mostly in the F16's DED display, which I was staring at because I remember being able to see the individual display pixels when sitting back in the cockpit. Now I can only see them if I move my face closer to it (hence, the obsession with checking if I'm running at suboptimal resolution) Or if running at a higher multiplier has benefits from effectively supersampling, that would be good to know too

It's not really noticeable... I will occasionally notice the frame "sharpening" as I look around, or if the frame rate drops a lot for some reason. But with the significantly increased detail and framerate, no, there is no downside. I'm generally running amazing clarity and 90 fps. maybe the shade-lighter box around the focus area, if you get it and it bothers you... some people see it, some don't. But still... totally worth it

oh nice! I'll definitely look at doing that for when I don't need a mic (like in DCS) .... or I'm sure wiring the pins to a mic as well won't add a lot of complexity