nd1312

No

I did some more testing and it seems the problem is dependent on the relation of the Quest 2 mirror image size to my monitor resolution. I'm seeing different results if I change any of the DCS 2D resolution setting the VR PD setting the "Use DCS system resolution" setting For example. If i check "use DCS system resolution" the mirror image on my monitor stretches to full width. And now I see the game in the top half of my Quest. If i increase the 2D resolution from 3440x1440 to something like 3440x3000 the problem goes away, but now I can't move my mouse to the bottom of the screen, because the mirror on my screen extends beyond the bottom of my monitor. If I set my PD to 0.8 it works on 3440x1440 but now the picture quality isnt great. I then tried to increase the PD via Oculus Tray Tool by 1.6 again. But then I get the same result as if I set the PD in DCS. It also doesn't matter if I start DCS with --force_oculus or not

If I set the Pixel Density at 1.5 for example, the game only gets rendered on part of the screen. The rest of the screen stays black and is collecting artefacts/ghosting from the MFDs over time. Even if I set PD to 1 there's still a couple of pixels at the bottom and right sides of the screen where it happens. The non-MT version works as expected My system: 13700k, RTX 4090, 64gb DDR5 Screen

Its worth a try. I think the top hats would still be a stretch (depending on your hand size) :) I saw his review of course but i think it's a bit nitpicky in some points. I had no problem with the mode button for example. And the mini sticks you'd get used to as well i thnk. Well, I liked the concept of the x55 as its not specific to one plane like the warthog. And it was cheaper of course.

I was in the same boat as you a year ago. Had the X52 which was beginning to fail. I ordered the X55 despite the mixed reviews. Unfortunately it was unusable for me. I couldn't even properly reach the DMS, let alone the trim hat. The throttle was so stiff even at the lightest friction setting that I would lift the base every time I moved it. I just couldn't justify the 200€ for a stick with that many flaws. I'm not saying it's bad for everyone of course, but it was just incompatible to my hands. So I sent it back the very next day and ordered a TM Warthog and I'm very happy with my decision.

Hab das gefunden: http://www.anythingaboutaviation.com/wp-content/uploads/2013/01/Aero-L-39-Flight-Manual.pdf

Logs after couple of minutes in A-10C Sunset Sierra. Win 10 64 i5 3570K AMD 7950 Logs.zip

Flaps still seem to work for me with these commands: But nav lights for example just cycle through with each toggle now

Does that mean you have to change your Target map around each time you change the aircraft? That seems a bit inefficient.

Uh, haven't you heard?

So excited!

I want a Hawk

Thanks, might as well...

My slider still works reasonably well. Sure it's a bit shaky sometimes but it usually stops when i move it a little forward and find a stable spot. But the scroll wheel is pretty unreliable for me. I use it as boat switch and AP mode selector and have to turn it a couple of times until it registers. And the rotaries are completely broken. Have to have most of the range as deadzones and just set them up as bands to simulate button presses. Yeah, i have to upgrade soon :joystick:

I'm using a PS3 eye at 75fps first with Freetrack, then FTnoIR and now with Opentrack. Sure, i never used TrackIR, but my setup works well enough that i don't have a reason to switch.