ESzczesniak

Thank you!

Is there any time that these 3 dashed lights illuminate 1) other than the lights test and/or 2) illuminate individually? I'm building a full put and Arduino outputs are certainly not valueless. As best I can see they only illuminate during the lights test and all together, so I could put them all on one output.

What type of loadout are you using? DCS simmers are a little aggressive on the load outs through TER's on, triple mavericks on a hard point, etc. These loads are notorious drag suckers and were rarely used. Particular at a hot Bagram with it's shorter runway, the A-10's just could not carry these operationally.

I'm looking for any of the experts out there that might be able to help me with a typical loadout for A-10C's out of Bagram late in OEF (2014ish). I'm having a hard time pinning down times from various photographs I'm finding. I think I'm getting to something like this: 1. Empty 2. LAU-131 - it seems APKWS is fairly common now, but if I'm correct, this would have been post 2014 for OIR? 3. AGM-65L - this seems pretty consistent, although I've found some with a SNIPER pod. From my readings, SNIPER on station 3 was earlier in OEF. 4. GBU-38 more commonly, sometimes GBU-12's 5. GBU-38 6. Empty - found one low res picture with what either looks like a Mk.82 or GBU-38 here. Article referenced 2012. 7. GBU-38 - I've found photos with GBU-31, but the information I've been able to gather is these would have been OIR birds 8. GBU-38 more commonly, sometimes GBU-12's 9. SUU-25 flare pod 10. LIGHTENING TGP - I have one book for 2007 - 2014 that identifies time pretty well. Most of the pictures at Kandahar earlier show the SNIPER, but the later ones from Bagram show the LIGHTENING pod. 11. Empty - when did the dual rail adapters stop being carried routinely? Of what I can find for later OEF birds, AIM-9's and the DRA were uncommon, but then they show up again for OIR birds. I'd appreciate any experts that can either confirm I'm on the right path, and/or note other common munitions. While I am also an avid DCS Warthog pilot, this is for a scale model being built of a 75th EFS bird in 2014 at Bagram. Hence the some what OCD detail attempt and effort to capture a static picture.

I'm starting to make some actual progress on my F/A-18C full pit. The right console has been my main focus and I have about 80% done/functioning. My basic construction are PC Flights panels connected at the panel to simple custom PCB breakouts. I've put each panel in a 3D printed enclosure underneath and lined the bottom with a basic LED strip/adhesive panel. Brightness is controlled with PWM through a MOSFET. It really isn't bad, but as I move on the lower MIP and then the left console, I'd like to tidy this up even more. So I'm looking at more formal backlighting options. There are principally 4 options as I see them: 1. The current solution: It works, but I'm not a fan of self adhesive's for long term fixation. My general experience is they tend to loosen and don't take well to repeat assembly/disassembly for trouble shooting and improvements. 2. Embedding thin LED light strips in routed channels on the top most panel. A Hornet's Nest has done this and it looks rather nice. However, I've had trouble sourcing 3 mm LED strips, and routing premade panels isn't entirely straightforward. I do have a CNC router, but without the source dimensions/files worry quite a bit about being off course and messing up the panels. 3. A separate LED PCB with SMD LEDs mounted sandwich between the inner clear panel layer and the switches. This has a fair bit of appeal if space wasn't an issue. But there is only 2-3 mm of space to mount such a panel in this area and this may not be possible. 4. Redoing the PCB's to incorporate SMD mounted LED's. I think this is the second most appealing solution. Being below the switches has the advantage of diffusing the light more, but the disadvantage of the switches and wiring shadowing out the light. So this brings me to my questions: 1. Does anyone have any advice on what methods to use? 2. Can anyone give me advice choosing a SMD LED? I have no experience here and could pick from fairly routine 0603, larger sizes with more light and possible with wider light cone angles. 3. Wire the LED's in parallel or series? I already am powering my LED strips with 24V power. But with forward voltages of approx 3V for the green SMD LEDs, in series I'd be limited to about 8 LED's still I think? In parallel, I could drop down to 12V and use a good PC PSU or similar. 4. Should I wire in capacitors? Would these defeat dimming with PWM? It seems like a lot of higher quality boards use the capacitors, but the ones I've worked with also only have 2-3 different light levels and not continuous dimming. I appreciate any advice and feedback. It's nice to see the pit coming along, but it also has me already wanting to think of ways to make it more real and polished.

Thank you!

