After starting DCS, there is one minute with periodic stuttering since 2.9.15. Visible on graph.

[YoYo]

33 minutes ago, BIGNEWY said:

threads merged 

I will ask the team about this, but it is also worth mentioning real time antivirus can also create issues that prevent a fast closing of DCS, its worth checking by excluding the DCS install from the scans. 

Personally, I have disabled antivirus monitoring of the DCS folder and his exe files long time ago, so the problem still persists despite this. 

The problem is related to the fact that currently DCS unnecessarily loads everything it has (all activated by user modules/maps) which causes long loading, long saving and stuttering during the game as well as long DCS exit, this was changed four patches ago. I dont know about the idea and reason of this changes. We have a solution - given in this thread, but I wonder why it was changed since it causes a drop in performance. 

Edited June 9 by YoYo

[Nightstorm]

16 hours ago, YoYo said:

Yes, this is good workaround. This is the first thing worth checking instead of drivers, memory, mods and God knows what else ;).

However now it is: bkg_load_signed_plugins = true, we havent here "all".

----------------------------------------------------------------------------------------------------

Since I don't want to interfere with the original files, I personally recommend adding this entry to:

• C:\Users\xvy\Saved Games\DCS.openbeta\Config
• go to autoexec.cfg (or create it), add this new line:
• bkg_load_signed_plugins = false

DCS is back to normal (no stutters at the beginning, fast saving, even the exit is immediate ect).

Btw. You can use my file as well:

autoexec.cfg 156 B · 11 downloads

I will test this ASAP.  Thank you!

[Raven (Elysian Angel)]

3 hours ago, YoYo said:

We have a solution

In my case it isn't. I tried both commands and they didn't fix anything.

[YoYo]

48 minutes ago, Raven (Elysian Angel) said:

In my case it isn't. I tried both commands and they didn't fix anything.

Of course, it is difficult to assess in this case what the individual problem is. The solution is to the fact that after starting DCS and at the beginning of the mission, you can feel a distinct stutter, which is caused by something constantly loading. This is related to activating and loading subsequent modules, even if you do not use them. After a few minutes, i.e. 1-4 minutes (depends on hardware and kind of the disk), it goes away and this is the topic of this thread. When making a save or exiting, when DCS saves some data, it happens again, which is why it all takes so long. This is currently without this "fix". However, if you still have stutter, during the whole mission and flight, it may also be unfortunately some other issue, unrelated to this loading problem.

[Qcumber]

I can confirm that the problem still exists for me as per YoYo's summary. It lasts for about 1 minute in the hanger. By the time I have loaded a mission it has settled down so I have not worried about it too much. I have a fast NVME drive so perhaps this is it. No further stutters in missions and the flying is smooth. 

[Raven (Elysian Angel)]

52 minutes ago, YoYo said:

However, if you still have stutter, during the whole mission and flight, it may also be unfortunately some other issue, unrelated to this loading problem.

Actually I experience both. Yes the stutters on the main menu last for about a minute and then go away. Then during the mission it's a stutter-fest again, and once I exit the mission there are the same stutters on the main menu once again.
It's why I'm posting in both threads...

[YoYo]

27 minutes ago, Qcumber said:

I can confirm that the problem still exists for me as per YoYo's summary. It lasts for about 1 minute in the hanger. By the time I have loaded a mission it has settled down so I have not worried about it too much. I have a fast NVME drive so perhaps this is it. No further stutters in missions and the flying is smooth. 

Check this trick, page before (my post).

21 minutes ago, Raven (Elysian Angel) said:

Actually I experience both. Yes the stutters on the main menu last for about a minute and then go away. Then during the mission it's a stutter-fest again, and once I exit the mission there are the same stutters on the main menu once again.
It's why I'm posting in both threads...

Do you have unparked cores? Windows 11 or 10?

[Raven (Elysian Angel)]

51 minutes ago, YoYo said:

Do you have unparked cores? Windows 11 or 10?

