DCS BIOS stability with ED updates?

[dhevans79]

Hi all,

 

I'm looking to start building some generic panels that could interact with DCS BIOS.

 

My question is whether I plan to use DCS BIOS for the advanced functionality , or whether I just build some generic button boxes mapped via the standard and limited controls to reduce "tinker time". My main worry is whether the DCS BIOS commands/module regularly break with the updates from ED, or whether the system is more or less stable over long periods. I want to be able to play the sim, rather than reflash and reprogram commands due to each update made by ED.

 

So as a general question to all users out there, how have you found the system so far, and is there anything you do to manage it better?

 

Regards,

 

Dave

[Blue73]

Hi, My experience with the Hornet, since August 2018 I've had to reprogram a few modules on two occasions. Though right now the FLIR switch and the one next to it no longer works. Usually it's the output elements like LEDs that are affected, input controls are mostly stable, aircraft specific of course.

Edited August 16, 2019 by Blue73

[BlackLibrary]

i do what i can to hold BIOS uptodate. ;)

[dhevans79]

i do what i can to hold BIOS uptodate. ;)

Whilst the gesture is appreciated, it's not the point of the question ;)

 

With regards to Blue73 response, if it's only a couple of updates a year, that's ok.

 

If I understand correctly, these are derived from the commands the developers use to control the sim, so I guess these basic function s shouldn't change much on complete modules (guess that's not the case for the F18 yet, due to still being in EA)

 

Sent from my SM-N950F using Tapatalk

[JG14_Smil]

Actually, it is the point.

 

If the mainpanel file gets updated, the module for DCS_BIOS needs an update. Some do it themselves, but as BlackLibrary says, he updates in a timely manner and I can attest to it. You would then use the new downloaded library files.

[Warhog]

DCS BIOS Modules written for airframes that are no longer in beta tend to never break. If, over time, new features are added to the airframe, those features tend not to disturb previous command arguments.

 

DCS BIOS modules for Airframes that are still under development can always break because... those Airframes are still under development:doh:. I would never start building panels for something that may change completely for some unknown reason. I would wait for the release version.

 

Now with the help of some enthusiastic persons, DCS BIOS modules have been written for beta airframes. But if you begin panel building before the release version, you need accept that things may (read:probably will) change. If you can't accept those conditions, do not start.

 

That said, if a panel does break from an update. It’s usually only code that needs fixing. Your choice.:pilotfly:

[dhevans79]

Thank you all for your comments. Given the information above, it doesn't sound like it should be troublesome to use DCS BIOS for my project, and as such I can benefit from all the work that you have all put in to supporting this project.

 

Here's hoping that I'll be able to add to this community in the foreseeable future.

 

Regards,

 

David

 

Sent from my SM-N950F using Tapatalk

[Bullant]

Modules in beta can change, teh amount of changes vary. Sometimes none, sometimes a few.

 

I was keeping the F18 module up to date with changes, but have slipped lately, I need to get back on top of that.

 

Any changes are not normally that bad that it takes a huge amount of work to fix (and it is easy to identify required changes by comparing a certain set of files using a file comparison tool).

[capthaltli]

Does DCS BIOS work with GoFlight modules? I currently use GFKeys, but looking to change it up maybe.