Open RedHaze opened 4 years ago
I checked my hl2 process with process monitor too today because I always have like more than a minute loading time for new areas/levels. The \MOD\ was certainly strange and so I found your github post here.
I did your steps to disable Workstation service (and could confirm it "working" by testing \mod path which immediately gave an error in explorer.exe), but it did not change the problem that hl2 is hanging for like ~1min7 on my system unfortunately.
Are there any other issues with hl2.exe that can result in such long loading times? I definitely see that during that time it basically just reads and writes around the saves folder because of the autosave ... but I also did not find a way to disable autosave (and marking autosave files as read-only did not help, maybe it's also the e.g. ep1_c17_00.hl1 files in that folder creating a problem ...)
I probably have to further check for issues :(
Did another process monitor trace and it looks like the UNC access to \\MOD is still a problem:
Though no idea how to solve that.
Affected Games Confirmed: Half-Life 2, Half-Life 2: Episode One, Half-Life 2: Episode Two I believe this affects all Source 1 Engine games, see later in the report for more info why.
Issue Description Whenever transitioning into a new map, the loading time seems to take approximately 60 seconds. This time frame is consistent, and I've narrowed it down to
HL2.exe
attempting to access the invalid network path\\MOD\\
via Process Monitor. I'm assuming Windows is attempting to find a computer namedMOD
and times out after 60 seconds. I'm pretty sure this was also the same reason the save hitch was occurring.I've marked this issue primarily as affecting all Source 1 Engine games as per the following stack trace taken from Process Monitor when
\\MOD\\
is accessed:From my little Source engine knowledge, it seems like only the Engine specific DLL's are touched. Please feel free to update the ticket title/labels if I'm wrong.
Reproduction
Workstation
service is running. In an administrator command prompt, execute the following:hl2.exe
. Make sure Process Monitor isn't in capture mode (magnifying glass should have a red X on it).\\MOD\\
.\\MOD\\
System Information
Workaround After days of researching how to remove the file share timeout in Windows and coming up with nothing, I've discovered that the easiest way to remove the hitch is by turning off the LanManWorkstation service. I believe this service is used as a client to connect to file shares. If the client is turned off, then the timeout countdown never occurs. Instead, all UNC path accesses immediately return an error thus removing the main cause for the slowdown.
Execute the following in an administrator prompt console. Please note, I do not take any responsibility for the damage this may cause to your machine:
Be sure to accept any on-screen prompts as they appear.
Other Notes I want to say thank you for fixing the save hitch issue recently. I'm hoping the fix can be applied relatively quickly due to its similar nature :D.
Related Issues
2798