

longuich
Members-
Posts
145 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by longuich
-
Thanks so much mate. I’ll try all of it asap cheers! Sent from my iPhone using Tapatalk
-
That certainly makes sense. Experience supersedes digits. But I’m looking fir a starting point. So what is the resolution in your dcs settings ? Sent from my iPhone using Tapatalk
-
So how is 126% related to your rig. Cause what I’m confused about is how the g2 is basically a 4k screen chopped two halves. But somehow setting dcs to a 4k res doesn’t seem to be the norm. Btw. I am playing on an i7 10700 rtx 3090. So I should be able to handle reasonable resolutions. But I’m confused because all the different settings seem to impact not only clarity but equally the sweet spot - which is quite narrow on the g2, isn’t it? Sent from my iPhone using Tapatalk
-
Hey now we’re on the subject of how bad the g2 is. What seems to work best for resolution and pd in the dcs and steamvr settings ? Sent from my iPhone using Tapatalk
-
Thanks fellas. Between all of the replies, I got it sorted. Probably was the wmr sensor setting. Cheers! Sent from my iPhone using Tapatalk
-
I just received my g2 over the weekend and once I figured out I needed to add dcs (standalone openbetq) to steam it just ran. I had some weird issues with my mouse not reaching the far right bottom end of the screen. But that was all. Yesterday I fired up all of the gear again and changed to resolution to 3840x2160 and 1 screen. I had it at a custom 6000x1440 with several viewports. Then rebooted and fired up dcs in the headset. Dcs fires up alright. I find myself in the hangar eith the start screen. But i can’t interact with it at all. No way to click anything. The controller beams just go right through the dcs screen. And when i try to use my mouse i get a window out of focus warning. Does anyone know what I’m doing wrong? Sent from my iPhone using Tapatalk
-
Left handed joystick to use for the radar stick?
longuich replied to Hawkeye91's topic in DCS: AJS37 Viggen
the tm t16000m stick has a converter kit i think. -
My guess is you’ll find better recommendations on the arduino forums. Sent from my iPhone using Tapatalk
-
Again .. Sent from my iPhone using Tapatalk
-
I have tried and failed many times. I will continue to do so until I succeed. Sent from my iPhone using Tapatalk
-
+1 ! Sent from my iPhone using Tapatalk
-
:) scratches need to be itched. Sent from my iPhone using Tapatalk
-
Most of these solutions are very unreliable. Why not get an (i2c) multiplexer to expand on pins? Sent from my iPhone using Tapatalk
-
Correct. We found that the current script does not support anything other than a single or double (of triple) pulse; bcause it’s a generic loop that catches all encoders and treats them all alike. Which is obviously the way we wwnt it in 2020 ,) Sent from my iPhone using Tapatalk
-
It definitely is bloated. And my coding skills don’t do it any good either. You’re absolutely correct. /but/ if your not using your fa18 ufc for your sabre or dora I figure the damage quite minimal. Personally I’m using this just for displays and an AOA indexer. So output mostly. All the buttons, encoders and pots are keyboard and joystick inputs. Sent from my iPhone using Tapatalk
-
I have NOT tested this. So it probably doesn;t work out of the box. (i'm obviously not a professional coder) The MC lines are from an actual working script. No if/thens needed. I remember testing this and could switch from av8 to fa18 and the mc light and switch would just work. To limit the load on your arduino or teensy you should incorporate ifs to not run unnecessary code. I don't have the module's names here but this is the idea: /* here's how to get the module name and cast it to a string */ String dasAircraft; FA18 = String("FA18_"); AV8B = String("AV8B"); void onAcftNameChange(char* newValue) { Serial.println(newValue); // print the name in the serial console dasAircraft = "newValue"; } DcsBios::StringBuffer<24> AcftNameBuffer(0x0000, onAcftNameChange); // use the dasAircraft string to activate part of the code and limit your *duino/teensy's resources with if/then's // // for example: void onUfcOptionDisplay1Change(char* newValue) { /* your code here */ if (dasAircraft == FA18) { String sNewValue(newValue); // catch newValue in string and replace odd characters char od11 = sNewValue.charAt(0); // grab individual char value at that specific index in the string char od12 = sNewValue.charAt(1); char od13 = sNewValue.charAt(2); char od14 = sNewValue.charAt(3); alpha4.clear(); alpha4.writeDigitAscii(0, od11,0); alpha4.writeDigitAscii(1, od12,0); alpha4.writeDigitAscii(2, od13,0); alpha4.writeDigitAscii(3, od14,0); alpha4.writeDisplay(); } if (dasAircraft == AV8B) { Serial.println("this is not for the av8b"); } else { Serial.println("not for an av8b nor fa18"); } } DcsBios::StringBuffer<4> ufcOptionDisplay1Buffer(0x7432, onUfcOptionDisplay1Change); this works: // start AV8BNA /* Master Caution Reset button on pin 15 */ DcsBios::Switch2Pos mCaution("M_Caution", 15); /* LED connected to pin 14 is Master Caution Light */ DcsBios::LED mcLight(0x786a, 0x0020, 14); // end AV8BNA // start FA18C_ /* Master Caution Reset button on pin 15 */ DcsBios::Switch2Pos masterCautionResetSw("MASTER_CAUTION_RESET_SW", 15); /* LED connected to pin 14 is Master Caution Light */ DcsBios::LED masterCautionLt(0x7408, 0x0200, 14); // end FA18C_ btw baco30, the code is a bit bloated because I was fiddling with replacing pieces of the dcs-bios output. But this is what you're looking for. I used the same type of displays ht16k33 with the adafruit library. Just get rid of the if's en thens and start experimenting.
-
Why aren’t you guys doing different modules within if statements? I’ve done that with displays and mcaution lights for three different modules and it works like a charm. Sent from my iPhone using Tapatalk
-
Solved more of less. Sent from my iPhone using Tapatalk
-
Oh wait. No that’s not going to work. I read a comma instead of a period . Sorry my bad. Sent from my iPhone using Tapatalk
-
Try the *2 directly in the joystick lines. (And delete the newly inserted lines). Sent from my iPhone using Tapatalk
-
rotaries = rotaries * 2; right under the last IFs should do it. Sent from my iPhone using Tapatalk
-
Just multiply the value of your encoder until it matches what you see. Sent from my iPhone using Tapatalk
-
Talk to Blacklibrary Sent from my iPhone using Tapatalk
-
Thanks. I see now. My bad. Sent from my iPhone using Tapatalk
-
Thanks. I meant the master caution led. Sent from my iPhone using Tapatalk