It takes 3+ minutes to enter the Multiplayer mode

[unchien51]

Hey guys,

I have two computers. On each I have a copy of KAM Remake. On my first computer I've been playing the game for a long time now, including the multiplayer games with the whole community.

However, on my second computer the singleplayer works normally, like it was supposed to, but I am having difficulties with the multiplayer mode. When I'm in the main menu (main screen) and try to press the "Multiplayer mode" button, the game freezes all over! Then I have to kill it with the task manager. And no matter how many times I restart my computer, or uninstall and reinstall the game the problem doesn't seem to go away. It just reoccurs everytime.

Has anyone ever encountered a similar issue and how did you solve it? Is there a solution to it? I really don't know what to do. :| :( :?

Hope you guys can help me out.

unchien51

[LauraRozier]

Honestly I have never had this issue.
A few questions, though:

• Now my question is: Did you update the game on that second computer or did you use a full installer?
• What operating system do you have on the second computer? (Like XP, Vista, 7, etc)
• What version did you install on the second computer?
• Could you provide a log with the issue?

With all the information I see right now I would suggest the following:

• Uninstall the game
• Download the most recent full installer, on the second computer, from the main website: http://www.kamremake.com/
• Reinstall the game with elevated(Administrator) rights.
• Run the game as a normal user and retry to open the multiplayer menu.
• If unsuccessful, run the game again as Administrator, then retry the multiplayer menu.
• If unsuccessful, we might need to make a firewall exception within your system.
• If that is unsuccessful more research will be required.

Thank you for filing your issue, please respond with your findings, whether it worked or not.
That might help us solve the issues someone else has in the near or distant future. :)

~ Thimo.

[unchien51]

Hi Thimo (thibmo),

Thanks for your reply. It seems strange to me as well. To answer your questions:

• On my second computer I had used a full installer (the latest 6.-something version).
• I run a Win7 x64.
• I would be glad to provide with a log, unfortunately I have no idea how to? As I stated earlier, it doesn't pop-up any message as to even give me an option: "See log" or similar. If you can tell me how to provide the log, I'd be glad to help.

I did all the procedures that you asked me to, however all have resulted in the same manner.

However, I tried another thing: I waited. I know it sounds something rational to have had done from the beginning already, however on my first computer it goes to the multiplayer mode immediately after pressing the button, but on my second computer it took roughly 2-3 minutes --> which of course isn't normal, but now it appears as it is working normally. So strange...

If the problem reoccurs and something strange happens, I'll write again. Thanks again for all the help provided!

p.s.: my first computer is Lenovo Win 8.1, my second is HP Win 7. -> no idea why such a lag on the 2nd one!

[unchien51]

Hi again,

Actually, the interesting thing that happens now is that every single time that you wanna go to the initial screen of the mutliplayer mode, you have to wait. So for example, I waited 2 min from the Main menu to Multiplayer mode. Then I have joined to a game. When I decided to go back to the servers room, I had to wait again for 2-3 min to return from lobby. Later I tried to just "Refresh the Server List" and yet again it took 2-3 min to do so. Such an annoyance!

What do you think the reason would be behind this issue? I mean, apparently there are some protocols running in the background and reeeeeaaaaallllly taking their time.

If you have any ideas, please let me know.

Thanks,
Unchien51

[LauraRozier]

Good to know that it takes time, that's a lead.
So two minutes.
That might be a thread hanging.
What processor do you have in the second computer?
And the logs can be found in the game folder.
For example: C:\KaM Remake\Logs or C:\Program Files\KaM Remake\Logs

[unchien51]

Ok, so yeah, around 2-3 minutes maybe even more, I'm not entirely sure.

The processor is: AMD Phenom(tm) II N660 Dual-Core 3.0 GHz.

And about the logs, I have no idea which ones to provide, so I'm gonna add a few from the last couple of days. Please follow this link to access the log file: https://www.dropbox.com/sh/gwhxdku5xal1zg0/AAAq_6AVOpkiUTUDCMiOEfWIa?dl=0

Let me know if you couldn't access, and if so, please advise how can I share other types of files besides png, gif or jpg.

Brgs,
Unchien51

[LauraRozier]

Maybe it would be a good idea to try an earlier version, r5503.
Here is the link to the download:
1> Download and install this: http://www.kamremake.com/files/kam_remake_full_r5503-exe/
2> Download and apply this: http://www.kamremake.com/files/kam_remake_hotfix1_for_r5503-zip/

Also, are they connected over WIFI or cable?

Please let us know the results.

[unchien51]

Now, when I tried the previous version, it worked slightly faster. It took roughly 5 secs to enter the multiplayer mode. However the problem is that no one still uses this version and I can't play against the rest (which would be the point of multiplayer mode :) )

I haven't tried the step 2 however, what does it do? If it makes it possible to connect with others who use the newer version, then that might be a temporary solution (fixing only the symptoms not the underlying problem).

Both my laptops connect via WiFi.

Should I try to apply 2> and then report back? Please meanwhile, let me know what this hotfix makes?

Thanks in advance!

[LauraRozier]

No, not yet, step 2 is only a fix for the scripted game play(Nothing to do with networking)
That's something we needed.
To see whether a previous version did work.
Now it is our turn to see where there was a change that might have effected the game's networking protocol.

Please be patient, we will work as fast as we can. :)

[unchien51]

Of course, please take your time and we'll stay in touch. If you ever need another test, let me know.

:)

Unchien51

[LauraRozier]

Michal1324, that is a negative.
Krom and I are looking into this as it is a NETWORK issue.
It doesn't bug out at the loading of the trees, but before that.

[unchien51]

Hi,

I don't think defragging the hdd would be a bad idea, however I also
believe it is not the underlying issue as other software (such as MS
Office, Chrome, Antivirus and so on) is working just fine, not perfect, but
fine.

What could possibly be wrong in my network settings....hmmm....
On May 26, 2015 10:27 AM, "Michal1324" notifications@github.com wrote:

Ehem it takes 42 minutes to load game resource in mp you should look up
the log

—
Reply to this email directly or view it on GitHub
#37 (comment)
.

[LauraRozier]

Michal1324,
Please read back my previous replies.
A previous version of the game functions properly.
This means that in one of the updates something went wrong.
That is the bug and we are working on it. :)
Nothing is blocking it, just a little typo or something that doesn't enjoy working with unchien51's NIC.
If it's a typo, it will be easily fixed, if not it will take a bit of time.

[lewinjh]

Michal1324, you misunderstand how the log works. The time deltas are simply the time difference between one log entry and the previous. It is not the amount of time it took to complete each item. Obviously it's not taking him 42 minutes to load the game or he would have mentioned it...

[TehPlayer14]

oh ok sorry

[LauraRozier]

No worries, Michal.
@lewinjh : I saw that there has been an update to OverByte ICS after the most recent release, perhaps this might solve the issue already?
I am still trying to find more updates related to networking.
Perhaps an idea to entitle commits with labels that concern the commit, like "Net", "GUI", "[xyz] menu", etc, would assist in these hunts to the updates that changed codes concerning networking.

[Kromster80]

Marking commits will cause more trouble than help. Many times commits might change parts that are loosely related, but still connected.
Since the bug is quite easy to track, I suggest to start a kind of binary search. Compile r5700, r5900, r6100, r6300, r6500 and check if they freeze. Then compile several evenly spaced versions in between good one and broken one. Repeat till the exact commit with the bug is found. IIRC Thibmo can do that without need of KM_SecureAuth or matching MP servers, since the freeze seems to occurs right on the first packet to/from MP master-server (on entering MP menu).

[LauraRozier]

@Kromster80 Got it, and true. I am able to start private dedi server matches without KM_SecureAuth.
I do have hex codes so searching for the revision numbers will be the hunt right now.
I will compile a few versions ASAP and make them available through Dropbox (Any suggestions for different methods are most welcome.)
I hope to have two versions (r5700 and r6500) available today (Around 8PM Amsterdam/Berlin time).

