multiplayer
has it been tested online? we r having problems connecting...
I have a standart 128/768 DSL conection..
The stuttering moving of all elements is not related to the conection speed, its a problem of the engine. So far, Carsten knows about this prblem since we played quiate a while ago, and he added a lot of those "flaws" to a list.
Since the DM mod is not that important so far, there are other things with higher priority.
The stuttering moving of all elements is not related to the conection speed, its a problem of the engine. So far, Carsten knows about this prblem since we played quiate a while ago, and he added a lot of those "flaws" to a list.
Since the DM mod is not that important so far, there are other things with higher priority.
was wondering cause nobody i know has ever been able 2 host with dsl. what did you do with your router?
by bug in engine do you mean it lacks prediction or what? carsten i would be glad to write some multiplayer routines if you would like...
Was also thinking of changing chat a bit and adding a nice HUD
by bug in engine do you mean it lacks prediction or what? carsten i would be glad to write some multiplayer routines if you would like...
Was also thinking of changing chat a bit and adding a nice HUD
DSL principally does not affect hosting, except for its inherent connection speed. If you cannot host via DSL, there are probably other factors involved (e.g. your DSL provider enforces some restrictions etc.)Shadow wrote:was wondering cause nobody i know has ever been able 2 host with dsl.
It doesn't lack prediction, as you can see on your own very smooth movement even across a slow server connection.by bug in engine do you mean it lacks prediction or what?
What is does lack is interpolation of the spatial origins of other players, which lets you see their very abrupt movements.
What exactly do you have in mind? Note that any prediction issues are a highly complicated matter.carsten i would be glad to write some multiplayer routines if you would like...
Best regards,
Carsten
Carsten
Yes, that's pretty well encapsulated in the core code. Just the special rules defined in the comments in HumanPlayer.cpp indicate that there is actually prediction going on underneath.Shadow wrote:and i dont really know how your multiplayer system works
Great to hear that, I'm looking forward to the results.so im just gonna make a manual system from the dmatch code using the position/orientation vars and the system clock
Best regards,
Carsten
Carsten
Well, you don't provide enough details about your network for a detailed statement, but here is some general advice:Shadow wrote:how do you get around firewalls? i tried setting my DMZ hosting on from my router, tried port forwarding but i just cant seem to figure it out...
If you try to connect to a Ca3DE server that is located within a "DMZ" and try to connect to it from within your LAN, please read this: http://www.fli4l.de/german/extern/artic ... arding.txt (Text is in German).
Besides that, if you properly configure your router to forward port 30000 to the Ca3DE server IP, it should work.
No other special measure is involved as far as Ca3DE is concerned.
Best regards,
Carsten
Carsten
ok i will try forwarding that port. is anybody willing to test sometime this weekend? im in the states tho (timzon GMT -6) so it might be hard to get a time... one more question, do i use the router IP as the host ip or my computers ip? and im pretty sure i forward the port to my computers ip right?
For clients that are connected to the internet choose the routers (public) IP as the host IP. Your computers IP is local to your LAN only, and not visible from public internet.Shadow wrote:one more question, do i use the router IP as the host ip or my computers ip?
Right.and im pretty sure i forward the port to my computers ip right?
Let us know if it works.
Oh, and just in the case that you could not read the text about "inner port forwarding" that I mentioned above: You can NOT access the server in your LAN from a computer that is also in the LAN via the routers public internet IP, even if port forwarding is enabled. The article above explains why that is the case. You CAN of course access it via the servers IP that is local to the LAN, OR from outside of the LAN via the routers public IP.
Best regards,
Carsten
Carsten
Who is online
Users browsing this forum: No registered users and 38 guests