OscarVictor11

Fourth monitor set up. I currently have two 2560 x 1440 monitors plus two 800 x 600 monitors and have allocated a main game screen of 2560 x 1440 and two (left and right) MFD's of 800 x 600. This set up is working fine but I would like to use the second, currently unused, 2560 x 1440 to display the lower central MFD together with a knee board. I understand the notion of allocating the various screen address's but am not sure how to expand the 'Settings/System/Monitors (currently LMFCD +Camera+ RMFCD) to four monitors to allow the use of a kneeboard and the lower central coloured MFCD. Any suggestions would be appreciated.

Hiya.........just looking at your approach to the UFC and related display's. Ive been working on mine for months but cannot seem to get the Arduino +LCD displays working properly at all. Ive also been looking at using an old Ipad mini for displaying the complete UFC and displays as in a youtuber solution (search YT for ' DCS F18 UFC on Ipad '). Its worth a look. Bob

Members 13 Author I am in the process of building an F18 UFC panel with the scratchpad and selection displays but cannot seem to write the Arduino/Dcs Bios sketch to present the Scratch Pad info. I have no previous computer or electronics skills so the process has been a fair old challenge. I'm using a Leo Bodnar for the switches and an Arduino Mega together with a Grove Base Shield V2 for the i2c LCD (Grove-Lcd RGB Backlight) i2c display. Having selected the suggested 'IRQ serial connection' and copied the relevant libraries for the sketch as shown below, I can compile as far as this. I know there are some line's of code missing but whatever I try fails to compile. The main source of instruction has been two youtube demos, both of which, with the best of intent, are confusing and fail to logically demonstrate fully. Having used the Arduino/ Grove base shield and the 16 x 2 Grove display I can easily install the ' Hello World ' sketch, change this to other info such as Com 1 140.000 in various colors so the kit works fine. Its the implementation of the scratchpad info that's proving to be difficult and any help would be much appreciated. #include <Wire.h> #include <rgb_lcd.h> /* Tell DCS-BIOS to use a serial connection and use interrupt-driven communication. The main program will be interrupted to prioritize processing incoming data. This should work on any Arduino that has an ATMega328 controller (Uno, Pro Mini, many others). */ #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" rgb_lcd lcd; } void onUfcScratchpadNumberDisplayChange(char* newValue) { /* your code here */ } DcsBios::StringBuffer<8> ufcScratchpadNumberDisplayBuffer(0x7446, onUfcScratchpadNumberDisplayChange); /* paste code snippets from the reference documentation here */ void setup() { DcsBios::setup(); lcd.begin(16, 2); } void loop() { DcsBios::loop();

I am in the process of building an F18 UFC panel with the scratchpad and selection displays but cannot seem to write the Arduino/Dcs Bios sketch to present the Scratch Pad info. I have no previous computer or electronics skills so the process has been a fair old challenge. I'm using a Leo Bodnar for the switches and an Arduino Mega together with a Grove Base Shield V2 for the i2c LCD (Grove-Lcd RGB Backlight) i2c display. Having selected the suggested 'IRQ serial connection' and copied the relevant libraries for the sketch as shown below, I can compile as far as this. I know there are some line's of code missing but whatever I try fails to compile. The main source of instruction has been two youtube demos, both of which, with the best of intent, are confusing and fail to logically demonstrate fully. Having used the Arduino/ Grove base shield and the 16 x 2 Grove display I can easily install the ' Hello World ' sketch, change this to other info such as Com 1 140.000 in various colors so the kit works fine. Its the implementation of the scratchpad info that's proving to be difficult and any help would be much appreciated. #include <Wire.h> #include <rgb_lcd.h> /* Tell DCS-BIOS to use a serial connection and use interrupt-driven communication. The main program will be interrupted to prioritize processing incoming data. This should work on any Arduino that has an ATMega328 controller (Uno, Pro Mini, many others). */ #define DCSBIOS_IRQ_SERIAL #include "DcsBios.h" rgb_lcd lcd; } void onUfcScratchpadNumberDisplayChange(char* newValue) { /* your code here */ } DcsBios::StringBuffer<8> ufcScratchpadNumberDisplayBuffer(0x7446, onUfcScratchpadNumberDisplayChange); /* paste code snippets from the reference documentation here */ void setup() { DcsBios::setup(); lcd.begin(16, 2); } void loop() { DcsBios::loop();