[Kromster80]

There is no need to start private server. So far it looks that the pure act of sending/receiving messages from master server (e.g. asking for servers list) freezes the game.
You will need to check if compiled EXEs are working in main/MP menus without old (pre 6720) data files.
I would also recommend to do more test versions, cos preparing one takes 10min and testing 1-2 days (until unchien51 comes online and grabs them and has time to test)

[unchien51]

Thanks guys for putting in so much effort. I am constantly checking the
updates and progress that you are posting. So in case you need me, I'll be
definitely available asap. If in the mean time you need any other "symptoms
check" please do not hesistate to ask.

Best regards,
Unchien51

2015-05-26 14:13 GMT+02:00 Krom Stern notifications@github.com:

There is no need to start private server. So far it looks that the pure
act of sending/receiving messages from master server (e.g. asking for
servers list) freezes the game.
You will need to check if compiled EXEs are working in main/MP menus
without old (pre 6720) data files.
I would also recommend to do more test versions, cos preparing one takes
10min and testing 1-2 days (until unchien51 comes online and grabs them and
has time to test)

—
Reply to this email directly or view it on GitHub
#37 (comment)
.

[LauraRozier]

Hello, oke. So first off, I would really much like you to test our most recent version, to see if the update of OverByte ICS might have solved the issue already.
I will upload every version to the following Dropbox folder, that will be available throughout this debugging process: https://www.dropbox.com/sh/lr8x2qa3s8lkimg/AAChVC6YVjmCmCAmMwQ8Ky2Ra?dl=0
Every version will be marked as kam_remake_rxxxx.exe (Will only change the exe name after compilation, and test them after the rename to be sure.)

With replies, please do send feedback using the exe's name, that would help us a lot. :)

I will give all the required files in the zipped files, if it is only the exe file I will leave it as an exe and not zip it.
You can just copy-paste the file(s) into your current game folder without uninstalling it.
Best practice would be to take the non-working version and putting the files in that folder.
I will keep the folder hierarchy so you won't have to figure out where the files have to go.
Just put them in, for example, C:/KaM Remake

[LauraRozier]

Tiny detail change, r5900 will be r5899 due to UI issues at r5900, the UI looks rather odd in r5899 as well, please use maximized screen or buttons might be missing.
All versions are up now.

I hope you don't mind testing them for us, as, to speak only for myself, I can't reproduce the error on my system.

One hint, start with the most recent version first, this due to r5700 changing a lot with fonts and texts.

[unchien51]

Hi Thimo,

Please let me know which .exe should I use [first] as I'm not so sovereign
to know exactly what to do next? Also, do I need to do anything with the
.zip folder, and if so, what exactly?

Sorry for asking for more help, it's just that I'm not so advanced in such
problem-solving procedures. After you let me know more detailed steps, I'll
perform them and report back asap.

2015-05-26 17:53 GMT+02:00 Thimo notifications@github.com:

Tiny detail change, r5900 will be r5899 due to UI issues at r5900, the UI
looks rather odd in r5899 as well, please use maximized screen or buttons
might be missing.
All versions are up now.

I hope you don't mind testing them for us, as, to speak only for myself, I
can't reproduce the error on my system.

—
Reply to this email directly or view it on GitHub
#37 (comment)
.

[LauraRozier]

Sure, no problem mate. :)
Here the prefered order:
1> Kam_Remake_development.exe
2> Kam_Remake_r6500.exe
3> Kam_Remake_r6300.exe
4> Kam_Remake_r6100.exe
5> Kam_Remake_r5900.exe
6> Kam_Remake_r5700.exe

The zip files you can open with a tool that is standard to Windows, no need to download anything for that. :)
Just double-click and unpack it to your KaM Remake folder(Directory)
I am sorry but I can't write in Slovenian. :/
Might you not be sure about it, please do tell me, I will try all I can to assist, even if it would mean a Google hangouts call or TeamViewer. :)

[unchien51]

Hi,

