Flappie

This is a core game fix, not a terrain fix. I'm pretty sure it will work for every terrains. For the sake of it, I'll check Sinai if this can reassure you. I'll first reproduce the issue in Release.

That's what I thought, but it does not seem to be always true, neither in this video nor in DCS (but maybe it's about being 1° below or above the threshold).

@Actium Devs are working on a fix to prevent a crash from happening with this wrong usage of the API. I'm pretty sure you were simply testing the limits of this function, but just in case, devs made it clear that tables with circular dependencies inside will never be in any circumstances correctly converted to JSON.

Hi @UnderTaker2003, this looks like a very old issue (2021). It was fixed the same year. It seems that you can reproduce this issue at will. Can you please record a short DCS track showing this black artifact?

Thank you, @Actium! Issue reproduced and reported.

Thank you. Then I really don't know what happens to you. You can open a support ticket: Log into DCS website. Click "Support". Click "Create a new ticket".

And you are 100% positive that you don't get this issue if you play MP with the same module without VR?

So far, I cannot see the crash in your log files. Don't you have at least one .zip file in the Logs folder? (.zip files are created in there when DCS crashes)

Thanks for your track. The loft was modified in December to solve issues of the same kind. It looks like it still needs some tweaking. In the video below, a first Kh-25ML goes straight to the target while the second one loft hard. It seems that both missiles hit their target. I don't know how to explain such a big difference in these two launches. Does the Frogfoot have some Loft/No-loft switch? Does it depend on the current altitude? That's a mystery. I'll test more then report to devs.

Ah, then it's probably a different issue. Ensure your VR gear cable is OK. Please attach the latest .zip file from "Saved Games/DCS.../Logs".

Hi, there is an ongoing issue. For some users, it's constant, for others like me, it's random. Take a look at this thread:

ED have both internal (paid) testers and external (unpaid) testers, just like most video game companies around the world.

@Weta43 It was reported internally following your finding in December, yes.

Here's the definition of PL1 and PL2 (sometimes they are simply called L1 and L2): PL1 = Power Limit for long-term steady power consumption. Intel recommends for PL1 to be set in consideration with limits of thermal cooling solution. PL2 = Power Limit for short-term maximum power consumption under heavy load. It means that PL2 shouldn't be set lower than PL1. It appears that the Intel 14900K series has stability issues, in games only, because compatible motherboards use non-recommended default settings in their "Auto" mode. Following this finding, Intel has asked these motherboard manufacturers to use lower default settings by May 31, 2024. In this linked page, you can see that Intel now recommends a maximum of 253 W for both PL1 and PL2. So it does not matter if your PSU is able to give 1000 W or more to your PC. As long as you have a motherboard with a 14900K in your system, your system may be affected - unless of course your motherboard has Intel recommended settings. The next steps for you are to: Confirm that you have a MSI PRO Z790 motherboard (it's what the Corsair Vengeance i7500 system is supposed to be based on), Check your motherboard PL1 and PL2 settings in the BIOS (Overclocking > Advanced CPU Configuration). If you have an MSI Z790, they will be called: Long Duration Power Limit Short Duration Power Limit If at least one of these two values is more that 253 W, it probably explains your system instability in games. And here's the procedure for the MSI Z790: Go to your system BIOS. Save your current settings into a profile so you can return to them later if you want. Reset your BIOS to default settings. Enable XMP. Go to Overclocking > Advanced CPU Configuration. Set Long Duration Power Limit(W) = 253 Set Short Duration Power Limit(W) = 253 Set CPU Current Limit(A) = 307 Save and exit. Test DCS. Of course, lowering your power limit settings means that performance will decrease a bit in games, but it's a choice you must make between "more frames per second" and stability.

Thanks @Shadow KT. The issue was reported internally a few months ago.

Thanks for your feedback.

This issue was reported a while ago. Here is its description: Destruction on Mission Start: client sees buildings removed, but trees remain. Destruction with Once trigger: When client is already connected: buildings and trees are removed. When client connects after it occurred: client sees buildings removed, but trees remain. Does it match what you witness?

Issue reproduced and reported. Thank you very much for the mission file.

Performance-related bugs are usually fixed quickly when they are easily reproducible. Please post an example so I can report it.

Thank you for this thorough report. The issue is now reported.

Some good news: I've tried my best but I'm unable to reproduce the issue with DCS internal version. This means this issue should be gone with the next DCS update.

So, that's what I thought: it is caused by the Damascus 116 MHz beacon. I hosted the mission on my own dedi server, with Voice Chat enabled, and as soon as I change the default VHF frequency (116 MHz in FC3 planes), the noise stops. I understand the issue for servers with Voice Chat turned off, because there is no way to turn that noise off. I'll ask the Syria terrain makers to change Damascus frequency, which is the simplest solution. EDIT: actually, this sound shouldn't be heard when Voice Chat is off, since it cannot be heard in SP. EDIT2: Damascus real beacon is really 116 MHz, by the way.

Thank you. These slots are taken! I'll wait in line. EDIT: it's OK, I took a dynamic slot and I can reproduce the constant squelch sound, thank you very much. A-10A is affected too, and Soviet aircraft cannot be spawned here, but I guess all FC3 are affected. It looks like the radio beacon issue. I'll check. Tracks don't replay the issue.

(all terrains are affected apparently) Persian Gulf is affected too. Syria is OK.

My mistake, it did. I'll check with devs whether it's intentional (I doubt it is). Is Caucasus the only affected terrain?