TZeer

I know My issue was more with the oscillation of the SCAS Yaw while NOT holding the button and flying straight. Making the heliocopter oscillating left/right. Should not the heliocpter be able to keep me flying forward WITHOUT inducing oscillation, when I'm able to do it with TRIM pushed down? But again, I don't know what triggers it, so hard for me to replicate it. Also if I activate ATT hold while flying forward oscillation stops. So with ATT hold in forward flight the oscillation stops, pressing and holding the trim reset button the oscillation stops. But just flying without any hold modes engaged, trimmed out and no trim reset active it oscillates. But I will post a seperate post with track when I have found out how to replicate it. Also need to find out if it even a bug, or just some funky flying on my side.

Is there any indication to tell me where I am seeking with the FCR in the vertical plane? Performance for me is very underwhelming. Elevation differences from where I am and where the targets are is giving me alot of troubles aquiring targets. I can be on a "flat" dessert area and get no locks. Elevation difference can be 300 feet (targets higher) over 3km. So targets are in a slight upward slope. Changing to manual sometimes get the targets on my scope. But not always. So while the FCR is the highest mounted sensor on the Apache, and should teoretically have the best conditions to get a picture of the battlefield. It's struggling to give me a lock on targets 3km infront of me. George sees them, I can see them with my own eyes. But the radar is completely blind So the scan, target and proritize within 30 seconds is only applicable IF you are able to get a good scan in the first place Ony tips out there? What does the markers in the elevation option mean? I guess it's scan height relative to the Apache. But how much and at what range? How does the auto option work? What's the limitations?

Still have som odd behaviour now and then. But it's not consistent. So hard to pin down if it's me or the HOLD mode acting up. Normally I just get my self stable, trim everything out and engage HOLD. 8 out of 10 times it works as I would expect. But have had a few "incidents" where my ATT HOLD mode starts inducing large over-corrections that would just increase in movement. Before anyone tell me I need to TRIM out. I'm already trimmed out ot the point my movement so small I'm within the crosshairs of hover symbology and airspeed is 0 knot. I can almost take my hands off my stick. But as I mentioned, need to test some more, to confirm it's not me doing something stupid I also have som slight oscillation on the yaw when flying straight, I can see the yaw SCAS moving left-right. If I hold the TRIM button the oscillation stops, release the button and the oscillation start again.

Incredibly hard for the FCR top pick up targets. Is this intended? Flat area, desert (Nevada) Track starts midflight, roughly 6,5km from targets. I can clearly see the targets ahead. 6 armoured vehicles. Start doing single sweeps into the area. It's not until I'm less then 1,5 km away it picks up the targets... Even at 100 feet AGL I cant pick up anything. AH64D_radartest.trk

Did some more test's and it seems to be some bugs. Will post track and make a separate bug report. But anyway: - Only got 4 out of 6 targets on my FCR. Roughly 2 km at my nose. In Hover. - Tried changing elevation manually on FCR, no change. Went to fixed mode and suddenly got 1 more target at my scope. Went back to previous mode, and target still there. - Raised my altitude to about 80 feet. Suddenly one of the targets changed position on the TSD to far right. But LOS was straight infront of me. - Also had serious problems picking up targets on a flat desert. In my test track I'll put on the bug report page, I had no targets on my FCR until I was less than 1,5 km away from them.

There is a small green X over each target you have sent a missile at.

Looking for info on the limitations of the FCR. Like minimum altitude, angles etc? Reason I ask is that I was testing out a low level attack, coming in at roughly 20 feet AGL on a SA-8. This SA-8 was situated in the middle of a large flat area in the desert. I as a pilot had LOS on this on my way in. But to my surprise, I was not able to get it on my scan. In the end I had to change to George and have him go guns on it. After I had killed it, I made some distance, climbed and turned around. This time I got it on my scan. I would have thought that the FCR would pick up the SA-8, when I as a pilot had LOS on it, and the radar is situated higher up. But maybe there was some limitations I was operating within?

Did a short run now just to test again. - Every time I engage ATT HOLD while in hover, the SCAS (green arrow) kicks to the left in the joystick overlay. I can sit in hover, dissengage ATT HOLD, instantly re-engage and it will still "kick" to the left. Sending the Apache left, before it starts trying to compensate it. - YAW SCAS (green mark) is oscillating slighty when flying straight. No modes engaged. Only trimmed out and stable. In this configuration the nose is oscillating left and right. It's not much, but enough to notice it. - ALT HOLD, engaging this makes the helicopter creep toward the ground. If I don't take over manually, it would drive the Apache into the ground.

