TZeer

My bad, for some reason my binding on the stick for AI Helper Short Left, had added +Alt in my keycombo. So nothing actually happened when I pressed it. No wonder he never changed weapons

No. I just moved from a G2 to a Quest Pro, and can tell you that you are 100% wrong in your assumption.

Been out of the Apache for a while and was met with a slightly different menu and mechanics. Now when I pull up the George-menu, there are no weapons to choose from. All I can tell him to do is search for targets and lase them. I have to pull the trigger on the hellfire even. Before I gave him consent to fire hellfire. Now he can't even change the amont of rockets to ripple. At least I don't have an option for it. Could someone point me to the latest mechanics on how George works and operates? Regards

So instead of having a good spot in the middle, everything looks like <profanity>? I don't think thats a good way to "simulate" the Quest Pro performance

@YoYo using link cable.

So.... just got my Quest Pro and had a quick test in DCS.... And it's definitly an upgrade from my G2. Have not done much tuning except from setting it to 1,5x resolution in the app. Can probably push it further, but will test with msaa as well. Reprojection is much better then I had on my G2. No wobbly text/artifacts on the Apache MPD's. Have not tested just running 45 FPS without ASW yet. Colours are nicer, and I actually noticed the bright reflections from the CPG's radioscreen when the sun hit it. Never had that with my G2. Comfort is better, feel more relaxed using it. No need to stare down in the mpd's just to get the sweetspot right so you can actually read stuff there, now I can just have a quick glance with my eyes . Will test more later today with some nightflying, to test how the blacklevels are in this headset. Overall happy with the upgrade.

Yeah, I was testing to see if there was any interest in it. Apparently it was and I got a decent price for it. So sold it when I got the chance. Heard so much positive feedback on the Quest Pro, and it's a used one for sale less then an hour away from me. So picking it up tomorrow. Was not my plan when I woke up yesterday

So, I put my G2 up for sale for fun last night. Within an hour it was sold Heading out tomorrow to grab a lightly used Quest Pro. So, anything I should be aware of? People using OpenXR with the Quest Pro as well? How should I go about to get myself a hasslefree setup as possible? Regards

Even if you have edge-to-edge clarity, your eyes can't focus on the entire panel et the same time. So in short you are wasting resources pushing pixels where your eyes are not focusing. You are not degrading any visuals. You are simply focusing on the highest possible detail where your eyes are looking, while the rest of the picture where you are not focusing is rendered in a slightly lower resolution. Correctly set up, you should not see much difference. But the hardware would have a much easier task. You would still have edge-to-edge clarity, as the focuspoint would move where your eyes would look. It's one of the reason some people on the Varjo Aero are able to puch 90 FPS in certain scenarios with a 4090.

@nikoel Thank you for your reply. I have as you, been lucky to enjoy DCS on the G2 with 60Hz without much issues. I also had the FPS tuned to 45 FPS with G2 @ 90 Hz a while back by locking the framerate. It was very good, but after an update something happend and the smoothnes went away. No matter how much I tweaked and tuned I was not able to get the enjoyable smooth framerates to come back. After that I have been running @ 60 Hz. Do you find the Quest Pro easier to run compared to G2? A little bit of ghosting looking to the sides should not bother me much. But any sort of "stutter" or "jumping" frames looking to the sides is what annoys me. But from what I understand the headset would give me what I'm looking for, and still have more room for improvement when better cards come out. Would I be correct in my assumptions then? Regards

How is the performance with the Quest Pro with AMD cards in the 6000 series and 7000 series? I have a RX 6900XT running with a G2 right now. But before that I had a RTX 2080 together with Quest 2, wich worked pretty good. I then upgraded to the RX 6900XT, and the performance together with thew AMD card was <profanity>. Pure frames it was okish, but it was artifacts, stuttering and overall less "smoothness" with the AMD+Quest 2 combo. ASW was noticably worse with the AMD card compared to the Nvidia. Has this been improved? I saw you @nikoel are running the combo. Have you experienced any problems? There is a used Quest pro for sale nearby me for less then 1000$. And I'm very interested in picking it up if AMD work better with the Quest Pro then it did with the Quest 2.

