Thanks, yea, I've seen a few other people do that but it seems silly when we're being punished for a playtest crashing. None of us mind the crashing, we know it comes with the play test, it's just frustrating when we do get banned though.
On the bright side, at least for now I think the...
@Yoshi - there's quite a few threads on the forums about people hitting this corruption issue on start and then getting banned as a result. Is there anything that can be done to make it so we don't get penalized when the game crashes like this? Steam does log when this happens so it is...
Well - I jinxed myself. I just saw the crash again and ironically it was the one time I didn't queue into a bot round first or verify my files. I had played like 3 hours ago so I figured it was fine.
My theory is that the crash is happening when a certain asset on the map gets loaded. To try to load everything.. I usually queue up, and try making a path that covers most of the map, i.e.
1. start on the left lane
2. get to lane
3. cut through mid across the map
4. head to the enemy base
I think you can use https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=windowsserver2025-ps to check if the port is blocked... I think maybe this:
Test-NetConnection -ComputerName localhost -Port 27015
If it's happening everytime, I wonder if there's something with your router/vpn blocking port 27015 which the console is indicating that it's trying to connect to. Based on a quick google search(https://help.steampowered.com/en/faqs/view/2EA8-4D75-DA21-31EB), it looks like port 27015-27050 are...
Fwiw, if you are trying to practice something locally there's a private bot match option you can use which doesn't penalize you for leaving as it's just and bots versus you, other players and bots.
Fwiw, if you want to skip the verify step, you could probably just queue into a bot round really quickly and this should suss out the issue where you crash as soon as the match starts.
I was getting this error fairly regularly and I did a few things to help alleviate it(I haven't seen it in a few weeks).
1. Moved the game to a separate hard drive.
2. Disabled steam shader cache.
3. Verify files before launching the game.
4. Queue up into a private bot match and make sure the...
I don't have any ram issues. Fwiw, I swapped the install of Deadlock from one hard drive to another (a slower one), disabled shader cache, verify all files before launching, and then do a quick local bot round before queuing up and I haven't seen this corruption issue in a few weeks.
To the original poster - I'm curious - have you played other MOBAs before? I think the experience coming from a FPS to a MOBA is going to be jarring if you haven't (i.e. the snowball effect).
The reason I say I'm skeptical is for me personally this is the only game where I've encountered anything like this error and for alot of others they seem to be in the same boat. This error also seems to happen w/Counterstrike (another source engine game) which makes me thinks it's something...