TZeer

@edmuss When you say "bubbly artifacts" in the MFD, are you referring to the apache? I have one artifact that kinda grinds me the most, and it's the one in the middle of the MFD on the engine page of the apache. If I switch to TSD or any other page the artifacts goes away or greatly reduced. And it's mostly noticeable if I pan my view side to side. The green columns "wiggles" or whatever you wanna call it. There are so many abbreviations floting around now I'm getting dizzy. And for only having had the G2 set for roughly a week, It get's kinda overwhelming SVR, OXR, WMR4SVR, WMRP. Toolkit for OXR x 2, developer settings for SVR etc. On top oft his again we have different versions of the actual Mixed Reality Portal, one from Steam and one from Microsoft Store.

OpenXR are already at 100%. Was unaware I had visibility range at ultra . AF never had much impact on performance when running via SteamVR, never did the resolution. But will test it out. Thanks!

So tested the OpenXR last night with the settings in the screenshot on a G2, 6900XT, 5800X, 32 GB RAM. 1. Test: Apache in Nevada on Groom lake airfield. No MR. 60-70 FPS. Better image quality than SteamVR. No doubt. Also better "flow" of the image than SteamVR. But still to much stutter for my personal taste. I'm very sensitive for stutter/lag etc. So other would maybe felt it was awesome. 2. Test: Same scene, but with MR activated. Smooth as silk @ 45 FPS. But I had that with SteamVR as well, but much better picture quality with less shimmering with OpenXR. 3. Test: Syria out in the countryside with the Apache. 30 FPS, MR on. But with some stuttering here and there. Not sure what causes it. Maybe reduce my preload radius or something. 4. Test: Caucasus, Apache and A-10C II, both giving me 30 FPS with MR on. A little surprised here that it was not able to give me 45 FPS with MR on. But if I would have noticed 45 vs 30? Doubt it. So far very happy with the results. If there is anything I want to kick on, it would have to be the quality of the MR. It has to get better. There are 3 places it sticks out ot me, where I had no problem in Steam VR. - Lower part of the IHADSS when you looking out left or right. Specially the FOV squared box becomes very "teared" when looking to the sides. - Upper part of the IHADSS when it overlaps the rotorblades. - Small distortion in the Left MPD when at the default engine page. But overall, a positive upgrade.

Will try this tomorrow. Not home atm. Only had my G2 for a week now and having smooth performance on a simple training mission in Nevada with the Apache. Running 45 fps and reprojection on. This with steamVR. But based on feedback I should get better clarity and better colours? Am I right?

Massive thank you to ED for this awesome module! A very good EA release. Although some bugs here and there, already an impressive product. Looks like they are on top of things in the bug report thread Looking forward as this module matures.

Ok, so have done some testing. Should have read the manual After the input from @killjoy555 & @Raptor9 I must say it behaves really well. At takeoff I did as stated in the manual, releasing the trim close to the power needed for IGE Hover. Kept my feet of the rudders as I gently pulled the last bit of collective to ease myself of the ground. Worked like a charm. Then I applied same technique going into hover for launching some hellfires. Trimmed out, got myself stable. Then all I had to do was as @Raptor9 said. Gentle inputs on the stick. So far I have a tendency to slowly drift forward more than backwards. But it's getting there. All this with just the force trim button. Now I just need to figure out how the "Att Hold" mode works.

Would have appreciated if someone with the knowledge could go in detail on how the "Att Hold" mode actually works. Been doing alot of practice on the hoovering bit. But after I'm trimmed out, relatively stable, 30 feet, less than 3 knots and engaged "att hold" I feel the heli starts drifting. I need to work more on the stick then just being manually trimmed out. Will test more tonight.

Had the Quest 2 first. But after so much rave about the G2 I had to test it. Glad I did. Better clarity. Sweetspot is actually quite ok with version 2. Also much better comfort out of the box from the G2 then Quest 2.

You might have 2 axis on your rudders. Make sure you are inverting the right one. I did the same mistake. Good luck.

https://forums.oculusvr.com/t5/Support/OVR25027186-fix/td-p/802494

Trying to find some info on how these systems work. In the quick start manual it says: • AT (Attitude Hold, Left). Toggles on or off the selected attitude hold mode (position, velocity, or attitude hold). (see TODO) • AL (Altitude Hold, Right). Toggles on or off the selected altitude hold mode (barometric or radar altitude). (see TODO) When I go to TODO list on the forum is says that it should be in place before the early access release. Had a quick look through through the manual but have failed to find any info on where to change mode, and what they do. I'm curious if some of it can be used to help you in situation where you wanna be masked behind something before popping up to engage targets, or scanning with the FCR (when it comes). I'm also curious if the flight system is in constant need of rudder inputs to hold your heading, or if there are systems to assist you as in the UH-60 Blackhawk, and modeled in the mod. There is a youtube video from The Air Warfare Group, where a former pilot explains how that chopper has a system that basically tries to maintain a certain heading. And as long as you do not manipulate the rudder pedals (combined with a microswitch), the Blackhawk will maintain a certain heading. Making it a very stable and easy platform to fly.

