Flappie

Here's the missing axes that I plan to report. I've also found a few bugs (clock and KM-2 instrument). Please check if I forgot anything. PILOT : ARK-15 Volume Knob Radio Jadro-1A Volume Radio Jadro-1A Squelch Knob Radio R-828 Volume Knob Radio R-863 Volume Knob SPU-8 Main Volume Knob SPU-8 Intercom Volume Knob Altimeter Baro Pressure Pilot Knob RMI-2, Course Rotary Knob ((autopilot route azimuth)) PKP72M Pitch Trim Knob Greben Latitude Knob SPUU-52 Test Adjustment Knob Recorder MC-61 Brightness Knob RV-5 Dangerous Altitude Knob ((radar Altimeter Adjust)) Sight, Manual Firing Distance Adjustment Knob Sight, Moving Crosshair Brightness Adjustment Knob Sight, Moving Crosshair Horizontal Adjustment Knob Sight, Moving Crosshair Vertical Adjustment Knob Sight, Fixed Grid Brightness Adjustment Knob Sight, Target Base Adjustment Knob Radio R-852 Volume Knob (keys are also missing?) Backup ADI Vertical Adjustment Knob (keys are also missing?) Cabin Pressure (keys are also missing?) Autopilot Heading Channel Delta Correction Knob (keys are also missing?) Autopilot Roll Channel Delta Correction Knob (keys are also missing?) Autopilot Attitude Channel Delta Correction Knob (keys are also missing?) CPG : ARK-15 Volume Knob SPU-8, Main Volume Knob SPU-8, Intercom Volume Knob Left Timer Interval Knob Right Timer Interval Knob Baro Pressure Knob RMI-2, Course Rotary Knob ((autopilot route azimuth)) (keys are also missing?) Sight Light Brightness Knob (keys are also missing?) Deviation compensator bug to be reported : KM-2 Set Magnetic declination (value does not change) EDIT: request made.

I'm seeing different results with different builds. I'll report to devs and I'll see what they answer. EDIT: Devs answered swiftly. A fix is in the making.

Thank you very much. In your mission, units are close to high buildings. Petrovich can't find them when I fly to the West. He finds them as soon as I fly to the East. I'll send my track to devs.

Missing buttons/switches/covers commands listed here a few months ago should be added to the next core update. Hi Benou! While we're at it, are there other axes needed?

Maybe I got lucky. I saw a lot of decoration objects down there. Bicycles, benches, light poles, barriers...

Many thanks for the example, @SemperFi. I gave it a go and Petrovich was actually able to find it. Since the map was updated some weeks ago, please make sure your DCS is up-to-date, just in case. M113_germany.trk

Come to think of it, I know some old planes/helicopters modules never got the JTAC item: UH-1H, Mi-8, MiG-15 (the latter does not have a compatible radio anyway)... and I think the L-39 is one of them. The F-86 module eventually got it in May 2025. I'll ask for it to be added to the L-39.

I gave it a try: I set up two JTACs, one emitting at 133 AM (VHF), the other one emitting at 256 AM (UHF). I can call the Radio menu from the L-39ZA using the "VHF Radio Button - Push to talk" command, but the "JTAC" item is absent. I can call the Radio menu from the L-39C using the "Radio Button (call radio menu)" command, but the "JTAC" item is absent. In the same mission, I can see the "JTAC" item when flying in a F/-18C and both JTAC answer whenever I call them. I'm not familiar with the L-39. I'm not 100% sure it is a bug. @razo+r Can you please give my track a go? L-39_no_JTAC.trk

Don't forget the periscope gyro can be botched, which prevents Petrovich to find targets (because he's not looking where you look at anymore). You can check whether the issue comes from the botched gyro by switching to Petrovich seat and try to find the target using the periscope.

Hi. Try this: Ensure you don't have a "headtracker.dll" in your DCS /bin folder. If you do, delete if, then retry your TrackIR in DCS. Still crashing? Close DCS and the TrackIR app. Go here : C:\Users\***\AppData\Roaming\NaturalPoint\TrackIR 5\ You should find some files and a "Profiles" folder. Make a backup of all these and place your backup in "Documents" or in another safe location. You can now delete these files. Run the TrackIR app WITHOUT admin rights. Customize your TrackIR commands (Pause, Reset, Stop). Run DCS and check whether it keeps crashing. Still crashing? Uninstall then reinstall the TrackIR software. Once the problem is solved, copy-paste the content of your former "Profiles" folder into C:\Users\***\AppData\Roaming\NaturalPoint\TrackIR 5\Profiles

