CannonFodderSE Posted November 12 Posted November 12 I've been doing small mission created with Briefing Room for the Huey. Close to 50% of the time when the mission starts and the helo spawns there is a bang and the main rotor goes flying off without the rest of the helo. Once the mission is running I can choose a new slot or even the same slot and all is good. What can I do to fix this? Any logs I can be looking at? Thanks! Randy Bancroft
silverdevil Posted November 12 Posted November 12 12 hours ago, CannonFodderSE said: I've been doing small mission created with Briefing Room for the Huey. Close to 50% of the time when the mission starts and the helo spawns there is a bang and the main rotor goes flying off without the rest of the helo. Once the mission is running I can choose a new slot or even the same slot and all is good. What can I do to fix this? Any logs I can be looking at? Thanks! Randy Bancroft hello. can you share a track or the mission? AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
Solution MAXsenna Posted November 12 Solution Posted November 12 Hot or cold start?What hardware are you using for throttle/collective?Have you enabled "sync with HOTAS at mission start" in the general settings?Asking because it seems the controls are in a position they shouldn't be at mission start the first time, then they catch up. You can even try to move your physical controls to their limits before you hit "fly".Cheers! Sent from my SM-A536B using Tapatalk
CannonFodderSE Posted November 17 Author Posted November 17 MAXsenna, It is a hot start. If it happens it only happens on first load in to a mission spawning on the runway. I don't change the position of any controls. I can select the next available helo and it does not have a problem when spawning. The cyclic and rudder peddles are at center detentes. Collective is is all the way down with throttle at max. Controls are a Thrustmaster warthog for the cyclic, collective is home made using Freejoy on a STM32 (Blue pill) and the rubber pedal are an Aliexpress special SN-1 also using Freejoy on a custom ST32 board. I can share a mission, but it is not mission specific. I haven't got a track. I'll try to create one tomorrow night with the prop flying off. Thanks, Randy
MAXsenna Posted November 17 Posted November 17 @CannonFodderSE Hi Randy! My computer is dead, alas, so the track would be for anyone else to check. 13 hours ago, CannonFodderSE said: If it happens it only happens on first load in to a mission spawning on the runway Did you check the sync HOTAS at mission start? As it seems the controls only get synced after the first run. Have you set the collective as a slider in the axis tune settings? I think this is the main issue. As this is how DCS works sometimes. If it's not a slider it will always be at 50 percent at mission start. Basically every axis that is not a stick or torque/rudder pedals, should be set as sliders. If it goes from 0 to 100, and not have a middle point like a stick. It's a slider. Cheers!
CannonFodderSE Posted November 17 Author Posted November 17 MAXsenna, I didn't know about the slider option. I'll check it out shortly. In the mean time attached is a zipfile with the mission and two saved tracks. One file (badStart.trk) with a free range rotor and the other (goodStart.trk) with a normal rotor. Thanks, Randy FreeFlyingRotor.zip
CannonFodderSE Posted November 18 Author Posted November 18 Greetings all, Well it definitely not the slider setting. Set both the collective and throttle to slider. Third time the mission launched it went bang and the rotor went sailing of into the wild blue yonder with out me . Thanks, Randy
CannonFodderSE Posted Wednesday at 04:33 PM Author Posted Wednesday at 04:33 PM MAXsenna, You are my hero! It was the "sync HOTAS at mission start." Launch the mission 12 times and not a single free range rotor incident. Don't know why that would not be the default setting. I can't ever remember changing it. Don't think I ever went into that section until now. Thanks! Randy
draconus Posted Thursday at 12:54 PM Posted Thursday at 12:54 PM On 11/12/2025 at 4:04 PM, MAXsenna said: Asking because it seems the controls are in a position they shouldn't be at mission start the first time, then they catch up. So is it a RL feature of a Huey that wrong controls position can end in the such mishap? Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 MiG-29A F-14A/B F-15E CA SC NTTR PG Syria
silverdevil Posted Thursday at 03:07 PM Posted Thursday at 03:07 PM 1 hour ago, draconus said: So is it a RL feature of a Huey that wrong controls position can end in the such mishap? i have some limited flight background. i have never seen a UH-1 preflight checklist. but i would guess, just like AC i am familiar with, there has to be something making one check controls are centered or whatever. imagine if the throttle for any AC was full on and the engine starts. or even minimally. an enthusiast remote control vehicle. don't turn on power prior to centering controls. you piqued my interest and found this https://www.facebook.com/groups/61123668011/posts/10163451232143012/ 17. Test Cyclic then center 18. Test Collective then lower 19. Test anti-torque pedals then center (they spelled pedals "petals"; stupid AI) AKA_SilverDevil Join AKA Wardogs Email Address My YouTube “The MIGS came up, the MIGS were aggressive, we tangled, they lost.” - Robin Olds - An American fighter pilot. He was a triple ace. The only man to ever record a confirmed kill while in glide mode.
Recommended Posts