As the title says, can't launch the game. Other games on BYOND work while SS13 doesn't. When I click JOIN on any server it just sits there and the client becomes unresponsive and I have to close it. Older versions make no difference.
| |
I just don't feel like going through that or dealing with BYOND anymore after having this problem for months now. Let me know when you guys figure out what's wrong or whatever; until then I'll play something else. Thanks though.
| |
You've had this problem for several months? That's probably not the same issue we're seeing in 509, then, but if you can get that data then I can certainly look into fixing it.
Here's the thing, though: Without data I can't fix it at all. Bugs don't get fixed if they don't get reported and enough info isn't available to find the cause, unless I'm lucky enough to stumble onto the cause blindly. If there are other SS13 users in your boat, you could make a real difference for them (and yourself) by just putting in a tiny investment of your time. | |
Real MVP xD, bye.
| |
Fine, don't you need to install a whole shebang of stuff in order to use windows debugger though?
| |
It's just the Windows debugging tools. It's a package you can download from Microsoft. While it includes a few other things, it's not like a huge amount of stuff. (Not like it's installing the full Windows SDK or anything like that.) Any debugger that can get a stack trace will work just fine; Visual Studio users for instance probably already have that setup as their debugger.
The key is that when the process is stuck, a debugger needs to be attached and a stack trace found so that it can be determined where it's stuck. | |
Okay so here's what I got. I feel like I did something wrong but here it is.
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. *** wait with pending attach Symbol search path is: srv* Executable search path is: ModLoad: 00000000`00070000 00000000`00125000 image00000000`00070000 ModLoad: 00000000`778a0000 00000000`77a49000 ntdll.dll ModLoad: 00000000`77a80000 00000000`77c00000 ntdll.dll ModLoad: 00000000`75390000 00000000`753cf000 C:\Windows\SYSTEM32\wow64.dll ModLoad: 00000000`75330000 00000000`7538c000 C:\Windows\SYSTEM32\wow64win.dll ModLoad: 00000000`75320000 00000000`75328000 C:\Windows\SYSTEM32\wow64cpu.dll (180c.624): Break instruction exception - code 80000003 (first chance) ntdll!LdrpDoDebuggerBreak+0x30: 00000000`77948aa0 cc int 3 0:001> ~* 0 Id: 180c.1408 Suspend: 2 Teb: 00000000`7efdb000 Unfrozen Start: *** ERROR: Module load completed but symbols could not be loaded for image00000000`00070000 image00000000_00070000+0x55aff (00000000`000c5aff) Priority: 0 Priority class: 32 Affinity: ff . 1 Id: 180c.624 Suspend: 1 Teb: 00000000`7efd8000 Unfrozen Start: ntdll!DbgUiRemoteBreakin (00000000`77994080) Priority: 0 Priority class: 32 Affinity: ff 0:001> ~1s ntdll!LdrpDoDebuggerBreak+0x30: 00000000`77948aa0 cc int 3 0:001> k # Child-SP RetAddr Call Site 00 00000000`0018eab0 00000000`77900b15 ntdll!LdrpDoDebuggerBreak+0x30 01 00000000`0018eaf0 00000000`7793d150 ntdll!LdrpInitializeProcess+0x17c7 02 00000000`0018efe0 00000000`778cb63e ntdll! ?? ::FNODOBFM::`string'+0x25b20 03 00000000`0018f050 00000000`00000000 ntdll!LdrInitializeThunk+0xe | |
Thread 1 appears not to be right; I'd try the other thread. When in doubt you can choose a thread, type k, choose another thread, and so on.
This was attached to dreamseeker.exe? The 64-bit .dlls don't look right. | |
Yeah it's attached to Dreamseaker.exe and I don't know why but sometimes the debugger works for it and other times it just says it can't connect to the executable. Dreamseeker also stays running each time I exit BYOND and I can't close the .exes.
| |
BYOND has some anti-debugger stuff built-in FYI; I don't think it actually cares if you attach a debugger after it has started though.
| |
IF there's a debugger in BYOND would that work better? Using Windbg doesn't seem to be getting me anywhere, although I've never used a debugger prior to yesterday so I could just be doing it wrong.
| |
Okay so out of curiosity I added an exclusion with my antivirus and now Dreamseeker launches but after it's done loading the resources for the server it crashes completely or I get "Dreamseeker has stopped working".
| |
A crash is good news; it should have left data in your Windows event viewer. If you open that up, what details does it give you for the crash?
| |
Faulting application name: dreamseeker.exe, version: 5.0.509.1315, time stamp: 0x5656852e
Faulting module name: byondwin.dll, version: 5.0.509.1313, time stamp: 0x563d36b8 Exception code: 0xc0000005 Fault offset: 0x0009f717 Faulting process id: 0x88c Faulting application start time: 0x01d12f7b81b96d50 Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe Faulting module path: C:\Program Files (x86)\BYOND\bin\byondwin.dll Report Id: c31d2a56-9b6e-11e5-8ec3-685d433f6122 Faulting module name? Is that like a corrupted file or something? There are also other crash reports with the faulty module name being byondcore.dll as well. | |
Problem: Your installation is messed up. The two versions don't match.
| |
Is there a way for me to fix that without reinstalling?
| |
So I've fixed the issue entirely and would encourage others to try this as these steps could potentially fix several different issues with BYOND.
1. Uninstalled BYOND and deleted all related folders 2. Restarted PC 3. Installed BYOND 4. Added antivirus exception for entire BYOND directory 5. Added firewall exceptions for byond.exe and dreamseeker.exe | |
1) Install WinDbg
2) Wait for Dream Seeker to hang
3) Attach WinDbg to dreamseeker.exe
4) Type ~* to get a list of threads
5) Find the thread with dreamseeker.exe or a BYOND .dll file (usually thread 0)
6) Type ~0s (substitute the thread number you got for 0) to switch to that thread
7) Type k to get a stack trace
8) Copy the entire window contents and share it with me via pastebin or something similar