Draken35 Posted March 9 Posted March 9 I've been trying to make pitch trim work with DCS FFB native for the Spitfire and the P-47 to no avail. I have TelemFFB installed and I use an axis from a trim wheel to control pitch trim. No double bindings or VJOY or similar software installed. Trim tabs and controls animations, work and trimming shows in the control indicator. Both planes feel nose heavy and go into a dive regardless of pitch settings. Any ideas or pointers will be welcome!
Art-J Posted March 10 Posted March 10 Maybe it's a similar issue to the one PawlaczGMD had with his Moza? i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
MAXsenna Posted March 10 Posted March 10 Maybe it's a similar issue to the one PawlaczGMD had with his Moza? OP states Vjoy isn't installed though. @Draken35 have you EVER had Vjoy installed and and added a virtual joystick? If yes, it has to be removed from the Windows device manager, as an uninstallation of Vjoy will not remove it.If no, do you have any other FFB devices connected? Like a racing wheel? DCS ain't fond of that.Cheers! Sent from my SM-A536B using Tapatalk
Draken35 Posted March 10 Author Posted March 10 (edited) 1 hour ago, MAXsenna said: OP states Vjoy isn't installed though. @Draken35 have you EVER had Vjoy installed and and added a virtual joystick? If yes, it has to be removed from the Windows device manager, as an uninstallation of Vjoy will not remove it. If no, do you have any other FFB devices connected? Like a racing wheel? DCS ain't fond of that. Cheers! Sent from my SM-A536B using Tapatalk I had VJOY installed a year or two ago and remember removing the device manually, but I went in to do double check. Nothing in device manager, but good call, this could be an easy gotcha for somebody. Now, I do not have any other FFB device but I used to have a TM Warthog base and your remark triggered my memory of seeing a Thrustmaster FFB driver installed... I just removed it and will test DCS in a bit... I'll update the thread with the results. @Art-J Thanks for looking! That was one the first threads I found with similar issues, before posting. Thanks! Edited March 10 by Draken35 1
MAXsenna Posted March 10 Posted March 10 Quick question. Does the stick move in the correct direction when trimming? On my MS FFB2, I always need to swap the axis under FFB tune in the Controls Settings, and in some modules I had to invert the X and/or Y axis. Sent from my SM-A536B using Tapatalk
Draken35 Posted March 10 Author Posted March 10 (edited) Did a quick test and I don't seen any differences after removing that FFB driver. I actually inverted the pitch axis in the FF Tune/Controls and saw no difference. Stick doesn't move with trimming, but looking at the DCS logs I see this: ERROR INPUT (Main): Joystick VPforce Rhino FFB Joystick {E58621B0-F2B5-11ef-8002-444553540000} set spring autocenter failed! Unspecified error Don't know if that is "normal" or not. Edited March 10 by Draken35 1
MAXsenna Posted March 10 Posted March 10 Did a quick test and I don't seen any differences after removing that FFB driver. I actually inverted the pitch axis in the FF Tune/Controls and saw no difference. Stick doesn't move with trimming, but looking at the DCS logs I see this: ERROR INPUT (Main): Joystick VPforce Rhino FFB Joystick {E58621B0-F2B5-11ef-8002-444553540000} set spring autocenter failed! Unspecified error Don't know if that is "normal" or not.Ah, never seen that error. But that's probably it. It feels nose heavy because the stick is still forward of the trimming point. Might want to ask in the VPForce Discord. DCS can't talk properly with the base is my guess. Sent from my SM-A536B using Tapatalk
Draken35 Posted March 10 Author Posted March 10 21 minutes ago, MAXsenna said: Ah, never seen that error. But that's probably it. It feels nose heavy because the stick is still forward of the trimming point. Might want to ask in the VPForce Discord. DCS can't talk properly with the base is my guess. Sent from my SM-A536B using Tapatalk Yeah, I did... Waiting for a response
Draken35 Posted March 10 Author Posted March 10 Found the culprit. I have all my devices connected to 2 powered USB hubs. I moved the Rhino to an USB port in my mother board, and unplugged the 2 hubs: no error. Next step was to plug each of the hubs individually with the Rhino in the MB. Found which one had the device causing the error and it turned to be an old Ejection Handle made by Cigar Bear coming as "generic usb device" ... Unplugged it, and all its good (quick test in 2d, active pause and the trim wheel axis moves the stick...) @MAXsenna appreciate the help! 1
Recommended Posts