DCS-BIOS F/A-18C library. Get it here!

While everyone else has been flying it, I have spent the last couple of days building a library for the F/A18C for DCS-BIOS, in the hopes of one day getting my pit built.

Until I can get in contact with Ian to get it rolled into an official build of DCS-BIOS, I've attached the files for anyone who wants to try it out.

Simply extract the zip file into your Saved Games\DCS.openbeta\Scripts\DCS-BIOS folder overwriting when asked.

The only things that I am aware are missing at the moment (due to limitations in the hornet module which I am sure will be fixed as development progresses):

1. An input for static source switch (switch does not appear to be currently implemented in the cockpit)

2. An input for fan test switch (switch does not appear to be currently implemented in the cockpit)

3. An export for the top fuel total line when the IFEI is in time set mode

4. An export for the engine nozzle positions on the IFEI

Final disclaimer: This is a beta module, things will change and this will likely break this library. I will try and keep on top of updating it as the Hornet gets updated.

All I ask is that if you find something that doesn't work, please let me know. Even better, if you figure out how to fix it let me know that as well so I can roll it into the final version.

edit 7th June - I have completed the initial version, please let me know if you find anything that doesn't work as expected. This has been tested with the latest 2.5.2.18307 build.

note 13th June - I have discovered that I forgot to include updated json files in the latest package. No problem, they will auto-generate with every flight, so just go fly a mission. Will include updated files in next version.

update: 1st October - Updated to v0.6 supporting Beta 2.5.3.22176

update: 9th November 2018 - Updated to v0.7 supporting Beta 2.5.3.23788

update: 12th November 2018 - Updated to v0.8 fixing COMM1/2 Channel selection rotaries

update: 13th November 2018 - Updated to v0.9 to remove AV8B entry that was causing lack of comms with DCS

update: 21st January 2019 - Updated to v1.0 to correct errant FUEL DUMP switch behaviour

NOTE: You should only download the latest version, I am only keeping the old versions here so I can get an idea of how many people are actually using the module.

DCS-BIOS v0.6.zip

DCS-BIOS v0.7.zip

DCS-BIOS v0.8.zip

DCS-BIOS v0.9.zip

DCS-BIOS v1.0.zip

Thanks a lot AndewW .

i can´t found control reference for F18 it´s missing or not available yet?

VR

The control reference should auto-generate the first time you start a mission with a Hornet ... but I have updated the zip file to contain the generated files so that the control reference works right from the start.

edit: was missing an important file. Updated the zip again, should all be good now.

New version uploaded. All of the 3 way springloaded switches were functioning incorrectly, I have fixed all of them except for the MC switch which stubbornly refuses to work.

So at this point every switch works in the cockpit except for:

MC Switch

Launch Bar

Hook Bypass

New version uploaded. All of the 3 way springloaded switches were functioning incorrectly, I have fixed all of them except for the MC switch which stubbornly refuses to work.

 

So at this point every switch works in the cockpit except for:

 

MC Switch

Launch Bar

Hook Bypass

By spring loaded switches, do you mean the magnetic switches that return to center/off in the real plane?

Just want to clarify to ensure I’m following along.

I said it on Reddit in a different post, but as a guy who knows nothing about programming about to embark upon building his first pit..your efforts are greatly appreciated. Thank you!

Sent from my iPhone using Tapatalk

By spring loaded switches, do you mean the magnetic switches that return to center/off in the real plane?

Yes and know. Some of them are magnetically held, others are simply spring loaded and return to center as soon as you let go of them. In the hornet module controls they are all currently defined the same.

Hopefully they will include parameters to tell us when a magnetically held switch is held in position or not allowed into a position like they currently do in the A10 in a future build.

The important thing is that these three way switches weren't working in my original version but they are now :)

I said it on Reddit in a different post, but as a guy who knows nothing about programming about to embark upon building his first pit..your efforts are greatly appreciated. Thank you!

Thanks, that is greatly appreciated.

Before anyone dives too far into using the current files ... coming up next I am reorganising all of the entries so they are broken down by panel in the aircraft rather than the sometimes confusing way they are at the moment which is based on the layout in the module's configuration files.

Did you find a way to read the RPM and APU RPM value?

Much appreciated!!! Time go get a move on with my build.

Did you find a way to read the RPM and APU RPM value?

Not yet, just waiting to hear back from Capt Zeen, I am sure he will set me on the right path for getting the output values.

New version uploaded.

