BARO/RDR ALT switch issue

[VpR81]

Hi all,

 

Not sure if this is a bug or my install is wasted. I have mapped the BARO ALT and RDR ALT in DCS to use it on my throttle and now recognised since the last update, that the BARO ALT function does not work anymore. Regardless what keybind i'm using, if i toggle the switch on the throttle or use the keyboard, i can now only switch back to barometric altitude by using the BARO/RDR ALT toggle function (or click the switch in the cockpit), but the pure BARO ALT function stopped working. Not realy a big deal as there is a workaround with the toggle function, but i think this should be mentioned. Does anyone else experienced that issue or may this be a install repair case?

 

Cheers

[Greyman]

The 2-way switches on the WH throttle will not work for functions like the one you describe, unless you amend the lua code to add the 2-way functionality. For example, to use the RDR ALTM switch on the throttle to switch between BARO(NORM) and RDR(DIS) you would need to amend the lua code first, to provide a mapping for the button (switch 25) being on and another for that button being off.

 

As you have previously had this working, it looks like you might have applied such an amendment in the past, but an update has reverted to the default lua file and therefore overwritten your changes.

 

Maybe keep the amendments safe, in another file, so that you can copy paste them back in again, after each DCS update?

[CBStu]

Not sure of the correct term but my TM throttle 'radar altm' still works although I am on stable. The switch is weird though. If I start a flight and it is in the forward or 'NRM' position to get the plane to go to RDR I have to move the toggle to it's other position and then back to 'NRM' to get the plane to switch to radar alt.

[VpR81]

The 2-way switches on the WH throttle will not work for functions like the one you describe, unless you amend the lua code to add the 2-way functionality. For example, to use the RDR ALTM switch on the throttle to switch between BARO(NORM) and RDR(DIS) you would need to amend the lua code first, to provide a mapping for the button (switch 25) being on and another for that button being off.

 

As you have previously had this working, it looks like you might have applied such an amendment in the past, but an update has reverted to the default lua file and therefore overwritten your changes.

 

Maybe keep the amendments safe, in another file, so that you can copy paste them back in again, after each DCS update?

 

Not realy. I have not modified my .lua file but have only mapped all 2 and 3 way switches in Target. Master Arm ON/OFF, Refuel probe RET/EXT, Laser Arm ON/STBY/AFT, Hook up/down, everything works fine and proir to the update the altimeter switch did too. I had BARO ALT on the "ON" position of a 2 way switch and RDR ALT on the "OFF" position. And now only the BARO/RDR ALT toggle functions work to go back to baro. And it is not a Target issue, since using the keyboard doesen't work as well for BARO ALT. This is definately a DCS issue unrelated to some .lua manipulation, as i never modified any lua files. Question is, is it a bug or a wasted install....

 

edit: One more thing. Using the throttle switch for BARO ALT in the controls setup does recognise the input (same when using the keyboard), it's just not working as soon as i try in the cockpit. So it has definately nothing to do with Target, my throttle or my keyboard. It is a DCS issue that occured after the last update.

Edited April 28, 2020 by VpR81

[Greyman]

ah, then maybe search for another, unwanted mapping, to a switch that you leave in the same position. If RDR ALT or maybe toggle has been mapped, by the update process, to another one of your switches, then maybe that might explain why it won't move from that setting.

[Greyman]

Not sure of the correct term but my TM throttle 'radar altm' still works although I am on stable. The switch is weird though. If I start a flight and it is in the forward or 'NRM' position to get the plane to go to RDR I have to move the toggle to it's other position and then back to 'NRM' to get the plane to switch to radar alt.

 

Do you have the sychronise controls check box set. Can't remember its exact name, but with that set, the module applies all of your controller switch settings to their corresponding in-cockpit control. If not, the aircraft will adopt all of the default control settings.

[VpR81]

ah, then maybe search for another, unwanted mapping, to a switch that you leave in the same position. If RDR ALT or maybe toggle has been mapped, by the update process, to another one of your switches, then maybe that might explain why it won't move from that setting.

 

