jaylw314

My understanding is that it is intended to be recorded on the HUD video camera, and reviewed after the flight for debriefing on a video player you can pause and step on.

Try https://www.digitalcombatsimulator.com/en/files/3315353/ or https://forum.dcs.world/topic/258743-agm-65-maverick-training-mission-stuck-at-mav-page/?do=findComment&comment=4539175

simply map the one on the stick into a 4-way hat. I use the ministick on a VKB gladiator to the TMS hat

If you're talking about the red exclamation mark, that occurs with binding errors, especially when you have a button bound to keybinds in both the aircraft section and the "UI Layer" section. If you have "Button 1" on Device A bound to ANY function in the UI Layer as well as any keybind in the A-10CII section, for example, the keybind in the A-10CII section will get the red "!" and will, in fact, no longer work. This is a good reason to delete ALL bindings in the UI Layer and program ONLY the ones you want with buttons that will never be used in any module otherwise. It doesn't explain why the OP's OSB buttons could not select the page on the MFCD as SOI, but given the first error, I'm inclined to believe there was some operator error there somewhere.

I have noticed this using stick control on a TWCS, WinWing Orion, and the ministick on a VKB Gladiator. It's most noticeable when you move the stick clockwise/counterclockwise at its limits. Occasionally, when moving around one corner, it will fail to register the next axis. So when moving right->right-aft->aft, the TGP goes right->right-aft->nothing until the stick is re-centered. I've tried this with curves, desaturation and cutting off the corners in joysticks that support this, to no avail. The TWCS uses pots, while the Orion and Gladiator have digital sensors, but the behavior appears identical

IIRC, they made a point of moving a bunch of UI and general controls to the individual modules, so if you're flying the A-10CII, it's there now. Weirdly, it's still in UI layer and allows only for a mouse keybind--go figure.

Just press the Master Mode button, it cycles the HUD mode from NAV -> GUNS -> CCIP -> CCRP Confusingly, if your in GUNS mode with the default gun reticle, and you're not in an attitude where the impact point is in range, the reticle will vanish and you'll get "CCIP INVALID" right where "CCIP" appears when you're in CCIP mode. Conversely, when you're in CCIP mode in the wrong attitude, you won't see the reticle or bomb fall line and you'll get no such error displayed.

I assume you meant DMS switch, not Coolie Hat switch. DMS left and right cycles weapons when HUD is SOI. HOWEVER: If the HUD happens to be in gun mode, DMS left and right cycles the gunsight reticle mode instead. That's why manually selecting a weapon fixed it, it switched you out of gun mode into the HUD mode connected to that weapon profile (CCIP or CCRP).

No, just the edit you can make to the lua brightness to find a reasonable medium between day and night

Yes, the A-10 is only for people who can multitask

Cool beans, thanks! I kind of liked @Caldera's boot size theory, though!

@Yurgon speaks correctly. The MVR setting corresponds to no button being pressed, and UP and DN correspond to the respective "Flaps Up<>Center" and "Flaps DN<>Center" keybinds. When you start, you might need to cycle the flaps switch to get it in the correct position, or have the "sync HOTAS" option in settings enabled.

I'd suspect more so that they're trying to get people ready for flight training in general, and just happen to be using DCS and the A-10. The A-10 is one of the most conventional flying jet aircraft.

In DCS the "night" setting just makes the HUD amber, which doesn't sound NVG compatible to me It depends on your NVG brightness, on full moon nights I don't have to change the HUD intensity, but on dark nights I'll have to turn the NVG's up and the HUD down. I've not had problems finding a setting that works for the HUD. The NVG's themselves, on the other hand, have had some challenges on and off over the last several updates

That would be nice if so! I wonder if the F-15E uses the same throttle, that would be a nice bonus

The WW Orion throttle? I use the upper 4-way switch and lower 4-way switch for the mic. China Hat switch is on the joystick in my setup. Remember the 4-way switches are both actually 5-way switches, you can press them in too

Late to the party here, but on the VR4DCS blog, it's been suggested that HAGS (hardware accelerated GPU scheduling) is on by default in Windows 11 and can result in some problems in some use cases. HAGS is not on by default in Windows 10. I don't use Windows 11, so I don't know much more detail, but you might want to look into that if you plan on Win 11 in the future

FWIW, upscaling results in some GPU overhead. You can see that additional GPU frametime in the "GPU scl" on the OpenXR Toolkit advanced overlay. In theory, upscaling can worsen performance if you upscale less than a minimum amount--the overhead could be more than frametime you gain in the reduced rendered resolution. To put it in perspective, in FSR 1.0, AMD calls "quality" 67% and "ultra quality" 77%. That seems to suggest above 77% you will get diminishing returns or even performance decrease. FYI, in Open XR Toolkit, setting a upscaling percentage over 100% reverses the ratio, so 120% = 83%, and 133% = 75% So you'd need at least 130% to get to AMD's "ultra quality" setting, and 150% to get to "quality". I don't have any experience with NIS, but given the reported similarities, I suspect the numbers work out about the same.

I recall in the past the check in with the AI JTAC would refer to APKWS as "AGR-20", both audio and text?

Either that or he realized he screwed up after intending to use the designator laser instead

LOL, neat!

I'm pretty sure the A-10 won't fly without the gun. Heck, I thought I recalled the empty casings are retained mostly to prevent the plane going out of CG limits. Is the max gross weight for the C significantly higher than the A?? I would have thought they'd be the same, there's no airframe structural change, right?

Very cool beans, thank you!

Wait, did you change them? I had tried injecting the commands from your post last week, and OPEN and HOLD worked, but not CLOSE

The biggest advantage of using "QNH" is that the altimeter setting is always in the DCS briefing and works over the entire map. Wish it worked that way in real life In US general aviation, when you're on the ground at an airport with no ATIS or automatic weather info, the FAA actually recommends pilots set the altimeter to the known airfield elevation, so it's not just a DCS workaround either