To be current, as I'm already on way to resolving the problem.

1. So, I unzipped the files from "development" to the folder of Kam Remake. Then I ran the game like I would normally (shortcut from desktop). It took the same time as the usual to enter the multiplayer mode --> 3 min or so :/
   Was I supposed to run the "Kam_Remake_development.exe"?
   1.1) Ok, so I ran the "..development.exe" and this time everything froze after trying to enter the Multiplayer mode. I'll now go to the next step.

2. So this time, I put the r6500.exe into the Kam Remake folder and I ran it. It happened the same result as in 1.1) --> everything froze after trying to enter the multiplayer mode :/

3. r6300.exe ---> same result as 2) (just to add extra info: Windows asks me every time: "Do you allow this application to access the home/public network?" Of course I allow it every time. But afterwards the screen goes black....aaaand everything freezes :/ (need to stop it abruptly by using task manager). However, I let it run for a while this time (even if black screen), and it DID eventually get me to the multiplayer mode, however again only after roughly 3 minutes.

4. Ok, so I tried 6100 here and interestingly it worked! It didn't ask me to allow the application to communicate with the home network, and it went straight to the multiplayer mode without any lag or delay. However, when I tried to "create a local server", the Windows DID make a request which I approved of course, and then it went into black screen and froze all over. My intention was to join a game and since there weren't any in the list, I tried to make my own server, to see if it would freeze when I would have exit from the lobby back to the servers' list. After a while (2-3 min), it did create a local server, however without me (host) in it. When I clicked "Back to the list" it went there immediately without any lag or delay ----> Hurray! :)

5. ... awaiting further instructions ...

[LauraRozier]

Yes, indeed. :)
I changed the post to the full names, I hope it is more clear that way. :)

[unchien51]

Ok, so far I have stopped at step 4 which seems to have worked on the original issue which was a huge lag when trying to enter the Multiplayer mode and now that lag is gone. :)

Please advise as to what to do next from my side. :)

[LauraRozier]

Then the issue lies between r6300 and r6100, now we narrow it even further. :)
Now instead of steps of 200 maybe steps of 25 or 50.
I hope to be able to bring you more builds tomorrow, I have a load of studying to fulfill this week.
I might try to slip some build in during my breaks, I will keep you informed. :)

[unchien51]

Hey, I know exactly how it is with the studies. I am just a couple of weeks away from the "exam-after-exam" period. :) So no worries, take your time, meanwhile I'll just use the other computer for MP, and the "troubled-one" for SP only ;)

Cheers!

[LauraRozier]

Well, that was quick... :P
Got all the new versions ready for testing.
My personal guess is that it might be between r6175 and r6200
This time only .exe files, so it should be easier.
Again the highest number down to the lowest number would be best practice. :)
Also, big thumbs up for your help so-far, without it we would be touching in the dark. 👍

One note why r6250 is missing: There have been a huge amount of new bugs and bug fixes in-between r6225 and r6275 which prevent me from compiling a working copy that's close enough to r6250 to be worth the try, I tried to combine tiny fixes that might have made it possible to fix the issues until I ran against the big fix for wave sound files, then I stopped, it would look a lot alike r6275 were I to implement that fix as well.

[lewinjh]

I'd guess it was caused when I added scanning the LAN for local servers via a UDP broadcast, which was r6234:
df59364

Maybe test the version before that first? I have no idea why it would cause lag though...

[LauraRozier]

@lewinjh Might be true.
Both have a few network related fixes... Could be both. :P
Only the test will tell.

Edit: I would find it odd that a UDP protocol would slow down everything..
As a connection-less protocol, you see... Doesn't have to wait for a three-way hand-shake like TCP..
Though I did see that before starting to listen it states "fUDP.StopListening;" @ 146
Maybe good to check if fUDP is even listening?

[LauraRozier]

It's been a while now, I hope you are alright. :)
I have added the files to the same Dropbox folder.

I hope to be able to receive a reply soon, on which versions do work and which do not.

[unchien51]

Hi,

Sorry for not writing back now in a while. To be honest, and this may sound slightly stupid, I was sure I was waiting for your reply and that it was your move and not mine.

Since it's so late right now, I will try the new files on DB tomorrow first thing in the morning and report back.

Sorry for the confusion!

Brgs :)

[LauraRozier]

Ghe, no worries, my bad then. :)
I will now make a new comment every time I change something, rather then edit one.
Thanks for letting me know. 👍

[unchien51]

Ok, so..

I started from top down, as previously:

1. 6275 didn't work (3min+ lag/force shutdown)
2. 6225 worked (it went directly to multiplayer mode) (however, when trying to create a local server, the whole thing froze, had to force shutdown)
3. 6200 - worked (it went directly to MP mode)
4. I stopped testing here as I now think "got" the logic...so apparently the problem is between 6275 and 6225? :)

Was the "Maybe check if fUDP is even listening" meant to me? If so, how do I do that?

Sorry again for the confusion, I hope all's fine :) :)

[LauraRozier]

Hey, yes indeed it would in between those two. :)
I think Lewin might be right then.
Some further testing will have to confirm.
That bit of text was aimed towards Lewin, as it is code-based.

I will make a few more versions ASAP and I will make a new commend upon the addition to Dropbox. :)
Meanwhile I will move the old files to the appropriate directories in Dropbox for our reference.

Thanks again. :)

[unchien51]

Hehe, super that you guys can cooperate so well together.

I'm on stand-by for further instructions! ;)

[LauraRozier]

Both uploaded to Dropbox, r6233 and r6234. :)

[unchien51]

So,

This time the results are as follows:

1. r6234 -> doesn't work (known issue)
2. r6233 -> works nicely

I have a feeling we're getting closer, however still lot of work to be done? :)

[LauraRozier]

Ghe. Lewin was 100℅ right.
The UDP update broke it for your system.
The only difference between the two versions I send you is the UDP update.
We can now start looking at what is the cause of the issue.
One question, whenever you open the game and click on multiplayer, does it pop open a dialog where you have to accept a exception in the firewall?
It should request this for every version using the UDP update.

[unchien51]

So it was the UDP, ok.

Yes, every time I pressed on MP it popped up a dialog for exception in the firewall. Only I chose "never show this dialog again" so that's why it didn't show when I tried the same version the second time. But for every new version I had to accept an exception.

Hmm...what is the upside of the UDP update that you put in the newer version. And also, how come that for example my primary lap top isn't making any troubles, meanwhile the secondary is - where is the big difference?

[Kromster80]

Which means you need to go to Firewall rules list and unblock r6720.

AFAIK UDP update is meant for LAN networks to discover local KaM Remake games, but I could be wrong and Lewin can correct me.

You probably have UDP allowed and saved on your other laptop or it's just in the "allow all UDPs" mode.

[unchien51]

Hi,

