dresoccer4 Posted October 10, 2021 Posted October 10, 2021 I seem to need to have the pitch trim almost full forward to maintain stick-neutral level flight (FFB). Is this correct? 1 Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
dresoccer4 Posted October 10, 2021 Author Posted October 10, 2021 4 hours ago, nick10 said: Nope. What trim settings are other people using for straight and level? Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Art-J Posted October 10, 2021 Posted October 10, 2021 52 minutes ago, dresoccer4 said: What trim settings are other people using for straight and level? About 2,2 divisions nose down, but that's with non-FFB stick (Thrustmaster Warthog) at usual power settings (between +7 lbs and +9 lbs of boost and ~2600 to 2800 RPM). 1 i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
SMH Posted October 11, 2021 Posted October 11, 2021 Disable FFB and it'll go to about +2, which is still way too far forward. FFB just doesn't work well in many DCS modules. And there's none of them where it doesn't throw off my trim settings. (We really need an X/Y FFB bias option in the Controls Options to adjust the hands-off centering position of the stick.)
hazzer Posted October 12, 2021 Posted October 12, 2021 @NineLine could this perhaps be added to the list of to - do items? The ffb effects in dcs generally are amazing and add so much to the aircraft (especially piston aircraft, but also the jets, force trim etc). The issue comes with the axis positions, trimming, curvature, resulting in having to add saturation or issues like the above. It would be amazing if these few things could be ironed out, as although not produced at the moment lots of people actually use ffb in dcs as it is great. RTX 2080ti, I7 9700k, 32gb ram, SSD, Samsung Odyssey VR, MSFFB2, T-50 Throttle, Thrustmaster Rudder Pedals
dresoccer4 Posted October 20, 2021 Author Posted October 20, 2021 this definitely feels off. when i lower flaps on base the plane pitches up so hard that I have to trim it literally all the way down for it to want to bring the nose down enough to descend. it reallllly wanted to keep ascending and i let it go for a while and it flew itself all the way down <80mph before she lowered her nose. it was actually pretty impressive how slow she flew. but not good for landing. in the screenshot you can see full forward trim and flaps down and I'm still pressing forward to get a decent descent. anyone else come across this way? Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Nealius Posted October 20, 2021 Posted October 20, 2021 1 hour ago, dresoccer4 said: anyone else come across this way? I would say it's definitely an FFB issue. My 20cm extended Warthog (no FFB) I don't really need to touch the trim much at all when configured for landing, and I'm almost always somewhere between 1 tick and 2 ticks nose down trim for all regimes of flight.
dresoccer4 Posted October 20, 2021 Author Posted October 20, 2021 1 hour ago, Nealius said: I would say it's definitely an FFB issue. My 20cm extended Warthog (no FFB) I don't really need to touch the trim much at all when configured for landing, and I'm almost always somewhere between 1 tick and 2 ticks nose down trim for all regimes of flight. I wonder if it has anything to do with my curves. I have it set pretty off-default to try and mitigate the twitchiness. Only other thing I could think of that's different besides FFB. Do devs every check these forums? I wonder if they could chime in as this is a pretty big issue for me atm Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Nealius Posted October 20, 2021 Posted October 20, 2021 That might exacerbate the problem. I run a deadzone of 3, curvature of 10 or 15, Saturation X and Y both default 100.
Art-J Posted October 20, 2021 Posted October 20, 2021 (edited) ^ I can confirm. Using extended Warthog with some small curvature (up to 15%, I don't remember) and full saturation, I never have to go beyond 2.5 ticks, so it's either FFB-related problem (I recall warbird modules tend to be a mixed bag with FFB implementation when someone wants to put curves on top), or saturation-related one, or both. Worth investigating and reporting, though. Edited October 20, 2021 by Art-J i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Weta43 Posted October 20, 2021 Posted October 20, 2021 3 hours ago, dresoccer4 said: I wonder if it has anything to do with my curves. I have it set pretty off-default to try and mitigate the twitchiness. Only other thing I could think of that's different besides FFB. Do devs every check these forums? I wonder if they could chime in as this is a pretty big issue for me atm You can't use curves with E.D. FFB - the FFB doesn't get 'curved' so the stick position and FFB get out of synch & the trim stops working correctly. Always been that way since LOMAC 1 Cheers.
dresoccer4 Posted October 20, 2021 Author Posted October 20, 2021 7 hours ago, Weta43 said: You can't use curves with E.D. FFB - the FFB doesn't get 'curved' so the stick position and FFB get out of synch & the trim stops working correctly. Always been that way since LOMAC gotcha, at least this proves my theory. I've never had to change any curves with any of the other modules so this was the first time I've encountered it. Time to remove all the curves Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Recommended Posts