Orion 2 throttle will not move in cold and dark startup

[FJR Pilot]

I’m not new to DCS, but I am to the Viper and the Winwing controls. I am using Grim Reapers profiles for the Orion 2 throttle and joystick and presently launching OB 2.9. If I start a free flight, the in-game throttle works fine and moves with my physical throttle. If I try a training mission where I’m started on the tarmac and ready to taxi, it works fine there as well. However if doing a cold and dark startup training mission, my in-game throttle does not move at all. Is this a bug in 2.9 or am I missing something basic here? Thanks!

[Dragon1-1]

In case of the Viper, the throttle will be in idle cutoff on startup. For this to work properly, you need to move the throttle to the idle cutoff position (make sure the rail is properly aligned and the idle cutoff button registers), ideally before starting the mission. Then, when starting up the engine, you need to move the throttle from the cutoff notch to idle. This is how you start the engine in the Viper.

[Slippa]

No expert but I’d check options, see that the bindings are looking as they should be and check if there’s a ‘Viper Sim’ vs ‘Viper game’ setting that makes a difference? I’m not at the pc so can’t check around any better. Since you’ve a shiny new HOTAS, check input titles for WW or Orion?

Might sound obvious but it’s sometimes the easy bits.

good luck with it anyhow.

ETA - Listen to Dragon, sounds more sensible and I really have had a serious lack of sleep for too many hours. Thank you, and goodnight.  

Edited January 9 by Slippa

[FJR Pilot]

Thanks Dragon for the quick reply, however this is not a procedure issue I’m having. My problem is that I can’t move the throttle out of idle cutoff. It’s as if the throttle mapping does not work in the cold and dark training. The binding seems to work in other missions, just not here. If I go into the control bindings, I can see the throttle moving as mapped, but when I return to the sim, the throttle is does not move. 

[Oscarn]

It sounds like you still haven't bound the idle cutoff? It is a separate button and not apart of the throttle axis itself, I don't know how winwing works but the thrustmaster warthog activates a button when you move out of the idle cutoff position. I might be wrong but this sounds like the issue if it's only happening in cold and dark

[FJR Pilot]

32 minutes ago, Oscarn said:

It sounds like you still haven't bound the idle cutoff? It is a separate button and not apart of the throttle axis itself, I don't know how winwing works but the thrustmaster warthog activates a button when you move out of the idle cutoff position. I might be wrong but this sounds like the issue if it's only happening in cold and dark

Thanks Oscarn, I'll take a look at that and post back up.

[FJR Pilot]

27 minutes ago, FJR Pilot said:

Thanks Oscarn, I'll take a look at that and post back up.

So I checked on the mapping for the idle cutoff and as you suspected, it was not mapped. However after mapping it the same situation exists. I realize that the idle cutoff is a function that has to be mapped in order to be utilized. But just for my own clarification, tell me if my assumption here is correct. In a cold and dark Viper, without touching any buttons or starting any startup procedures, I should still be able to physically move the throttle out of it's idle cutoff detent and run the throttle through it's entire range, correct? 

[Oscarn]

That is correct assuming that a button is built into the idle cutoff detent on your physical throttle, I'm not at my computer right now but I can check how I set it up later. As I said though I haven't used winwing before so I'm not sure if you have to do anything different with that, my warthog I just bound it and it worked. When I first load in to the plane I do have to cycle my physical throttle in and out of the detent once for it to be recognised, I do that before I start any of the start up procedure, it could be worth a try 

[LeCuvier]

6 hours ago, FJR Pilot said:

...tell me if my assumption here is correct. In a cold and dark Viper, without touching any buttons or starting any startup procedures, I should still be able to physically move the throttle out of it's idle cutoff detent and run the throttle through it's entire range, correct? 

in a cold start mission, the software needs to "see" the event of the throttle going to the cut-off position. I always start the mission by moving the throttle to cut-off before anything else.

[Razor18]

...and if it is there by default, then it's better to move it up and back down again, so DCS kinda "wakes up" and recognizes the hardware is there. Weird, but it is what it is...

[LeCuvier]

1 hour ago, Razor18 said:

...and if it is there by default, then it's better to move it up and back down again, so DCS kinda "wakes up" and recognizes the hardware is there. Weird, but it is what it is...

Right, it needs to "see" the event.

[rob10]

Because of the way WinWing works (every position has an active button, rather than ON=ON else OFF it's ON=ON, OFF=OFF), I would try ticking the SYNC CONTROLS ON START to ON in the SETTINGS OPTIONS.  It can cause some issues for some users, but I have the F-18 Orion throttle and using the SYNC ON START option means everything goes to whatever position I have all the switches set for.  Occasionally on 2nd launch I'll have an issue with the gear (or due to user error leave a switch in the wrong position when I start and can't figure out why something is happening ), but other than that it works well for me.  IIRC I used to have to do as suggested (move things prior to startup) when I had Thrustmaster.

Edited January 11 by rob10

[FJR Pilot]

Thanks for all the tips!  I'm putting my simpit back together after some mods, so hopefully will be back to testing tomorrow. I will post up my results. 

 

[FJR Pilot]

FINALLY!!  After getting my rudder pedals reinstalled, I was able to do some more testing. I found a video that showed exactly how to map the idle cutoff. It's not difficult, but must be done a certain way. I'm now able to work my way through the rest of the startup checklist. Thanks for all the input.