The problem affects several terrains. Ugra Media have been working on this matter on Germany but it looks like it needs more work. Some terrains have multiple "decoration" objects, such as walls, barriers... and the Petrovitch AI has to process them to know whether it can see an enemy or not. The more objects, the more Petrovich gets lost. I believe it can also cause performance issues. Without data, devs won't be able to identify problems. When this issue arises, please provide a short track. If you can't provide a short track, at least provide target coordinates along with the Hind heading. I'll reproduce the issue and show it to devs.

I'm in the process of making comparison GIF for all aircraft. So far, I made 6 of them and I can tell you that: HUD boldness is not affected by resolution for the following aircraft: JF-17 (the result is very clean) A-10C Ka-50 (the result is poor because characters are much too bold, whatever the resolution) EDIT: AH-64 HUD boldness is indeed affected by resolution for the following aircraft: AV-8B F-16 F/A-18C EDIT: F-15E affected too, even though it's less striking I stand corrected about the AV-8B. This GIF method is the best I could find to demonstrate the issue (even to myself). Thanks for pushing me harder when it's needed, gents. Once I'm finished, I'll report all affected aircraft individually.

My screen is the same size and I run DCS at this resolution. Here's another test I'm about to do: I'll compare HUDs of 2560x1440 versus 3440x1440 screenshots.

Thank you, @SignorMagnifico! I'm able to reproduce the issue in your track as soon as I add Motion Blur, even after I take control over it (which is rarely the case with tracks showing the infamous flickering black screen). I tried your track with a different aircraft (F-16) and couldn't reproduce the bug anymore. I then made a new mission over Caucasus with dense fog and a sunset with two F-4En and... I made a strobe light out of DCS. Still no such issue with the F-16. I'll try some more aircraft before reporting it. EDIT: I'm now able to reproduce the issue without fog. I believe there are two issues: the F-4 induced motion blur issue (I'll report it), and the one described by @HR-Crumble that I'm yet to reproduce. F-4 induced issue reported.

Reproduced in a short track. Issue reported.

Many thanks, @nakushh. Issue reproduced, but the track is very long. I'll see if I can make a shorter one.

Devs said they won't do it, sorry.

Please attach a short DCS track.

I cannot reproduce the issue for now, even with fog. Can you please post a track demonstrating the issue?

My test: zoom out and see if characters are still readable. HB AJS37, F-14 : different tech (letters don't seem to be made of segments) -> they are perfectly OK RB M-2000C : text doesn't appear to use boldness at all -> I think it's OK, even though characters seem too thin when zooming out (they almost vanish) ED A-10C, AH-64 (helmet HUD), F-16, SU-25 and Su-27/33/JF-11 : text boldness does not appear to increase when zooming out -> I think they're OK RB AV-8B and F-15E : text boldness does not appear to increase when zooming out -> I think they're OK Deka JF-17 : text boldness does not appear to increase when zooming out -> I think it's rather OK, even though characters seem a bit too "fat" when zooming out. Aerges Mirage F1 : text boldness does not appear to increase when zooming out, yet texts are small they are very hard to read from a distance -> I think there should be an option for bigger text ED F-15C MFCD, MiG-29 MFCD, F/A-18C HUD and Ka-50 HUD : text boldness appears to increase when zooming out ->I think they're bad Modules with no HUD, or no HUD text: CH-47, F-4E, F-5E, F-86, L-39, MB-339, Mi-24, Mi-8, MiG-15, MiG-19, MiG-21 ,Mosquito, OH-58 ,all 8 warbirds, SA342, Yak-52, UH-1H. For now, I'll make separate reports for the Ka-50, the F/A-18C, the F-15C MFCD and the MiG-29 MFCD. If you know any another way of showing whether fonts are unreadable in some circumstances, please tell. EDIT: 2025/08/02 - thanks to the making of GIFs (below), I revised my judgement about AV-8B, F-15E and F-16C HUD boldness. @BJ55 I cannot reproduce your issue, even when using your options.lua. I'm pretty sure your issue comes either from your graphics card settings or your shaders cache. First try purging your shader cache (in your Saved Games/DCS folders, empty the "fxo" and "meatashaders2" subfolders). EDIT; I'll test with fog and repot back in the other thread.

@-Scrat- I'm on it. I'll publish here the list of all affected aircraft and make separate reports for devs (some modules seems to be OK: A-10C, F-16C, AH-64, AJS37...).

The situation is much exaggerated in your JPG screenshot. Here's a PNG taken with the default zoom view: yellow figures are OK, green figures are not very readable, indeed.

@BJ55 This does not look normal at all. I'll try this resolution right away. Can you please send me your options.lua ? (from Saved Games/DCS/Config)

I've just filed a request to devs.

@Peter33 It seems the bug was fixed (again) at some point, I cannot reproduce it anymore.