Cant host ccop

make sure both of you guys have the map downloaded WHEN !START IS USED, as the game can't start without the map.
also check that you there is a Zero-K V1.8.6.9 (or whatever version you guys are playing on) below adv.options and not something like Zero-k $VERSION

Hi,

I just checked on my side I have my version number (1.8.5.3). Will check on friends when online. It also happened on maps we have already played and downloaded.

It occurs when trying to start skirmish/custom battles.

I've found something in the logs files (XXX_infolog.txt) but dont know if it's related or just a normal behavior as we use steam to join the game :

Warning: [UDPListener::TryBindSocket] opening socket on loopback address, other users will not be able to connect!
[f=-000001] [UDPListener::TryBindSocket] binding UDP socket to IPv4-address 127.0.0.1 (127.0.0.1) on port 8452
[f=-000001] [UDPListener] successfully bound socket on port 8452

Thanks for the help.

This sounds to me like you are building ridiculous amounts of units which your computer isnt able to handle anymore.
Either you are having 1500+ units on the battlefield or your computer is somewhat weak, as the Server itself doesnt seem to be the problem.

I would suggest to not endlessly stack units or maybe try to figure out how many units are needed to lag you out of the game.

Will try that.
CPU is for sure not an issue on both side.
My friend has a poor upload that can maybe explain why it's unstable when he host.
Thank you Porkchop :)

I tried the NetworkLossFactor = 1 in both files (springsettings.cfg and IGL_data.lua) and we could achieve 3 games without any issue tonight, The not syncing problem seems fixed.

Thank you ;)

If anybody has an idea about the host problem I will be happy to try, im still not able to host a game.

Kinnes Glad it worked for you!

For later reference and tweaking, I believe this NetworkLoss=[0,1,2] parameter works by marking any packet that "takes too long" to be automatically resent (as long as bandwidth is available). I don't know how the priorities are assigned for new versus old packets. As far as I can tell, it starts sending additional packets when round-trip times exceed:

0 = 400ms
1 = 200ms
2 = 100ms

Something to explore might be how a ping-based recommendation could be taken into account for this setting for peer-to-peer connections. An idea of what might be happening is that players with higher ping to each other than the value in the config are sending an amount of duplicate packets that become a problem in the late game on a home connection. If this is actually the cause, an ideal 'baseline' might be for the ping limit of NetworkLoss to be one notch higher than their expected ping for the match.

A more basic approach might be a setting like "Optimize Co-op Networking for [Local/Regional/World]". Those probably wouldn't fall too far off the mark from the ping times above.

Here's a completely wild guess. Do you have the same ISP as the person you're playing with? If not, I wonder if your ISP placed you behind a shared IP?

This is sometimes called carrier-grade NAT, some information about how it works

At least in my area some ISPs have switched to having tiers of service that use terrible CGNAT on lower plans that completely ignore your router NAT settings. Had this silently happen at one point and hosting games on steam became somewhere between impossible and a huge PITA. It was worth upgrading just to have a proper IP again.