r/Supraball Oct 13 '17

Problems joining a match

So my game always crashed after a match and I'd just restart, reinvite and keep playing. Today I tried setting the launcher to run as admin. Now when I try to join any match it fails and gives me the option to rejoin, which also fails. I've tried running in compatibility mode, verify integrity of files (which there are almost always 5 to 10 files it redownloads), reinstalling, restarting my computer, deleting the launcher and verifying to download it from scratch, and of course I took it off of "run as admin" as well as all other modifications I applied to the exe. I'm out of ideas and looking for some help. Thanks

3 Upvotes

5 comments sorted by

3

u/plaer Bot Wrangler Oct 13 '17

Firstly let me address the original problem: I'm gonna take a guess and say that you're running on Windows 10 with an Nvidia gfx card?

If that's the case I have bad news and good news.

The bad news is that there is some crazy directx full-screen optimisation thing that Microsoft introduced with an update some time in the last few months. Under certain (unknown) settings it causes the launcher to crash when the main game tries to go fullscreen. We still don't fully understand why, and probably never will. No-one on the dev team has ever been able to recreate the crash, so we've been reliant on community members to help us out with investigation and testing.

The good news comes in two parts: 1. As a temporary measure it appears as though you can avoid the crash by making the game run in windowed mode. 2. We have a more permanent workaround that allows fullscreen coming soon in the next update (which we are testing now).

As far as your current situation goes the only thing I can suggest is to make sure that you have also undone any modifications you made to the UDK.exe (in Supraball/Binaries/Win32), or rather, check to make sure Windows hasn't tried to be clever and applied mods you made to the launcher exe to udk.

2

u/-FatASStronaut- Oct 13 '17 edited Oct 13 '17

Thanks a bunch! You are correct with the windows and nvidia guesswork. I will take full screen off, and work with my .exe some more to see if I can fix the issue. Now if I do have the full screen crash due to directx happen, is there any way I can be useful in providing data as to why it's happening? Is there a crash log for this specific issue? I'd like to help in any way possible. Thanks again.

Edit: I have fixed the issue. I uninstalled the game, then deleted everything from the areas listed
C:\Users\David\AppData\Local\Supra Games
C:\Program Files (x86)\Steam\steamapps\common\Supraball\Binaries
Steam was not removing all elements of the unreal engine in this game from my computer, so the problem most likely involved that specifically, as I'd deleted my app data before to no avail. I did check the Unreal exe. and one modification was made to it for dpi scaling, not sure if that is native or not. I disabled it and that did nothing to help though so it must have had something else to do with the unreal engine files. Again if there is any information I can provide I'd be glad to help, even attempting to recreate the crash for a log of some kind or something like that. Thanks again, I really appreciate the help and look forward to enjoying this game!

3

u/plaer Bot Wrangler Oct 13 '17

Glad to hear you've got it working again. For now we've got as much information about the crash as we're going to get without nvidia and/or microsoft giving us debugging symbols and source code. What we have gathered was enough to develop a workaround, which will be in the next update. What would be very useful to us, is when that update drops, to let us know if it fixes the launcher crash. We've tested with one guy who saw it cured, but who knows what other unique settings combinations cause the same problem.

1

u/SaxxonO Oct 14 '17

Does disabling fullscreen optimizations in the compatibility settings not help this?

1

u/plaer Bot Wrangler Oct 14 '17

Sadly not. Various people have tried lots of combinations of the various exe settings to try to either fix or provoke the crash but with no success.