Not home atm, but is the "wobbly" artifacts in the MPD`S of the apache gone now with MR activated?

Could this be part of why it feels different? This was fixed in the same patch as MT was introduced.

I noticed the same thing on my right eye after updating. Intense blinking/stutter. AMD RX 6900XT and a reverb G2.

Everything loaded fine, but have a terrible "blinking" that comes on my right eye when I move around. Reverb G2 and AMD 6900XT.

Thank you for the feedback. I don't think the triangles are the problem here. I would put my money on the number of objects. I did a test a few years ago with 3d models in DCS that I found was less optimized. I could find 3d models consisting of 40-150 objects. That was scattered around. In certain areas there was a high amount of these objects, which caused massive FPS drops when you came into those areas. Construction cranes, containers, small sailboats, and some parts of the cargo trains. Some did not have a "very" high amount of objects, but when there where large amount of small sailboats or containers, it caused the number of objects to double in certain areas. Renaming these objects, causing them to not render in-game, doubled my FPS. As the number of objects would go from close to 2000 and down to 700ish. I remember one model alone added 300+ objects into the world when shadows was activated as well.... With CPU's getting better and better, I guess this issue was less of a problem. But getting close to 4000 objects I guess we are close to the limit again of what the CPU can handle without having problems. The funny thing with the test back then, was that the quality of the model had nothing to do with number of objects. I found newer optimized objects only consisting of 2-3 objects, while older models had close to 20... Newer models had less objects but more triangles. I also placed x number of units in a deserted area on the map and compared the FPS between them. "High object" 3d models gave crap performance, while newer "low object" 3d models gave superior performance. I'm not home right now, but I will test this next week when I'm home again.

What is causing the object count to skyrocket? Is it the shadows? I think this is the main problem here. Object count has always been a big issue with DCS as it's heavily CPU bound.

@lefuneste01 I'm not sure if it's still valid, as it's such a long time ago. But I will have a look when I get back from work ( next week).

It's not the triangles that affect the performance the most. It's objects. I don't know if many remember the performance issues we had way back, in the area around Novorossisjsk area? Anyway, at that time I did alot of research to find what was hogging performance in that specific area. It turned out to be certain 3d models of containers and construction cranes populating the port. As soon as the you got the port in view the object count shot up from 700+ objects to well over 2000 objects. This was taxing the CPU and and it was not able to feed the GPU with instructions. So you had what seemed like a completely normal scene bringing the FPS to it's knees while the GPU was not even close to running 100%, due to CPU bottleneck. Deleting/renaming those edm models doubled the FPS, with no loss in visual fidelity, except some random cranes and containers no longer populating the area. It would be interesting to see if some of those badly optimized models are still with us today. Well, this was a little of topic. But triangle count of 3 mil is nothing....

I work as an automation technician. Oscillation makes me think the settings are not quite there yet when it comes to the values for the PID-controller. The behavior (increasing oscillation) is typical to see in any automatic regulation where the P function of the PID-regulator is adjusted incorrectly. If the total amplification value in the loop is higher then 1 oscillation will increase, lower then 1 will decrease oscillation. P-function in a controller is the way to adjust this. There are techniques to calculate the "correct" P-values, or at least an optimal setting to start tuning from. Ziegler Nichols first and second method. One of them is based on step response, the other is looking at when the loop is going into a self sustained oscillation.

@baylor703 I saw a tip somewhere about going with PCI-E 3 instead of 4 in BIOS. Some have had success with that.

I just use the command where I tell him to fire, and assign it to the same trigger as I use for firing weapons, but with a modifier. This way I use George to find and lase a target. Hold the modifier button and press trigger. This way he will only fire 1 missile. And if I tell him to lock a new target, he will not fire anything until I tell him to engage again.

He could try and change his max_fps setting in the config.lua file, then turn off the max FPS in Nvidia. I had issue with my RX6900 XT being underutilized, and very low FPS combined with low GPU usage. Changing the max_fps in the config.lua to 300 or so, boosted my FPS from 50-60 to well above 200 inside certain cockpits and outside view. For some reason the default max_fps in DCS messes with the FPS output from high end GPU's. What I found out, the more overhead the GPU had, the more it held back the FPS. Huey gave me the worst frames, while the Apache gave me the best. Until I did F2 view, then the FPS dipped the same way it did on the Huey.

You could also try and disable windows search indexing.

Maybe we are talking past each other Your video and Floyd's video basically shows the same thing. But I feel Floyds video makes the issue pop out a little more. The later videos are also a response to you and @BIGNEWY question if the issue is still there. From the replies I think we can conclude that the issue is still present. PNVS = It "stutters" as in the video. TADS= Smooth and nice, no stutter. I'm not home atm, but I will gladly provide you with any logs, tracks or videos you need to hunt down this bug. Regards