daniellegraham

I would like to have this function because I don't have enough physical keys to bind all 8 switches. Or, maybe a key for all MAIN, another key for all AUX fuel pump. Another solution is: 1. ALL left MAIN 2. ALL right MAIN 3. ALL AUX

I also found this issue but I am not sure about it at that moment. I just feel weird.

Make sure you have enabled the hook release on the overhead panel.

You can put your throttle to FLIGHT for taxi. Just keep your stick center and raise the collective a little. Then you will move forward.

No. It cannot bcoz the physical detant maps a different virtual key from GROUND -> OFF.

Hi, I have the VKB STECS throttle system which support multiple detants in the throttle axis. Currently, I set my throttle axis to the ENG COND lever and also set the detant to the gate which allows me to enable the gate in the special setting. However, currently there is only one key binding to the gate. If I need to move the lever to OFF position. I need to move my throttle all the way back and forward to cross my detant(in order to press the gate button) then go backward again to the OFF position. If there are 2 ways gate buttons, then I can set one detant button to OFF -> GROUND, and another one to GROUND -> OFF. BTW, I don't know if the real thing has the gate for GROUND -> FLIGHT or FLIGHT -> GROUND. If that is true, my STECS can also support it.

You saved my life

I was trying to limit it to half the headset's target framerate. I listened to your suggestion and the latency is now 13ms which is still a number in yellow.

I limited the framerate to 45fps. The screenshot shows my game latency is 22ms rock solid in menu. If I release the framerate lock, the latency can be lowered as 13ms. With the same setting, I can gain 10ms in game. So, it seems that the main menu has a performance issue. Can I disable the big plane behind the menu?

I mapped 2 axis to INSTRUMENT and Console light(overhead panel) respectively. In the control setting, I can see DCS can recognize the full range of my physical axis knob. Axis is defined as a "slider". However, if I turn my physical knob from full to half(decrease), in the cockpit, the knob will turn from full to zero. I don't know if other knob has the same problem. At least, these 2 have.

We encounter the same problem. I have the same rig as yours but 4080. I also play VR. Without MT, I got a very smooth framerate.

Hi I found this bug on day 1 and I cannot tolerate it anymore. When the Quest 3 controllers go to sleep(inactive), it does not disappear like my Pico 4 did BUT pop up in front of my headset's position which is blocking my view. Sometimes, two controllers will pop up simultaneously. I have no solution unless I disable the hand in the VR setting. Pls help. i

My PC env: i7 13700 + 4080 + Quest 3(Pico 4 has the same issue but I sold it already) Win 11 + Virtual Desktop 1.29.0 or 1.29.3 beta (Sound output is set to headset only) Reproduce steps: 1. Flying in the middle, pause or not pause does not matter 2. Remove my headset from my head and put it aside 3. After the headset goes to sleep 4. Wait 1-2 mins 5. Come back and put my headset on 6. VD starts to reconnect and then go back into the cockpit 7. Sound output is now PC speaker

In the patch note, I saw nothing about the flight model. But I felt that the landing and hovering is more stable than before. Before v2.9, in order to make a safe hover landing, I had to change to cruise sym mode to make sure my tail wheel touched the ground first, then the front wheels. Now, it seems that I can do whatever I want such as 3 wheels touch down. Also the hovering, I can make much more stable hovering right now. It seems that the aircraft slides less.

Lock button? I don't recall such a button. Which one?

Do you mean you cant swap the freq?

I pasted 4 layers of soft contact pad at the top of the frame to make the upper part thicker than it was. Now it tilts down when I put it on my face.

After you said you had no issue, I returned to the game and re-adjust the headset. It seems that I have to tilt my headset downward to the floor as much as possible to make the LOS at the front of my eye, which is very uncomfortable and puts all the pressure on my cheek.

Hi forks, I just got my Quest 3 and I found that the IHADSS crosshair is not at the center of my eye. And I changed back to my Pico 4 and there is no such issue at all. I am sure it is not the sitting height problem coz no matter how I move my head or changing my stance, the LOS is remaining higher than where it used to be. With this problem, I cant even boresight the IHADSS. It never align unless I nod my head down and stare my eye up.

May I know why I have to uncheck the "Realistic TDC" to make it work? If I checked this box in the special setting, I cant slew the camera by using the TDC control. UPDATE: hold the "depress" button then move the TDC

I use steam version. I can confirm MT works but very blurry in VR.

U are right. I got the same issue. All new features are grey out. i got RTX4080 and the latest Nvidia driver and playing in VR. update: confirm that I have to run the MT version to make it work

It has been more than 1 year. And I still can't find the convoy either.

It is quite useful in VR coz my stick has no re-center. It is always ON in HUEY. I can find it in Apache

I just updated the open-beta version, and I found that I need a way more left pedal(around 85%) for take-off than before. Is that real in life?