TZeer

Not tested that yet. Only quick setup with ASW disabled to compare frames. But ASW has worked without much problem before. And was better on quest pro then what I got with MR on my G2

@nikoel & @mbucchia I can confirm it's working on my AMD RX 6900XT card.

@nikoel & @mbucchia I can confirm I'm still in the AMD Meme Team . I'm at work right now, plan is to go home sometime tomorrow. I will test it and report back

Really appreciate the effort and extra work you guys put into making this possible. @mbucchia & @mimamema

Looking forward to an update with DFR. Are you tweaking the FOV as well now? Or running default?

@Nikoel where do I put the ticket? And what should I put in it? And is it still only Nvidia cards that will support DFR in DCS?

Hmm, this can get very interesting then. Combine FOV tweaking and DFR, and the possibility to run on either 72, 80 or 90 Hz. Maybe no need for ASW soon

I have made a secondary FTR button on my collective to deal with the same problem as @Floyd1212 mentioned. I use my pinky button on my collective. It's also much easier to do really fine adjustments to my cyclic when I don't have to keep holding a button on the same cyclic, specially when going from forward to hover, or turning the Apache while in hover. I'm just waiting for some parts so I can lower my cyclic down, this way I can rest my arm om my thigh, and get proper support for my arm. Should make it much more comfortable holding FTR while flying, and prevent unwanted cyclic inputs.

I have same type of setup, and I mostly trim when moving the stick. Reason is to have the flightcontrolsystem work WITH you and not AGAINST you. If you don't trim, there is a bigger possibility that your system will get saturated. Specially on the tailrotor. Small corrections it's not always necessary. But I trim when picking up speed, slowing down to hover, doing turns etc. Doing this I always give the system the best possible conditions to "assist" me.

Just some feedback to you. - You are using to much stick when correcting. This can be hard with the Warthog base, specially if you also have a short stick. I have used that base myself, and it's a PITA with helicopters. Also, even with a much smoother base, I do not hold my entire hand around the cyclic. Very easy to induce to much correction to the cyclic. Doing small corrections I only use my thumb, index and middle-finger. You should also have something to rest your arm on. Makes it much more comfortable, and when only using the three fingers I mentioned, much easier to hover. - After you activated your "Hover-Hold", you kept moving your stick. This will override your "HOLD" if you move past 2,5%?? I think it was. Basically you are overriding any input the "HOLD" mode wants to do. Just try to hover as best you can do, hit "HOVER" and let go of the stick, to prevent you moving the stick. - Another thing that can help you, move the trim-commands to a hat that is easy to reach and don't interfere with your cyclic inputs. Specially if you are not able to rest your hand. It's very easy to induce unwanted cyclic inputs when trying to reach whatever hat you have assigned your trim to, if it's on your cyclic. Personally I have an extra trim button on my pinky on the collective, that I use when I'm transitioning from forward-flight to hover. This is until I get an extra part on my setup that I can lower my cyclic so I can properly rest my arm on my thigh when flying. This makes it easier for me, as I can use tiny corrections coming into hover, while holding my trim button on the pinky switch. When I'm happy I can use my "hover-hold" command on my cyclic as normal.

@Belphe axis been inverted in the setup?

@Turd Ferguson Yes, you can tune the setting in the VPC software. The easiest way is to change the interface to LITE from Pro, and just scroll to the right on the overview. There is a separate column showing deadzone.

I have the same behavior while taking off. Getting light on the wheels, countering the yaw with my pedals. At the same time I need to put in cyclic to prevent the skidding. But as you get light enough and takeoff, the Apache almost wants to tip over. You can counter it, but I get the same behavior as Casmo. But as soon as you are clear of the ground and the "wobble" is taken out, it's all stable. Both my pedals and cyclic is set to "Joystick without springs and FFB". I have also removed all deadzones on the stick and pedals, as there is no need for a hard center since I don't need to to be able to reset the joystick to center after trimming. Unfortunately I'm at work now, so can't give a video or trackfile.

Or they leave the resolution at standard in the occulus software, just to fire up the ODT 2 sec later and pushing the multiplier...

@davidrbarnette it's not about the IHADDS itself. It's about the monocle that projects the IHADDS.

Just made a small post in the "Controller Question and bugs" section of the forum. It's a topic I don't think is very well know, but can be very important in trying to control this beast. Primarly aimed towards Virpil users, but can be relevant for others as well.