I checked the controls again and couldn't find any unwanted mappings. I find it to be strange, that the input via throttle AND via keyboard is recognised in the controls setup, but both input devices do not work in the pit with that mapping. I mapped BARO ALT with LSHIFT + V and RDR ALT with LCTRL + V. I tried to map BARO ALT with other keybinds, still the same problem. Input is recognised in the controls setup, but does not work in the pit. Not when toggling the switch on the throttle and not when pressing the keys on the keyboard.

 

Maybe someone could do me a favor and map BARO ALT in DCS, jump in the pit, switch to radar alt and then try to go back to baro alt with that keybind. I'm curious if it's just my install or if i found a bug...

[Greyman]

You haven't been switched back to the actual TM throttle controller, instead of the virtual one created by Target have you?

[VpR81]

No, i haven't. Always started DCS with the virtual controller already running. You think that a mapping on the actual TM throttle may cause this issue? But how does it come, that using the keyboard doesen't work either... and the inputs are recognised perfectly in the controls setup. That's realy strange...

[Greyman]

I'm not sure, as i don't use Target for my WH, but it might still be worth removing any mappings from the physical one that might interfere. It would only be one or two mappings that you'd need to remove, just to prove that they aren't interfering.

[VpR81]

Ok, i'll give that a try and report. Still curious if other users have the same issue with that function...

[Stubbies2003]

Not realy. I have not modified my .lua file but have only mapped all 2 and 3 way switches in Target. Master Arm ON/OFF, Refuel probe RET/EXT, Laser Arm ON/STBY/AFT, Hook up/down, everything works fine and proir to the update the altimeter switch did too. I had BARO ALT on the "ON" position of a 2 way switch and RDR ALT on the "OFF" position. And now only the BARO/RDR ALT toggle functions work to go back to baro. And it is not a Target issue, since using the keyboard doesen't work as well for BARO ALT. This is definately a DCS issue unrelated to some .lua manipulation, as i never modified any lua files. Question is, is it a bug or a wasted install....

 

edit: One more thing. Using the throttle switch for BARO ALT in the controls setup does recognise the input (same when using the keyboard), it's just not working as soon as i try in the cockpit. So it has definately nothing to do with Target, my throttle or my keyboard. It is a DCS issue that occured after the last update.

 

 

Well the kicker for your success is TARGET itself. Greyman is correct if you are not using TARGET but programming the throttle directly in DCS as the center position is not a switch position. Easily verified thru Windows game controller management. TARGET by virtue of how it worls will allow you to program all.

[VpR81]

Well the kicker for your success is TARGET itself. Greyman is correct if you are not using TARGET but programming the throttle directly in DCS as the center position is not a switch position. Easily verified thru Windows game controller management. TARGET by virtue of how it worls will allow you to program all.

 

I'm aware of that. As i stated above, i have every switch position mapped in target, but for the BARO ALT function, there is no effect ingame since the last update. The input is still recognised in the DCS control settings, but has no effect ingame. Not when using the switch on the throttle and not when pressing the keys on my keyboard.

[VpR81]

So i started DCS without target running but there are no mappings on the physical controller. I clicked on category delete for the Warthog Throttle to make sure i have not missed anything, but the problem remains. BARO ALT function can be assigned and input is recognised in the DCS controller settings, means i press the buttons on the keyboard/toggle switch on the throttle and it jumps to the BARO ALT line in the controller setup, but there is no effect when trying that in the pit. So i'm pretty sure this is either a faulty installation, or a bug that came up with the last update.

 

If anyone could try this out in his settings/pit would be much appreciated. Still thanks for all the attempts to help me out...

[majapahit]

So i started DCS without target running but there are no mappings on the physical controller. I clicked on category delete for the Warthog Throttle to make sure i have not missed anything, but the problem remains. BARO ALT function can be assigned and input is recognised in the DCS controller settings, means i press the buttons on the keyboard/toggle switch on the throttle and it jumps to the BARO ALT line in the controller setup, but there is no effect when trying that in the pit. So i'm pretty sure this is either a faulty installation, or a bug that came up with the last update.

 

If anyone could try this out in his settings/pit would be much appreciated. Still thanks for all the attempts to help me out...

