hughlb Posted July 24, 2016 Posted July 24, 2016 It's not an issue with the indicator - both the in-cockpit indicator and the overlay (r-ctrl+enter) show the needle moving up and down. The issue is it's not affecting (not linked to) the aircraft pitch in any way. Trim works here. You might want to check the Trim Elevator indicator to see if it works as intended. Circled red in picture: As you trim "up", the needle moves up from 0 to whatever. A good Trim for takeoff is 2, when empty. up to 8+ when loaded. Hope this helps. | Windows 10 | I7 4790K @ 4.4ghz | Asus PG348Q | Asus Strix 1080TI | 16GB Corsair Vengeance 2400 DDR3 | Asrock Fatal1ty Z97 | Samsung EVO 850 500GB (x2) | SanDisk 240GB Extreme Pro | Coolermaster Vanguard S 650Watt 80+ | Fractal Design R4 | VirPil T-50 | MFG Crosswind Graphite | KW-908 JetSeat Sim Edition | TrackIR 5 | [sIGPIC][/sIGPIC]
Art-J Posted July 24, 2016 Posted July 24, 2016 Yep, trim is not working for me at all, I did a straight and level at constant speed, and ran the trim to its maximum positive and negative value, and the aircraft didn't move at all. I run a Logitech G25 with FFB for Assetto Corsa, and use the pedals as rudders - I think it's probably the FFB on the wheel, but I'm not sure how to fix it without disabling the wheel FFB entirely, which will affect its usage in other games.. any suggestions? Since Alt-J trick stopped working, I don't there's any way of getting around this bug at the moment. I switched from G25 to T500 recently, but turning off FFB in its cpl doesn't help either. At least devs are aware and look into it, but who knows how long we'll have to wait for the fix. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
jmijnen Posted July 24, 2016 Posted July 24, 2016 Trim works mighty fine, even with my FFB joystick. Modules: too many System: I7-7700K, GTX 2080 Super, 64GB DDR4, 500GB SSD, 3TB HDD.
Spectrum Legacy Posted July 24, 2016 Posted July 24, 2016 For temporary fix, you will have to find a way to disable ffb entirely for g25 device when you fly dcs and re-enable it for Assetto or anything else. I don't have the device, so can't guide you step by step... However I would check first the utility software that comes with the wheels and pedals, save/backup all the profiles you currently have and then look if there is any option to turn forcefeedback off in the utility. If not, there might be custom or at least some kind of simple/generic driver without ffb replacement on the web that could allow you to use at least the pedals for dcs. Another chance is it might store the settings in the system registry, so you wouldn't have to swap drivers everytime you want to fly dcs. Basically for dcs, you want to temporarily remove FFB-enabled flag from the second device (g25), so dcs will ignore it and trim will work. Or we can wait and hope that the current implementation will be reconsidered and changed by ED for those who use multiple devices (ffb and nonffb at the same time). Yep, trim is not working for me at all, I did a straight and level at constant speed, and ran the trim to its maximum positive and negative value, and the aircraft didn't move at all. I run a Logitech G25 with FFB for Assetto Corsa, and use the pedals as rudders - I think it's probably the FFB on the wheel, but I'm not sure how to fix it without disabling the wheel FFB entirely, which will affect its usage in other games.. any suggestions? It's not an issue with the indicator - both the in-cockpit indicator and the overlay (r-ctrl+enter) show the needle moving up and down. The issue is it's not affecting (not linked to) the aircraft pitch in any way. Sent from my pComputer using Keyboard
Erk104 Posted July 24, 2016 Posted July 24, 2016 (edited) Yep, trim is not working for me at all, I did a straight and level at constant speed, and ran the trim to its maximum positive and negative value, and the aircraft didn't move at all. I run a Logitech G25 with FFB for Assetto Corsa, and use the pedals as rudders - I think it's probably the FFB on the wheel, but I'm not sure how to fix it without disabling the wheel FFB entirely, which will affect its usage in other games.. any suggestions? Highlb, I have a g25 Logitech to and use it just like you do thiisfixed the issue. Go to run on you computer type in regedit then follow these instructions: I found the issue on my side. I was using a virtual joystick driver which has the force feedback property. I used this registry hack to remove the force feedback property: http://vjoystick.sourceforge.net/site/index.php/forum/5-Discussion/1149-solved-disabling-force-feedback-support#3674 Edit: You can check the dcs.log if a device with force feedback capabilities was detected! I am not a computer programmer however I do know that the regedit function can really break a computer unless you know exactly what your doing. My question is if I remove these and I find out that this is not my problem how do I get these back in? Just rename the entries :) e.g. add '_' before the name This has fixed my problem. Thank you f4l0 Edited July 24, 2016 by Erk104
Again Posted July 25, 2016 Posted July 25, 2016 (edited) Highlb, I have a g25 Logitech to and use it just like you do thiisfixed the issue. Go to run on you computer type in regedit then follow these instructions: This has fixed my problem. Thank you f4l0 SO stupid, he didnt answer! SO stupid this problem isnt going to be fixed! So studid, i got banned from Steam cause i get angry<< first i made a thread, to show MANY peopels using ffb racing wheels as rudders.. than my thread get closed with a video same as another thread "how trim works"<< than i was a bit drunken and scream a bit (sccreeaaaammmm in a threadd) woaw...i scramed so much^^ OK i got banned...MR.K... Anyway...Thank You for your finding..cause other peopel might not could...!!!! Edited July 25, 2016 by Again
Recommended Posts