no bug Immediate Fire Light at Engine Start F1EE

[ST0RM]

As soon as I press the start button, the fire light comes on and stays on. Stock Cold Start Mirage F1EE at Nellis mission

LastMissionTrack.trk

[Vibora]

You're starting with throttle at idle. It should be in the cut position. If you had the throttle at idle, before pressing the start button, you should set it to cut and make a crank before attempting the engine start.

[ST0RM]

2 hours ago, Vibora said:

You're starting with throttle at idle. It should be in the cut position. If you had the throttle at idle, before pressing the start button, you should set it to cut and make a crank before attempting the engine start.

So odd, as I'm using my HOTAS and it's physically in the Cutoff position. I'll visually confirm and recheck my binding. Thank you and I apologize for not catching this. 

[Vibora]

14 hours ago, ST0RM said:

So odd, as I'm using my HOTAS and it's physically in the Cutoff position. I'll visually confirm and recheck my binding. Thank you and I apologize for not catching this. 

You'll probably have to use 'Throttle Cut/Idle switch - Cut while held pressed'.

[MAXsenna]

So odd, as I'm using my HOTAS and it's physically in the Cutoff position. I'll visually confirm and recheck my binding. Thank you and I apologize for not catching this. 

Does your physical HOTAS have a physical cut off switch/detent like the TM Warthog? Bringing the throttle all the way back puts it in idle, not cut off.
Cheers!

Sent from my SM-A536B using Tapatalk

[ST0RM]

1 hour ago, MAXsenna said:

Does your physical HOTAS have a physical cut off switch/detent like the TM Warthog? Bringing the throttle all the way back puts it in idle, not cut off.

It's the WW Orion 2, F-16 setup. 
Honestly, up to the day I posted the thread, I'd never had the issue previously. So I think it's something that changed with my hardware. I'll now visually confirm it's in cutoff. Thanks

[MAXsenna]

It's the WW Orion 2, F-16 setup. 
Honestly, up to the day I posted the thread, I'd never had the issue previously. So I think it's something that changed with my hardware. I'll now visually confirm it's in cutoff. Thanks

Right! I see. Don't know how the WW stuff works. Maybe the binding got unbound?

Sent from my SM-A536B using Tapatalk

[Spooky Mulder]

I've had the issue a good bit over the past year with my Winwing Orion 1.

Something about the Orions seems to initially sync with the F1 oddly in such a way that the throttle is imperceptibly past the cutoff. But enough to allow excess fuel to enter the engine and then fire.

The best, safest way to mitigate this issue is to perform the following:

Quote

Before opening any firewall or fuel valves, use the clickable cockpit interaction to cycle the throttle from cutoff to idle and then back to cutoff.

There's other things I have noticed stopping the issue but this one seems to have a 100% success rate.

Very strange. No idea why this happens with the F1 and seemingly no other aircraft.

[Vibora]

Can you provide a trk where the issue reproduces, please? (A short trk recorded in Caucasus would be ideal).