dcs-skunkworks / dcs-bios Goto Github PK

The V/UHF, VHF, VOR, NAV, and ADF knobs do not work as expected via DCS-BIOS Control Reference Live Preview with the C101CC.

V/UHF - Cannot set a new set_state and have it be properly represented in DCS set_states higher than 2 only INC.
VOR/NAV - INC, DEC, and set_state only INC. Cannot set a set_state.
ADF - Most changed values in the Live Preview are either not reflected ingame, not reflected in the Live Preview, or both. In at least two cases, changing a Live Preview value will result in a different Live Preview being changed.

An unknown number of C101EB UHF commands change C101CC UHF rotary positions.

Just stumbled across these. I don't fly the module too much but another user of my software that uses DCS-BIOS noticed some issues.

1. /METHANOL_WATER _PRES_VALUE has a space in the middle of it
2. I'm not sure what's going on here, but IGN_ON doesn't seem to work (and BAT_ON, and potentially others)
   
   

The ignition and seat height switches on both the front and rear cockpit of the C-101 are three position switches, where the central position is OFF, but in DCS-BIOS they behave as two position switches making impossible two access all three positions.
On the control reference page they only have one pin but they should have two.

This means that on the seat height switch is only possible to select the "up" or "down" positions not the "off", so the seat is constantly going up or down and can’t be stopped at a middle position. Same with the ignition switch, the “off” position can’t be selected.

The non-working switches are:

FRONT_CONT_ING_START
BACK_CONT_ING_START
FRONT_SEAT_HEIGHT
BACK_SEAT_HEIGHT

It is not reading the acceleration values ​​correctly, in previous versions it worked correctly. Thank you.

I noticed the following status lights are missing from the Viggen:

• AFK enabled light (not the AFK warning light on the caution panel)
• AFK 15deg aoa light
• falld last light (no stores remaining)
• transsonic flight light
• afterburner stages 1-3 lights

Has anybody found a good way to deal with magnetically-held switches? The hornet, for example, has plenty of these (e.g. APU control switch and engine crank switch). When using the set_state bios command, it seems to fix the switch in that state until it is manually moved to a different state, even though the switch should automatically disengage when certain aircraft parameters are met. It makes sense to me why bios does this, however I'm wondering if there is some sort of command that can be sent that hands control of the switch back to the game or something.

I get the Agrument changes but cant send any inputs

The NS430 seems to be the only module I can't get to work, from the chrome extension app I cannot control or receive any switch position info from the NS430. I do have the Mi8 and Hind working though.

Thanks

The hornet has L0, L50, L100, R50, and R100 texture outputs, but no R0 texture output.

Side note - do you know which bios code should be used to get the nozzle position on the IFEI? I couldn't find it anywhere. I've been using EXT_NOZZLE_POS but I'm not sure if that's exactly what's on the IFEI (e.g. at very low nozzle positions like 3%, the IFEI reads 0% - but that may just be a resolution thing).

Also potentially missing:

• The fuel_up/down gauges should have an L/R texture as well I believe, which I couldn't find either.
• In Time Set Mode on the IFEI, the output corresponding to txt_T is missing

This means that anybody cloning the master branch will need to manually modify biosdevmode in order to get the json files to regenerate.

I'd suggest either modifying the default behavior or documenting this feature; it stumped me for a few minutes.

The targeting mode reset button doesn't work.
It's being pressed in the cockpit but the button LED doesn't light up and nothing happens.

This is a weird one (and potentially a module bug?) - the A-10C II "Toggle Steerpoint" AAP_STEER control does not seem to functionally work. What's weird is that changing the value in dcs-bios works, and you can see the switch move in game, and dcs-bios shows the value of the switch in game - but the switch doesn't do the thing it's supposed to do when you use dcs-bios.

Example:

1. Load into A-10C II Takeoff Instant Action
2. Look at AAP and left/right-click the steerpoint switch. Then look at the HUD and notice the active steerpoint has changed.
3. Now do the same with dcs-bios. Notice that while the switch moves, the active steerpoint doesn't actually change.

