Flappie

Hi. You may encounter the issue described here: The solution for me was simple: look for old .diff.lua (and sometimes even .lua) in your "Config/Input/..." folders. Please make a backup of your Input folder before you start deleting files.

Oh, you're right, I forgot that "bin" had become the default. False lead, then.

Yes. Because so far neither Heatblur nor ED devs manage to reproduce the issue. It's hard to fix a bug when you cannot witness it on your own PC. An idea has just crossed my mind: please ensure you run DCS from ".\DCS World\bin" (not bin-mt) and see if you can still reproduce the issue. ("bin" and "bin-mt" folders contain the same binaries)

@Habu_69 You there?

This issue was reported internally in November. I've just added @Avalanche110's track to the report since it allowed me to reproduce the bug.

Issue reported.

I think the current version of the ME works approximately like this when it comes to sound files: You create a SOUND trigger and pick an audio file for it: the file is put into the .miz file the trigger has a relative link to the sound file (e.g. MY_TRIGGER(./my_sound.wav, ..., ...). You change your SOUND trigger to another type: the sound file is still contained in the .miz however there's no trigger that refers to it anymore, therefore this sound file is not referenced in the ME anymore You save your .miz: since no trigger refers to this sound file anymore, the ME ignores the sound file and only saved the rest. The audio file is then lost. We need the ME to keep an index of each sound files contained in the .miz independently of the triggers, so even when all SOUND triggers are deleted, you can still pick any sound contained in the .miz file. And I think the ME handles Lua script files exactly the same way.

You're welcome. All mission designers, me included, have been struggling with how the ME handles sound files. It's time for a change. I took the opportunity to ask for a combo list showing all added sounds, something like this:

Hi. Try to lower your "Preload radius" setting in DCS (lower it to 100 and see if it helps). If it does not help, please attach: your Export.lua file (from "Saved Games/DCS/Scripts") - it's OK if you don't find any, it's optional your DxDiag log (here's how to obtain one)

I've just found an internal report about this issue. It says the issue only happens when AIRCRAFT ADDITIONAL PROPERTIES > Realism > "No alignment and fixtaking needed" setting is applied, but I'm not so sure. I sometimes manage to get the wind on the PVI but I need to know how. EDIT: OK, you need to change that setting, change the wind conditions and then you will have wind in the PVI (this is just a workaround). I'll bump the report.

Reported as well, then.

Many thanks! I'm able to reproduce the issue. It is now reported. By the way, is that normal that Airport point labels don't appear on the map?

Issue reported.

@Weez I cannot reproduce this issue. Is it fixed for you?

Hey, thanks for the video. I'd very much like to get your track, please.

Thanks @Rolds. The issue is now reported.

OK. If you want to make the test, just use this Disable/Enable feature, it works very well (you won't break anything, you just tell Windows not to use such device for now, but you can tell it otherwise whenever you want). If you want to try and uninstall, a DCS user found the solution here: https://www.reddit.com/r/steelseries/comments/qcnfy4/steelseries_gg_installed_the_new_sonar_update_and/

Thanks guys. Magnitude devs said it was fixed but I didn't know if the fix was already in Release or not. It appears it is, I'll tag this as fixed.

It sure looks like a difficult mission because targets are hard to find. Also, the first part of the nav is a lot of fog. I had to flew on top of it, until the left turn, then I gradually lowered my altitude until I saw the ground and then made it to the target zone, which has less fog. In that case, I had to enable labels (Shift + F10) to find the targets.

The Ka-50 module never had this effect. Devs are planning to implement it to the Kamov. I'll check the mission.

The issue happens when GUI scale is other than 1, and a fix is coming.

Thanks @pctoptech. Issue reported.

Can you please share your mission file? I'll see if I can reproduce your issue.

The F-5E performance issue is reported internally. About the Mirage F1, please read this thread:

Great news! Thanks for your feedback.