Not applicable (see signature - but you probably mean parked cores) and W11. I didn’t have any problems before 2 patches ago so anything related to my specific setup doesn’t apply: I didn’t change anything on my end - as I said in the other thread.

[Lange_666]

21 hours ago, YoYo said:

Since I don't want to interfere with the original files, I personally recommend adding this entry to:

• C:\Users\xvy\Saved Games\DCS.openbeta\Config
• go to autoexec.cfg (or create it), add this new line:
• bkg_load_signed_plugins = false

DCS is back to normal (no stutters at the beginning, fast saving, even the exit is immediate ect).

Works fine...

[Nightstorm]

On 6/8/2025 at 4:50 PM, YoYo said:

Yes, this is good workaround. This is the first thing worth checking instead of drivers, memory, mods and God knows what else ;).

However now it is: bkg_load_signed_plugins = true, we havent here "all".

----------------------------------------------------------------------------------------------------

Since I don't want to interfere with the original files, I personally recommend adding this entry to:

• C:\Users\xvy\Saved Games\DCS.openbeta\Config
• go to autoexec.cfg (or create it), add this new line:
• bkg_load_signed_plugins = false

DCS is back to normal (no stutters at the beginning, fast saving, even the exit is immediate ect).

Btw. You can use my file as well:

autoexec.cfg 156 B · 16 downloads

This solved it for me as well.  It performs the same now as 2.9.14.  I haven't noted any side effects or issues yet.  Thank you!

[Lange_666]

12 hours ago, Lange_666 said:

Works fine...

Reacted a bit to early I guess.
Came from a multiplayer session, ended the game and exited was greeted with a 30 sec black screen on exit.
Because of that, restarted DCS, selected a single player mission, loaded it, quit and exit... again that 30 sec black screen.
Checked autoexec.cfg, bkg_load_signed_plugins = false still in place...  
 

[YoYo]

8 hours ago, Lange_666 said:

Reacted a bit to early I guess.
Came from a multiplayer session, ended the game and exited was greeted with a 30 sec black screen on exit.
Because of that, restarted DCS, selected a single player mission, loaded it, quit and exit... again that 30 sec black screen.
Checked autoexec.cfg, bkg_load_signed_plugins = false still in place...  
 

For me its still ok. Give a feedback after few days of testing, thanks.

[Nightstorm]

34 minutes ago, YoYo said:

For me its still ok. Give a feedback after few days of testing, thanks.

I was working on some mods yesterday and in/out/in/out many times over the course of several hours.  No issues.  The fact that you don't even have to *think* about what's taking so long means it's not taking so long  It's back to normal with normal being its behavior on 2.9.14.

I'm glad to be back on the current version and regained access to the Germany map.

[Lange_666]

1 hour ago, YoYo said:

For me its still ok. Give a feedback after few days of testing, thanks.

If it doesn't work or partially doesn't work a few times it isn't a full proof solution. No need to wait a few days.
It's not that i wait until Friday that it will change from working sometimes into always.

Edited June 10 by Lange_666

[Ironious]

I tried the bkg_load_signed_plugins = false to no avail. Still ~30 second black screen on exit. For record I use Windows Defender for AV and have exclusions for everything DCS related.

Edited June 10 by Ironious

[Ironious]

25 second black screen on quit to desktop. It seems the black screen on shut down is consistently shorter after I added bkg_load_signed_plugins = false to the autoexec.cfg. About 25 seconds now. Before that it would vary in time and sometimes be much longer. A consistent 25 second to shut down is acceptable for me. It just used to not do that.

dcs.log

Edited June 10 by Ironious

[Dangerzone]

On 6/9/2025 at 6:50 AM, YoYo said:

Yes, this is good workaround. This is the first thing worth checking instead of drivers, memory, mods and God knows what else ;).

However now it is: bkg_load_signed_plugins = true, we havent here "all".

----------------------------------------------------------------------------------------------------

Since I don't want to interfere with the original files, I personally recommend adding this entry to:

• C:\Users\xvy\Saved Games\DCS.openbeta\Config
• go to autoexec.cfg (or create it), add this new line:
• bkg_load_signed_plugins = false

DCS is back to normal (no stutters at the beginning, fast saving, even the exit is immediate ect).

Btw. You can use my file as well:

autoexec.cfg 156 B · 29 downloads

Hey Yoyo. Thanks for providing this. Are you able to advise where you found the info for bkg_load_signed_plugins please?And do you have any more documentation on what it does or the change?

I mean, I understand that it doesn't load all the official modules in at the start - but what are the downfalls. When does it load in the modules? Only when a player joins a server with them? Is this like a 'test feature' that ED has put in for testing with the plans of actually making it a core change in an upcoming change - or is it solely for debugging?  You've sparked my interest - because it seems to make sense not to load modules in unless they're needed, but yet it's a hidden option with no documentation that I can find. The only google search for "bkg_load_signed_plugins" reveals this thread. 

[Dangerzone]

On 6/11/2025 at 9:05 AM, Dangerzone said:

Hey Yoyo. Thanks for providing this. Are you able to advise where you found the info for bkg_load_signed_plugins please?And do you have any more documentation on what it does or the change?

I mean, I understand that it doesn't load all the official modules in at the start - but what are the downfalls. When does it load in the modules? Only when a player joins a server with them? Is this like a 'test feature' that ED has put in for testing with the plans of actually making it a core change in an upcoming change - or is it solely for debugging?  You've sparked my interest - because it seems to make sense not to load modules in unless they're needed, but yet it's a hidden option with no documentation that I can find. The only google search for "bkg_load_signed_plugins" reveals this thread. 

Just a follow up - does anyone know more about bkg_load_signed_plugins  ?

Is this a fallback to an OLD way of doing it (undoing what was introduced recently), or is this a test flag for a new way that could be implemented in the future? Is there any negative/downside to using this?

Or is this just a setting that someone stumbled across in the dark, tried it - it fixed issues but no one knows anything more?

[Rene Coulon]

On 6/8/2025 at 10:50 PM, YoYo said:

Yes, this is good workaround. This is the first thing worth checking instead of drivers, memory, mods and God knows what else ;).

However now it is: bkg_load_signed_plugins = true, we havent here "all".

----------------------------------------------------------------------------------------------------

Since I don't want to interfere with the original files, I personally recommend adding this entry to:

• C:\Users\xvy\Saved Games\DCS.openbeta\Config
• go to autoexec.cfg (or create it), add this new line:
• bkg_load_signed_plugins = false

DCS is back to normal (no stutters at the beginning, fast saving, even the exit is immediate ect).

Btw. You can use my file as well:

autoexec.cfg 156 B · 48 downloads

Hi,

 

Thankyou so much...going to give this a try

[jnr4817]

"

In DCS (Digital Combat Simulator), the configuration setting bkg_load_signed_plugins = false is related to how the simulator handles the loading of plugins. Here's a breakdown of its significance:

1. Background Plugins Loading:

   • DCS allows the use of plugins to extend or enhance its functionality. These plugins can include aircraft modules, tools, or other software components that integrate with the simulator.

2. Signed Plugins:

   • Signed plugins are plugins that are digitally signed by an authorized developer or vendor. Digital signatures are typically used to verify the authenticity and integrity of the plugin, ensuring that it hasn't been tampered with and comes from a trusted source.

3. Setting Behavior:

   • When bkg_load_signed_plugins is set to true, DCS will only load plugins that are digitally signed. This is a security measure to prevent the loading of unverified or potentially malicious plugins.
   • When bkg_load_signed_plugins is set to false, DCS will allow the loading of unsigned plugins. This can be useful for developers working on custom plugins or for users who want to use third-party plugins that aren't officially signed."
     
     Chatgpt description.

[Nightstorm]

32 minutes ago, jnr4817 said:

"

In DCS (Digital Combat Simulator), the configuration setting bkg_load_signed_plugins = false is related to how the simulator handles the loading of plugins. Here's a breakdown of its significance:

