Bullant

Agreed, this is an important question (down to 16 now). If I am going to order, it can't be until after the 21st of July ...

Can anyone confirm if this is the case, or if it charges immediately?

30 units left ... once they are gone does the pre-order price go as well? How's that throttle video coming? ;)

Those examples are "only" displaying text which is reasonably easy with a combination of dcs--bios and the libraries that usually come with the LCD screens. However displaying a gauge like the attitude indicator is a different story because it means taking the raw output from dcs-bios (roll, pitch) and using that to determine how to display a graphical image. Now this is processing that is already done inside Helios so it would be an interesting project to look at the helios source code for the attitude indicator (for a start) and see how hard it would be to convert it to arduino code. edit: I've downloaded the helios source for inspiration and I just so happen to have a spare LCD screen with aurdino interface that I bought for my UFC but it doesn't fit, so I guess I know what I'm doing tonight!

Also not sure if makes a difference, but I am flying the hornet, not the tomcat.

Yep understood, and I did some comparisons and it is actually not too bad. HTC charge US$110 to ship a Vive to Australia for instance.

Any news on the throttle video and/or review units going out? AU$1500 is a BIG commitment!

This might be asking a bit much, but this range pack mod makes NTTR all that it should have been to start with: https://forums.eagle.ru/showthread.php?t=181232 But ... it introduces a whole new raft of radio commands that aren't supported by VAICOM PRO. How much work would be involved in getting support added? I'm assuming it is not something I could do myself and would require code changes at the back end?

I say "Stennis, inbound" and get the carrier specific call and response "mother, angels, fuel state etc" and "brc etc" response.

You must have got lucky, still showing as sold out to me.

You're welcome. In case you didn't know the official arduinos are quite expensive, but the chinese clones on ebay work just as well and are very cheap.

They are both the same version :) Have a read here for very detailed instructions on how to setup dcsbios https://github.com/dcs-bios/dcs-bios/blob/master/Scripts/DCS-BIOS/doc/userguide.adoc Note this documentation is on the original non-maintained version of dcsbios so do not download it from there (but the documentation is still totally valid).

There's no reason at all why you couldn't run an arduino with dcs-bios just to handle the outputs driving LCDs. This version of dcsbios has support for the F14 https://github.com/DCSFlightpanels/dcs-bios

The labels are directly on the Nano. If you look at where you have the red wire plugged in it is labelled as D10, so you would use the following command for your LED DcsBios::LED apuReadyLt(0x74ba, 0x80000, 10) The important thing to remember is that if it is a digital port (Dxx) then you just refer to it as xx in your sketch For analog ports (Ax) refer to it as Ax in your sketch

LOL As per my last post, ignore pin number and look at the labels.

D10 is referred to as 10 in a sketch A1 is referred to as A1 in a sketch So you need to be referencing 10 for the LED, 11 for the APU switch and 12,13 for the crank switch based on how you are wired up.

Use my dcsbios library, it is already configured to send the command three times when you trip the switch ;) sorry saw you aren't using dcsbios.

First thing that jumps out is that you have the switches defined as pins 14, 15 and 16 but have the wires connected to pins 11, 12 & 13. The second thing I'd do is grab a multi-meter and make sure that the switch changes from open-closed or closed-open circuit when you out the meter across the two pins that you have connected and flip the switch (I only say this because the switches both have dual pins and it is possible that you have connected both wires to the same side of the switch) Third: check that you added this line to your export.lua dofile(lfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) Install being on a different drive to the user saved games folder is not an issue (my saved games is on C: and install is on external drive F:) also well worth trying this to make sure that dcs-bios is talking to DCS correctly, before trying to get the arduino setup working. MoVoa-BUOkQ

Thanks, registering now :)

This is awesome. NTTR map has been crying out for this. Well done for releasing your hard work freely. Might be a silly question, but is there a map somewhere with all the target complexes on it (names, type etc)?

Agree 100% but I am happy if it is user configurable.

Ok I think I understand, looking forward to the video :)

Good to see heaps more info on the shop link, however ... Hopefully the finger lifts are only required for the Idle detent, the afterburner should be a push through.

6 hours to pre-order. Who else is getting excited? :) Any chance you are going to release a list of who the review units are going out to? I am very interested, but could not even consider committing that sort of money without knowing it had been well reviewed.

The embedded video above didn't work for me, but this should (after doing some snooping to find the source)