Batmensch

I'm trying to get my new Virpil Ace Interceptor Pedal brakes working with DCS, specifically the Grinelli F-22A mod. None of the wheel brakes give me an option to bind to the pedals. The rudder itself seems to work fine. None of the Wheel Brake binds give me any options to choose, nor does the "F-22 Systems" brakes. Specifically, in the "F-22 Systems" "Wheel Brakes Both" option, when I hover over the "VPC Rudder Pedals" it says "No command available for this device", and double-clicking on it does nothing. It's currently bound to the keyboard "W" key. Under "Systems" there are three options to bind, "Wheel Brake Left", "Wheel Brakes On" and "Wheel Brakes Right", and although I can double click on them, they don't give me any options to choose, and they don't respond to my pressing the brake pedals on the Virpil device. I am running the latest 2.9 beta as of 11/30/2023. The pedals work fine in MSFS. I also have the latest version of the Virpil software, but it's kind of, well, opaque to me, other than simple calibration. Anyone have any experience with this?

OK, it's working. Following your note, LeCuvier, I went to the Axis commands. I noticed that the single "thrust" was set to Joy_z. I deleted that, and then set the thrust left to joy_ry and thrust right to joy_rx, and then went to Axis Tune Panel for each and set them to "Slider". Now it works just like my old Logitech throttle worked, and I can use 100% of the throttle and turn on the afterburners! And I also have separate controls for each engine. Now I just need to figure out exactly where in the percentage the afterburner detents should be, and it'll be perfect! Thanks!

Thanks for the post! I am only flying the Grinelli F-22A mod at this point, and my previous HOTAS, the Logitech/Saitek X.52, works as expected, that is, that you can go to full power at about 90% of the throttle range, and the last 10% engages the afterburner. With the Winwing, however, all the way to end of the throttle, even past the afterburner detent, doesn’t give me full power OR the afterburners. However, I didn’t know about right-clicking on the throttle axis binding. I’ll give that a shot!

Hi, I’ve just received my Orion Hotas 2, and I’m trying to get the throttle working properly. It actually works, but it doesn’t seem to use the full range of the throttle on my plane, and the afterburner doesn’t seem to work at all. I’m not sure how to fix this. In Winwings SimAppPro app, when I move the throttle the maximum, it says the throttle IS at maximum. However, in DCS, although the throttle moves up, it never gets to max, nor does the afterburner run, even when pushed to after the afterburner detent. I just don’t know how to fix this.

I have a 4090 and an Aero. I've seen "stuttering" both with the 4090 and my old 3090, and I've seen it without. It seems to be a problem that happens sometimes, at least for me. Generally a reboot fixes it. I'm using OpenXR, and all I did was put the .dll in place and run with the --force-steam-VR flag. No other changes.

So, just starting with DCS, I mostly bought it so I could fly the F-22! Which mostly works great. However, when doing a "Fast Action" mission for the F-22, the plane is, by default, not armed with missiles. So I press COM1, go to Ground Crew, and do a Rearm and Refuel. I choose my load, and hit OK. At this point I hear "Request Rearm" over coms, and then, if it all goes well, I hear the reply "Copy", and then in a few seconds my missiles are loaded. However, about two times out of three, I don't hear "Copy" and the missiles are never loaded. I am using version 2.8 of DCS. For the Fast Action mission I'm basically using the defaults, i.e. the Caucasus, random location, random season, random weather (or clear), and 12:00 for the time since I don't know how to turn my lights on yet! And unfortunately, I don't know how to use the coms on any of the other aircraft so I can't test them yet. Does this happen to anyone else?

I just wanted to thank everyone who contributed to this guide, especially Supma! I've got it all sorted and running DCS in Varjo OpenXR Mode with my Varjo Aero and it works wonderfully. My ONLY problem at this time is that, when I start DCS, the main DCS screen seems to be at my feet in the virtual space, which I can fix just by hitting NUM5. I installed openvr_api.dll, and I started DCS with the --force_steam_VR flag. That seems to be pretty much it, all that is really required. OpenVR and OpenXR are both turned on in the Varjo Base app. I don't have the cursor offset in the cockpit that I got in Varjo OpenVR mode, and I don't have to look at the awful flickering that I'd get while loading DCS in Steam OpenVR mode, nor do I need to use the "crosseyes" tool. Framerate is smooth and I can run my 3090 with a lot of options on "high".

I am also having this problem. When I run with --force_steam_VR, it does indeed fix the position of the cursor, but now when I move my head around the entire image warps.