As I'm endeavoring on my journey to move from Hub to Fork on DCS-BIOS and also start programming my own boards (servo gauges in particular), I have 3 questions: 1. Where's the best place for the most active support/help? I'm guessing there's a discord somewhere, but Googling "DCS-BIOS Fork Discord" didn't get me very far. 2. Is there a way to automatically connect the com ports? I've gotten far enough to use the multi-com-ports.cmd file, but I'd love to minimize anything I need to do beyond start DCS. 3. I'm having a problem with the connection to my Uno board only last a few seconds before getting "permission denied" in the connection window (screenshot attached). I had one connection earlier today that was stable, but that was it. It's been enough for me to almost have my first servo gauge running (F/A-18C Battery Voltage Gauge), but I'm not sure what to do about this once I try to start flying.

Thank you! I've never fully spent the time to learn navigating GitHub and it showed!

I came to find out I had been using the 4 year old hub rather than the new Fork to run a couple of my TekCreations panels. I think I'm about ready to try doing a few of my own servo gauges and have updated to the DCS-BIOS Fork. But I'm stuck trying to get BORT. Is this still the current program to monitor DCS-BIOS I/O. All I can find on the github is to download the source code. I don't see any setup programs or anything.

I am brand new to exploring this utility. I'm struggling through the forum and posts to find details. For what I'm trying to accomplish, I think the presets and config files are what I'd be looking for, but am not clear exactly what "manage config folder" does, or how to create/adjust presets. I'm trying to accomplish... 1. After DCS update, copy edited default.lua in to the F/A-18C joystick folder or add 4 lines of code (to enable fuel dump and pitot heater for WinWing startup panel) And, launch DCS in 1 of 3 configurations... 1. Non-VR, non-Tobii eyetracker ("turn off" headtracker.dll in main bin folder, set displays.lua to file created from Winwing Simapp Pro for MFD's) 2. Non-VR, +Tobii (restore headtracker.dll in main bin file, set displays.lua to single screen) 3. VR (disable headtracker.dll, enable VR settings) Does anyone have any advice if DCS Update GUI Utility 1) can help with this, 2) what functions to use, and/or 3) help point me to documentation?

There’s a reason the mission is often SEAD (suppression) instead of DEAD (destruction). Like almost all warfare, new technology doesn’t stay new very long and the opposition finds ways to counter the new threat. In the case of anti radiation missions and air defenses, it’s been learned to not make yourself a target long. Integrated AD’s can pass off from various emitter’s so none stay a target very long. And a competent crew sorts decoys rather well. So destroying the entire network is very challenging. However, if you accept the goal is simply to get the strike package through, you can force the network offline with enough SEAD assets. If you can keep enough HARM’s in the air, you can force the radars off for a short window to avoid destruction. Then add a bit of advanced jamming and some decoys, whatever radar sites do light up long enough to launch, may not launch on a very high PK solution. Hence the more common/practical mission being SEAD instead of DEAD.

I am having an issue with some of my Winwing devices not showing in SimApp. This is apparently related to Windows updating the driver to some version that causes SimApp to not recognize it beyond as a USB game controller. In an FAQ they review uninstalling the driver, clearing the registry with a .bat file, and reinstalling... https://wwsimstore.com/view/help.html?nav=W3siaWQiOjIsInRpdGxlIjoiU2VydmljZSJ9LHsiaWQiOjgsInRpdGxlIjoiU29mdHdhcmUifV0=&id=d3d0NDU= I am on the latest build of Windows 11 and their instructions are not matching with what I'm finding. They direct to Window>Devices. I don't directly have a "Windows" menu option, and if I type devices, all I get is "bluetooth and other devices". The next steps are to open properties, select a driver tab, then uninstall. This seems most like the Windows device manager, but I can't figure out how I could possible identify a specific device. Under human interface device, I get a lot of generic names as shown in the attached picture. The game controller menu doesn't give me driver options. Can anyone help me with how to uninstall the drivers a game controller?

If we are in the middle of the campaign and upgrades released, what is the correct upgrade process to not lose progress? Is it as simple as copying the new files? Also, I just re-downloaded the campaign about 5 minutes ago and mission 4 briefing still states push :20. Easy enough for me to cross it out since I saw the note for :30, but just FYI.

Thank you all! I was looking for Bankler’s solution. I’m looking for how to add a JTAC/TOO coordinate waypoint for on-call CAS missions.

This must be a stupid question, but all the YouTube videos about adding a waypoint that I've found so far add the waypoint to a sequence (HSI->Data->WPSEQUFC->INS...). How do I just add a waypoint in to the navigation system outside of a sequence? I'm think about if I were to add a JTAC target, or a specific IP, etc.