dcs-bios
dcs-bios copied to clipboard
DCS-Skunkworks
F-14B: Values out of range
NS430 values
Util.lua: value -4356.000000 is too small for address 1540 mask 65535
F-14 values
Util.lua: value -1.000000 is too small for address 4652 mask 32768
Util.lua: value -13616.000000 is too small for address 4908 mask 65535
Util.lua: value 66524.000000 is too large for address 5218 mask 65535
Util.lua: value 66527.000000 is too large for address 5224 mask 65535
Util.lua: value -65535.000000 is too small for address 5296 mask 65535
saw these a handful of times
Util.lua: value -26.000000 is too small for address 5000 mask 65535
Util.lua: value -26.000000 is too small for address 5178 mask 65535
4652 mask 32768
RIO_TACAN_MODE_NORMAL_INV This switch seems to be in -1 upon spawning in (at least in a hot start), but toggling it removes it from this state. May be a module bug.
4908 mask 65535
PLT_SWEEP_POS seemed to go away after adjusting wing sweep - so maybe an issue with the initial module state again? (fun fact, if you use your mouse wheel to scroll the wing sweep adjust down to 0, it will loop back around to the top lol - somebody should probably file a bug report with heatblur)
5218 mask 65535
RIO_DDD_RANGE_ROLLER only occurred a handful of times shortly after spawning in
5224 mask 65535
RIO_TID_STEER_ROLLER only occurred a handful of times shortly after spawning in
5296 mask 65535
EXT_YAW_STRING_LR @jdahlblom could you check out this one with insight? Draw argument 2500. Looks like this one is outputting -1, but I'm not aware of any draw arguments that output <0 (and I don't think we support that anywhere 🤔 )
FIXED 5000 mask 65535
PLT_FUEL_TOTAL_1 Not sure what's going on with these gauges. Looks like this is happening every time the gauge rolls over and it ends up just ever so slightly below 0 (like -0.0003)
FIXED 5178 mask 65535
RIO_FUEL_TOTAL_1
2023-10-13 17:16:22 ERROR MemoryAllocation.lua: value -1.000000 is too small for F-14:RIO_TACAN_MODE_NORMAL_INV (address 4652 mask 32768)
Insight : -1
2023-10-13 17:16:22 ERROR MemoryAllocation.lua: value -65535.000000 is too small for F-14:EXT_YAW_STRING_LR (address 5296 mask 65535)
Insight : 0
I believe the cause for the tacan mode was addressed in my initial post. The draw argument being 0 in insight and yet -65535 in bios seems... Incorrect? You were checking draw argument and not regular argument, right?
EXT_YAW_STRING_LR@jdahlblom could you check out this one with insight? Draw argument 2500. Looks like this one is outputting -1, but I'm not aware of any draw arguments that output <0 (and I don't think we support that anywhere 🤔 )
This one outputs -1. (draw argument)
I believe the cause for the tacan mode was addressed in my initial post. The draw argument being 0 in insight and yet -65535 in bios seems... Incorrect? You were checking draw argument and not regular argument, right?
No you lost me, I usually check the regular argument. Which one do you want me to check?
A draw argument value of -1 tracks with the output were getting from bios - I think it's just weird because no other draw arguments for any module output anything less than zero.
Maybe we should take another look at the dcs luas and see if anything is defined there that could help us.
Checked in modelviewer, EXT_YAW_STRING_LR is in fact -1 to 1. The other controls that are out of range seem to be module issues. Will submit a PR to fix the yaw string issue.