Constant DCS-BIOS error in DCS.LOG - ideas welcom

[Nagilem]

Anybody have ideas on why I keep seeing this error in my dcs.log?

 

I am running DCS-Bios v0.10. This happens in empty missions as well as populated ones.

 

 

2020-06-05 05:05:45.748 ERROR   Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Users\Rob\AppData\Roaming\DCS-BIOS\Plugins\module-commondata\CommonData.lua"]:26: attempt to index local 'selfData' (a nil value)
stack traceback:
   [C]: ?
   [string "C:\Users\Rob\AppData\Roaming\DCS-BIOS\Plugins\module-commondata\CommonData.lua"]:26: in function 'v'
   [string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Protocol.lua"]:169: in function 'step'
   [string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:85: in function <[string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:83>.

Edited June 5, 2020 by Nagilem

[BlackLibrary]

Try updating commondata.lua . I loaded up a fix a while ago

[Nagilem]

Hi BlackLibrary - where would I download that from? Git?

[Nagilem]

Ok. I replaced the commondata.lua file in the appdata area with your code. That caused a different error with the util.lua. Pulled your version down of that file and now getting the error below -

 

2020-06-05 15:28:09.257 ERROR   Lua::Config: Call error LuaExportAfterNextFrame:[string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Util.lua"]:122: attempt to index local 'value' (a nil value)
stack traceback:
[C]: ?
[string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Util.lua"]:122: in function 'setValue'
[string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Util.lua"]:753: in function 'v'
[string "C:\Program Files\DCS-BIOS\dcs-lua\lib\Protocol.lua"]:169: in function 'step'
[string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:85: in function <[string "C:\Program Files\DCS-BIOS\dcs-lua\BIOS.lua"]:83>.

 

I am using DCS bios for some arduino boards for a F-18 UFC and Right panel. Would reverting to an earlier version of DCS-BIOS be worth it?

 

I use VR so getting more data out of DCS for airspeed and attitude for gauges isnt really necessary. The commondata.lua looks to do just that. Any way to disable those features I dont need? I play alot of MP so these errors are concerning since there are plenty of other issues in MP without having controller issues.

Edited June 5, 2020 by Nagilem

[Nagilem]

Ok. Did something interesting. I went into the commondata.lua file and cleaned all text out except the two top lines that set the module, and the very end line closing out the module and the errors went away. I assume that file is about getting exporting instrument information if I had need of that data for gauges or dials that are physical / mechanical in nature.

 

Is that true?