bmbpdk Posted December 20, 2022 Author Posted December 20, 2022 Problem possibly found: 1: I deleted any bind keys and axis for the rotorbrake, in keys and in axis. 2: The engines spools up fine using the mouse to click off the rotorbrake. 3: I binded a button on my Virpil throttle CM3 for releasing the rotorbrake. 4: The engines spools up fine. 5: I deleted the key and binded an axis instead (I used the Flaps lever on the CM3 throttle). 6: I see the animation and hear the sound. 7: The engines did NOT spool up. 8: I recalibrated the axis in VPC interface. 9: Rebinded it in DCS settings. 10: I see the animation and hear the sound. 11: The engines did NOT spool up. 12: In the same session i mouseclicked the rotorbrake handle on and off. 13: The engines spools up. My hypothesis: The rotoraxis goes to 100% when you push it, and then it "relaxes" back to 99%, making the game read the axis movement, but re-reads it as only 99% without reading that as rotorbrake on and without updating the animation. Perhaps there is a wiggleroom of a few percents we arent show in game or there is an inherent axis bug in the CM3 throttle? My advice/solution: DO NOT have axis as the rotorbrake, ONLY buttons or mouseclicks. Inno3d RTX 2070 Twin X2, ASUS STRIX Z270E Gaming, Intel i7 7700K, 32GB Corsair vengeance, Kingston Hyper X FPS Alloy Cherry MX Red, Logitech G102 Prodigy, Track Ir 5, Thrustmaster Warthog HOTAS, Saitek Combat Rudder pedals, Beyer Dynamic DT770, Acer CB280HK 4K monitor, Win 10 Pro 64bit
LeCuvier Posted December 22, 2022 Posted December 22, 2022 I do use a Virpil Stick , the Original Mongoos T-50. But it does not control anything related to engine start. I don’t have access to my rig this week. When I’m back home I will check if I have a duplicate binding on the rotor brake. However this seems unlikely because in my case only one of the engines fails to spool up. LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
bmbpdk Posted December 22, 2022 Author Posted December 22, 2022 1 hour ago, Flappie said: @bmbpdk Can you please check this? I can confirm that: If i have the RB as a axis (On my Virpil CM3 throttle, the flaps lever), the animation vs input is not synchronised. If i invert the axis in controls/settings, it does not make any difference. 1 Inno3d RTX 2070 Twin X2, ASUS STRIX Z270E Gaming, Intel i7 7700K, 32GB Corsair vengeance, Kingston Hyper X FPS Alloy Cherry MX Red, Logitech G102 Prodigy, Track Ir 5, Thrustmaster Warthog HOTAS, Saitek Combat Rudder pedals, Beyer Dynamic DT770, Acer CB280HK 4K monitor, Win 10 Pro 64bit
bmbpdk Posted December 27, 2022 Author Posted December 27, 2022 On 12/25/2022 at 10:51 PM, Flappie said: Rotor brake axis issue reported. Thank you. Merry Christmas and Happy New Year! 1 Inno3d RTX 2070 Twin X2, ASUS STRIX Z270E Gaming, Intel i7 7700K, 32GB Corsair vengeance, Kingston Hyper X FPS Alloy Cherry MX Red, Logitech G102 Prodigy, Track Ir 5, Thrustmaster Warthog HOTAS, Saitek Combat Rudder pedals, Beyer Dynamic DT770, Acer CB280HK 4K monitor, Win 10 Pro 64bit
LeCuvier Posted December 28, 2022 Posted December 28, 2022 On 12/20/2022 at 8:48 PM, Flappie said: Let's summon him. @LeCuvier Hi, can you please tell us if you have some Virpil hardware? We're trying to udnerstand why you too get this strange failure during aircraft startup. I reported this issue for BS-2 and I never found the cause of the issue. It still occurs when I run auto-start in the mission "Death Valley" with the BS-2. However, I made a copy of the mission and switched the helicopter to BS-3. Auto-Start now executes perfectly. As I will not fly the BS-2 going forward, I consider the issue as closed. 1 LeCuvier Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5
Recommended Posts