The picture above is when FRONT_ROCKET_MODE 0 is used from the Live Previewer. This switch should not have a center position like that. It is a three way switch, the directions indicated by the cutouts.

FRONT_ROCKET_MODE 1 goes to the "Train" position.
FRONT_ROCKET_MODE 2 goes to the "2" position.

Since the 2.7.7 update (10/20/2021), the tomcat is broken.
They surely have changed the ids.

I've discovered it when trying to press the cap buttons...

UH-1H/WIPER_SPD currently only offers fixed_step adjustment and not set_state. Is this something that can be added, or is it up to the module to implement?

Seems to be a simple copy-paste error, I believe this is the problematic line https://github.com/DCSFlightpanels/dcs-bios/blob/f2b9f8e88343f1cda02860e28ede65da435e791e/Scripts/DCS-BIOS/lib/VNAO_T-45.lua#L34

Just improved some logging on my end and found a few more problem names... they all have whitespace where they shouldn't. This should be all of them!

https://github.com/DCSFlightpanels/dcs-bios/blob/fdeebac9429e951b831128426fe7d40cf1dc18f7/Scripts/DCS-BIOS/lib/A-4E-C.lua#L267
https://github.com/DCSFlightpanels/dcs-bios/blob/fdeebac9429e951b831128426fe7d40cf1dc18f7/Scripts/DCS-BIOS/lib/Mi-24P.lua#L642
https://github.com/DCSFlightpanels/dcs-bios/blob/fdeebac9429e951b831128426fe7d40cf1dc18f7/Scripts/DCS-BIOS/lib/VNAO_T-45.lua#L243

C-101CC/Colimador:

• C-101CC FRONT HUD Depression 0XX C-101CC/CC_FRONT_HUD_DEPRESS_0XX
• C-101CC FRONT HUD Depression X0X C-101CC/CC_FRONT_HUD_DEPRESS_X0X
• C-101CC FRONT HUD Depression XX0 C-101CC/CC_FRONT_HUD_DEPRESS_XX0

The "set_state" for the above controls via the Live Previewer do not work as intended. When "set_state" is above zero, they increase by one. When "set_state" is zero, they decrease by one.

In addition, the "set_state" for C-101CC FRONT HUD Depression 0XX goes from "0" to "9", but there are only 3 positions that the dial can be in.

Image of the Depression Selector for reference:

Hi there!

I'm developing a plugin for Touch Portal and need to process the data stream coming form DCS-BIOS to create the correct messages to be sended to TP.
But there is something I'm missing when I read the Developer Guide, because if I try to process the data manually, usin pen, paper and calculator, I can't find the correlation between the information received and charts of data available in the airplane json file, the CommonData, the MetaDataStart and the MetaDataEnd json files.

Here you can see the a couple of datagrams sorted in 16 bits words;

00-14------------20
00-02------------2
20-20------------8224
04-4A------------1098
00-04------------4
00-0F------------15
03-C8------------968
74-A0------------29856
00-02------------2
A0-20------------40992
STREAM END
00-16------------22
00-02------------2
20-20------------8224
04-00------------1024
00-04------------4
2E-30------------11824
2E-37------------11831
04-4C------------1100
00-02------------2
03-CC------------972
74-A0------------29856
00-02------------2
STREAM END

The left side are bytes pairs in big endian to match with the address showed in the Advanced view of the DCS.BIOS Web console.
The right side are just those 2 bytes converted in ushort numeric type.
I know that only the addresses would follow this simple conversion, but looking at the json files (F18, CommonData, MetaDataStart and MetaDataEnd) I can't find any of those ushort numbers as a valid address in the named files.

Ok, to be precise I could found one: 74-A0 is the Hook Lever and 00-02, if I undo the non-Little endian operation, is the mask to be applied.

But that is the only address I could find, so I know that I'm missin something very simple but very important and after several hour of test and fail I can't find what is it.

