need track replay Throttle at max power at hot start on the ground

[Logan54]

Every time I m using hot start on the ramp I should reset my throttle to idle (even if they at idle). Even  with setings that allow game to check my controls.

 

[draconus]

Some devices do not send any signal until you command first input. The workaround is to click any button or move any axis on the throttle device before clicking "Fly".

[Logan54]

12 часов назад, draconus сказал:

Some devices do not send any signal until you command first input. The workaround is to click any button or move any axis on the throttle device before clicking "Fly".

Tbh this not happens with F-15E, Viper, M2000, MiG-29S but happens with some other planes like MiG-15, MiG-21, MiG- 29A, so this could be not because device issue. 

 

Edited July 28 by Logan54

[MAXsenna]

On 7/28/2025 at 11:01 PM, Logan54 said:

Tbh this not happens with F-15E, Viper, M2000, MiG-29S but happens with some other planes like MiG-15, MiG-21, MiG- 29A, so this could be not because device issue.

Have you set the throttle axis as a slider? 

[Logan54]

1 час назад, MAXsenna сказал:

Have you set the throttle axis as a slider? 

I tried it, no effect. I showed it on video. Problem not in slider imo.

[BIGNEWY]

please include a track replay

[Logan54]

27 минут назад, BIGNEWY сказал:

please include a track replay

Sure, here are F-16C, F-15E, MiG-29A, MiG-29S, MiG-15 and MiG-21.

hot_start_test.trk

[MAXsenna]

22 hours ago, Logan54 said:

I tried it, no effect. I showed it on video. Problem not in slider imo.

Right, so you didn't have it as slider before. Anyway, a throttle is a slider, so keep it as slider.

Only sticks/pedals should be non-sliders. Everything else like throttles, collectives, volume knobs, toe brakes etc. should be sliders.

I assume from your first post that you have tried the "sync with HOTAS at mission start" setting.

What throttle do you have? Have you checked for axis conflicts in the affected modules? It's not clear from your posts. Should have been my first question to be honest.

Cheers! 

[Logan54]

11 часов назад, MAXsenna сказал:

I assume from your first post that you have tried the "sync with HOTAS at mission start" setting

Correct, HOTAS syncronised

11 часов назад, MAXsenna сказал:

What throttle do you have? Have you checked for axis conflicts in the affected modules?

I`m using VKB STECS standard throttle

[MAXsenna]

I`m using VKB STECS standard throttle

Right, that's a dual throttle. For single engines, you only configure one axis, right? And for dual, you set both as sliders, right?
Have you any other peripheral connected that could potentially be in conflict? DCS is notorious for assigning peripherals to the wrong settings.

Sent from my SM-A536B using Tapatalk

[Logan54]

1 час назад, MAXsenna сказал:

For single engines, you only configure one axis, right?

Sure

1 час назад, MAXsenna сказал:

Have you any other peripheral connected that could potentially be in conflict?

I know that axis should work w/o interference. As I said before, different jets work in different ways with hot start. F-15E, F-16, M2000, MiG-29S woks good, but MiG-29A, MiG-21, MiG-15 have max AB with hot start. During my test my STECS was at idle. Issue not in user actions, but somewhere in coding. Thank you.

[MAXsenna]

6 hours ago, Logan54 said:

I know that axis should work w/o interference.

Not sure what you mean by this. I'm asking if you have double checked if you have conflicts. No worries. 

You might find my questions stupid and irritating, while there are reasons for me asking. Not many users have reported this, so I'm just trying to give my recommendations for what have solved it for others in similar cases. For many FC modules I just do what @draconus suggested, to move the throttle all the way forth, and then all the way back. Can't remember last time I had this issue.

You have proved a track. Lest hope ED finds the solution. 

Cheers!