Re: build 5963 slower to load game windows...
You can make this same determination. Launch a slot from your team, and while it is loading, open up the Diablo 3 folder and locate D3Debug.txt. While the splash screen is up and the game is doing nothing, it is waiting for Blizzard's Agent.exe for 30+ seconds. During this time, nothing happens in D3Debug.txt, it says something like this:
- Code:
User defined symbols path: C:\Program Files (x86)\Diablo III
2014.03.16 11:39:05.081829600 Diablo III Release (No Assertions) running under Windows 7-64 SP1 (Version 6.1.7601)
2014.03.16 11:39:05.081952900 <BUILD>2.0.2.22274 (89714-1183230)</BUILD>
2014.03.16 11:39:05.082065200 Cheats: DISABLED
2014.03.16 11:39:05.082450600 CPU Vendor: GenuineIntel
2014.03.16 11:39:05.082662200 CPU Details: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
2014.03.16 11:39:05.082804900 CPU Processors: 1
2014.03.16 11:39:05.082950900 CPU Cores: 4
2014.03.16 11:39:05.083113600 CPU Threads: 8
2014.03.16 11:39:05.083278200 16359.06 MB of total physical memory
2014.03.16 11:39:05.083432600 OS Language: English
2014.03.16 11:39:05.083569900 Application Path: C:\Program Files (x86)\Diablo III\
2014.03.16 11:39:05.086494200 --- OS memory stats -----
2014.03.16 11:39:05.086612900 Virtual size: 189.36 Mb
2014.03.16 11:39:05.086722600 Total free: 3890.32 Mb
2014.03.16 11:39:05.086828600 Largest free block: 2047.29 Mb
2014.03.16 11:39:05.086931200 --- OS memory stats end-----
2014.03.16 11:39:05.087037900 ----------------------------------------------
2014.03.16 11:39:05.087140200 Command Line: -launch
2014.03.16 11:39:05.087499900 Monitor BPP: 32
2014.03.16 11:39:05.087616200 Monitor BPP: 32
2014.03.16 11:39:05.088011900 Lowest monitor BPP: 32
2014.03.16 11:39:05.394153900 Clock freq = 3331240
2014.03.16 11:39:05.394434900 WinSock started successfully!
2014.03.16 11:39:05.395303600 Adjusted initial working directory: C:\Program Files (x86)\Diablo III
2014.03.16 11:39:05.395462200 Detecting first installed locale.
2014.03.16 11:39:05.395700900 Detected: enUS
After the 30 seconds is up, it continues launching after adding:
To show that it is NOT from build 5963, Inner Space build 5944 is available from the Archives -- https://www.lavishsoft.com/innerspace/archives. This build is from Feb 5, long before this change. The same thing happens in the log.
Anyway, just thought I would share: I believe the change that caused this was on Blizzard's end, unintentional, and not Inner Space; it's a coincidence that it happened at about the same time.
