TZeer

Is this implemented though? Last time I checked, the CAS was still giving inputs to the tailrotor while taxing. Although less then before, but I could still see the green marker applying extra input to the YAW channel unless I hold the trim reset button down while taxing.

Yes. The video that I posted was captured with AMD's capture software in the drivers, then youtube did it's thing with it. So conversions and compression kinda hides the issue a little bit. But @Floyd1212 new video where he captured his VR with his phone, really shows how bad the PNVS picture stutters when looking around. Has been like this since the Apache came out.

YES!! Finally! That is how it is when using the PNVS! To bad you didn't include the TADS, as it's smooth as silk compared to the crappy feeling we have with the PNVS. Anyway, I noticed that the video I posted earlier, the easiest way of looking at the difference in that video between PNVS and TADS, was trying to focus on the buildings/hangars in the distance. With the PNVS it impossible to focus on them, as they "blur" out. But when I changed to the TADS, you can keep focus on the buildings while I pan my view.

What is your in game settings? I have the same card, and run some high settings. And I push 70-80 frames consistently in Nevada flying the Apache. Post your DCS graphic and VR settings please.

I had Quest 2 before I changed to G2. Does the FOV trick work with Quest Pro as well? And have you tried FSR on it?

@corbu1 Try using the TADS as your source instead of the PNVS. Specially if you fly VR. There is currently an issue with the PNVS. You get picture and everything, but it "jumps"/"stutters" very bad when looking around. Put alot of strain on your eyes. Changing source to TADS will give you much smoother visual. Although the CPG will loose his ability to use the TADS for scanning and finding targets while you are using it. Also if you move you head quickly, it might not keep up, as it slews slower than the PNVS.

When you say it "seems to be stuck", is it stuck, or does it fluctuate? If you have 45 FPS in game, but 90 FPS while in menus. You most likely have MR on, but not locked. Check the OpenXR settings while on Windows, it's the purple OpenXR icon. See if it's activated. If it is, deactivate. Then go into game, and hit ctrl + F2 to get up the OpenXR toolkit window.

I know. But when you have one patch 2.7 --> 2.8 creating this kinda behaviour, something is off. I would put it in context of the issues many are seeing with loss of FPS and higher loading times with 2.8 vs 2.7 I have not yet updated to 2.8 due to all issues with performance, so I don't have first hand experience with it. But if he is going from 60-70 degrees up to 90 degrees on the GPU.. there is indiaction that the bottleneck was previously on his CPU, and going to 2.8 has moved it over to his GPU, or at the very least taxing his GPU significantly higher than before. People loosing 10-15% performance, going from 120 FPS to roughly 105-110 FPS, wont notice. But VR and 4K users running 50-60 FPS will notice theese drops very easily. Then again, "smooth frames" is a personal taste. There are people running 30-50 frames claiming it to be smooth

It's not good if it's hotter and more used without getting more performance.

@speed-of-heat or @Hammer1-1 How did you install the 2k mod for the Apache? I downloaded it, but the instructions was not working for me. I found the Saved games folder, but had no Liveries folder, so I made one and dropped it inside there, but no joy. I also renamed the default cockpit folder. Just ended up with no cockpit at all. Just internal of the helicopter.

@Tepnox I saw a video somewhere that one thing people did "wrongly" going to the Quest pro was tightening to much. But I don't know if your pressure is due to weight or tight fit. I see on the reviews an feedback that people are very split when it comes to comfort with the headset. Either they love it or hate it.

AMD just came with the prices: RX 7900 XTX for $999 RX 7900 XT for $899

I have a G2 running on an AMD 6900XT. I'm also running my G2 on 60Hz right now. Yes it has a very distinct "flicker" on bright scenes. But currently flying right around when it gets dark or during night. But it's also so so smooth now. No need for MR and I have enough overhead to consistently run 60 FPS. As long as one is looking straight aheaad, it's hard to notice. But start looking around and off to the sides it gets quite horrible, really quick.

Looking around for some feedback from early adopters, and found this. So G2 clarity across the whole display, bigger FOV, black comparable to Vive Pro V2 without glare and godrays.

The interesting part was the comments about resolution. As he said, on paper, it didn't seem impressive, as it looks like it is roughly the same as the Quest 2. But since you had 2 seperate displays, versus 1 in Quest 2, and no area of the displays got "wasted" and individually adjusted it gave you a 37% higher PPD then the Quest 2. This will put it higher then the Reverb G2. Combine it with "the best lenses" he has ever seen, good quality displays and edge to edge clarity... Makes it an interesting option when I'm due for an upgrade. But would want to see some more reviews and feedback. Came to think of one more thing. If you can get good clarity with optimising the optics, and not constantly pusing the pixels, it will be easier to run for the hardware...

Here is a quick video of me changing between the PNVS and TADS. Pay close attention to the straigth lines in the pavement infront of the Apache. I'm starting out with PNVS activated, before changing to TADS. One can clearly see the difference in how smooth the picture is when using the TADS. But to be honest, the video does not do it justice. It's much more noticable when you have the picture right on to your face in VR.

Had a test on 2.7 today and the stutter is very visible when on the PNVS. When using the TADS it's smooth, but moves a little slower, as normal. I will check on 2.8 after I have updated, but will wait until the performance issue is sorted regarding VR. I'll see if I can find some way of capturing the issue with a video.

Been away fro a while due to work, and I noticed a significant improvement in FM, I'm still on the latest 2.7. Like to see the VR performance issue getting fixed before I jump over. But from what I have noticed. - It seems a bit more stable - Easier to decelarate without dropping all lift Looking forward to test any changes done in 2.8.

@Ganesh What is your ingame settings in the toolkit for OXR?

Just a heads up. Was playing around with the different settings in the toolkit, changing the FPS lock. 22,5, 30, 45, unlocked etc. I had problems keeping stable 30 FPS, it was always dipping below, or some sort of stutter. But at the same time I could go up to the next level, 45 and lock it there, and then getting dips again below. This is the interesting part. After looking at a video on youtube (posted below), I had a look at the simulation numbers he mentioned. And I saw this would go up and down relative to my FPS lock. I guess this woud be normal as you are restricting the FPS output. But, when I took away the locked mode, and set it to "unlocked", the stutter was reduced and I was locked in on 45 FPS. Not very noticable looking straight ahead, but looking to the sides inside the Apache, it was greatly improved. I don't know why it did this, but locking the reprojection rate at 30 or45, always gave me 2-3 frames short. So pulling up the FPS counter in both the toolkit and ingame, showed 27 more often then 30, and 43 more often then 45..... Running a AMD 5800X with a OC 6900XT.

Why not do some testing in an area where CPU bottlenecks are the smallest? - Either go to the an isolated spot on the Caucasus map, where there are no objects or other parts that will load up the CPU. - Or go to Nevada, in a spot where there are close to nothing going on. This way you will be able to compare how much an uplift the card itself will give.

Gonna wait and see what AMD actually pulls out of their hat.

The correct thing to do is getting into a stable hover and trim, before activating any of the hold modes. If you dont, you might end up with a system that has very little left before it gets saturated. The hold modes is not to get you into a stable hover, it's there to help you stay there. Thats how I "understand" the system. I might be wrong, as I'm not a real pilot

@skypickle Do you actually have a target locked up there? Or is it only the LOS line that is pointing in that direction? If George don't have a target he will be looking straight ahead. And I think (from memory) if you pop over a hill, or the nose of the helicopter points in upward direction, the LOS will move out, until it hits a surface. You can see this behavior close up as well if you start tossing the apache around without a target locked. The LOS line will move over the terrain relative to where the copper is pointing it's nose.