This is primarly for Virpil users, but it may be relevant for others as well. I don't know how how your software or sticks are. Anyway, ALL Virpil devices come with a default Deadzone. Stick, collective, rudders, etc. This can mess up your flying as you suddenly "lose" connection with the helicopter everytime you cross the deadzone area on the stick. Examples: Collective - This has a default DZ of 2% on each end. Thats why nothing happens when you start lifting your collective as you are about to take off. You can easily see this as you have to lift a little bit before you see the collective on the Apache actually starts moving. Not a very big deal. Rudders - This has a 5% DZ in the middle. If you need to reset to center after trim, this is not very notable. But you can most likely decrease the DZ and get quicker respone when you move the pedals. If you have modified the pedals as I have, and dont need to recenter, this is VERY noticable every time you cross the centerpoint. As you will have a 5% gap where nothing happens as you move your rudders. Cyclic - Yes, this one also has a 2% DZ in the middle of both axis. And again, if you need to recenter after trim, maybe not that noticable. But, you will have a small spot in the middle where nothing will happen when you try to do microadjustments trying to hover. If you also have a DZ set inside DCS, that will come on top the one that is already default in the VPC software. If you have a WarBRD-D where you can use the clutch and have a cyclic that behaves as a real cyclic, you will have 2 DZ to deal with. One every time you pass the middlepoint of the roll and one when you pass the middlepoint of the pitch. This can really mess up your attempts to hold hover, as you are constantly moving around atleast one of those axis. Now imagine suddenly losing authority of the helicopter as you move through the DZ trying to hover. And with how small adjustments you need to correct and tune, this can really make the helicopter feel hard to control. Happy flying, hope this helps some of you.

Force 45 FPS, ASW off, run 80 Hz refresh. 80 Hz from the setting page in the occulus software. The rest from ODT.

So basically you can change to 0.85, then increase resolution or do an override in the tool if you are already maxed? Get roughly same performance but better visual quality, or just better performance if you fancy that.

Just a quick tip. Played around with the trim today, and put an alternate secondary trimreset mapping on my pinky switch on the collective. Worked wonders in taming the beast while trying to slow down into hover, trimming while manual hover and hitting the trim while turning in hovermode. This is a temporarly solution until I can lower my cyclic and rest my arm on my thigh. I already have a Virpil with extension and curve set to 10 and only 1 deadband. But when trying to trim, due to how sensitive the Apache is, slight unintended movement in the cyclic due to trying to trim just makes it harder. This way I can use only my fingertips moving the cyclic, while holding the trimreset with the pinky on the collective.

You need that to get localdimming to work?

Although the FM has improved there is still some "strange" behaviour out there. Few I notice. - Oscilation on the yaw. Had a few times where I have come to a hover, and with no inputs on collective or pedals, I can see the yaw channel working, with a small movement back and forth on the nose. - Sudden large needs for yaw input when slowing down. Comming in nice and easy, everything going good, then a sudden need for larger yaw inputs, as you are passing a "limit". Smooth movement goes to a sudden need for yaw input. - Stability, very "twitchy"? I have virpil extension, and a 10 setting on the curvature on pitch and roll. I have also reduced my deadzone to 1 from 3, as the deadzone was to much how "twitchy" it is now.

A few more days of flying. I must say, I'm impressed by the Quest Pro. Right now I think I have copied @nikoel settings with 4864x2448 @ 90 HZ running without ASW with forced 45 FPS. A little bit of ghosting. But much smoother than trying to do the same with the G2. I'm also running 4x MSAA. I can still push the settings in the Occulus app to 5408x2736. But I don't have the juice to do it right now. If I use ASW, the artifacts are much less than what I had in the G2. So I have not yet landed on running with/without ASW. Of course, it's not as high res as the Varjo Aero, but again, it's not in the same pricerange either. And it works standalone. One of the things you suddenly really appreciate is the ability to read EVERYTHING in the cockpit by just moving your eyes. Just casting a quick glance down on any MPD/MFD, without needing to move your VR set to adjust your sweetspot over what you want to read. Looking down to the right/left consoles without needing to twist and turn in your seat to get your sweetspot over whatever knob you are trying to find. One thing I have also noticed, is the lack of "strain" on my eyes. No mather how I adjusted the G2 previous, I always felt "something" was of. Even though things where clear, I still felt my eyes where working harder. Now it feels very natural looking into the Quest Pro. I think that is something Luka S./Wolta mentioned as well in his preview of the Pro. Now it's just wait for the next gen GPU's and crank everything to the max

Issue is still here after latest patch. Running a Quest Pro now, and still seeing distinct stutter when using the PNVS. But, I found out that when running my Quest Pro with AWS off and constant 45 FPS, both the TADS and PNVS will stutter when paning the view. If I unlock my FPS and hit my refreshrate, the TADS become smooth, but PNVS still stutter. So there is definitely something with the refresh rate of the PNVS image vs the TADS image.

The other thing people keep missing is that yes, the resolution is comparable between Quest 2 and Pro, but some of the area is wasted in the Quest 2 due to how the screens are. Quest 2 has one single large screen, Quest Pro has 2 individual screens. I think I saw somewhere this difference translated to roughly 30% higher resolution/pixeldensity on the area you could see. Edit: Found it, it's actually almost 40% more pixels per inch.