markturner1960 Posted November 12, 2021 Posted November 12, 2021 Hi, not sure if this is a hardware or software issue. I was just setting up all the controls for the Harrier, on my new PC and was unable to get the left toe brake axis detected for the left wheel brake when assigning the axis. Which was strange. So I tried in the Hornet, which had it assigned, from when I set up the Hornet controls , some months back on the new PC. When I deleted the old binding, again I was unable to assign the left wheel brake using the rudders axis. So I looked in c0ntrol panel, devices and game controller settings for the rudder, all was well there, The axis was being detected in windows. So why is DCS not picking it up? And only the left one, right one is fine….. thanks System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
dburne Posted November 13, 2021 Posted November 13, 2021 (edited) Have you checked the range of axis movement of that pedal in MFG config software? Possibly could need re-calibrating in MFG software? Edited November 13, 2021 by dburne Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
markturner1960 Posted November 13, 2021 Author Posted November 13, 2021 Hi Don, thanks, did not know there was even a software for the rudders! let me check. Although I calibrated in windows and seems fine there, looks like a DCS thing. Can try in MSFS I guess to confirm that System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
markturner1960 Posted November 13, 2021 Author Posted November 13, 2021 Update, that worked!! Thanks a bunch mate!! System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
dburne Posted November 13, 2021 Posted November 13, 2021 6 minutes ago, markturner1960 said: Update, that worked!! Thanks a bunch mate!! Glad to help - enjoy! Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
No1sonuk Posted November 13, 2021 Posted November 13, 2021 Does the Harrier even have differential wheel brakes?
markturner1960 Posted November 15, 2021 Author Posted November 15, 2021 Well...all not well again. I am setting up a Helo sim pit as well, and ordered rudders for that. As they were newer V3 editions with damper, I swapped them into the hornert simpit. They are detected as V2 rudders and after calibrating, again, all seems fine in windows and the MFG software,BUT........ I cant get any inputs detected for any axis in DCS...... I have emailed MFG support...lets see what they say..... Why is this stuff so complicated...... System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
Lt_Jaeger Posted November 15, 2021 Posted November 15, 2021 15 minutes ago, markturner1960 said: Why is this stuff so complicated...... Why are you breaking stuff all the time
markturner1960 Posted November 15, 2021 Author Posted November 15, 2021 (edited) Ha ha.....yes..with all this hardware comes complications.... Just spent an hour or so farting around, but currently have no functioning rudders or wheel brakes for the Hornet. Going to swap the rudders back around and see what happens...... So....just swapped the rudders around. The old V2 set that were working fine, now also dont work at all, no axis input detected within DCS for rudder or toe brakes.....this set also working fine within the MFG software and windows. I say fine - they are detected and the axis inputs show up within windows test / calibration, under devices, but the raw data range is small and so are the movements shown in the axis window. Not like how they were when it was all working properly. I am starting to think its something to do with the MFG software, as never had any issue up until now with the rudders, was just plug and play.... lets see what MFG support say...... Looks ;like no flying tonight FFS....... Edited November 15, 2021 by markturner1960 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
markturner1960 Posted November 15, 2021 Author Posted November 15, 2021 (edited) I have plugged the new V3 set into another PC, they are detected as a V2 and show exactly the same range of movement ( IE, quite small, not as before) etc as on the sim PC.....if that helps in any way? Edited November 15, 2021 by markturner1960 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
dburne Posted November 15, 2021 Posted November 15, 2021 (edited) You are calibrating only in the MFG software right? Go back to your Windows Joystick setting, and set the rudders to default settings. Do not calibrate there. Then go to MFG software and do your calibration after resetting the Windows setting to default for the pedals. Also insure you are using latest version of the MFG software. Only calibrate in MFG software - ever. Edited November 15, 2021 by dburne Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
markturner1960 Posted November 15, 2021 Author Posted November 15, 2021 Hi Don, I tried that, no difference. What raw values do yours show in the MFG software? Mine are X 1400 - 2100 and Y 1700 - 2300 rZ 685 - 1400. I was just told that DCS looks for max deflection values when it detects inputs, which would explain why DCS cant detect the inputs. The range of values is small and within the middle of the range it should be, which MFG software says should be 0 - 4000. So now just need to figure out why the range is small and how to fix it. This is happening with both sets of rudders as well, so cant be one set faulty..... System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
dburne Posted November 15, 2021 Posted November 15, 2021 (edited) 5 minutes ago, markturner1960 said: Hi Don, I tried that, no difference. What raw values do yours show in the MFG software? Mine are X 1400 - 2100 and Y 1700 - 2300 rZ 685 - 1400. I was just told that DCS looks for max deflection values when it detects inputs, which would explain why DCS cant detect the inputs. The range of values is small and within the middle of the range it should be, which MFG software says should be 0 - 4000. So now just need to figure out why the range is small and how to fix it. This is happening with both sets of rudders as well, so cant be one set faulty..... Mine shows 0 - 4096 in raw value for rZ axis. X and Y are also 0-4096. You did reset the pedals in Windows to default before trying to calibrate in MFG software? Edited November 15, 2021 by dburne Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
markturner1960 Posted November 15, 2021 Author Posted November 15, 2021 (edited) Yes, I did. And uninstalled them from windows and plugged them in a differnt port and re installed them....no difference Edited November 15, 2021 by markturner1960 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
peachmonkey Posted November 15, 2021 Posted November 15, 2021 check this topic out, it has couple of utils to clear up the calibration in the devices, maybe it could be useful for MFG's as well:
dburne Posted November 15, 2021 Posted November 15, 2021 4 minutes ago, markturner1960 said: Yes, I did. And uninstalled them from windows and plugged them in a differnt port and re installed them....no difference Ok - I am sure Milan will get you sorted. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
markturner1960 Posted November 15, 2021 Author Posted November 15, 2021 Just plugged the new V3 set into another PC and getting the same range of data input on the axis there……which is strange, how can the same thing be happening on 2 sets of rudders on 2 different machines? Anyway thanks for the help Don, as you say let’s hope Milan can help. Although no reply to my email yet, which is disappointing……….. 15 minutes ago, peachmonkey said: check this topic out, it has couple of utils to clear up the calibration in the devices, maybe it could be useful for MFG's as well: Thanks buddy, no time now to run these tools etc as I am off to bed, early start….will try on Thursday when back at my sim PC. 1 System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor.
MustangSally Posted November 18, 2021 Posted November 18, 2021 Mark, please, please, please don't use the Windows calibration tool on any of your gear. It's a really easy way to brick your devices. All the later sim gear including the Warthog have their own onboard eprom which requires configuration from their own dedicated software. Only use the Windows game controller app to 'CHECK' that a device is working in windows! Ryzen 9 7950X3D - MSI MAG X670E TomaHawk MB, ASUS ROG Ryujin III 360 AIO 64gig Corsair DDR5@6000, Gigabyte GeForce RTX 4090 AORUS Winwing Super Taurus, Orion2, TO / Combat panels, Collective with Topgun MIP Winwing Skywalker pedals, NLR Boeing Mil Edition Simpit, 55" Samsung Odyssey Ark, Trackir
Dos Posted February 11, 2022 Posted February 11, 2022 @marlturner1960 Hello sir I was wondering if Milan ever got back to you. Because so far, I have had a horrible experience with them. When I got the rudders, the box was soak and since the rudders are not in plastic or any wrap, they were wet. I diligently wipe them dry and wait a few days to plug them in. The website say plug and play but first calibrate so I am thinking this will be easy. I plugged the rudders V3 in and launch the configurator V2.15. When it took forever to load the software, I knew something was not right. When it did load it did not detect the device. I am not getting any reply from Milan. Windows sees them almost everything that senses a device see the rudder except the software to calibrate it. I also tried to update the firmware but that software to does not see the rudders. Has anyone experienced this and has a fix? Thank you Oh yeah, the software sees the pedals as V2 instead of V3 like the engraving.
Recommended Posts