If you have stutter it sounds like some settings are not what it should be optimally. I'm running a quest 2 on a 6900XT. And don't have much issues keeping it locked at 72 FPS. Unfortunately ASW seems to work less optimal on AMD cards then Nvidia cards. So I'm unable to run DCS at 45 FPS with ASW on. To much artifacts. As to you question, check out some of the other threads here, going into great details on settings, performance etc. on what you are asking about. Cheers

Heads up. ASW is crap on AMD cards. For some reason I get more artifacts with my new AMD card than my old nvidia card. For me, ASW is useless on AMD.

Did some testing again now. Wow, the FOV trick was a massive performance gainer. I did not notice any loss of FOV physically inside the oculus set. I put them at 0.8 on vertical and horizontal. My setup: 6900XT OC @ 2650Hz GPU memory default 5800X @ stock settings 32 Gb Ram All DCS settings pretty much as in @speed-of-heat excellent thread , but MSAA OFF, visibility to extreme and scenery details factor 0.8. FSR installed , default settings. ASW OFF Rock solid at 72 FPS except for a small second where it dropped to 66FPS in the turn around the hill inverted over the forrest. But hardly noticable. So during the whole test track, it was buttery smooth, no artifacts and the GPU still had some headroom to play. Kept the load between 82-95%. Apparently what taxes the card the most is close up to forrest while flying inverted. So all I see is forrest. I love how much knowledge there is out here when it comes to tuning the cards and settings in DCS. It's just a matter of compiling it all and getting it out to the masses. Edit: Flying in Nevada during sunset must be a dream now. Hardly any forrest, and some headroom to increase the resolution a bit more. Now I just need to find some sort of shader that can fix the colours and works with oculus. Looks kinda washed out.

@ppokit I have been using OTT up until now. But I guess I can use the official debug tool now. I did some tweaking, and turned off ASW as you mentioned. Much better! Running the track now I get a minimum of 60-63 FPS as I am coming around the hill close to ground inverted over the forrest. Sitting on the carrier deck (training mission F/A-18) I have 72 FPS. Looks promising. Even now, trying ASW makes to much artifacts. yo @TED, With a G2, are you able to lock your frames at 45 FPS and get smooth performance? Like no jitter or stutters?

@ppokit FOV? From DCS or oculus software?

Ok, I got my 6900XT up and running. Currently have some issues. 1: Testing with Speed-of-heat`s test track I`m around 45 FPS at the lowest. This is with vrperfkit @ standard settings. With same settings as Speed-of-Heat in DCS. 2: Having ASW enabled produces more artifacts with my 6900XT than my old 2080. 36Hz with ASW was really nice on my 2080. But was only realistic in Nevada due to being less demanding to run. Setting maximum FPS in AMD software does nothing. I had it at 45 FPS, but DCS was still pushing 50-60 FPS. And 90 FPS in the menu. Was hoping I could test stable 45 FPS without ASW enabled (90Hz refresh), or get ASW enabled with 72Hz refreshrate (36FPS).

Pulled the trigger on a 6900XT. Gonna run it with a Quest 2 for now. Thank you for this guide. WIll make it much easier to dial in the correct settings for optimal performance.

Just installed this mod and figuring my way around it. Great mod by the way. Is it just me, or has it a tendency of tipping left/right as you land? I feel I have to be super careful as I go down. As soon as the backwheel touches, the helicopter easily starts to tipp and can quickly clip my rotorblades. I have been able to land without doing it. It was just a behaviour I noticed. As I could come to almost complete stop. Hover, and then start descend. And then suddenly I`m tipping over Any tips for minimising this behaviour? Cheers

Done

Is it starting up Steam VR and Oculus at the same time? I have been able to provoke oculus launching both the steam VR and oculus VR at the same time. That made everything a slideshow.

Would have been nice to have some lesser zoom then what the 2 current options give us. Any way of tweaking how much zoom the lesser one gives? Feel it gives me just a bit too much of what I need inside the cockpit.

1000 miles = 1 dollar.... In store credit. So for the apache they increased it how much? 4000 miles or something? We are talking about 4 dollars. And the module itself will cost 80$ without any bonuses when it's finished. And people are acting like someone robbed them from a large amount of cash.....

Yes, as long as you don't use any miles to cover some of the cost of the apache module.

I hope most of the people on this forum know it's not feature complete at launch. I wrote "feature complete as possible" in reference to an early access module, as we all should know by now. But yeah, I guess it doesn't hurt to point it out, as some like to interpret things in their own way to the extreme.