Search the Community
Showing results for tags 'dcsbios'.
-
Good afternoon! I have installed: DCS World Open Beta. Also, I have been testing on DCS World 2.8.7 DCS-BIOS Openbeta bort-0.2.4.Setup.exe dcs-bios-arduino-library-0.3.9 I am using a MIG-29 (FC3) DCS World Open Beta test. During the flight the flight characteristics (speed, overload and others) are not displayed, but it is worth to exit to the menu, the characteristics begin to be displayed as if it is downloading from the buffer, the data changes, but during the flight nothing happens (Bort, the same situation with Arduino). Test DCS World 2.8.7 During the flight is displayed a small part of the flight characteristics (pilot's name, speed), but some characteristics during the flight are not displayed (for example, overload), but it is worth to exit to the menu, the characteristics begin to be displayed as if there is an upload from the buffer, the data change, but during the flight nothing happens. I tried to display information on the LCD 1602 (l2c) using Arduino uno - the information also starts with a delay only after being displayed in the menu. Who has encountered a similar problem ?
-
I have started trying to build my own home cockpit panels for the F-5 as a fun project. I have heard that DCS BIOS is what I should be using but after hours and hours of trying to understand and trying to get DCS-BIOS to work I am stuck. I have no clue what I'm doing. I have a Teensy 3.5 and an Arduino Uno to use. I know there is some way to just use the Teensy as a HID but I don't know how to code at all and the internet was not helpful. Thanks for the help. -Ben (I'm really cheap so it is not a perfect replica.)
-
Reluctantly selling my Tek Creations F/A-18 Startup Panel. Custom made for me, with everything you need to start up from cold and dark plus other essential switches. Fully working APU light. Dimmable green backlighting. Uses DCSBIOS as the interface. Top quality craftsmanship. Only used it once or twice and I don’t fly much now, so better someone else has some use out of it. Based in UK but can ship worldwide (at cost). £275 + shipping I’ll also throw in some authentic 3D printed Boeing knobs too!
- 1 reply
-
- tek creations
- dcsbios
-
(and 1 more)
Tagged with:
-
Hi, Working on this project I noticed some strange things on the CDU in the A10C2. From SYS Page. Page 1 : EGI page is not reported to DCSBIOS ? Page 1: LASTE then WIND , the Temp near ***/*** is not reported at the correct position on dcsbios ? (just in front of WNDEDIT ), same when you press WNDEDIT again Page 2 : Press MXLOG lower right , MXLOG page is displayed correctly on the CDU, but a different page is reported on the Right MFD? (shows CADC page instead ) FPBuild , the page number right to scratchpad is not send to DCSBios ( by the way, i also made a AH64 use of this )
-
Hello everybody, I share with you my solution to the DCS-Bios multi-module management for any button box. The code is based on an ESP32 that allows fully wireless communication with DCS, that means it is not required any USB port https://github.com/pavidovich/ESP32_MultiModuleDCSBios The code can be easiliy adapted to your button box, just replace the function getButton() (present in the ESP32_Code.ino) with any other that gets the button ID from your button box. There are 3 examples based on the A-4E-C, F-5E-3 and T45 modules. Just take into account that these examples are based on my button-box, so you should adapt them to your necessities.
- 4 replies
-
- 3
-
- dcsbios
- button box
-
(and 3 more)
Tagged with:
-
Hello, I'd like to share a project I'm working on that is fully detailed on Github. Compact input controller with 19 switches and 4 rotary encoders. Functions as a joystick in DCS, so it's easy to map controls. Supports DCS-BIOS for more advanced control mapping. Overall, it provides up to 120 control inputs via a 3-way mode switch. I find it to be a great addition in VR. After developing some muscle memory, it feels relatively natural to locate controls for startup, navigation and weapons. The project includes 3D models, schematics and arduino source code. If you'd like to help with the development of this, such as adding DCS-BIOS scripted controls or some other idea for VR input, I'd love to hear from you.
- 2 replies
-
- hardware
- controllers
-
(and 1 more)
Tagged with:
-
I've been working on a project for a little bit now, and now that the final necessary components are falling into place I'd like to introduce this project... TouchDCS (Out now!) Who is TouchDCS? TouchDCS isn't anybody, it's a computer application. What is TouchDCS? In short, TouchDCS allows you to use your tablet to control DCS. More technically speaking, TouchDCS is an application that acts as an interface between OSC applications (in this case, TouchOSC) and DCS-BIOS. When is TouchDCS? TouchDCS is the future. Lucky for you, the future is now. TouchDCS is now! Where is TouchDCS? https://github.com/charliefoxtwo/TouchDCS Why is TouchDCS? I started TouchDCS after coming to the conclusion that I simply fly too many different aircraft, and there was no way for me to buy or build physical controllers that made sense for all of them. What if, instead, you could simply load up a layout that had the controls you need for your aircraft, exactly where you want them, and nothing else? This is the problem TouchDCS aims to solve. Create your own layout for your aircraft that has exactly what you need. It can be used for critical controls (though I wouldn't try to control the stick with it personally) or just about anything else in the game. It's great for panels that you don't want to dedicate precious hardware buttons to, but you'll need eventually. How is TouchDCS? Great, thanks for asking! But like, how does it work? TouchDCS needs to be configured with your tablet's IP address and communication ports (set within the TouchOSC app). Likewise, TouchOSC needs to be configured to talk to TouchDCS. Once that is complete, TouchDCS will listen for any commands from DCS-BIOS, and forward them on to TouchOSC (translated to the OSC protocol). TouchDCS will also listen for any OSC messages from TouchOSC, and translate and forward them to DCS-BIOS. The result is two-way communication for any control that DCS-BIOS supports, and shareable layouts that require no additional configuration/mapping. It (theoretically) supports an infinite number of phones/tablets, each with their own layout, however practically speaking I'd be surprised if you got more than 5 working without communication delays. What if I don't want to use DCS-BIOS? Does it support mapping to DX buttons? Not at the moment. Maybe at some point in the future, but don't count on it. How much is TouchDCS? TouchDCS, the application I have developed, is free and can be downloaded by anybody. However, TouchOSC - an application developed by a third party - costs $10 (on mobile, $18 on desktop). I have been working with the developers of TouchOSC in order to get more features that would benefit TouchDCS into the latest version, but I don't receive any commission or payment of any kind and I don't personally know the developers. There's no sponsorship here - I chose TouchOSC because it seemed like the best way to accomplish my goals, and they've been really receptive to feedback and changes/features I've requested. I want to see pretty pictures!