1. Background Plugins Loading:

   • DCS allows the use of plugins to extend or enhance its functionality. These plugins can include aircraft modules, tools, or other software components that integrate with the simulator.

2. Signed Plugins:

   • Signed plugins are plugins that are digitally signed by an authorized developer or vendor. Digital signatures are typically used to verify the authenticity and integrity of the plugin, ensuring that it hasn't been tampered with and comes from a trusted source.

3. Setting Behavior:

   • When bkg_load_signed_plugins is set to true, DCS will only load plugins that are digitally signed. This is a security measure to prevent the loading of unverified or potentially malicious plugins.
   • When bkg_load_signed_plugins is set to false, DCS will allow the loading of unsigned plugins. This can be useful for developers working on custom plugins or for users who want to use third-party plugins that aren't officially signed."
     
     Chatgpt description.

bkg_load_signed_plugins = false - I can confirm that with this in the autoexec.cfg I'm not missing anything.  I have many mods installed and I doubt those are signed plugins.  I haven't had any issues with loading or exiting since adding that line.

Whatever that did, it stopped the behavior where it was evidently loading a bunch of plugins every single time you started DCS.  I can't speak to the accuracy of the Chatgpt description, only my observations.

Edited June 17 by Nightstorm

[buceador]

 

33 minutes ago, jnr4817 said:

Setting Behavior:

• When bkg_load_signed_plugins is set to true, DCS will only load plugins that are digitally signed. This is a security measure to prevent the loading of unverified or potentially malicious plugins.
• When bkg_load_signed_plugins is set to false, DCS will allow the loading of unsigned plugins. This can be useful for developers working on custom plugins or for users who want to use third-party plugins that aren't officially signed."

And the:
bkg_load_all_plugins = false ?
Prevents ALL plugins being loaded?

[scommander2]

1 hour ago, jnr4817 said:

In DCS (Digital Combat Simulator), the configuration setting bkg_load_signed_plugins = false is related to how the simulator handles the loading of plugins. Here's a breakdown of its significance:

1. Background Plugins Loading:

   • DCS allows the use of plugins to extend or enhance its functionality. These plugins can include aircraft modules, tools, or other software components that integrate with the simulator.

2. Signed Plugins:

   • Signed plugins are plugins that are digitally signed by an authorized developer or vendor. Digital signatures are typically used to verify the authenticity and integrity of the plugin, ensuring that it hasn't been tampered with and comes from a trusted source.

3. Setting Behavior:

   • When bkg_load_signed_plugins is set to true, DCS will only load plugins that are digitally signed. This is a security measure to prevent the loading of unverified or potentially malicious plugins.
   • When bkg_load_signed_plugins is set to false, DCS will allow the loading of unsigned plugins. This can be useful for developers working on custom plugins or for users who want to use third-party plugins that aren't officially signed."
     
     Chatgpt description.

Thanks for explanation.

If  "bkg_load_signed_plugins=true" sets, I guess that DCS should run the most clean environment since no custom plugins with the better result for "overall"?! I am not sure that I make this statement sense or not based on reading.

Thanks.

 

 

[Dangerzone]

7 hours ago, jnr4817 said:

"

In DCS (Digital Combat Simulator), the configuration setting bkg_load_signed_plugins = false is related to how the simulator handles the loading of plugins. Here's a breakdown of its significance:

1. Background Plugins Loading:

   • DCS allows the use of plugins to extend or enhance its functionality. These plugins can include aircraft modules, tools, or other software components that integrate with the simulator.

2. Signed Plugins:

   • Signed plugins are plugins that are digitally signed by an authorized developer or vendor. Digital signatures are typically used to verify the authenticity and integrity of the plugin, ensuring that it hasn't been tampered with and comes from a trusted source.