Like many of you I've had fairly good service from my Thrustmaster Warthog set up over the last five years but need to start replacing the 4 left thumb switches located down the right side of the throttle. I've rebuilt the 4 way comm switch using new omron Tactile switches, it was a faff but now works well. The three lower switches are definitely beginning to fail ie sticking or intermittent fails. The whole of the throttle side plate is easily removed to expose the wiring but the actual removal and replacement of the switches looks a bit of a challenge. Has anyone managed to remove these switches and what replacements might you recommend?. Going back to the fourway comm switch the parts are easy to fit and solder as long as you take photos as you go along but being made of plastic the three part barrel housing is inherently weak given the amount of use its likely to be subject to, has anyone found a good replacement/alternative?. Keep well, Bob.

I've been in the process of building an F18 UFC and have completed the 'easy ' bit, ie wiring the main switches and buttons, but have hit a problem with the character displays. I cant seem to find a simple example of a DCS-Bios and Arduino Mega sketch that would drive a 16 x 2 lcd to provide the Comm 1 and 2 frequencies. I understand the basic construction of how the sketch is put together ie the various library's needed to drive the display but the only example online I can find is a youtube demo, which is clearly well meant, but is not at all straightforward to follow or implement. Can anyone suggest a likely sketch outline that would illustrate how I might achieve a simple 16 x 2 display that shows the selected radio frequency?. I'm using an Arduino Mega 2560/ Seeed Industries Grove LCD RGB Backlight 16 x 2 (I2c) and related library. many thanks.

A penny for your thoughts...........I'm contemplating building an f18 UFC pretty much along the lines of Brun's excellent work but for desk top space reasons I'm not able to follow the 'printed route'. I have decided to use acrylic sheet approach ie top surface/labelled and back lit, with a second layer to carry the lighting solution and the switch fittings. I'm not electrically minded so if I can keep the soldering and wiring at its simplest I should be OK. I'm thinking of using the Bodnar BUO 836X board, together with any recommended switches. I'm not particularly interested in the accuracy of visual representation, much as I admire the work done by Brun and other contributors, its really a question of function rather than form. I fly the f18 within a regular online squadron, usually at very low alt, so 'head down' as little as possible. At some point I'd like to include the oled screens as well, but I'm under the impression that they would have to be 'driven' via an arduino/separate solution. One of the main attractions for this project is that I can build it in stages as my knowledge/skills improve. So, 1) use the acrylic sheet approach as the initial build, 2) use switches and buttons as per thread suggestions, 3) initially concentrate on the construction/wiring before any 'form' considerations (this should allow me to use a thin plywood sheet for initial build), 4) suck it and see!. If you have any thoughts regarding the Bodnar board, or a personal choice of the button/switches, or in fact anything you might find worth sharing I'd appreciate it, and finally, simplicity works really well for me. many thanks Bob V

Hopefully someone can put me right here...…….Ive been having consistent problems with both my pilot default head position and the size of the heads up display information. Quite often in MP my head position is so far off centre that its beyond adjustment via either seat adjustment or leftshift-alt and numpad key adjustment, it requires jumping back out to A/c selection screen then back in again. Sometimes it works and sometimes not. My 'heads up' display information is also inconsistent in that it can be magnified beyond useable viewing ie I can only see some of the required info with the rest being off to one side or t'other. Again, the above two methods of adjustment sometimes work and sometimes not. Is there a means to simply reset all my viewing angles to default as I suspect that I might have pressed an evil setting in my keyboard wanderings...……..Fixed missions or offline the problems don't appear. Or might a new re install be the quickest answer? many thanks Bob

One recent issue I've found is that there appears to be no simple way of allocating different, co located, TGT wp's within the same flight. The copy paste idea simply reproduces all Nav settings in the one flight, and as DD above observes, entering WP after WP is long handed and prone to fat fingers!.

Good on you Joey, thats the spirit............if and when we leave , we'll need that attitude!. Well done matey.

Thanks boys....sorted. For some reason my assigned settings had two right turn movements for two separate control inputs ie no left turn .....hmm..........odd, but I deleted both, corrected the error and all seems fine.

I have a TM A10 stick and throttle and since installing F18 have been unable to steer accurately enough to take off. Have mapped steering wheelbrakes left and right to stick switches but as soon as I start to move it keeps turning right and only changes to left momentarily if I reduce throttle to a walking pace. S key makes no or little difference.............. I kind of 'waddle' down the taxiway and then lose control as soon as I open throttle! I'm obviously doing something wrong...........thanks Bob.