Guppy

I've got another question for you all. To display the RPM for the L or R engine the string buffer is set as 2. This works fine when the RPMs are <100, however when the value is >= 100 it truncates the last digit. I'm outputting to a OLED. IE: 98 displays as 98; 100 displays as 10. In order to resolve this I set the string value to 3. Now this works for >= 100 but not for <100. IE: 98 displays as 989; 100 displays as 100. Any solution with the Arduino code to work around this? I understand in theory how to do this IE: If value <100 String = 2 elseif >= 100 string = 3... however I'm not very good with arduino syntax yet.

Fri13, it's important to understand the word "cheating". Cheating: act dishonestly or unfairly in order to gain an advantage, especially in a game or examination. No one is acting dishonestly or unfairly. Doing something that is not "real" is not cheating. It's just that, not real . When you "fly" do you have a leg pad with all the real procedures and checklists to follow? If not you're cheating simulation. Everytime you start the Hornet do you follow NATOPS standard start up proceedure? You ensure all your switches are in the correct orientation before you start up? If not you're cheating. Many people do not want to have to reach for a mouse, turn and flick a switch in the pit every time they need to use it. This is far more effort and coordination than what is required in the real world. Especially when you factor turning away from your monitor. You lose spacial awareness. It's a game bro and no one is cheating by mapping controls that arent made for a HOTAS to their HOTAS. Stop being a rivet counter. And to your comment about VR - I would argue it is even more of a necessity to have as much stuff mapped to your HOTAS as possible. Good luck finding that mouse... super immersive.

By this definition if anything is mapped to your HOTAS other than HOTAS functions then you are cheating. Extra buttons on your X52? NOPE. Cheater. Extra switch on your Warthog... CHEATER. Come on bro, come back to Earth.

Correct and they hired someone new to help out with the 16; these are the things I'm saying. They plan to get out of EA for the viper in early 2021. But this "oh they only care about Navy fans" is out of control and childish.

Dude you sound like a small child. https://forums.eagle.ru/showthread.php?t=269757 They have different teams working on different items; the Super Carrier being one of those the and the Hornet and Viper being others. The Hornet is the priority for them because it came out far before the Viper. The community demanded they pivot back to the hornet and they did.

I believe it's just repairs done and it has not faded.

While true I'm not sure the LSO would guide you IRL...

I guess I don't understand the difference. I use DCS BIOS with my own homemade panels using Arduino boards and switches; specifically the Mega. IDK how to make it work with that.

uploaded where? I'm sorry?

Hey guys having an issue with the Hornet LST/NFLR switch. I've tried two ways: DcsBios::Switch2Pos lstNflrSw("LST_NFLR_SW", 9); and const byte lstNflrSwPins[3] = {9, 10}; DcsBios::SwitchMultiPos lstNflrSw("LST_NFLR_SW", lstNflrSwPins, 3); The switch will not move, I've tried different toggle switches just incase it was a mechanical issue. Arduino reads it, DCS does nothing. Interestingly it will send signals and move the FLIR switch. Any ideas

AHHHHHHH! it worked. Okay thank you very much!

Can someone please explain how this is supposed to work? The only call that is working right now is "inbound". In the instructions it stated for it to correctly work I would need to follow the flow from the SC documentation...great. "Inbound" or "established" or "commencing"...only "inbound" works "checking in" does not work "platform", does not work "see you at 10"...does not work "ball"...does not work "kissoff" does not work. So then I looked more at the VIACOMPRO instructions..."There are new keywords in the database: make sure to go through the FINISH steps." Where are the finish steps? Ideally, I'd just like to follow the basic COMM menu. "inbound", followed by "see you at 10", followed by "ball" for Case1. The only thing that is working is Inbound. Help would be greatly appreciated.

Do you have an example of this? It makes sense, I'm just a bit confused on how to write the actual code.

Hey guys - I have a question. I have 3 position switch that are on(mom)-off-on(mom). I occasionally like to use these instead of Potentometers or Rotary Encoders for lights. I've used these switches to toggle the brightness of lights up/down. I only need to hold the switch in the given position until I have the lighting I wish to use. I have several Ardunios that show up as USB Joysticks. Mapping is done through DCS itself and it is super easy. In terms of DCS BIOS; how would I create this same logic? I initially thought using the RotaryEncoder function could work, but it does not for these types of switches. here is an example of what I'm trying to do: DcsBios::RotaryEncoder instPnlDimmer("INST_PNL_DIMMER", "-3200", "+3200", 30, 32); I know these switches are not rotaries (obviously!) but in theory they are doing the same thing? sending a "pulse" on the given input...

removing for proper thread.

Hey Virus - I sell my work. I can rework my UFC to your specifications and support any tweaks you might have. Feel free to send me a DM for details.

Hey Guys - So I'm pretty fluent in designing things in CAD and I'm working on my own UFC. I'm a bit disappointed in most of the cut-out hole button options, which obviously leads me to the use of tactile switches. As you probably know tactile switches are mostly used with some sort of PCB. Since I'm designing my own UFC I want to also design my own basic PCBs that I can have some manufacturer make. Does anyone have great tutortials/free software guides to do this? It seems relatively easy, but I also feel like it's probably more complicated than I think. I've been toying around with Design Spark... I'm having some issues getting things placed in the exact measurements I need. Curious for any KB articles or advice on this endeavor.

No performance change for me. Lowest possible settings in game, including all shadows off. 1.0 pd; no improvements. HP REVERB 2080Ti 32gb RAM 8700k @ 5.2 SSD

I use a small amount hot glue. It's just sticky enough to prevent this from occuring.

I was just about to respond with an update. The newest Nvidia drivers are the problem. Reverting back to 442.74 resolved this issue for me.

I mean really bad. Here is the track from the 104th. 120 FPS down to 10, sometimes 20 FPS. https://drive.google.com/file/d/1BTrGfaxlfdwrb2SJzO7-Q3WUnz9CoJ_k/view?usp=sharing

[REPORTED] SA PAGE DROPPING FPS I’m going from 120+ FPS down to 10-20 FPS every time I turn on the SA page on multiplayer.

Thank you sir!

I mean... everything is literally a choice. I, as a consumer, set my level of expectations and willingness to participate. My apologies if my minimum standard is higher than yours. There are a plethora of other games that I can play without these kinds of issues.... and so I do.

BN - can you please provide us an update after you speak with the team? IE: do they acknowledge there is an issue or is it just us? Have they identified a source of the issue but it just needs time? I appreciate you relaying our feedback to the team, but sometimes it feels like we don't get 360 feedback. That is, we hear you're bringing our issue to the team, but we don't know where it falls. Maybe it's de-prioritized; Maybe you're months from a fix. As upsetting as that is, it would at least temper our expectations. Right now I eagerly wait for patch notes just to see nothing related to the performance issues me (and many others) are encountering. Right now I cannot play and I have not played since 2.5.6 dropped because I fly MP with my friends who all play on the beta channel, like most of the community. I recognize there is a Release channel to play on, unfortunately I only fly MP and that community is overwhelmingly in the beta channel. So for me, I have not touched DCS in quite some time except to validate a patch has not worked for me.