Frequently asked questions.

Start on the OpenHornet Start Here page. The current latest hardware release is available here.

The drawings, manufacturing files, parts lists, and related build documents are all available from the hardware build package. Use Start Here to get the latest package.

OpenHornet supports the DCS-Skunkworks, formerly DCSFlightPanels, branch of DCS-BIOS: DCS-Skunkworks DCS-BIOS fork.

Software is tracked separately in the OpenHornet-Software GitHub repository.

Minimum tooling requirements are listed on the Start Here page. The current guidance assumes a capable shop with CNC routing, laser cutting or engraving, 3D printing, electronics assembly, and careful measuring.

The build mainly consists of painting, structure, electronics, and software.

Fabrication

You will fabricate MDF, acrylic, and 3D printed parts, including the upper instrument panel, lower instrument panel, left console, right console, center tub, seat, flight stick, and throttle. After fabrication, you will paint and assemble the parts.

Electronics

Electronics work includes wiring, backlighting, panels, screens, PCBs, Arduinos, and gauges.

Software

Software work includes Arduino code or sketches and DCS-BIOS setup.

OpenHornet does not prescribe a specific surround sound system. Builders should choose whatever is locally available, fits their budget, and meets their individual cockpit requirements.

OpenHornet assumes builders are using a CNC router, so the drawings do not fully detail every CNC-cut or flat part for hand fabrication. Several builders have successfully built the structure and associated parts by hand using common woodworking techniques. You will need to lay out the SVGs from the build package, print them at 1:1 scale, and use those printouts as fabrication templates.

OpenHornet is designed to use 0.75 inch, 0.50 inch, and 0.25 inch MDF. Some metric builders have successfully substituted 19 mm, 12 mm, and 6 mm MDF with a minimum of tweaks to printed parts.

Approximately four 4 x 8 foot sheets of 0.75 inch MDF, one sheet of 0.50 inch MDF, and one sheet of 0.25 inch MDF. OpenHornet is designed around MDF; material substitutions are at the builder's own risk.

That is fine. Use the guidance on the Start Here page for model access and download paths. Treat raw models and working files as reference unless the release package says otherwise.

ABSIS, the Arduino Based Simulator Interface System, is the OpenHornet electronics layer. It consists of PCBs connected to Arduinos. You download or write the Arduino sketch, wire the PCB to the panel or component, and connect it into the system in accordance with the OH-INTERCONNECT drawing.

Yes. Reference the OH-INTERCONNECT drawing in the build package. You can download the build package from Start Here.

Follow the OH-INTERCONNECT drawing in the build package. The build package is available from Start Here.

Yes. OpenHornet primarily uses DuPont and Molex connectors, plus several others. Follow the OH-INTERCONNECT drawing in the build package.

Pre-crimped DuPont and Molex wires are available; builders often find them on eBay or AliExpress. Buying many pre-crimped wires can save time compared with crimping every wire yourself, though you will still want appropriate crimping tools for cases where custom wires are needed.

OpenHornet uses ABSIS. Obtain the correct PCBs by having them fabricated from the manufacturing files in the build package, purchasing them from an OpenHornet Authorized Vendor, or arranging a group buy in Discord. Once you have the PCBs, wire everything according to the OH-INTERCONNECT drawing.

OpenHornet generally sources electronics components from DigiKey and Mouser. If a component is not available from those two, try Octopart to search distributors. After that, plain old Google can help track down alternates or remaining stock.

McMaster-Carr is the primary hardware source referenced by OpenHornet, mostly because McMaster part numbers are convenient and precise for design documentation. You do not have to buy every item directly from McMaster. Use the specified McMaster part number to identify the size, material, finish, and standard, then source equivalent hardware locally or from another supplier when that makes more sense. That can be much cheaper than buying a box of 100 screws when you only need 3.

OpenHornet specifies the screens required for DDI, AMPCD, IFEI, SARI, RWR, and other displays in the build package drawings. Download the build package from Start Here, then review the drawings for the assemblies that contain displays. Screen part numbers are listed in the parts lists.

Displays are installed using the relevant 3D printed mounting structures specified in their respective assemblies.

The decision was mainly based on how the real F/A-18C operates. The real aircraft does not have force feedback in the stick except for mechanical reversion FCS mode, which is extremely rarely used by DCS pilots. Adding active force feedback would increase cost and complexity without much practical benefit for most users.

The flight manual does describe AOA feedback and increased stick force with AOA. In the F/A-18C, stick input rate to the FCS decreases as AOA increases, so the pilot needs more stick travel for the same control surface deflection. More deflection requires more force, which creates the force increase described in the manual.

The OpenHornet stick is designed to replicate the real aircraft's range of motion, force gradients, breakout forces, and damping forces.

The OpenHornet team has not tested third-party panels for compatibility, so there is no official yes or no. Several builders have tried third-party panels, and they generally do not fit without modification.

Not under the public noncommercial license alone. Selling parts, designs, or derivatives would violate the NonCommercial clause. Apply to become an OpenHornet Authorized Vendor before selling OpenHornet-based parts or assemblies.

Every commercial use case is different. Reach out through the Contact Us form with a detailed description of the use case you are envisioning.