longuich

Hear, hear ! Sent from my iPhone using Tapatalk

Yes. With dcs-bios. Sent from my iPhone using Tapatalk

Sorry for not saving the track. I’ll save it when it happens again . Sent from my iPhone using Tapatalk

Incorrect atc Flying over the persian gulf map I get response from caucasus ATCs in audio as well as text. Happens since latest open beta. Sent from my iPhone using Tapatalk

Flying over the persian gulf map I get response from caucasus ATCs in audio as well as text. Happens since latest open beta. Sent from my iPhone using Tapatalk

Makerbeam [emoji3590] DCS [emoji3590] Arduino aye [emoji40][emoji106] Sent from my iPhone using Tapatalk

Realize an encoder is not just two buttons. The encoder sends steps (of 4 usually) which tell other electronics (such as an arduino) whether it’s turning left or right and how far. You probably need to tell the board you’re using that what you connected is in fact an encoder. Sent from my iPhone using Tapatalk

The ground wire goes to a ground connection. The a/b pins connect to a pin that reads the state changes of the encoder. With arduinos and teensies this works perfectly with the appropriate code. Sent from my iPhone using Tapatalk

Jan, As an IT person myself I know what your on about. Thank you for your work on dcs-bios and the time you’ve put into it. I hope this decision helps you sort things. If you need to offload web things dm me. I’m happy to host or store some content. Cheers! Sent from my iPhone using Tapatalk

On the exports? Or the main viewport? I’ve seen a fps drop since the first 2.5.6 patch on the main viewport. And also longer load times. And sometimes a joysticks needs a replugging. Multiplayer has been sluggish. Sent from my iPhone using Tapatalk

Issues like..? Sent from my iPhone using Tapatalk

for the 223: U8G2_SSD1305_128X32_NONAME_F_4W_HW_SPI ScrPad(U8G2_R0, /* cs=*/ 10, /* dc=*/ 7, /* reset=*/ 6); the other (i2c) displays: U8G2_SSD1306_64X32_1F_F_HW_I2C OLED_2(U8G2_R3, /* reset=*/ U8X8_PIN_NONE); U8G2_SSD1306_128X32_UNIVISION_F_HW_I2C OLED_3(U8G2_R0, /* reset=*/ U8X8_PIN_NONE, /* clock=*/ SCL, /* data=*/ SDA); I'm using them with a teensy board. Not arduino.

Hey bugz, It is a 2.23 sd1305 i found on amazon. I prefer i2c for its simplicity and all my other displays are. But this is an SPI version. It’s supposed to be able to do i2c as well but I don’t really fancy desoldering tweezer size resistors. Cheers! Sent from my iPhone using Tapatalk

You just need the 4 last fonts in the big file. The changes are mainly this: changed to this Sent from my iPhone using Tapatalk

After a couple private messages I solved the encoding error and we solved the compilation errors. To use the fonts your best bet is to use a script editor such as textwrangler to open the u8g2_fonts.c file. Copy the last 4 fonts (the ones that have dcs in the name) and paste those into a new utf8 text file which you then save as hornet_fonts.h (or whichever name you prefer). Then in your sketch, where you plan to use the fonts, paste this on one of the first couple lines: #include "hornet_fonts.h" I have that right after #include "U8g2lib.h" Now your sketch should compile just fine. As an example I've attached a picture of what the code below does: tcaselect(2); OLED_3.setFont(u8g2_DcsFont_tf); OLED_3.clearBuffer(); // clear the internal memory OLED_3.drawStr(01, 32, ":ATTH"); OLED_3.sendBuffer(); // transfer internal memory to the display tcaselect(3); OLED_4.setFont(u8g2_DcsFontHornet4_tf); OLED_4.clearBuffer(); // clear the internal memory OLED_4.drawStr(01, 32, " RALT"); OLED_4.sendBuffer(); // transfer internal memory to the display tcaselect(5); OLED_6.setFont(u8g2_DcsFontHornet3_tf); OLED_6.clearBuffer(); // clear the internal memory OLED_6.drawStr(01, 38, " BALT"); OLED_6.sendBuffer(); // transfer internal memory to the display my 2cts. thanks again to Sky! cheers

That’s just beautiful. BTW, I’m getting encoding errors with the fonts file. Is it a windows encoded file ? Sent from my iPhone using Tapatalk

You are legend. Cheers! Sent from my iPhone using Tapatalk

Applying that solved all issues.

oh hey mate, I never caught your response. But love the lead tho. thanks heeps! cheers, michel

But for when you don’t use dcs bios for input, it’s easily solved with an “if else” and joystick output from your arduino or teensy. Sent from my iPhone using Tapatalk

Oops.. if 1 and 3 are NOT high. 2 must be assumed. (Even though in and on-off-on, it can’t be). Sent from my iPhone using Tapatalk

I should have recorded it. So no. I don’t. Sorry. Sent from my iPhone using Tapatalk

I’m presuming this is really a programming question. You need to check a pins for a change from high to low or the other way around. If 1 is on, 2 and 3 are not. If 2 is on, 1 and 3 are not. If 3 is on, 1 and 2 are not. That way you can always cut one pin from a on-off situation. Sent from my iPhone using Tapatalk

Just after updating to the latest OB, tried flying the FA-18 around normandy. Catapulted from stennis and headed for Jersey. After about 2 minutes the hornet started shaking violently. F2 revealed I had lost the wings entirely. Don;t know why. I Could still bank and pitch though. Didn't try, but think I could have landed. Pretty awesome for a Hornet. But I suspect it's not a feature. single player via mission planner. took off from stennis near jersey. 4x agm65F and sidewinders. headed for mont st Michel.

@obious there are a couple in brun’s fa18 ufc. Not certain if they’re correctly sized though. Sent from my iPhone using Tapatalk