You could argue that not all the data exported fits in 16 bits, string data for example, yes I know it.
But the very first 16 bits of each datagram are the begining of the packet, just without the four 0x55 characters which mark the start of a new packet, and I can't fing any address correponding with the bytes 0x0014.
Then I can't start to process the information of the packet because I don't know what mask or shift need to be applied.

Could you help me to understand what I'm missing?
Thank you very much and sorry for the long post.
Cheers!

Currently the Yak-52 has the key FRONT_RADIO_VOL used for two separate controls. Is this intentional? I have no experience in it, but my understanding was that all keys should be unique (per aircraft). If I sent a command to DCS-BIOS to update FRONT_RADIO_VOL, which control would be updated?

Changing this could also potentially be a breaking change for somebody.

----- SPU-9
definePotentiometer("FRONT_ICOM_VOL", 28, 3001, 80, {0, 1}, "SPU9", "Fore Intercom Volume Knob")
definePotentiometer("FRONT_RADIO_VOL", 28, 3004, 81, {0, 1}, "SPU9", "Fore Radio Volume Knob") -- here
defineToggleSwitch("FRONT_ICOM_STBY_DISTR_SW", 28, 3007, 82,"SPU9" , "Fore Intercom STBY Distributive Switch")
defineToggleSwitch("FRONT_ICOM_RDF_SW", 28, 3009, 83,"SPU9" , "Fore Intercom RDF Switch")
----- BAKLAN-5
definePotentiometer("FRONT_RADIO_VOL", 27, 3002,  90, {0, 1}, "BAKLAN-5", "Fore Radio Volume Knob") -- and also here
defineRotary("FRONT_RADIO_MHZ", 27, 3011, 88, "BAKLAN-5", "Fore Radio Tune mhz")
defineRotary("FRONT_RADIO_KHZ", 27, 3008, 89, "BAKLAN-5", "Fore Radio Tune khz")
defineToggleSwitch("FRONT_RADIO_SQ", 27, 3020, 91,"BAKLAN-5" , "Fore Radio Squelch")

When trying to monitor the status of the pitot tube buttons, for example, I press Main Pitot Heating On, but Standby Heating Off is toggled in the DCS-BIOS Live Preview. I get different, but still odd and incorrect results when trying to modify the panel using Live Preview. I cannot determine the logic. It does not seem like a simple switch of two numbers.
Effected Controls: (L-39ZA/Electric System)

• Standby (Left) Pitot Tube Heating OFF Button L-39ZA/PITOT_HEAT_OFF_L
• Main (Right) Pitot Tube Heating OFF Button L-39ZA/PITOT_HEAT_OFF_R
• Standby (Left) Pitot Tube Heating ON Button L-39ZA/PITOT_HEAT_ON_L
• Main (Right) Pitot Tube Heating ON Button L-39ZA/PITOT_HEAT_ON_R
  DCS-BIOS 0.7.38

I just came across this issue in the base dcs-bios repo. I'm curious - is this something that should be fixed? I've worked around it in my usages, but it is frustrating when bingo 500 sends as 500__ but is supposed to be displayed right-aligned on the IFEI as __500 (underscores indicate spaces, since github markdown trims spaces in code formatting).

The channel knobs for the AV8B don't work with the PZ069.

Current version of DCS-Bios and Flightpanels.

How can I see if DCS-Bios picks up the changes made in game?

I'm really not sure how this happened, but even though I'm in an A-10C, dcs-bios is also sending data for the F-14B. This is in a fresh launch of the game where I haven't flown the F-14B yet.

hi,
on radio panel , uhf , vhf & vor knob show selection with error

uhf : 1 on DCS , 0 on saitek ( -1 and 0 exist )
vhf : 2 on DCS , 1 on saitek (-1 )
vor : 108.3 on DCS , 109.3 on saitek (-1 )

From Discord:

