Flappie

It should be fixed in the next update.

A fix is coming this way.

Thanks, @UnderTaker2003. Antialising looks "OK" to me. It has its limits as stated previously by user @Czar66. I tried to reproduce the black smudge issue with my NVIDIA GPU (you never know) but I couldn't. I'll now ask my fellow testers with AMD GPUs to try and replicate the issue.

Can you take a screenshot of your shortcut (just like I did above) and attach your autoupdate_log.txt as well, please?

I'm still pretty sure the cause of your issue is here: 2025-02-21 01:48:37.191 ALERT WRADIO (Main): Error in wMessage::buildSpeech(), event = wMsgLeaderCheckIn:: [string ".\NATO.lua"]:333: attempt to call global 'isHeavyAircraft' (a nil value) stack traceback: [C]: in function 'isHeavyAircraft' [string ".\NATO.lua"]:333: in function 'make' [string ".\NATO.lua"]:937: in function 'make' [string ".\NATO.lua"]:948: in function 'make' [string "./Scripts/Speech/common.lua"]:3223: in function 'make' [string "Scripts/Speech/speech.lua"]:150: in function <[string "Scripts/Speech/speech.lua"]:129> because, as you can see, part of the mentioned Lua files deal with JTAC comms (below an extract from NATO.lua). --JTAC local function isHeavyAircraft(pUnit) return pUnit:hasAttribute('AWACS') or pUnit:hasAttribute('Tankers') or pUnit:hasAttribute('Transports') or pUnit:hasAttribute('Strategic bombers') or pUnit:hasAttribute('Aux') end I thought the repair would fix these Lua files, but maybe they were already OK, which would mean something else is causing the issue, maybe a mod. But just in case, try this: Browse to ".\DCS World\Scripts". Delete the folder called "Speech". Run a DCS repair (yet another one). See if you the issue is still present.

This issue is completely random. You may think you don't have it anymore but it will come back. Fortunately, the next core update should fix this (I cannot reproduce this issue anymore with ED internal build).

On this page, there's a link to a zip file. Download the zip, then extract its content to ./DCS World/bin/ and accept overwriting. You now have a valid DCS_updater.exe file. Make a shortcut from this DCS_updater.exe file. Edit the shortcut (Right-click > Properties) and in the "Target" field, place the cursor at the right end (after the double quote character), press [SPACE] once, then type repair You should now have something like this: Click "OK" to save. Double-click the shortcut you created. It should start a DCS repair.

With 64 GB of RAM, Windows gives a default 4 GB pagefile, which is enough for now.

Actually, I wasn't. Thanks for notifying me. And it seems there's a lot more "semi-unofficial" frequencies available for some aircraft (purple cells in my spreadsheet that I need to test). I want this spreadsheet to show what's officially supported by the real aircraft, but I might add an "unofficial frequencies" page someday.

A long time ago, I made a lot of MP missions for my community. Which is why I started this document. Later, my friend made his radio presets mod so I don't spend time manually setting frequencies in the ME.

@rob10 Forget about the old link, I'm working on a new version (WIP): https://docs.google.com/spreadsheets/d/1m8bXImR4A-P4r0QGYxYyjVC-uLgJxuq-_zSGix4cfhI/edit?usp=sharing The most important part is on top: these are ranges that are common between most aircraft (except MF/HF which is almost only used by Soviet-era aircraft).

You are right, this mod was not designed to switch between AM and FM. But why not use the VHF AM 118-136 MHz range to have F-16 communicate with F/A-18? AM has a much better range (you will lose the signal quicker in FM)

I believe the textures are here: .\DCS World\Bazar\Textures\TerrainCommon

The real aircraft manual states: That must be it: TR is for training.

This F-100 manual from another sim states: Maybe TR is for "transient"?

Here's the same instrument with the "TR" marking: https://www.recoverycurios.com/f-86-sabre-type-a-4-variable-gun-sight-selector This pages reads "When a high speed attack was made on a slow moving target, the switch would be set to LOW. The switch would be set at HI when the speed of the target was the same as the pursuing aircraft." I'm not sure what "TR" means..

I wasn't, devs did. I hope they are right. We couldn't reproduce the issue after the fix, but since it's a random issue, I'll wait for your feedback a week or two after the next core update before calling it "fixed".

The next core update will contain a fix for this issue.

A few years ago, a friend of mine made a program to set frequencies in .miz files. I don't know if it still works (it's from 2020), but I suggest you give it a go: https://github.com/zedroopy/DCS_Radio_Mission_Mod

Hi @MartinCo. What would help here is a track able to reproduce the crash. When this kind of crash happens, open the latest zip file from the server's "Saved Games/DCS/Logs" folder: if a .trk file is present, attach the whole zip file here.

I checked and it does not seem to be a new behaviour. This was done in 2023 ("Added AN/ARC-210 default FM in 136...155.9975 MHz"). Maybe you weren't using the same frequencies before? Since the current behaviour is intended, I've asked devs for a subtle change: Typing a frequency automatically should select its default modulation (unchanged). Fine tuning the frequency using the "<>" arrows should not change set modulation, unless the new frequency is the beginning of an exclusive AM or FM range (e.g. if the set frequency is "155.9 AM", a click on ">" changes to "156 FM").

@Kappa-131st It should be fixed in the next core update.

That's strange. I can reproduce your issue but for 20 seconds only. Please attach your options.lua (Saved Games/DCS/Config/options.lua).

Well, I've just told you. Example: 1. You change an action from "SOUND to COALITION" to "SOUND to ALL": the sound will be kept so you don't have to look for it. That's a very small fix but that's a good fix. 2. You change "SOUND to ALL" to "DO SCRIPT" or any other action which does not start with "SOUND to...", the sound path will be lost, and you won't find it back by re-selecting a "SOUND to" action (the file is still in the .miz file but the ME has no access to it). In this case, you don't want to save the mission otherwise you will lose the sound file for good (as usual).

A fix is coming with the next core update: whenever you will change a "SOUND TO x" action to a "SOUND to y" action, the sound file path will stay the same. That's all I could get for now, but it's a good thing.