cannot reproduce King of the hill mission defective

[BaronVonVaderham]

The mission does not allow the aircraft to start up, either manually or via auto startup. When start 2 is selected, the engine spools up to 20%, but after that nothing else. The JFS light does not go off, and moving the throttle to idle out slightly beyond idle, does not start in the engine.

 For info, my throttle quadrant has the idle switch set up for idle, and the off switch for engine off. 
also note that during auto start up I have the throttle on idle. The auto start moves it to off, and to idle when needed. 

[Tholozor]

Wait for the SEC caution light to extinguish before moving the throttle to idle. Engine RPM must stabilize at ~20%, not just reach it.

A track would also help us see what's happening.

Edited September 2, 2023 by Tholozor

[BaronVonVaderham]

I’ll do some more investigation tomorrow. I just noticed that it started happening with another mission too when I tried it a second time. The constant is that I left the physical throttle in idle during startup. 
doggies that becomes an unrecoverable error as restarting the aircraft won’t help. I can recover it by restarting dcs with the throttle in off. 
 

I’ll try to reproduce it tomorrow and post a track. 

[Tholozor]

If the throttle is placed in idle before the RPM stabilizes, it's a hung start. Only way to recover is to shut down and repair.

[MAXsenna]

10 minutes ago, BaronVonVaderham said:

The constant is that I left the physical throttle in idle during startup. 

If you do that in that other sim. You'll set fire to the engine. 

10 minutes ago, BaronVonVaderham said:

I can recover it by restarting dcs with the throttle in off. 

That's correct procedure. Why would the you start the engine in idle when the training mission teaches you not to, or do you mean it's a hardware issue? In the main game settings. Have you enabled synced with HOTAS at mission start? 

[BaronVonVaderham]

5 hours ago, MAXsenna said:

That's correct procedure. Why would the you start the engine in idle when the training mission teaches you not to, or do you mean it's a hardware issue? In the main game settings. Have you enabled synced with HOTAS at mission start? 

I don’t think I did, but I will check. 
as a beginner it’s an easy mistake to make, to not set the throttle back to idle before attempting to start. 
 

I wouldn’t expect the game to remember the problem for a particular mission until I restart the game though. If I restart the mission with the throttle in off, it should work normally again. Soo to me that seems like a bug. 
 

another consideration is that when a training starts in flight, and my throttle is in idle, or off, rather than in mil, this does not become a problem. 
In fact, I tried starting up with auto start with the f-14 once, with throttle in max. And once I let go of the brake, it launched me into the ocean . 

Edited September 3, 2023 by BaronVonVaderham

[BaronVonVaderham]

5 hours ago, Tholozor said:

If the throttle is placed in idle before the RPM stabilizes, it's a hung start. Only way to recover is to shut down and repair.

But this shouldn’t be persistent. If I close the mission and select it from  scratch, and start with the throttle in off, it should be able to perform a start. 
In other words, it looks like the situation is latched in dcs memory. And that to me is a bug. 

[MAXsenna]

1 hour ago, BaronVonVaderham said:

I don’t think I did, but I will check. 
as a beginner it’s an easy mistake to make, to not set the throttle back to idle before attempting to start. 

My bad. I thought you might have done it on purpose. I often fail to do my "physical" pre-flights, so I often end need to restart a mission.  

 

1 hour ago, BaronVonVaderham said:

I wouldn’t expect the game to remember the problem for a particular mission until I restart the game though. If I restart the mission with the throttle in off, it should work normally again. Soo to me that seems like a bug. 

It doesn't. Are you sure the mappings for the keybinds are set correctly? 

 

1 hour ago, BaronVonVaderham said:

But this shouldn’t be persistent. If I close the mission and select it from  scratch, and start with the throttle in off, it should be able to perform a start. 
In other words, it looks like the situation is latched in dcs memory. And that to me is a bug. 

It doesn't, trust me. I'd say, you either have some conflict with mappings, some error in the mapping and/or checked "sync with HOTAS" like I asked you. 

Errors in the mapping could be that, as say some switch is set to to toggle instead of "off/else on" or "on/else off". Several devices are mapped to the same keybind, and then you have selected "sync with HOTAS". 

A track is nice. What devices/throttle do you have? Screenshots of your mappings can also go a long way. 

Cheers! 

[BaronVonVaderham]

4 hours ago, MAXsenna said:

My bad. I thought you might have done it on purpose. I often fail to do my "physical" pre-flights, so I often end need to restart a mission.  

All good . I think it’s easy to get wrong when mixing virtual with real controls.

 

4 hours ago, MAXsenna said:

It doesn't. Are you sure the mappings for the keybinds are set correctly? 

Unfortunately it did with me. Switching the aircraft off in mission and restarting the aircraft from scratch didn’t work, closing and restarting the mission from scratch also didn’t work. The only thing that worked was restarting DCS, hence I believe it’s a bug.

 

4 hours ago, MAXsenna said:

It doesn't, trust me. I'd say, you either have some conflict with mappings, some error in the mapping and/or checked "sync with HOTAS" like I asked you. 

Errors in the mapping could be that, as say some switch is set to to toggle instead of "off/else on" or "on/else off". Several devices are mapped to the same keybind, and then you have selected "sync with HOTAS". 

A track is nice. What devices/throttle do you have? Screenshots of your mappings can also go a long way. 

I’m not using on/ else off/on in any bindings, and I’m fairly certain there are no double mappings of devices for the same binding (I am fully aware of this one, because with each device update, multiple devices automatically get mapped to the same axes.

I’ll have to check the sync with HOTAS option. I’ll do that today. I’ll get a track at the same time.

[MAXsenna]

@BaronVonVaderham
I see. Never heard of it before, which makes me wonder how the mappings are setup. Like with a Warthog throttle, you definitely want to use off/else on in the Viper. It even has a special setting for it. I have the old Cougar, so I currently don't use that feature. Point being, if it's setup incorrectly DCS tends to be confused, especially if the bla bla sync with HOTAS is enabled. Mind me, I love that feature, but quite a few modules have some issue with it. So the switches/toggles sometimes needs to be turned on/off and vice versa, so they actually gets synced.
I'm sure we can solve it. Just screenshot the mappings and provide a track. And again, which throttle.

Cheers!

Sent from my MAR-LX1A using Tapatalk

[BaronVonVaderham]

Did another attempt just now. Recorded the tracks for each attempt. I suspect the inability to start up again may have been associated with me switching to idle just a tat too early.

I will include bindings in a follow up post as I couldn't grab screenshots for some reason ( I don't have  a printscreen button and for some reason the win-shift-S button doesn't seem to work, maybe because by default dcs launches full screen on the main monitor?

As for the TQ, its a winwing F-16 quadrant, 10th anniversary edition.

I set up the sync controls now. Not sure I'll like that as I tend to forget to set up the HOTAS for the start of the mission configuration (and some trainings and missions start in flight, which means with sync on, the LG will extend, and the speed brakes could deploy, depending what I did before)

king of the hill early throttel start no hotas sync reattempt.trk king of the hill early throttel start no hotas sync.trk king of the hill ly throttle in idle start hotas synced.trk king of the hill ly throttle in off start hotas synced.trk

And here are the bindings  

note that I didn’t spot an “on/else…” for the throttle controls  I did see them for other controls though