Verde Posted May 27, 2017 Posted May 27, 2017 Trimmer is not working in 2.1 without it flying is not possible, anyone has a issue?
Beta Sokol Posted May 27, 2017 Posted May 27, 2017 For me, trimmer only works on ground, or just after a hard landing it works again.
Isegrim Posted May 27, 2017 Posted May 27, 2017 For me trim only works sometimes or restricted, defenitly a strange behavior but the switch on the stick inside the Cockpit is moving like normal. "Blyat Naaaaa" - Izlom
Flagrum Posted May 27, 2017 Posted May 27, 2017 afaik there was something changed in regards to the FFB implementation. maybe this is a side effect? what type of joystick do you guys use? ffb? non-ffb?
Redglyph Posted May 27, 2017 Posted May 27, 2017 I confirm it's not working as expected in the air since version 2.1.0.5677.215, I see the trim button moving on the stick but it has no noticeable effect on the flight model. Didn't have the time to check whether the neutral light was switching on/off. (Thrustmaster joystick as in the sig below, no FFB) System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
Snap Posted May 27, 2017 Posted May 27, 2017 I confirm it's not working as expected in the air since version 2.1.0.5677.215, I see the trim button moving on the stick but it has no noticeable effect on the flight model. Same here (Saitek X-52 Pro)
Beta Sokol Posted May 27, 2017 Posted May 27, 2017 actually using X 52 pro, if i trim, the stick centeres back, but as i said before, it works on ground.
Endmonster Posted May 29, 2017 Posted May 29, 2017 Same problem here with X-52 pro: stick in cockpit moves but has almost no effect. Win10Pro, i7-4770K, 32GB, RTX-2070S OC, VPC WarBRD Base, VPC Mongoos T-50CM2, Warthog Throttles, MFG Crosswind, TrackIR 5
rolandero Posted May 29, 2017 Posted May 29, 2017 Dev here: indeed it has to do with the FFB implementation. For this version you need to disable FFB for the mig (there's a keybind in the controls), not the FFB from the game options. The next patch will fix this problem, the MiG will detect FFB.
Redglyph Posted May 29, 2017 Posted May 29, 2017 Dev here: indeed it has to do with the FFB implementation. For this version you need to disable FFB for the mig (there's a keybind in the controls), not the FFB from the game options. The next patch will fix this problem, the MiG will detect FFB. Thanks! :) The default mapping is RAlt+RShift+J, works nicely. System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR
Recommended Posts