WolfK33 Posted March 28, 2019 Posted March 28, 2019 (edited) Hi, a weird problem of which I´m not sure it´s a Tomcat problem, but as I only have it in the F-14 here it is: After yesterdays patch I was flying and everything was allright, today (before today´s hotfix!) suddenly all my mappings of my Warthog (stick only, throttle is ok) are messed up, without me changing or doing anything. For example trim isn´t mapped at all anymore and everything else is just random stuff all over the place. Only the Tomcat seems to have that problem. Nothing too wild as I will just remap it, but I thought I´d mention it. edit: now that I´ve wrote it: What I did before was to update VAICOM Pro, which said that the AIRIO-package is now supported. Will post this also in the VAICOM thread, maybe something went wrong there although I don´t know if that could have any influence. Edited April 13, 2019 by IronMike
hornblower793 Posted March 28, 2019 Posted March 28, 2019 I have just upgraded VAICOM Pro and purchased / installed the AIRIO extension without issue (did backup the input folders just in case though :-)) Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal
wowbagger Posted March 28, 2019 Posted March 28, 2019 (edited) Yes, I'm experiencing the same exact thing, under the same circumstances regarding AIRIO extension. Although in my case I can't find the controls listed to re-map: eg. is only one axis available for thrust. Edit: Hollywood_315 is on the case. Edited March 28, 2019 by wowbagger no sig
Agent_wolf Posted March 28, 2019 Posted March 28, 2019 (edited) Same here. If I run Vaicom Pro with AIRIO it brakes all inputs for the F-14B module except mouse. No keyboard, trackIR, Warthog Hotas. To get controls back to the F-14B I had to uninstall the F-14B module and reinstall it. As soon as I run VA with Vaicom again it brakes it again. So definetily a Vaicom AIRIO problem EDIT: Hollywood is aware of the problem. Hotfix pending Edited March 28, 2019 by Agent_wolf [sIGPIC][/sIGPIC] ANON6-1 | Wolfie
Oesau Posted May 1, 2019 Posted May 1, 2019 Did the hotfix fix it for you Agent_Wolf? I've got the latest version of VA and Vaicom and its still breaking my F-14 rudder inputs...
Pawsie Posted May 1, 2019 Posted May 1, 2019 Hmm...from time to time, something similar happens to my Viggen config: some keystrokes are remapped, and I am unable to change them. Restarting the sim revert controls back to my mappings. I have seen this only on Viggen module
Oesau Posted May 2, 2019 Posted May 2, 2019 I have to delete the f14 pilot input folder every time I restart DCS otherwise I just can’t make the rudder axis (yep, just the rudder)
Recommended Posts