sm64o
sm64o copied to clipboard
The Tool freezes when i wanna host.
Everytime i click the "Create server?" button, it makes everything turn Grey and it won't let me close it unless i restart my PC, i am using 1.3.1 and using project 2.3 (i was using 1.6 but IT didn't work) i followed the instrutions, i did port forward, but the tool doesn't evento put my IP, can someone please help me?
According to other reports from the Discord server, other people have the same issue. Apparently this was introduced with version 1.3.1. 1.2 did not have this issue.
We'll have to see if we can figure out what's causing it. I think it would help if everyone that has this issue posts a comment here containing some information about your setup, so we might be able to debug the cause. My suggestions would be:
- Your operative system (Windows 7, 8.1, 10? Mac/Linux with Wine?)
- Your installed .NET Framework versions. This guide has a handy tool to check called Raymondcc .NET Detector
- The directory where the tool has been extracted (Documents? Downloads?)
- The name of your anti-virus software
If the .NET Framework tool I posted sees you're missing some packages then it might be wise for you to download them.
You may also make sure that you did not extract the zip to any already existing files from an older version. Doing so causes issues in most cases.
Another thing that comes up in my mind is to disable any unused network adapters your PC may be having. If you have any virtual network adapters too it might be best to disable it as well, in case checking the "Create Server?" checkbox confuses it with all different available IP addresses. You can do this by going to "Network and Sharing Center" on Windows and then navigating to "Change adapter settings".
Hello, I am experiencing the very same problem. My setup is a as follows:
- Windows 7
- .NET Framework version 4.7
- Extracted into an empty folder on my desktop (tried different locations, too)
- Avast Free Antivirus
I set my anti-virus software to let the whole folder do as it pleases.
The Framework tool tells me I'm missing some packages, yet when I try to install them, the program tells me that it is unnecessary since I already have the newest version installed.
I only have one available network, so the .exe file has no way to miss its destination.
What happens when you run this version? https://ci.appveyor.com/api/buildjobs/3epdbqy3og33o18y/artifacts/SM64O%2Fbin%2FSM64O%20Build.zip
The .exe still freezes after I tick the box "create server?"
Update: Version 1.3.1 Hotfix does work for me now (sometimes).
I tried running a server on my laptop but the result was still the same - freeze upon clicking "create server?". Then I tried for a second time and this time, it actually worked! Out of curiosity I tried for a third time and it went back to freezing.
I tried to replicate what caused it not to freeze and I came to the conclusion that it is completely random, sometimes it works but most of the time it just freezes. So this is what I recommend doing: Starting the .exe -> checking the box "create server?" -> if it freezes, open the task manager and kill the process "SM64O.exe" -> repeat until it works. It's more of a workaround than a solution but at least it lets you create a server.
I also wanna mention, when I created my server it told me the port I'm using isn't forwarded, which it actually is! And even though it said this, I'm still able to play online with my friend, so the program seems to have trouble detecting open ports.
Another update: Version 1.3.1 works for me now and I sort of figured out why it didn't work before.
It was a problem with my router. Apparently I had to change the way my router connects to the internet. So I can conclude that the program has trouble grabbing the remote IP address if the router isn't set to a specific kind of connection. I hope this information helps fixing this problem for future releases!
@OceJosh What setting was changed exactly?
@Missiongames I don't know exactly, I just know that my router changed the way it connected to the internet. I changed it back though, because it turned out I could not use my phone anymore. So it probably took over the entire phoneline or something, which obviously is a much bigger problem than not being able to set up a Mario server properly.
The easiest solution in my opinion would probably be to make the automated IP grab optional, that would pretty much solve the issue for people with non-standard router setups.