-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A-10C data stops exporting after start #151
Comments
I have no problems at all?! with the old radios maybe something can be done like: if a-10C then old radios |
I think we should figure out why you aren't having problems but other users are 🤔 It's happening for me in single and multithread openbeta. |
Pls test with latest release https://github.com/DCSFlightpanels/dcs-bios/releases/tag/v0.7.48 |
still an issue? |
Still having this issue. I can receive some string data, but not any integer data (update counter never moves). Attached dcs.log and dcs-bios.log. the bios log is almost entirely the following:
Note that address 4494 mask 15 is |
These Entries in DCS_BIOS.log are there since i started with bios. They are no gamebrakers. but what crashes your output is in the DCS.log BIOS related: also a crash, but i dont know the programm: to the bios related: maybe booth programms work together? may concider testing without Export_BEH_Motion_Cls.lua |
This occurred in one of the hot start missions on Sinai. It also happened earlier on a different in-flight hot start, also on Sinai. I believe the BEH motion lua is for the Brunner device I have. I don't use it with dcs so I can certainly disable that lua and see if it makes a difference. It's certainly possible for us to read a value outside of the expected range. When we build the luas for each plane we're just providing an address for each control. If we were to provide the wrong address, for example, then we could end up reading a different memory address than we expect and end up with some weird data. |
A-10C_Test.zip no BIOS log entries in DCS.log DCS_BIOS.log looks different than yours this is my export lua. Master branch and my local dev branch atm the same. |
I have similar problem and it looks like it is somehow connected to SimShaker, with: dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]])
dofile(lfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]])
local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') I got error in dcs.log:
and I can not see A-10C radio data. Without SimShaker it is working. Looks like ptoblem is only related to A-10C since other planes are working correctlly. |
Removes attempt to stringify a global variable which is never set (but can be set by other plugins). SimShaker had a table stored in a global variable `msg` for some reason, and when `setValue()` was called with a`nil` argument (which happens sometimes in the A-10, though that may be a separate issue) it attempted to format the table as a string, which is not supported.
This relates to SimShaker-for-Aviators/SimShaker-for-Aviators-Releases#10 |
…a-error #151 Fix simshaker incompatibility
This should be fixed with the latest update. @emcek are you able to confirm? |
Yes, both:
and
are working fine with: 8fa573f |
The A10 will initially push data, and then it seems as if bios is crashing or something. Commenting out the old VHF and UHF code seems to fix this (however, these radios are used in the original A-10C so we probably can't just remove these lines).
The text was updated successfully, but these errors were encountered: