Raven1606688515 Posted May 2, 2019 Posted May 2, 2019 Played DCS the night before and everything working like a charm. The next day opened up DCS to play and no axis control working correctly on joystick and throttle. If you move the axis just a little, it will max out the axis direction. The buttons all function properly. The HOTAS is showing up on the computer just fine. Do have TARGET software loaded, but setup controls in the sims. Tried reinstall HOTAS software, calibrating with TM calibration tool, deleting input.lua files. Nothing seems to work. Also, tested on other flight sims and the same problem. If anyone has any idea's, it would be greatly appreciated. [Phanteks Enthoo Elite Case, Gigabyte Z370 Aorus Gaming 7 MOBO, Intel Core i9-9700K OC 5.1, G SKILL Ripjaws DDR4-3466 RAM 64GB, 3 x Samsung 970 Pro 1TB NVMe M.2, 1 x 4TB HDD, 2 x Gigabyte Aorus GeForce GTX 1080 Ti Waterforce WB Xtreme Edition 11G, Corsair AX1600i Modular Power Supply, 7 x Cooler MasterFan Pro, 7 x Phanteks Fans, Koolance Cooling System, Custom Lighting, Windows 10 Home, Alienware AW3418DW Curved Monitor, TrackIR 5, Warthog Hotas, MFG Rudder Pedals.]
Supmua Posted May 2, 2019 Posted May 2, 2019 Check axis input settings in DCS and make sure you don’t have double binding issues. If you use Target then only TM Virtual device should be used to control these axis inputs. DCS loves to auto-populate axis inputs especially after you add new devices to the PC. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
Raven1606688515 Posted May 2, 2019 Author Posted May 2, 2019 Yeah, did this already too. No duplicate bindings. [Phanteks Enthoo Elite Case, Gigabyte Z370 Aorus Gaming 7 MOBO, Intel Core i9-9700K OC 5.1, G SKILL Ripjaws DDR4-3466 RAM 64GB, 3 x Samsung 970 Pro 1TB NVMe M.2, 1 x 4TB HDD, 2 x Gigabyte Aorus GeForce GTX 1080 Ti Waterforce WB Xtreme Edition 11G, Corsair AX1600i Modular Power Supply, 7 x Cooler MasterFan Pro, 7 x Phanteks Fans, Koolance Cooling System, Custom Lighting, Windows 10 Home, Alienware AW3418DW Curved Monitor, TrackIR 5, Warthog Hotas, MFG Rudder Pedals.]
Supmua Posted May 2, 2019 Posted May 2, 2019 I would redo all the axis bindings in DCS settings, just clear and redo them one by one. See if that works. Also in Target window, click on joystick control panel and open up TM virtual controller properties and try to move axes around and see if it works outside the game. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
Raven1606688515 Posted May 3, 2019 Author Posted May 3, 2019 I've deleted all axis bindings and set them up again already. How do you check Target software to see if axis is recognized? I don't know the software. [Phanteks Enthoo Elite Case, Gigabyte Z370 Aorus Gaming 7 MOBO, Intel Core i9-9700K OC 5.1, G SKILL Ripjaws DDR4-3466 RAM 64GB, 3 x Samsung 970 Pro 1TB NVMe M.2, 1 x 4TB HDD, 2 x Gigabyte Aorus GeForce GTX 1080 Ti Waterforce WB Xtreme Edition 11G, Corsair AX1600i Modular Power Supply, 7 x Cooler MasterFan Pro, 7 x Phanteks Fans, Koolance Cooling System, Custom Lighting, Windows 10 Home, Alienware AW3418DW Curved Monitor, TrackIR 5, Warthog Hotas, MFG Rudder Pedals.]
Supmua Posted May 3, 2019 Posted May 3, 2019 I assumed you have Target running in the background with an active profile when you said you have it loaded. If that isn’t the case just use Windows USB game controller setup and double click on the joystick or throttle that you want to check and see if the axes are working properly when you move them around. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
SGT Coyle Posted May 5, 2019 Posted May 5, 2019 I've deleted all axis bindings and set them up again already. How do you check Target software to see if axis is recognized? I don't know the software. Use the device analyzer under the menu bar of the Script Editor. In it, you'll see the raw DX axis, buttons, and hats input. You don't need to have a script running. If your axis is FUBAR you will see it in the output. Night Ops in the Harrier IYAOYAS
Raven1606688515 Posted May 6, 2019 Author Posted May 6, 2019 Used the Windows UBS game controller setup and Device Analyzer and still the axes are not working correctly. Both the joystick and throttle are recognized in both programs. The buttons work just fine, just axes don't. Don't know what else to do!!!! [Phanteks Enthoo Elite Case, Gigabyte Z370 Aorus Gaming 7 MOBO, Intel Core i9-9700K OC 5.1, G SKILL Ripjaws DDR4-3466 RAM 64GB, 3 x Samsung 970 Pro 1TB NVMe M.2, 1 x 4TB HDD, 2 x Gigabyte Aorus GeForce GTX 1080 Ti Waterforce WB Xtreme Edition 11G, Corsair AX1600i Modular Power Supply, 7 x Cooler MasterFan Pro, 7 x Phanteks Fans, Koolance Cooling System, Custom Lighting, Windows 10 Home, Alienware AW3418DW Curved Monitor, TrackIR 5, Warthog Hotas, MFG Rudder Pedals.]
Supmua Posted May 6, 2019 Posted May 6, 2019 Have you tried different USB ports, or powered USB hub? Try to plug in just one device at a time and test it. One last option before contacting TM support would be to try the Bootloader method (google it). If that doesn't work then it's support time. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
Davee Posted May 7, 2019 Posted May 7, 2019 (edited) Have you tried different USB ports, or powered USB hub? Try to plug in just one device at a time and test it. One last option before contacting TM support would be to try the Bootloader method (google it). If that doesn't work then it's support time. Perhaps reload the latest firmware from TM. Or try the hotboot method. If I can recall - hold trigger in and red bomb release button at the same time while unplugging and replugging your USB cable. Also, plug USB into a USB 2.0 recepticle if your system has it. Edited May 7, 2019 by Catseye
Raven1606688515 Posted May 7, 2019 Author Posted May 7, 2019 (edited) Unplugged from computer and plugged into another computer and the same thing. Yes, tried other USB ports and latest firmware also. NO JOY!! Thanks for everyone's advice on this matter. Edited May 7, 2019 by (+)Raven(+) [Phanteks Enthoo Elite Case, Gigabyte Z370 Aorus Gaming 7 MOBO, Intel Core i9-9700K OC 5.1, G SKILL Ripjaws DDR4-3466 RAM 64GB, 3 x Samsung 970 Pro 1TB NVMe M.2, 1 x 4TB HDD, 2 x Gigabyte Aorus GeForce GTX 1080 Ti Waterforce WB Xtreme Edition 11G, Corsair AX1600i Modular Power Supply, 7 x Cooler MasterFan Pro, 7 x Phanteks Fans, Koolance Cooling System, Custom Lighting, Windows 10 Home, Alienware AW3418DW Curved Monitor, TrackIR 5, Warthog Hotas, MFG Rudder Pedals.]
SGT Coyle Posted May 7, 2019 Posted May 7, 2019 Run this https://www.digitalcombatsimulator.com/en/files/3302470/ on TARGET Script Editor, NOT the GUI. It will just give you axis control as a virtual controller. Try it as a trouble shooting step. See if you get your axis back. If not. You're no worse off. If you do get the axis back, stop TARGET and see if their still working. Good luck Night Ops in the Harrier IYAOYAS
Recommended Posts