RazorbackNL Posted September 23, 2016 Author Posted September 23, 2016 (edited) check today's patch :) Sweeeet!! Thank you, ED! Now all we need is to get it implemented into the Ka-50, the Gazelle and every future helicopter mod :music_whistling::thumbup: Edited September 23, 2016 by Razorback[NL] Asus ROG Crosshair VIII Hero (Wi-Fi) | AMD Ryzen 9 5900X @ 4,5Ghz | 128Gb DDR4 3200Mhz | beQuiet! Dark Power 12 1200W | 2 x 2Tb M.2 Samsung SSD | 2 x 4Tb M.2 Samsung SSD | Aorus RTX3090 Xtreme 24Gb | Windows 10 Pro x64 | HOTAS Cougar (heavily modified) | MFG Crosswind pedals | CH Throttle Quadrant | TrackIR5 | Oculus Quest 2 | VoiceAttack Aviate Navigate Communicate
sydost Posted September 23, 2016 Posted September 23, 2016 Hi! I do also have a different problem with this same FFB logic change in the game. My version is 2.0.3.56503. I have a so called PeterP style frankenstick which uses two MSFFB2 joysticks to provide FFB for one stick. See this thread to get an idea of what this DIY stick is like https://forums.eagle.ru/showthread.php?p=1366037#post1366037 . As the MSFFB2 has a deadzone at the center of travel I have used Leo Bodnar BU0836X device for sending the stick position data to DCS World so I have bound my pitch and roll axis to the Bodnar device and the MSFFB2 devices are there only to provide the force feedback (benefit is to get rid of the irritating deadzone and get a better resolution out of the stick). Previously DCS World sent FFB commands to all plugged in FFB devices even no axis were bound to any of the FFB devices and so my DIY device was based on that gimmick but unfortunately it does not work that way anymore. Not a big problem since DCS needs at least one axis bound to one FFB controller for it to send FFB data to all plugged in FFB devices so I can live with it but I was thinking maybe this problem could also be solved . My suggestion is to add FFB on / off toggle to the controls menu's FF tune menu. This way user could toggle on / off FFB devices per module and even select which FFB devices receive the FFB signals. This would give very good control to the user about the FFB and would allow us who prefer the old way to continue to use our DIY devices like we designed those to work. The users who prefer to use FFB on some modules and not on others could also easily do the required selections without the need to unplug the FFB device.
Terrorvogel Posted September 26, 2016 Posted September 26, 2016 My suggestion is to add FFB on / off toggle to the controls menu's FF tune menu. This way user could toggle on / off FFB devices per module and even select which FFB devices receive the FFB signals. This would give very good control to the user about the FFB and would allow us who prefer the old way to continue to use our DIY devices like we designed those to work... +1 ASROCK X79 Extreme11 (WC), i7-4930K (WC), 32GB G.Skill TridentX, Vertex 3 120GB, GTX 980ti, 3x 39,5" Philips 4K, TrackIR 5, TM Warthog with PeterP´s FFB2 Mod, 2xSaitek Throttle, 2x Thrustmaster Cougar MFD Bezel, Simped Vario Pedals modded with toe brakes, Opencockpit Cards, 4x Soundcard, 2x Buttkicker Gamer 2, 4x GTX 950 with tons of touchscreens...
sydost Posted October 6, 2016 Posted October 6, 2016 I'm just wondering did anyone notice the problem I described at post #27 or should I have started a new bug thread about it so it would be noted and maybe corrected eventually. I understand that it is not high priority.
Recommended Posts