Psifire Posted April 20 Posted April 20 Hello all, I just purchased an Orion 2 Navy Ace throttle, and I can't map the throttle axis. I can map everything else, and the throttle works for aircraft that already have it set as default in their profile, but unless it is set as default, I can't map Rx or Ry to any controls. I have tried this both with SimAppPro running, and with it shutdown, and I get the same results both ways. I have tried a game repair. I know the game can see it, I know it registers the axis, but for some reason it just will not register when I try to map it. Winwing support wasn't much help, and honestly I'm not surprised. This seems like a DCS issue. Anyone ever run into this before? More importantly has anyone ever fixed this before? Please tell me how.
Psifire Posted April 20 Author Posted April 20 This also means that I can't use any aircraft that don't have a profile uploaded in SimAppPro, so if someone could upload any crappy profile that has Rx and Ry mapped to throttle for the aircraft that don't have any profiles uploaded that would help me out a ton. I need the following: F-86F (Full Fidelity, not flaming cliffs) I-16 Sa-342 (All variants) MB-339 (Not sure you can upload this on SimAppPro, it doesn't even show up for me in aircraft.) Mosquito (Same, doesn't show up in aircraft list for me in SimAppPro.) Before someone mentions it, I just want to state that I wouldn't use prebuilt profiles if I didn't have to. To reiterate, I can't map Rx and Ry to anything, but I can use it if it is already mapped in a profile. I need these SimAppPro Profiles that have thrust mapped to Rx and Ry. I'm going to remap everything else.
Nightdare Posted April 20 Posted April 20 Have you correctly calibrated your axes (Idle and afterburner points)? Intel I5 13600k / AsRock Z790 Steel Legend / MSI 4080s 16G Gaming X Slim / Kingston Fury DDR5 5600 64Gb / Adata 960 Max / HP Reverb G2 v2 Virpil MT50 Mongoost T50 Throttle, T50cm Base & Grip, VFX Grip, ACE Interceptor Rudder Pedals w. damper / WinWing Orion2 18, 18 UFC & HUD, PTO2, 2x MFD1 / Logitech Flight Panel / VKB SEM V / 2x DIY Button Box
Psifire Posted April 20 Author Posted April 20 3 hours ago, Nightdare said: Have you correctly calibrated your axes (Idle and afterburner points)? I did calibrate the axes. I'm still messing with the detents, but they are physical and shouldn't affect DCS being able to detect the axis during mapping.
Psifire Posted April 20 Author Posted April 20 7 hours ago, Nightdare said: Have you correctly calibrated your axes (Idle and afterburner points)? Ok, got it working! Took me awhile, reinstalled the software, repaired DCS and it is now working for some reason. I think this was an issue with my computer or install, not the software or DCS.
Recommended Posts