Bastlwastl Posted May 23, 2021 Posted May 23, 2021 (edited) Hello there, whenever i start a mission with the F-18 in the newest open beta, i have the weird behaviour that the stick is fully deflected to the left and all other axes go like crazy as well. When i touch the axis for the first time it get's back to their normal (or as they really are) position. It only happens in the F-18 and neither the F-14,F-16 nor the A-10C II. Is anyone experiencing this as well ? I have attached a picture that shows the controls on mission start. Thanks for your help! https://imgur.com/dGdpPJb Regards Sebastian Edited May 23, 2021 by Bastlwastl 1
LeCuvier Posted May 23, 2021 Posted May 23, 2021 Check your axis bindings. There are probably multiple bindings on the same axes. This happens sometimes after updates. 1 LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Bastlwastl Posted May 23, 2021 Author Posted May 23, 2021 Thanks LeCuvier, i already tried that. It happens also with the default mapping (deleted custom controls folder in „Saved Games“). 1
schmiefel Posted May 24, 2021 Posted May 24, 2021 There was another thread already that describes the same thing: looks like it has something to do with HOTAS sync function. 1 Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64 Spoiler Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64 Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64 Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker
Bastlwastl Posted May 24, 2021 Author Posted May 24, 2021 Happens to me in the P-51 as well and only when the "HOTAS-Sync"-option is activated. All my other modules work fine (F-16,A-10CII and F-14).
vCSG3 Bloat 203 Posted June 9, 2021 Posted June 9, 2021 happens to me with X52 and Orion (separately, 1 connected at a time). Hot spawns in the Hornet are fun with the sync function on... bit of a pain to have that option off... wonder if this has anything to do with AI tankers flying with full surface deflections in a straight line... maybe the default positions have been flipped somehow...? :pilotfly: BrotherBloat
Svend_Dellepude Posted June 11, 2021 Posted June 11, 2021 As others have pointed out, sync HOTAS option is the culprit here. Happens on other modules as well. [sIGPIC][/sIGPIC] Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.
Gwalker99 Posted June 20, 2021 Posted June 20, 2021 On 6/11/2021 at 4:18 AM, Svend_Dellepude said: As others have pointed out, sync HOTAS option is the culprit here. Happens on other modules as well. whats the solution?
Brun Posted June 20, 2021 Posted June 20, 2021 (edited) On 5/23/2021 at 6:55 PM, Bastlwastl said: Thanks LeCuvier, i already tried that. It happens also with the default mapping (deleted custom controls folder in „Saved Games“). The default mapping is the cause of axis conflicts. You have to specifically clear the unwanted assignments from each device. Edited June 20, 2021 by Brun Asus Z690 Hero | 12900K | 64GB G.Skill 6000 | 4090FE | Reverb G2 | VPC MongoosT-50CM2 + TM Grips | Winwing Orion2 Throttle | MFG Crosswind Pedals
Recommended Posts