Jump to content

Obnoxious DCS startup times since 2.8.6.41393 OpenBeta MT (around 120 seconds!)


Go to solution Solved by BIGNEWY,

Recommended Posts

Posted (edited)

Hello friends.

I have very long DCS startup times with the newest 2.8.6.41393 OpenBeta Update.

I can perfectly replicate the issue by rolling back and forth between the last two updates - I measured the time from clicking the shortcut until the main-menu is fully loaded after second launch (DCS MT, VR and no-VR have the same loading times) - shaders folders were already re-established:

DCS 2.8.6.41066 Open Beta MT: 35 seconds average (the auth-verification takes alone around 10 seconds)

DCS 2.8.6.41363 Open Beta MT: 120 seconds on average (the auth-verification takes alone around 40 seconds)

I already did slow repair with extra file inspection and deleted the SavedGames/DCS folder after switching between updates. Issue persists.

Something is clearly off with the newest 2.8.6.41393 OpenBeta.

Anyone else?

Edited by Tepnox
  • Like 16

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted (edited)

So the auth issue is server load related, so should be discounted really. Did you clear metshaders2 and FXO folders, let the cache rebuild then launch and see if the second launch is quicker?

I, too, have noticed that the load times have increased with this OB, but not to the same degree you are experiencing. The texture loads once in game have been steadily slower for at least the last 5 OBs in my experience.

Edited by zildac
  • Like 1

14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero

Posted (edited)
6 minutes ago, zildac said:

So the auth issue is server load related, so should be discounted really. Did you clear metshaders2 and FXO folders, let the cache rebuild then launch and see if the second launch is quicker?

I already stated I deleted the complete Saved Games / DCS folder (this includes the shader-folders) after switching the updates.

And yes, I measured the average loading-times after the second DCS launch where the shader folders already have been re-established.

Why should I discount the auth-issue? The auth-verification takes with DCS 2.8.6.41066 around 10 seconds, with DCS 2.8.6.41363 it is 40 seconds. This is clearly no server issue.

Edited by Tepnox
  • Like 2

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted

It's definitely more lengthy for me too. Haven't measured the time but the authorisation process is taking longer compared to last OB version

  • Like 3

MAIN SYSTEM SPECS: MSI PRO Z690-A WIFI DDR4, Intel Corei7-12700K @ 5.0, 64Gb RAM Kingston KF3600C18D4/16GX, EVGA RTX 3080 FTW3 ULTRA GAMING 12GB, Samsung SSD 970 EVO Plus 1TB, Virpil T50CM3 Throttle, VKB Gunfighter MkIV Ultimate with 20cm extension, VKB T-Rudder MKIV, Quest Pro

Laptop SPECS: Alienware X16 R2, Intel Core Ultra 9 185H, RTX 4090 mobile 16GB, 32GB LPDDR5X, 2TB Micron NVMe
 

SOFTWARE: Microsoft Windows 11

Posted
24 minutes ago, Tepnox said:

I already stated I deleted the complete Saved Games / DCS folder (this includes the shader-folders) after switching the updates.

And yes, I measured the average loading-times after the second DCS launch where the shader folders already have been re-established.

Why should I discount the auth-issue? The auth-verification takes with DCS 2.8.6.41066 around 10 seconds, with DCS 2.8.6.41363 it is 40 seconds. This is clearly no server issue.

 

Understood. Sorry, but the auth servers were busy as heck yesterday due to the F15 dropping. But if you’re saying even the auth process is quicker when you roll back, then I have no idea. I don't see an increase in auth server time between the current and previous build.

14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero

Posted

Yeah, a bit slower than the previous version, but it's not like we're talking 20+ minutes here, it is less time than it takes to make a cup of tea.  I do wonder how some DCS players cope with real life sometimes.

  • Like 4

Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs,  pit WIP (XBox360 when traveling). Quest 3S.

Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.

Posted
10 minutes ago, Lace said:

I do wonder how some DCS players cope with real life sometimes.

I have that exact thought at least once a day.... 😂

  • Like 4

"Muß ich denn jedes Mal, wenn ich sauge oder saugblase den Schlauchstecker in die Schlauchnut schieben?"

Posted
3 minutes ago, Lace said:

Yeah, a bit slower than the previous version, but it's not like we're talking 20+ minutes here, it is less time than it takes to make a cup of tea.  I do wonder how some DCS players cope with real life sometimes.

If you try to fiddle around with VR settings and need to restart DCS each time you would think a little different, I assure you. Clearly I have better things to do than sitting and waiting for a loading screen.

When you only start DCS one time the evening I would not have a problem with that for sure (despite the fact it still is an increase of more than 300 %).

  • Like 10

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted
6 minutes ago, Tepnox said:

Clearly I have better things to do than sitting and waiting for a loading screen.

Clearly 🤣

Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs,  pit WIP (XBox360 when traveling). Quest 3S.

Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.

Posted (edited)

This is the initial first run with 2.8.6.41393 OpenBeta - fxo and metashaders not available:

dcs.log.old

This is the second run with 2.8.6.41393 OpenBeta - fxo and metashaders were already available from first run:

dcs.log

I am using following command in my DCS-Shortcut: "C:\GAMES\DCS World\bin-mt\DCS.exe" --force_disable_VR

EDIT:

This in comparison is the log for the second startup while rolling back to DCS 2.8.6.41066 (procedure was downgrading to previous version, doing a slow repair with extra file sweep and the Saved Games/DCS folder completely deleted):

dcs-2.8.6.41066.log

Edited by Tepnox
  • Like 2
  • Thanks 1

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted

i noticed yesterday the same thing, being i was having issues installing the new plane and had to keep restarting dcs it kinda sucked.

Posted (edited)

@Tepnox Thank you.

It takes your PC 1'43" to get to end of init with the latest update. It used to last 34" seconds before.

Here are the most significant delays:

+15" here

2023-06-23 10:39:19.103 INFO    ED_SOUND (Main):   1: ID: "{0.0.0.00000000}.{9e0ff122-6818-4016-831c-400c19627f9f}", Name: "Headphones (Oculus Virtual Audio Device)"
2023-06-23 10:39:40.741 INFO    SOUND (Main): Added sound path: Sounds

+9" here:

2023-06-23 10:39:42.593 INFO    Dispatcher (Main): Loading installed modules...
2023-06-23 10:39:55.636 ERROR   Scripting (Main): bad argument #1 to 'pairs' (table expected, got nil)

+8" here:

2023-06-23 10:40:06.393 INFO    Scripting (Main): PLUGINS DONE--------------------------------------------------
2023-06-23 10:40:17.860 INFO    EDCORE (Main): Loaded C:/GAMES/DCS World/CoreMods/tech/SouthAtlanticAssets/bin/SouthAtlantic.dll

+12" here:

2023-06-23 10:40:25.550 INFO    EDCORE (Main): (dDispatcher)enterToState_:1
2023-06-23 10:40:41.516 INFO    UIBASERENDERER (Main): Cannot load font [C:\GAMES\DCS World\dxgui\skins\fonts\]!

+13" here:

2023-06-23 10:40:43.932 INFO    APP (Main): Loaded C:\GAMES\DCS World\Scripts\Hooks\webGUI.lua
2023-06-23 10:40:59.456 INFO    Dispatcher (Main): //=== END OF INIT ======================================//

This is astonishing. It seems this latest version has a hard time getting data from the drive.

Whatever the version you run, try what follows. It helps DCS start faster.

  1. Add "C:\GAMES\DCS World" to your antivirus exceptions.
  2. Ensure DCS.exe is not run "As administrator".
Edited by Flappie
  • Like 5
  • Thanks 2

---

Posted
27 minutes ago, Flappie said:

Whatever the version you run, try what follows. It helps DCS start faster.

  1. Add "C:\GAMES\DCS World" to your antivirus exceptions.
  2. Ensure DCS.exe is not run "As administrator".

Thx for the info. I am simply using Microsoft Defender in Windows 11 (fresh Win11 install since yesterday - no extra Antivirus-Software is installed). I excluded DCS World folder:

image.png

DCS is always running without Admin-rights.

Still getting around 2 minutes startup time on second launch with 2.8.6.41363 Open Beta MT:

dcs.log

Looks like I will return back to DCS 2.8.6.41066 Open Beta MT until this gets resolved internally.

No other option for me right now, because I was fiddling around alot with some VR-settings and benchmarks - 2 minutes waiting time after each DCS restart is just unbearable.

  • Like 2

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted

 

I don't have comparative logs, but I noticed the same delay all of the sudden.

three  things have changed recently.

1.  The latest patch.

2.  I started using the MT steam version.

3.  Just recently installed the Oculus software.

 

  • Like 1
Posted

I noticed longer loads compared to before patch this week. In my case it takes longer than getting another beer, a bathroom break. No tea 🤪

  • Like 5

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted
12 hours ago, Flappie said:

It didn't change much, indeed.

Some testers noticed the same thing. I don't know what caused this change. Maybe it's only happening with DCS MT.

FWIW mine is the same, also not running MT, and also an Oculus user. 

Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs,  pit WIP (XBox360 when traveling). Quest 3S.

Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.

Posted (edited)

I have the same problem. 

Since the last openbeta update and F-15E install it takes 3 - 4 times longer to start DCS (MT) for me. 

Mission loading times are not affected, but from desktop to main menu takes ages.

@Tepnox do you have the F-15E by any chance? Just trying to find a starting point.

Edited by Sile
  • Like 5
Posted
5 minutes ago, Sile said:

I have the same problem. 

Since the last openbeta update and F-15E install it takes 3 - 4 times longer to start DCS (MT) for me. 

Mission loading times are not affected, but from desktop to main menu takes ages.

@Tepnox do you have the F-15E by any chance? Just trying to find a starting point.

 

Hi! No, I am an Apache guy and didn't purchase the F-15E.

So this problem seems to be a core issue, not module related. 

  • Like 3

Ryzen 7 5800X3D // 64 GB RAM // RTX 4090 // Quest Pro // Quest 3

Posted (edited)
6 hours ago, Nevyn said:

I don't use MT, so it doesn't seem to be purely an MT issue.

hi. agreed. i noticed it with ST version too since that is how i update. i run the original shortcut, get patched, load new plane or terrain, then close DCS. then start MT. i do not see any difference. still slower. i will compare my logs for time stamps. and share findings.

Edited by silverdevil
  • Like 1

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted (edited)

Basic Game with a few mods, Game load up times are insanely slow now, almost unplayable. 3-5 minutes !!

Mission loading is fine.  

Edited by crazyeddie
  • Like 1
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...