Jump to content

Flappie

ED Beta Testers
  • Posts

    17385
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by Flappie

  1. 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.
  2. 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.
  3. 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.
  4. Reproduced in a short track. Issue reported.
  5. Many thanks, @nakushh. Issue reproduced, but the track is very long. I'll see if I can make a shorter one.
  6. Devs said they won't do it, sorry.
  7. Please attach a short DCS track.
  8. I cannot reproduce the issue for now, even with fog. Can you please post a track demonstrating the issue?
  9. 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.
  10. @-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...).
  11. 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.
  12. @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)
  13. I've just filed a request to devs.
  14. @Peter33 It seems the bug was fixed (again) at some point, I cannot reproduce it anymore.
  15. @Chipensaw Tested with today's update. It works fine in MP on my server (tested with the "Easy Rhino" slot and the 135 AM frequency).
  16. Some progress have been made in the Mi-8 DISS-15: now the "LEFT/RIGHT" and "FORWARD/AFT" signs are placed correctly.
  17. We need a track for this kind of issues, please.
  18. Fixed in today's update.
  19. Sorry to disappoint, I'm more into RedHat.
  20. Thank you. Wow, it's the Windows equivalent of "dnf". I had no idea this thing existed.
  21. Hi gents. I don't know winget at all. Can you please tell me which commands to use in order to get the wrong version displayed? If possible without the need of installing DCS.
  22. I saw your issue and simply moved the "ROE = HOLD FIRE" instruction at the top of the pile. It works in MP now. JTAC Test_MP_fix.miz
×
×
  • Create New...