Dreamseeker byond11/7/2023 ![]() ![]() I don't know why this entire phenomenon occurs over a period of eight and a half to nine minutes EVERY SINGLE TIME I log on, reconnect, or after the server reboots. I have tried to look at 'Options and Messages' to see if there were any resources downloading, but there aren't. Also, strangely, during this period, the game only seems to be affecting my computer's memory by 2%, which is extremely abnormal, when Dreamseeker usually takes 10-15% memory, which makes me think something is preventing the game from working properly. It is as if the chat box is its own little program and is unaffected by these periods of freezes. Strangely, while the window says it is not responding, even if minimized (showing a preview of the window) or maximized, the chat scrolls on as if absolutely nothing is happening. In addition the station clock, say, if I joined at 13:08, it stays 13:08 for the entire 8-9 minute duration, in which it then updates the time after the problem subsides. It allows me to minimize, for some reason, but, again 5-8 seconds for it to respond to maximize again, if it lets me, at all. Sometimes, I do not even receive that luxury and the game decides to not respond. IF I managed to click something during that half or quarter of a second margin, I have to wait another five or eight seconds for a response from the game or for anything to pop up, in which the process repeats itself for another nine minutes. Dreamseeker says I have a latency problem of 1.7k-2.5k ms or so, it says the window is (Not Responding.) For some reason, the 'Get Ready' window seems to disappear at times, and even separates itself from the SS13 window in the toolbar (it shows up as a separate tab). Let me elaborate.Īfter I log on to the server, reconnect to the server, or after the server reboots, every five or eight seconds or so, I have a half a second margin to click on a tab, click on a verb, click 'ready', or click on anything for that matter, because while the game is attempting to fulfill my request, the window is in a period of (Not Responding) like this: during that period of time. And if you have a small amount of memory, upgrading that would probably also be a good idea then even if you didn't find the source of the problem you could make it happen less often.So, every time I log on SS13 or relog after a disconnection or after the server restarts, I have to wait nine minutes before the game is fully functional. I'd also check into what else you might have started running recently that might be sucking up resources, perhaps due to a memory or GDI leak. However, a full scan for malware would not go amiss (run your virus scanner, and also try out Malwarebytes). You did mention that you're fine after a reboot for a few days, so probably the only thing you have to do to fix this is restart your computer more often I doubt the reinstallation is necessary. To me this sounds like your system is running low on memory or resources. ![]() Either you have insufficient memory or other system resources to launch Dream Seeker, or a virus is corrupting (or deleting) dreamseeker.exe or one of its associated DLL files so that it won't launch. Because the path it reported is presumably valid, I can think of only two possibilities. The pager is going through this sequence of events:ġ) Lookup world URL you tried to join to get the byond://ip:port - which it does.Ģ) Find the path where dreamseeker.exe is stored so the game can be launched - which it does.ģ) Attempt to launch a new Dream Seeker process. The message that dreamseeker.exe could not be started and perhaps you should reinstall is genertated by the pager. Not only does 422 not start Dream Seeker with a -pager argument, but it doesn't have a build number over 1020. ![]() I was a little confused by your report at first because the version number you put in is incorrect. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |