Puma

Are there any indications of how AR might work with DCS? As a simpit owner, the dream would be being able to draw a horizontal plane in meatspace, and above the plane show DCS, below do passthrough.

I think one suite used osb16 to show their flight number and ship number within that, however 1433 would not be valid for such a number, so it could be a made up EDism, or something that has changed with the suites.

I think the concept behind showing the menu even if you’ve keyed the wrong radio is that it mimics real life. Nothing stops you from speaking after you’ve keyed the wrong radio, so the burden is on you to confirm radio usage before transmitting. In multiplayer it will broadcast as well so you can hear the unintended broadcast and correct the caller. I’m mot following what you mean when you say “Intercom with UHF tuned”? The intercom control panel rotary affects only the front mic switch. Aft and down positions are unaffected. Not 100% sure DCS has the modelled correctly, but thats my understanding of how it should work. UHF for tower comms would be most common in USAF as far as I know, so stick to UHF for best results.

Indeed I don’t think that ED realizes they control the assignment of developers. Somehow just saying that a developer was re-assigned is not a good look since someone inside the organization decided to re-assign him in the first place. I respect complexities of limited resources, but I think they would gain more respect by being honest that the project was deprioritized versus other modules.

Sorry I’m late to this. The dcs-bios arduino flightpanels fork has a solution where one pin can control both a cover and a switch and does the sequencing for you. https://github.com/DCSFlightpanels/dcs-bios-arduino-library For example: // A switch that has a cover in DCS that must be opened before the switch itself can be activated DcsBios::SwitchWithCover2Pos pltLaunchbarAbort("PLT_LAUNCHBAR_ABORT", "PLT_LAUNCHBAR_ABORT_COVER", 6);

Enable control reference (rctrl+enter) and make sure you aren’t having an axis or binding issue?

Is this the mode where if you now slave all to spi, you can get your tgp to track your gun predicted point of impact?

TAD hook and HMCS hook have always been separate as far as I know. I have intentionally hooked different symbols in tactical situations months ago.

Is there any additional information required to have this at least looked at?

I have also experienced this a couple times in dozens of flights, under very similar conditions (mission file). I support your theory that it relates to trim, but have no conclusive evidence to add yet. 100% confident there is an issue in here somewhere though.

In pit, CMSP on in STBY. Right click DISP switch. Observe switch stays up/on as long as right click is held and observe the CMSP display shows the settings of the current program. Release RMB. Observe the switch returns to center and the CMSP display continues to show the settings of the current program, allowing you to the set the SET + NXT to make adjustments. All good so far. Now, bind a keystroke to CMSP DISP Menu and repeat the test above. Observe that when releasing the keystroke, the switch returns to center but the CMSP display also returns. Thus to make adjustment to the program, one must hold the DISP keybind down while making changes. The keybind and the cockpit mouse binding to the same switch should have the same effect.

TO1A-10C does have the warning clause “Aerodynamic blowback may not fully retract the flaps”, so it seems fair that DCS chose to model partial blowback. It likely should be a function of airspeed rather than initial flap position, but it can’t be said its “wrong” as it stands. Fun bit of trivia to have discovered, thank you.

My bet is leftover wake effect from -1 landing ahead of you. As -2, adjust your aim point 1000' down the runway (assuming you have enough runway of course).

TO 1A-10C-1, 2 APR 2012, pg 1-319

In real, vhf fm guard is 40.5. Not sure if thats true in DCS though. Monitoring simple radio may give a hint? Selecting EMER will also transmit on that radio’s guard freq.

FWIW, Looking at the few references to suites in the 2012 -1, the arc-210 actually proceeded suite 5, but obogs was in before suite 6, so that makes me think suite 5 is the closest match?

It is an observed behaviour that from level flight, the radar altimeter switches to XXXXR at approximately 35 degrees of bank in either direction. Comparing to the publicly available A-10C -1, this is not the correct behavior. The -1 states that above 3,000’, if the pitch is +- 35 degrees, then the radalt should function up to +120 degrees of bank in either direction. If pitch is 35-50 degrees, only +-15 bank is tolerated. Beyond 50 pitch behaviour is undefined. Below 3000’ its actually better, with less than 45 degrees of pitch providing 120 degrees of bank, and 45-60 pitch allowing 15 of bank. Page 1-69 for the original wording.

Were your fire handle still out? If so that starves fuel to whatever is out, so maybe your apu and right engine handles were pulled?

I regret to inform you... that I am an idiot. I confused the hdc hook symbology with the tgp frame. Sorry folks; will vet my reports better in the future!

Configured without tgp. No manipulation of spi. Selected steerpoint showed the dashed box around it which looked like the tgp fov symbology despite not carrying a tgp.

Set any cms program. cmsp in manual. start 6 flare and observe the program display Z (correct). before the 6 flares finish, start 6 chaff. Wait for the program to finish and observe that the program remains on Z (bug). Can be cycled back but takes clicking through the whole alphabet. Expected behaviour: after any quick-program Z, the original non-Z program should be restored.

Have your tried manually entering your hot instead of relying on the terrain database? Your tgp with laser should give an accurate elevation for your target markpoint, but it dts mode I still think the terrain database will impact ccip. Set manual hot to the correct elevation and try again.

Great write up Sleepy. I’ll offer additionally that a key fundamental would have helped as well: if -2 lost visual on -1 (and therefor was unable to maintain formation), “blind” should have been called which would have notified -1 that -2 needed navigational aid. As lead, you have a short right to assume -2 is still in the last called formation until a blind call. You did well to notice and of course -1 is ultimately responsible. It’s never fun to call blind, but I’d propose that it is a more universal solution to a situation like that.

The radio presets bug is a real challenge to work around in multiplayer. Pilots think that using presets other than 2-5 “work” but above 6 the radio can be on a different freq each time you use the preset. Yes the bug is “reported” but I agree that at least an update on these would be good pr. Many bugs in A-10C 1 remained reported for years, so I don’t think that the community puts much faith in the tag

Best you could do today is setup a viewport lua for a custom screen layout, and position one exported mfcd offscreen.