I have completely reworked the control groupings so that it matches the layout in the NATOPS manual and so that controls/indicators etc are grouped by panel.

I have written extensive custom code to handle non-standard buttons like the weird toggles and spring loaded switches, even got the eject switch to actually eject after calling it just once.

I've got some info from Capt Zeen to set me on the right path, and the next step is to get the other (non indicator) outputs working.

Good news.

I have fixed the input settings for the Standby Attitude Indicator and RADALT.

And with some great help from the awesome Capt Zeen I have added outputs for all of the analog outputs (servos) as well as the UFC and IFEI.

There are a couple of analog outputs that are causing issues, so it will be tomorrow before I upload the (for now) final version.

Final (for now) version updated.

All switches except the static air source switch are working.

Only other issue is that there is no export for the top fuel display line in the IFEI when in time set mode.

Enjoy, and let me know if you spot anything that doesn't work.

Awesome, thanks again dude!

Thanks again for putting in the work on this stuff. It really rounds out the module with all of the gauges and outputs.

I tested the IFEI outputs and overall they worked really well. Just a few issues came up that you may want to look into:

• Seems a couple of texture visibility outputs are missing: Z (zone), L and R for top/bottom fuel. NOZ too, but I think that always follows the scale texture, so it's not really necessary..
  
• You have the texture visibility output for the pointers, but not their actual angles/positions (not sure if it is possible to extract that)
  
• Missing output for top fuel row during time set mode (for +/- hour offset for zone)
  
• Missing ET/timer outputs (bottom time display)
  

• Seems a couple of texture visibility outputs are missing: Z (zone), L and R for top/bottom fuel. NOZ too, but I think that always follows the scale texture, so it's not really necessary.. These are missing from the hornet module, but as you said not a huge issue
  
• You have the texture visibility output for the pointers, but not their actual angles/positions (not sure if it is possible to extract that) This is not available in the module outputs at the moment
  
• Missing output for top fuel row during time set mode (for +/- hour offset for zone) Correct, I was aware of this one (see post above)
  
• Missing ET/timer outputs (bottom time display) Let me look into this one, I thought it was working
  

Thanks for the feedback and testing :)

Thank you for the work you have done! I'll take a look at the F/A-18C DCS-BIOS files this weekend and see how the transition from my old interface system to DCS-BIOS will work out :)

Do you guys use any commercial led output shields with Arduino or clones? I earlier used PhidgetLED64 board for my indicators but I'm thinking about moving to Arduino.

Do you guys use any commercial led output shields with Arduino or clones? I earlier used PhidgetLED64 board for my indicators but I'm thinking about moving to Arduino.

To be honest, no I am not planning on doing that.

For the small number of LEDs that need to be driven and being able to buy nano clones in bulk for around $3, I plan on using one nano per panel. Plenty of outputs there to drive one LED per output without any fancy processing.

edit: I just realised who was commenting on my work. I have watched all your youtube videos, you were on of my main inspirations for making a fully functional F/A-18C cockpit, so thanks :)

This will add some more realism to the pit:

https://foxtrotalpha.jalopnik.com/boeing-will-sell-you-an-ejection-seat-1826638123/amp

Just like the old Miller High-Life motto: “If you’ve got the time [$$$], they’ve got the beer”

Another small update:

* Add export for IFEI Zulu texture visible

* Add exports for IFEI Timer H, M, S

* Move VSI and Standby Altimeter analog outputs to their correct category

I have an error to write the Arduino file on lines:

DcsBios::LED aoaIndexerLow(0x5406, 0x4000, A1);

DcsBios::LED aoaIndexerNormal(0x5406, 0x2000, A2);

DcsBios::LED aoaIndexerHigh(0x5406, 0x1000, A3);

For reasons unknown to me, after copying the DCS-Bios F-18 to the basic folders. When I check lines in Google. I see quite different lines to copy.

I think I'm doing something wrong, how to put these files in the folder correctly? To show me the right lines to copy.

DcsBios::LED flpLgRightGear(0x5404, 0x2000, PIN);

DcsBios::LED flpLgNoseGear(0x5404, 0x0800, PIN);

DcsBios::LED flpLgLeftGear(0x5404, 0x1000, PIN);

I'm not sure exactly what your problem is but I can see that you are using an old version of the library so as a start I strongly recommend downloading the latest version and trying again.

The problem is that I download the latest version, and after loading the files I can see the old one. And I never downloaded the older version, the first time two days ago.