In bios P-47: The commands "Recovery Flaps Switch Cover" and "Recovery Flaps Switch" do not work. Instead they move the "ARM & SAFE (BELLY)" switch. (DCS-BIOS_0.7.38 & DCSFlightpanels_x64_4.2.10)

In bios P-47: The command "UV Instruments Light Rheostat" at the maximum value moves the knob by 15%. (DCS-BIOS_0.7.38 & DCSFlightpanels_x64_4.2.10)

hi,
speed return from dcs-bios is different from HUD SPEED in dcs
same thing with MACH which is really really different ...

F-16 FUEL_QTY_SEL_KNB not switch to TEST

A-10C/TACAN_CHANNEL
A-10C/ILS_FREQUENCY_S

does not show the middle segment on the display - for example, "0" instead of "8" - in all digit

Hi! Improving DCSFlightpanels. Where did the "Copy"/"Clone" button go:thinking: ? It's a very handy button.
And a suggestion to expand the functionality:sunglasses: : add buttons "Up" and "Down" to move the necessary lines up or down.

Parkbrake Handle is not working via live preview

https://github.com/DCSFlightpanels/dcs-bios/blob/59ee8fa751df4ea90a7de7bc3651302eb3648c91/Scripts/DCS-BIOS/lib/Mi-24P.lua#L126

I believe the ID should be 229 instead of 299.

For reference, this is from the lamps.lua DCS file:

R_GEAR_DN_P							= create_warning_lamp(229,	Warning_Lights.FLAG_R_GEAR_DN_P)

Hi

I'd like to be able to use DCS-BIOS to send the odd HOTAS command, particularly at the moment I'd like to send commands for the Dogfight/Missile override switch in the F16.

Possible at all?

Thanks

F-5

define3Pos2CommandSwitchF5("AUTOBAL", 4, 3006, 3007, 383, "Fuel", "Autobalance Switch, LEFT/NEUT/RIGHT")

not fully functional,
Left right ok
neutral dont work, only via double left/right

I haven't looked too closely into what's going on here, but incrementing/decrementing VHFNAV_KHZ seems to also affect the state of VHFNAV_VOL in BIOS (though, not visually in game). While these controls are situated on top of each other in the module, modifying one should not modify the other.

Edit: It appears there is also a similar problem with VHFNAV_MHZ and VHFNAV_PWR

Repro steps:

1. load into Huey
2. open UH-1H > VHF NAV Radio in BIOS
3. press INC/DEC for VHFNAV_KHZ
4. observe state of VHFNAV_VOL changes by variable step suggested step amount

EMERG_GEAR is present in two places. I'm not familiar with this aircraft as I don't own it, but looks like just a naming collision.

https://github.com/DCSFlightpanels/dcs-bios/blob/281f8d8116f99082ee94301c7c3539757b1cdd66/Scripts/DCS-BIOS/lib/MiG-19P.lua#L210
https://github.com/DCSFlightpanels/dcs-bios/blob/281f8d8116f99082ee94301c7c3539757b1cdd66/Scripts/DCS-BIOS/lib/MiG-19P.lua#L355

DCS recently did some revamping of the A-10C and released it as the A-10C II. As far as I can tell dcs-bios works fine with it, but there is a small inconsistency: dcs-bios reports ACFT_NAME as A-10C_2, however it uses the same A-10C json files and lua files as far as I can tell.

I would suggest one of two solutions:

• A-10C_2.lua file (this makes sense as DCS has separate mappings available for the A-10C vs the A-10C II, and treats them like separate aircraft, since I think the A-10C II has extra capabilities and things to map)
• Change the ACFT_NAME that is output for the A-10C II to just be A-10C

To be clear: this isn't causing anything in dcs-bios to break currently. Some code that I wrote makes some assumptions about the data dcs-bios sends, and that has broken. If you feel dcs-bios should behave exactly as it does currently you're welcome to close this issue - but I do feel this is an inconsistency worth addressing.

