Bullant

Can't answer your first question as I haven't worked it out myself yet. As to your second, it's official as it can be for now. I've tried unsuccessfully to contact Ian to get the library rolled into the official DCS-Bios release. So for now I will just have to keep releasing updates here.

Thanks mate, I am downloading the update now and will make changes and upload as soon as I can.

I am more than just a little excited :)

That would be a bad idea. There is no reason that you have to be the "active" screen for a button press to work. And by that I mean there is no reason you can't change options/select a different page on the left DDI while the right DDI is the active screen.

Known bug unfortunately with super wide resolutions https://forums.eagle.ru/showthread.php?t=210382

Just tested with a physical pushbutton and it works perfect for me. Stupid question but do you have one side of the pusbutton connect to the I/O pin and the other connected to GND?

Not sure why this is marked unable to reproduce either. This is definitely an issue.

I have gone back to a single monitor solution for now until this is fixed. Not ideal, but at least it is flyable.

If the MFDs are exported then they will not be displayed in F2 view. If you just want to disable them all together you can even just "export" them to a single monitor view, giving them a 1 x 1 viewport size. Also, and I haven't tested this, but I believe that if you look for the following lines in Mods\aircraft\A-10C\Cockpit\Scripts\MFCD\indicator\MFCD_init.lua if LockOn_Options.flight.easy_radar then render_target_always = true purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW,render_purpose.SCREENSPACE_OUTSIDE_COCKPIT} else render_target_always = false purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW} end and change it to if LockOn_Options.flight.easy_radar then render_target_always = true purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW,render_purpose.SCREENSPACE_OUTSIDE_COCKPIT} else render_target_always = false purposes = {render_purpose.GENERAL} end then this should stop them being displayed in HUD only view.

Unfortunately I have exactly the same problem. However ED have stated that export is not currently implemented/supported for the Hornet so I expect this to be fixed in future builds. I am impressed with what has been achieved right now considering it isn't supposed to work at all!

Thanks for the kinds words. A basic DCS-BIOS sketch is very simple to get up and running. I highly recommend following this tutorial before you dig into anything more complex. http://dcs-bios.a10c.de/docs/v0.7.0/userguide.html

You are a champion mate.

OK I have found the problem ... I included an old copy of the hornet library json files. These are regenerated every time you start a flight in a hornet. So go and have a quick fly and if you have dcs-bios set up correctly it will regenerate the documentation. Correct page should look like this:

nice work fellas :)

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.

Would be much easier to ask ED really nicely if they could add export variables for the lens position and waveoff lights.

That throttle is making me super excited!

I noticed this for both the Launch Bar and Hook Bypass switches. Only the up (1.0) command has an effect (to toggle the switch). Resulted in the following switch definition for DCS-BIOS. moduleBeingDefined.inputProcessors[msg] = function(toState) local fromState = GetDevice(0):get_argument_value(arg_number) if fromState == 0 and toState == "1" then GetDevice(device_id):performClickableAction(command, 1) end if fromState == 1 and toState == "0" then GetDevice(device_id):performClickableAction(command, 1) end end

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

After implementing the DCS-BIOS library for the hornet, I have found the following to be missing. It would be good to get some feedback on whether they are planned to be implemented or not? * An input for static source switch (switch does not appear to be currently implemented in the cockpit) * An input for fan test switch (switch does not appear to be currently implemented in the cockpit) * An export for the top fuel total line when the IFEI is in time set mode * An export for the engine nozzle positions on the IFEI Thanks for all the great work, I was pleasantly surprised that this was all that was missing in the first beta release.

I was considering cheating and going down the dogfight boss cockpit route, especially as they now produce an aluminium skin version complete with panels ... however looking closely at the photos I know there are things that will niggle me over time. I am really hoping the openhornet project comes through, and hoping the might release the cockpit structure plans before the entire system is complete so that I could start working on the main structure.

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 :)

Thanks for the feedback and testing :)

Can't seem to get hold of Ian to get my F/A-18C profile to DCS-BIOS, so I will add it here. Simply unzip into Saved Games\DCS.openbeta\Scripts\DCS-BIOS folder overwriting when asked. Can't seem to link twice, file can be found here

Purchased back in 2011, just found this thread ;) S/N: 04517 Location: Queensland, Australia