Bungle_uk Posted February 14, 2020 Share Posted February 14, 2020 When attempting to apply trim, the stick moves but no trim is indicated on needles or applied to the jet. Engaging autopilot attitude hold does not hold the jet either. Tested hot start and air start with the same results.trim test.trk Link to comment Share on other sites More sharing options...
fat creason Posted February 14, 2020 Share Posted February 14, 2020 are you using FFB? Did not experience this in testing Systems Engineer & FM Modeler Heatblur Simulations Link to comment Share on other sites More sharing options...
TLTeo Posted February 14, 2020 Share Posted February 14, 2020 I just tried replicating this on my end (T.16000m stick) and it seemed to work fine. Link to comment Share on other sites More sharing options...
Bungle_uk Posted February 14, 2020 Author Share Posted February 14, 2020 (edited) are you using FFB? Did not experience this in testing Not FFB but will check to see if it has reset it to on.. Edit. FFB set to off but issue persists. It must be a local issue as others aren't experiencing it it seems. I am using a Racing wheel (Logitech G25) for rudder pedals so I suspect it is related to that and FFB in some way but will investigate further. It is strange however as it is only affecting the Tomcat of those I have tried (Viggen and AV8B seem ok) Edited February 14, 2020 by 214th_bungle_uk Link to comment Share on other sites More sharing options...
Bungle_uk Posted February 14, 2020 Author Share Posted February 14, 2020 Well, its definitely related to the racing wheel. Removed it and trim was fine. As soon as I plugged it back in, aircraft went haywire. I have noticed a "New feature?" in FFTune under controls. Could it be its trying to apply FFB even when it is unchecked in options? Cant understand why it only has effect with the F14 though. Link to comment Share on other sites More sharing options...
fat creason Posted February 15, 2020 Share Posted February 15, 2020 We do some special stuff to the trim functionality on the tomcat when non-vJoy FFB devices are detected. Can you try disabling FFB on your wheel? Systems Engineer & FM Modeler Heatblur Simulations Link to comment Share on other sites More sharing options...
hawke04 Posted February 15, 2020 Share Posted February 15, 2020 I think it's better to set it as an option of the module instead of automatic detection. Link to comment Share on other sites More sharing options...
Richard Dastardly Posted February 15, 2020 Share Posted February 15, 2020 At least have it check the DCS system FFB setting & stop any special stuff if it's off... Most Wanted: the angry Naval Lynx | Seafire | Buccaneer | Hawker Hunter | Hawker Tempest/Sea Fury | Su-17/22 | rough strip rearming / construction Link to comment Share on other sites More sharing options...
fat creason Posted February 15, 2020 Share Posted February 15, 2020 Not sure we can query that option via the API, but we may look into making it an option. Systems Engineer & FM Modeler Heatblur Simulations Link to comment Share on other sites More sharing options...
probaco Posted February 15, 2020 Share Posted February 15, 2020 Sorry to budge in but I have the same since the update. TM Warthog + logitec G25 racing wheel. Use the pedals for rudder and steering on the ground. Same as OP. When flying it trims to the sky. Trim needle is at 0%. FFB both in settings as in the game are turned off, but still same issue. Removing G25 solves pitch problem, but that is not an option. Need rudders in the F-14. Link to comment Share on other sites More sharing options...
Bungle_uk Posted February 15, 2020 Author Share Posted February 15, 2020 (edited) Yeah. I tried disabling FFB in wheel settings too but no different. Might try that vjoy or joystick gremlin and see if that helps. Edited February 15, 2020 by 214th_bungle_uk Link to comment Share on other sites More sharing options...
probaco Posted February 15, 2020 Share Posted February 15, 2020 Went back to DCS 2.5.5 and trim issue is gone. So it's update related. Link to comment Share on other sites More sharing options...
RuskyV Posted February 15, 2020 Share Posted February 15, 2020 Having the same issues here with a T300RS racing wheel, no FFB enabled and the plane is not trimming. I've noticed that the in game stick shows the trim movement but the trim gauge is not moving. Animation in the cockpit stick is moving but no actual trimming of the plane. Like others have said i cant disconnect my wheel as im using the pedals as rudders. Worked fine before the update... Link to comment Share on other sites More sharing options...
Jedra Posted February 15, 2020 Share Posted February 15, 2020 (edited) I am having the same issue since the update. I am using a TM Warthog. I don't have a racing wheel but I do have a Logitech G940 Hotas plugged in which is a FFB joystick. I use it for the extra buttons on the throttle for PTT. Was not a problem before yesterday's update and it doens't affect any other plane. FFB Mode is not selected in options. Unplugging the G940 USB cable resolves the issue, but this is not an ideal situation as I use it for PTT and VoiceAttack functionality. Edited February 15, 2020 by Jedra Processor : Intel Core i7 7800X (3.8 - 4.2 GHz) . Motherboard : ASUS TUF X299 . Memory : 16Gb DDR4 1333 . Graphics : NVIDIA GeForce RTX 2080 Super (+100 CC +700 MC) . Install : DCS on 500Gb SSD . Screen : 3440 x 1440 display with GSYNC . Control : TM Warthog HOTAS, CH Pro Pedals, Naturalpoint Track-IR . Software : VoiceAttack with VAICOM Pro, DCS BIOS Link to comment Share on other sites More sharing options...
Sofapiloz Posted February 15, 2020 Share Posted February 15, 2020 Same here: Uncheck „use FFB“ Box: same Issue. Disconnect my MSFFB2, NOT assigned to the Tomcat in any Way: solved. Please Fix this, I have to disassemble half of my Huey-simpit to unplug it, not at thing i like to do everytime i want to fly the cat.., Link to comment Share on other sites More sharing options...
kievbsm Posted February 15, 2020 Share Posted February 15, 2020 The same for me - Saitek X-65F. Trims don't work and autopilot doesn't hold altitude. Link to comment Share on other sites More sharing options...
cdjung1 Posted February 15, 2020 Share Posted February 15, 2020 Same issue for me with Warthog HOTAS Link to comment Share on other sites More sharing options...
Blackeye Posted February 17, 2020 Share Posted February 17, 2020 (edited) Here's a workaround that allowed me to use my Sidewinder FFB pedals with the latest patch and have trim working: Download and install vjoystick http://vjoystick.sourceforge.net/site/ and configure it if necessary (reboot might be needed) run a mapper tool for vjoystick - I've used UJR https://github.com/evilC/AHK-Universal-Joystick-Remapper/releases/ others(newer) versions should work as well use the tool to map all axis and buttons (of the ffb device) you need to the vjoystick Edit/Create <User>/Saved Games/DCS.openbeta/Config/autoexec.cfg and add no_device_hotplug = true Run DCS and configure the controls to use the vjoystick instead of the FF device Exit DCS Exit the mapping tool Disable your FF device in the device manager (unplugging might work as well), reboot might be required Run DCS (and enter mission - should work even if you don't) Tab out and enable the FFB device (or plug it in) Run the mapping tool (UJR) Tab back into DCS You now should be able to use the buttons and axis on the FF device via the vjoystick and with hot-plugging diabled DCS/F-14 won't pickup the FF device and use the old trim method. Repeat steps 7 to 12 if you need to (re)start DCS. It's not pretty but it works for me, I can have my pedals and trim working in the F14. Heatblur should definitely add an option for this though :) Edited February 17, 2020 by Blackeye Link to comment Share on other sites More sharing options...
Bungle_uk Posted February 19, 2020 Author Share Posted February 19, 2020 A lot of steps there. Appreciate the guide but I think ill wait for a fix on this one. Until then the tomcat is grounded for me. Link to comment Share on other sites More sharing options...
Jedra Posted February 19, 2020 Share Posted February 19, 2020 I also appreciate the post, but I have also garaged the F14 until Heatblur issue an update! Processor : Intel Core i7 7800X (3.8 - 4.2 GHz) . Motherboard : ASUS TUF X299 . Memory : 16Gb DDR4 1333 . Graphics : NVIDIA GeForce RTX 2080 Super (+100 CC +700 MC) . Install : DCS on 500Gb SSD . Screen : 3440 x 1440 display with GSYNC . Control : TM Warthog HOTAS, CH Pro Pedals, Naturalpoint Track-IR . Software : VoiceAttack with VAICOM Pro, DCS BIOS Link to comment Share on other sites More sharing options...
Jedra Posted February 20, 2020 Share Posted February 20, 2020 Sadly, today's update has not addressed this issue. Processor : Intel Core i7 7800X (3.8 - 4.2 GHz) . Motherboard : ASUS TUF X299 . Memory : 16Gb DDR4 1333 . Graphics : NVIDIA GeForce RTX 2080 Super (+100 CC +700 MC) . Install : DCS on 500Gb SSD . Screen : 3440 x 1440 display with GSYNC . Control : TM Warthog HOTAS, CH Pro Pedals, Naturalpoint Track-IR . Software : VoiceAttack with VAICOM Pro, DCS BIOS Link to comment Share on other sites More sharing options...
Blackeye Posted February 20, 2020 Share Posted February 20, 2020 Unfortunately. That "Fixed trim not working" in the change log got my hopes up...:cry: Link to comment Share on other sites More sharing options...
kievbsm Posted February 21, 2020 Share Posted February 21, 2020 (edited) the same from my side: As you can see the autopilot can't hold the altitude. If I set trimms manulay my plane has no reaction on it and slowly trimms change their positions to full down with the same result... Edited February 21, 2020 by kievbsm Link to comment Share on other sites More sharing options...
Pubicbeard Posted February 22, 2020 Share Posted February 22, 2020 i hope they fix this soon, no point playing the game without my f14 Link to comment Share on other sites More sharing options...
hawke04 Posted February 22, 2020 Share Posted February 22, 2020 2.5.6.43872/43931 not fixed Link to comment Share on other sites More sharing options...
Recommended Posts