[SWITCH POS REPORTED]TGP and X: Cockpit Argument in Range

[Rowan]

The TGP seems to be causing issues with the "X: Cockpit Argument in Range", not sure if just one specific argument, as I have a list if arguments that need work at once to trigger a flag, or general thing in "X: Cockpit Argument in Range". If I load the mission without the TGP the arguments work fine. I have tried this in three different mission on three different maps all with the same result.

 

I may try separate the arguments at some point and see if it is one specific one, but I am a little bit lazy to do that tbh, it's a bit of a chore.

Edited September 14, 2019 by BIGNEWY

[BIGNEWY]

If you can do a short track replay it would help us.

 

Thanks

[Rowan]

After thinking about it during the day I have some ideas I want to try tonight, so I will get back to you Big.

[Rowan]

Ok, it seems to be these to arguments:

 

-- Targeting Pod, FLIR

elements["pnt_439"] = default_3_position_tumb(_("FLIR Switch, ON/STBY/OFF"), devices.TGP_INTERFACE, tgp_commands.Flir, 439)--, false, anim_speed_default * 0.5, false, 0.5, {0,1})

 

elements["pnt_441"] = default_button_tumb_v2(_("LTD/R Switch, ARM/SAFE/AFT"), devices.TGP_INTERFACE, tgp_commands.Ltdr, tgp_commands.LtdrArm, 441)--, false, anim_speed_default * 0.5, false, 0.5, {0,1})

 

Not sure how a track will help you in this, but if want one I will happily provide one.

[BIGNEWY]

If you could attach a simple mission showing the issue I would appreciate it, it ensures we are looking at the same issue.

 

Thanks

[Rowan]

No problem.

 

TGP OFF is with the TGP loaded, you will see two messages pop up 439, 441.

 

TGP ON is with the TGP loaded, you shouldn't see the messages.

 

Edit: I uploaded the .miz files too, not sure which format you wanted.

TGP OFF.trk

TGP ON.trk

TGP OFF.miz

TGP ON.miz

Edited September 14, 2019 by Rowan

[BIGNEWY]

Edit:

 

I have tested this again this morning and all seems to work as intended, with TGP on I do get the messages when using the switches.

 

Can you take another look, and attach your dcs.log after the attempt.

 

Also if you have not already please remove any unofficial mods and run a cleanup and repair

 

thank you

Edited September 16, 2019 by BIGNEWY

[Rowan]

Seems that when the TGP is not loaded the switch defaults to the middle position, when you load the TGP the default becomes the AFT position, only noticed this behavior now that I went back and had a look at it. Bear in mind this is in the beginning of a cold and dark start. So the triggers on the switches work as they should, just their position changes depending on if the TGP is loaded or not.

 

See attached pics.

 

Just upgraded my hardware and reinstalled DCS, so it should be as fresh as a daisy, no mods.

dcs.zip

Edited September 16, 2019 by Rowan

[BIGNEWY]

Hi and thanks,

 

yes I have reported the switch position to the team.

 

As it looks like it is related to the position of the switch we will mark this reported, hopefully the issue will be resolved in a future patch.

[Rowan]

Thanks mate.