When i try to join a game,my scroll wheel stops working no matter what application i'm in, all buttons on byond and some on other applications don't work, and its stuck not joining until I close the byond window. Is there any known way to fix this and have any of you experienced this before?

I've already used beta branch, cleared cache, and reinstalled and none of those worked BTW.
I have the same issue. It returns to normal by itself after a while but I get a dreamseeker.exe crash in the Event Viewer. Do you get one too? See Event Viewer -> Windows Logs -> Application and find the most recent Application Error.
Event viewer crash details will be very important for determining the problem. If you can post those I may be able to find something.
Faulting application name: dreamseeker.exe, version: 5.0.513.1501, time stamp: 0x5ddeaa66
Faulting module name: ntdll.dll, version: 6.1.7601.24384, time stamp: 0x5c6e2180
Exception code: 0xc00000fd
Fault offset: 0x0002ed07
Faulting process id: 0x3c0
Faulting application start time: 0x01d5a9bc9616b443
Faulting application path: E:\513.1501_byond\byond\bin\dreamseeker.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: fe389ead-15af-11ea-b5ee-e839356142b4
That crash is a stack overflow, so the only way I'll be able to investigate further will be if you can get a minidump (Windows error reporting typically generates those automatically) and send that to me, as long as it's not more than a few megabytes. With that I might be able to get a stack trace.

However, because this is a stack overflow it's possible that the stack trace won't go back far enough; the only way to tell is to examine the dump file.
I can't seem to get a minidump, it just doesn't generate it or says it did but there's nothing on that path. Other applications seem to normally generate a minidump but I don't think they're having stack overflow errors.
I got this stack trace by running dreamseeker.exe in some debugger program. I don't actually know what to look for so here's an image:
That does look very useful, because I see there are two routines in dreamseeker.exe pingponging off each other. However I'll need to know where dreamseeker.exe was loaded in memory to be able to put that information to use. Any way you can get the info on where the various modules were loaded?

(The reason I need to know where they were loaded is because the addresses you have in that stack trace are absolute, whereas I need to know the offsets from where dreamseeker.exe begins. With that information I can figure out which routines those addresses correspond to.)

Login to reply.