dim3 Forum

Full Version: Latest Server Won't Work
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Brian, I have this here little problem:
I wanted to make a multiplayer game (yes, I changed my mind about networking)
and I ran into trouble
1) on b17u2, the server crashes as soon as I attempt to join and throws a HostError
2) On b15, it still works, but the projectiles don't get synched, and if I don't start the engine from the editor and quit the map first the engine crashes if I attempt to join.
3) Sometimes the engine says it couldn't bind to IP and port
There are some more problems, my brother and I are still testing
that hapens to me

Macintosh HD Wrote:
3) Sometimes the engine says it couldn't bind to IP and port
There are some more problems, my brother and I are still testing


After closing Server.app and before opening the same one again, wait up to 5 minutes and the 'stuff' will be reset and it will work. I don't think there's a work-around for this, says Brian.

I've had the wierdest problem in muliplayer, if I use a model for a projectile it apears as the player model (only to other people) and it gives my errors like player.js named animation does not exist: bounce.
So now I have to use projectiles like bullets as missiles.

Macintosh HD Wrote:
Brian, I have this here little problem:
I wanted to make a multiplayer game (yes, I changed my mind about networking)
and I ran into trouble
1) on b17u2, the server crashes as soon as I attempt to join and throws a HostError
2) On b15, it still works, but the projectiles don't get synched, and if I don't start the engine from the editor and quit the map first the engine crashes if I attempt to join.
3) Sometimes the engine says it couldn't bind to IP and port
There are some more problems, my brother and I are still testing


Yeah, I'm still doing work on some of these. I'll have the crash on join bug fixed ASAP, I'm working on that now.

#3 is a killer -- sometimes -- and I think it's not as bad as it used to be -- OS X (and windows, too) holds the port even after I've told it to close. There's a sanity time out that kicks it at certain moments (say, for instance, it's not getting it's hand sake from the connected machine), and this forces you to wait for a minute or two before restarting. This could be my fault but I don't see where.

[>] Brian

Reference URL's