Tried the apache again after some time away from DCS. Holy smokes, the hold mode is dangerous! Completely trimmed out, almost dead center holding the position in hover mode. Activated hold mode, and a short second later I was on may way sideways into the ground.

Check ypur virpil settings. There is a default dead band on all virpil analog axis. This deadband will come on top of any deadband you have inside DCS. So when you trim, then recenter your stick, there will be a noticable area in center where your stick does nothing. Also check your collective. You will have to pull a little before the collective in game actually moves from it's default off position.

@Qcumber That's why you see more upside when using QVFR/DLSS whatever. @diego999 already using his CPU more. He's also rocking a 3060ti vs your 4070. You have way more headroom both in the CPU and the GPU department.

Maybe because he is more CPU bound. @diego999 running i5 10400, while you @Qcumber running 5800X3D.

Made an order earlier today as well Wonder how long it will take them to actually start shipping.

If I understand you correctly, you want help in finding targets while in the CPG seat?? You basically just do what George do. George doesn't find any target unless you tell him to search in a specific area. All you have to do is searching the same way with the TADS. You are George. If you are unable to find targets with the TADS, I guess you can turn on labels

It sounds like you are messing with the power levers as @Floyd1212 mentioned. After startup, there should be no need for you to change the power levers. Not until you are back the ground again and ready to power down. Only use the collective.

There is a bug/error in how the FMC controls the Yaw input on the Apache. Could you confirm that my observations are correct @Raptor9? In the manual it states: What I observe is that when in Position Hold submode, you need far more than 3% displacement on the pedals to actually break the Heading Hold. It will not dissengage the mode until the input it close to saturated, or roughly 10% displaced. The hold mode will fight you until you are close to the end of the limits of the +/-10% authority. If I slowly move into 20-30 knots, and transfer into the Velocity Hold submode, I need less pedal displacement to disengage the hold mode. This can easily be observed by just bringing up the control input indicator, and play with the pedals. Roughly halfway to +/-10% limit the hold mode will disengage, which seems correct as the manual states 6% in the Velocity Hold submode. If my observations and understanding of the systems are correct, we now need over 3 times the pedal displacement in Position Hold submode than what should be necessary to start turning the helicopter. Due to this error, the apache will "fight" the pilot more than necessary when trying to turn while in Position Hold submode. Regards

And if someone need more than what you get inside the occulus software, just do it from DFR app and increase the multiplier in the sweetspot. Pushing pixels past maximum setting in occulus software with other apps is just a waste of pixels as you are increasing pixels on the entire display, instead just in the sweetspot.

I can only echo what @Sandman1330 is saying. I have done what he mentioned. Centerstick, extension and resting my arm on my leg, and using fingertips to do corrections. No fatigue, better control, fine adjustments etc. And use the visuals OUTSIDE the cockpit much more. Changing to the "hover" symbology to early just makes you chase the instrument. No point in using the symbology if your not first able to keep it realitvely stable just using the visual cues from outside the cockpit, at least in my opinion. Helped my quite a bit. Currently just flying around on Nevada, in hilly areas. Going from cover to cover, practicing the transition from forward flight to hover, just using the visuals, and trying to keep the same altitude. Very easy to go from 50-60 feet and suddenly be 10 feet of the ground when you finally have come to a hover

Used a 6900XT with Reverb G2 without problem. Now running it with a Quest Pro, no issues.

After some flying and testing, I'm able to pull 72 FPS, no ASW and 4xMSAA @ 4864x2448 in occulus app, with default DFR settings in the Apache. I'm running fairly high settings in DCS, but low on clouds and shadows. AMD 5800X OC RX 6900XT 64 GB 3600Mhz RAM I'm doing this on the Nevada map, have not tried other maps yet. I guess I will struggle there. But oh boy is it immersive. No stutters, no glitches from ASW or anything. Smoothnes all the way. @nikoel how much "overhead" do you have after changing to a 4090? Do you ever dip below 72 FPS?

Ingame settings?

I don't think it's the actual colours or contrast that changes. It's just a biproduct of change in resolution. Lesser resolution, more "pixelated" and colours are distributed on fewer pixels. That means whatever nouances that was there, disappears as there are lesser pixels to put them out.

Performance is related to standalone apps running on the headset. Not PCVR.