no problem here

[SnapRoll]

I checked the controls again and couldn't find any unwanted mappings. I find it to be strange, that the input via throttle AND via keyboard is recognised in the controls setup, but both input devices do not work in the pit with that mapping.

 

 

The problem you are seeing has most likely to do with the duration your virtual button or switch is being pressed. I've seen this in the F/A-18 that some switches need to be pressed for longer then the default of the "pulse" function in TARGET has set. This is the reason you see it in the setup menu react to your button press and also when you press the key by hand, but not when flying.

 

 

You could use the TARGET function "press" and then "release" with some delay like 50ms or so before the "release" to have the virtual button pressed for longer.

 

 

Just keep in mind that you need to take care that you always follow a "press" by a "release", otherwise everything can get blocked when your keyboard key is being pressed forever afterwards.

[majapahit]

have you renamed/backup your saved games settings folder, DCS rebuild a new one and see if this disappears. could be old version key definitions file/corrupted. your bindings revert to defaults.

[VpR81]

The problem you are seeing has most likely to do with the duration your virtual button or switch is being pressed. I've seen this in the F/A-18 that some switches need to be pressed for longer then the default of the "pulse" function in TARGET has set. This is the reason you see it in the setup menu react to your button press and also when you press the key by hand, but not when flying.

 

 

You could use the TARGET function "press" and then "release" with some delay like 50ms or so before the "release" to have the virtual button pressed for longer.

 

 

Just keep in mind that you need to take care that you always follow a "press" by a "release", otherwise everything can get blocked when your keyboard key is being pressed forever afterwards.

 

Yes, i experienced that as well for buttons, wich is why i use the "pulse" function only for toggle switches. I'm going to try this out. It sounds promising, but still does not explain why pressing LSHIFT+V (my keybind for BARO ALT) on the keyboard does not work either.

 

have you renamed/backup your saved games settings folder, DCS rebuild a new one and see if this disappears. could be old version key definitions file/corrupted. your bindings revert to defaults.

 

No, haven't tried this. But will try this out tomorrow.

 

Thanks again for your help guys! Much appreciated.

 

Cheers

[LTRMcrew]

does LSHIFT+V auto set the baro? such a chore scrolling for long ways if the pressure is quite off from standard...

[SnapRoll]

YIt sounds promising, but still does not explain why pressing LSHIFT+V (my keybind for BARO ALT) on the keyboard does not work either.

Cheers

 

 

Oh, sorry, I miss read this part. If it does not work with the keyboard directly, than it must be something else.

[VpR81]

No problem. Since Majapahits BARO ALT function works as intended, i'm more and more convinced it is a faulty installation/corrupted file. I'm gonna try his suggestion and installation repair. If that wont help, i'll propably give up on this, remap the switch and use the ALT/BARO toggle function instead... Not as nice as the 2 way switch solution, but better than grabbing the mouse for that. However, i will report the results.

Edited April 30, 2020 by VpR81

[majapahit]

does LSHIFT+V auto set the baro? such a chore scrolling for long ways if the pressure is quite off from standard...

I use Baro set and Radar Alt warning straight to TMWH ENG OPER buttons (Up off Dwn).

 

Spawn > RadarAltwarning to 1 tick above Off (else Radar Alt don't work) > set Baro alt to airport < good to go.

[VpR81]

After this post, i'm not sure if this is clear. I'm talking about the RDR/BARO Alt switch for the HUD, to switch between displaying radar and baro altimeter on the head up display...

[majapahit]

After this post, i'm not sure if this is clear. I'm talking about the RDR/BARO Alt switch for the HUD, to switch between displaying radar and baro altimeter on the head up display...

If someone says "set the baro" I just mentoin how I dial in field baro, but you're maybe referring to AP BARO?

Whatever. Of course this is about having problems with his BARO/RDR altimeter switch for HUD, and mine works no problem.

[majapahit]

does LSHIFT+V auto set the baro? such a chore scrolling for long ways if the pressure is quite off from standard...

There is no default LSHIFT+V

I think.

What exactly is your 'auto set the baro'? That rotating the baro knob right?