3. Setting Behavior:

   • When bkg_load_signed_plugins is set to true, DCS will only load plugins that are digitally signed. This is a security measure to prevent the loading of unverified or potentially malicious plugins.
   • When bkg_load_signed_plugins is set to false, DCS will allow the loading of unsigned plugins. This can be useful for developers working on custom plugins or for users who want to use third-party plugins that aren't officially signed."
     
     Chatgpt description.

Don't trust ChatGPT. It makes things up when it doesn't really know the answer) - and often gives different answers. For instance, I just asked it and it gives this response:

In autoexec.cfg, the bkg_load_signed_plugins setting controls whether DCS loads digitally signed plugins in the background during startup:

true: Enables background loading of signed plugins. This can improve startup time by parallelizing plugin initialization.

false: All plugins (even signed ones) are loaded sequentially, possibly making startup slower but more stable for troubleshooting.

It's mainly a performance tuning flag. Most users can leave it set to true.

... which is a completely different response to what you got. Plus, if no one has any unsigned plugins (or even if they do) - I don't see how setting it to false would fix the issue, as @YoYo has mentioned. There's something more going on here. I can't find any documentation about it on the internet - and ChatGPT seems to be just making things up. 

Additionally, when I asked ChatGPT for it's source for this information it gave:

The information about bkg_load_signed_plugins in DCS World's autoexec.cfg file is primarily sourced from user discussions on the ED Forums. For instance, a user named @Nightstormreported that setting bkg_load_signed_plugins = false resolved performance issues introduced in version 2.9.15, such as startup stuttering and mission saving problems. This suggests that disabling background loading of signed plugins can lead to more stable performance in certain scenarios.forum.dcs.world

However, there is no official documentation from Eagle Dynamics detailing the exact function of this setting. The understanding of its impact is based on community observations and troubleshooting experiences.

For more detailed discussions and user experiences, you can refer to the ED Forums thread where this topic is discussed: forum.dcs.world.

We're stuck in a loop. ChatGPT is referencing us, and we're referencing it. 

This is why I asked the question where people are getting their information from, or even knew that this setting existed in the first place. There seems to be no official documentation available.

Is someone doing searches through the binaries for text constants and found this as an option and decided to throw it into autoexec.cfg to see what it does, and it just worked?

Or did an insider recommend to a friend to try the setting, who recommended it to another friend, and it finally made it's way 'leaked' to this forum? 

Or did this come from someone who submitted an official support ticket to ED, and they said to try it?

Or does the first person who recommended it actually know more information about this setting, and is able to provide deeper information as to any potential side effects to watch out for. Or if there's no potential side effects - can we get ED to set this as the default to fix the countless people struggling with the same issues that don't frequent this forum. 

What's so bizarre about all this is that multiple 'stuttering' threads are popping up on this forum, with very few getting a response by ED reps. Then this comes out apparently from nowhere, with no source of origin.

I'm beginning to wonder if this is a dev fallback solution that ED put in for a change they've made with 2.16 and it's leaked its way to us. And if so - it's very disappointing that ED hasn't acknowledged there's been a change that they introduced that has caused this problem, and being more forthcoming about trying this setting themselves to resolve it in the numerous 'stuttering' threads that are popping up. But this is conjecture - we seem to be very much in the dark about it. 

Plus, I'm beginning to wonder now how many more secret/hidden autoexec.cfg settings there are that could help increase our experience with DCS - which is another reason I'm eager to know the source of this information. 

[YoYo]

7 hours ago, Dangerzone said:

There seems to be no official documentation available...

You probably expect too much ;). No developer (unless it's Open Source software) will simply share their documentation and codes. It would even be against business assumptions. You won't find any advice or documentation, possibly 3rd Party developers have a lot of knowledge and tools, but this is more about the SDK itself than the functioning of the game. In our case, it's more about tracking what's in the DCS files and drawing the right conclusions, but without 100% guarantee, because some elements can affect others, which we may not be aware of. You should rather expect a lot of trials and tests and draw conclusions yourself. Personally, I suggest not to delve that far because at some point you will hit a wall, which is understandable, I guess .