I did that. Already prior to even commenting here. I went to the Windows firewall and added r6720 to the allowed programs list, and just to be sure I also did the same with an external provider (in my case: Comodo: https://www.comodo.com/).

Perhaps I will re-check everything.

Thanks for the explanation.

[unchien51]

Ok something interesting. So, I tried to add all possible exceptions, I even looked for more detailed settings and allowed all UDP and TCP in any directions etc etc ... I did this both on Win Firewall and Comodo. -> Then I opened the game, and the same issue appeared when trying to go MP.

Secondly...I turned off BOTH firewalls for the time. I tested again, and yet again it failed.

If both firewalls were turned off, could it still be firewall problem, or would it be something else?

[LauraRozier]

Then perhaps it is something else.
also, if you changed something and it didn't work, always put it back as it was, that for your own safety. :)

[LauraRozier]

Oke...
Made some quick edits, to see whether it is the stopListening procedure of the socket causing issues.
Only added a property that determines whether the socket is listening the yes or the no.

The version is called KaM_Remake_r6830.exe and is in the Dropbox folder right now.
(Also, sorry Lewin for fiddling with the code, I hope you don't mind. :x)

[Kromster80]

@unchien51: Did you reboot your PC after changing the settings? Usually this is not required, but that could help.

[lewinjh]

Sounds like it freezes up whenever it tries to open a listen socket. When you first enter the multiplayer lobby it opens a UDP port to listen for local servers. And when you create a server it opens a TCP port to listen for clients. You said it freezes in both of these cases. I don't think it's specifically related to the UDP listening for local servers since you said it also happens in the old versions when you try to create a server.

This could be related to your firewalls. It may block KaM Remake from opening listen sockets while it asks you to allow or deny it, causing KaM Remake to freeze. As Krom suggested you could try disabling the firewalls and rebooting. You could also try (temporarily) uninstalling 3rd party firewalls (anything other than Windows firewall) since that's something specific to your setup (but most users will have Windows firewall).

Did you try running KaM Remake as administrator to see if that makes a difference? (from the right click menu)

It might also be a port clash, if you have some other program running which is already using the ports used by KaM Remake (56789 and 56788).

[TehPlayer14]

Uninstall comodo install some other antivirus or disable firewall and use default one

[unchien51]

Hey guys, sorry for not being active, I had loads of work yesterday, which will continue today. I think maybe today in the late evening or tomorrow morning, I'll be able to make more tests. Thanks for your patience. I will try to apply all of your propositions.

[unchien51]

Hi,

Me again. After a tough day I found an opportunity window to make some tests. So, please, read carefully as I believe there was some misunderstanding due to my expression (dis)abilities:
So first thing to clarify, it is not true that when I try to "Create a Local Server" I run into trouble. Meaning, I can easily create a server, or enter any other game. However after I try to go back to the servers list, I have to wait again for 3 min or so.

Ok, as for today's tests, the results:

1. First I tried the latest r6830 version, I ran it as admin, I added a firewall exception, confirmed the windows pop-up dialogue and so on. Pressed the MP button. --> 3 min of painful waiting :/
2. I uninstalled Comodo, restarted the pc, tried to run the r6720 (I'll call it the "normal-one") with admin rights, pressed the MP button.---> same result: 3 min of waiting.
3. I did the same with r6830 as in 2) and it resulted in the same result as in 1) or 2).

No idea what's happening with my UDP ports :/ Are you guys running out of options, or do you think there is still something we could try?

On an unrelated note, I am about to download PANDA and use it as my third party firewall.

Oh, and, how could I check if "It might also be a port clash, if you have some other program running which is already using the ports used by KaM Remake (56789 and 56788)." might be true?

[LauraRozier]

Hey, thanks for testing yet again.
Now.. To see which ports are open on Windows you must open command prompt (Start -> type CMD -> Right click -> Run as Administrator), then there is a tool called netstat.
To see all the ports and the application that opened it, type: netstat -a -b

Then you will recieve a list(That might take a time to create itself) looking like this:

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             Thibmo-LAPTOP:0        LISTENING
 [Skype.exe]
  TCP    0.0.0.0:135            Thibmo-LAPTOP:0        LISTENING
  RpcSs
 [svchost.exe]
  TCP    0.0.0.0:443            Thibmo-LAPTOP:0        LISTENING
 [Skype.exe]

Though there is a little trick within netstat to speed this up. :)
You can type: netstat -a -b -p UDP
This creates a list with just the UDP protocols, even though the above is better, since it shows all the ports, this one is good for a quick reference.
It's list looks like:

Active Connections

  Proto  Local Address          Foreign Address        State
  UDP    0.0.0.0:443            *:*
 [Skype.exe]
  UDP    0.0.0.0:500            *:*
  IKEEXT
 [svchost.exe]
  UDP    0.0.0.0:1434           *:*
 [sqlbrowser.exe]

There, try to see if you can find anything using ports 56789 and 56788, if so try closing that program and retry.

[TehPlayer14]

Have you tried updatin to win 10?

or trying to launch kam remake in virtual machine to see if the problem occurs too?

[Kromster80]

Closed as not reproducible.