hi,
using RAD_GAIN_DIAL move RAD_CHAN_B button almost gain button in cockpit
move gain button in cockpit change right values in dcs-bios

FRONT_BOMB_REL_SEL 0 puts the switch in the position shown in the picture instead of full down. FRONT_BOMB_REL_SEL 1 puts the switch up (which is correct).

It may be an animation argument error.

When using the Live Previewer, the "Current Value" is not shown for the Radar Altimeter High Setting. There may be an issue with the DCS model because the knob does not stop turning if you manually turn it past the bottom (zero feet).
UN-1H
Front Dash
Radar Altimeter High Setting (UH-1H/RADAR_ALT_HI)

Similar issue as #35.
UH-1H
Doors
Door Left (UH-1H/DOOR_L-PTR)
Door Right (UH-1H/DOOR_R-PTR)
When using the live previewer, INC, set_state 1, and TOGGLE work as toggles.
DEC and set_state 0 do not work.

The mapping for the cargo release safety on the overhead panel does not seem to exist. I think the entry should be something like

defineToggleSwitch("CARGO_REL", 12, ???, 228, "Overhead Panel", "Cargo Release OFF / ARM")

but I just don't know enough about how these entries work to say for certain.

UN-1H
Flex Sight
Pilot Sight Armed / Safe (UH-1H/SIGHT_ARM_PLT)
When using the live previewer, every button seems to act as a toggle instead of fixed_step or set_state.

Hi there,

Asked about STM32 support in the original Arduino library repo a while back, seems no one is active there.
Was looking yesterday and just happened to see that there was a pull request there from someone who had added STM32 support.

Given the depth of my panels the Arduino mega 2560 has run out of space, is there any chance this repo could include the changes that allow STM32 support?

Are the devs here open to other suggestions / requests?

Thanks for your effort,
Virt.

I have a program that loads in DCS BIOS's configuration data for its own use, and I noticed when running it on the latest version of DCS BIOS that the key LIGHTS appears twice in VNAO_Room. I don't know anything about VNAO_Room so feel free to close if this is intended, but this is the only duplicate key issue in all of the modules so I'm assuming it's not intended.

Offending lines in VNAO_Room.lua:
18: defineToggleSwitch("LIGHTS", 6, 10003, 387, "Systems", "Light Switch")
29: defineFloat("LIGHTS", 387, {0, 1}, "Gauges", "Lights")

F-16C Radio Channel Frequency is not exporting any data, just shows nothing. Data exports on other modules(A-10C, FC Aircraft) and other values on the F-16C module properly export/import.

F-16C Module using DCS OB and DCSFP V07.40

In the browser plugin and with hardware(used encoder, works fine), the EHSI CRS Set Knob only increases with an input.

Go to browser plugin and try changing the CRS Set Knob with INC and DEC and you will see the issue.

I will see if other F-16 encoders are borked and report back if I actually do work to find issues.

When the day/night switch is set to night, the lights are dimmed. By my testing, it looks like the value is ~0.38, which is less than the 0.5 threshold for sending a 1 for a light (when the day/night switch is set to day, the value is ~0.95).

Has any thought been given to sending 0-65535 for lights? I tested the code on my end and it seems to work just fine, but could definitely be a breaking change for many (I know things of mine would break).

At any rate, I think the simple fix would probably be to change this line from 0.5 to something smaller like 0.1
https://github.com/DCSFlightpanels/dcs-bios/blob/59ee8fa751df4ea90a7de7bc3651302eb3648c91/Scripts/DCS-BIOS/lib/Util.lua#L290
(and probably change the corresponding inverted method to 0.9)
https://github.com/DCSFlightpanels/dcs-bios/blob/59ee8fa751df4ea90a7de7bc3651302eb3648c91/Scripts/DCS-BIOS/lib/Util.lua#L322

Hi,

DcsBios::LED nmspHarsBtn(0x1110, 0x0100, PIN);
A-10C/NMSP_HARS_BTN

hi,
if possible , adding frequencies at left screen from preset in radio module ?