Others not responding in observer mode

BLASTER Wisconsin · Post by **BLASTER Wisconsin** » Fri Jun 09, 2006 2:39 pm

Every time iam in "Observer Mode" every one else goes to NS and I get kicked for being idle to long. Iam told this should not happen cause iam in observer mode..........HELP !

JeffM · Post by **JeffM** » Fri Jun 09, 2006 4:31 pm

the problem is often due to a router in your line. Check your router settings and make sure it is set to let UDP packets go both ways.

BLASTER Wisconsin · Post by **BLASTER Wisconsin** » Sat Jun 10, 2006 3:59 am

Thanks ... But how do i do that !?

Linuxx0r · Post by **Linuxx0r** » Sat Jun 10, 2006 1:48 pm

put the ip of your router in a browser adress field
most likely its 168.192.0.1 or 168.192.0.2
if its the right adress, you should see a page with some options

H0ley · Post by **H0ley** » Sat Jun 10, 2006 7:24 pm

JeffM2501 wrote:the problem is often due to a router in your line. Check your router settings and make sure it is set to let UDP packets go both ways.

Half true.

The problem is with some buggy routers, especially my d-link router. I'm using DMZ on one of my machines and I still have the whole NR problem. UDP packets are working fine with my bittorent client, why not bzflag? All my firewalls are disabled. I dont get it.

Edit: I did a bit more testing with it. It happens after about 5 mins in observer mode. The lag goes from my normal 50ish to about 1000ish when that NR starts kicking in. According to other players on the server, I'm not NR though. Just everyone else looks NR to me.

JeffM · Post by **JeffM** » Sat Jun 10, 2006 7:42 pm

from the experiments I did, it seems to have to do with the router not liking just geting UDP packets and never sending them. observers don't send updates or anything with UDP.

H0ley · Post by **H0ley** » Sat Jun 10, 2006 8:09 pm

Ok, so I've been tinkering with this router all morning and I think I have a solution. The instructions I'm about to give will only work for D-Link related routers but might work with others.

1) So access your router though http. You know that 192.168.0.1 thing? Yea that.

2) Click the "Advanced" upper tabs.

3) On the side menu, click "Applications".

(This is the important part)
4a) Click Enable
4b) Give it a name "BZflag"
4c) For Trigger Port put: 4000 - 6666
4d) For Trigger Type put: "Both"
4e) For Public Port put: 4000 - 6666
4f) For Public Type put: "Both"

That's it. It doesnt go NR anymore.

According to the router help...

Special Applications
Some applications require multiple connections, such as Internet gaming, video conferencing, Internet telephony and others. These applications have difficulties working through NAT (Network Address Translation). If you need to run applications that require multiple connections, specify the port normally associated with an application in the "Trigger Port" field, select the protocol type as TCP (Transmission Control Protocol) or UDP (User Datagram Protocol), then enter the public ports associated with the trigger port to open them for inbound traffic.

Hope that helps people! Cheerio.

Edit: Changed the range, that should work for 95% of all bzflag servers.

BLASTER Wisconsin · Post by **BLASTER Wisconsin** » Tue Jun 13, 2006 10:54 pm

Ive added a screen shot here because what I tried did not work.
Maybe iam doing something wrong. (Probably) Anyway I tried to follow your (HOley) instructions its still does the whole NR thing.
If all else fails iam trying the other solution we talked about.
Thanks

H0ley · Post by **H0ley** » Wed Jun 14, 2006 1:32 am

That looks correct. Looks like a slightly different router than mine but still the same thing. Try switching it from "Both" to "UDP" and see if that works for ya. Also make sure you have that "WAN Ping Blocking" disabled.

Edit: Also restart your router if it doesnt already do it for you.

BLASTER Wisconsin · Post by **BLASTER Wisconsin** » Wed Jun 14, 2006 10:15 pm

Left it on both and restarted the router and BZF still goes NR in obs mode.
Switched it to UDP and restarted the router and still goes NR in obs mode.

BLASTER Wisconsin · Post by **BLASTER Wisconsin** » Fri Jun 16, 2006 8:21 pm

Now ! When I go NR everyone else goes NR also and when I respawn
everyone else stays NR. then bzf starts to go nuts. ! everyone exploding all around me lol ........ Reseting router to the default settings.

H0ley · Post by **H0ley** » Fri Jun 16, 2006 9:35 pm

LOL!

Check if there's a firmware, after you reset it.

Post by **joevano** » Fri Jun 16, 2006 11:29 pm

OK. This is a realllllllllllll LONG shot... but have you tried getting rid of/renaming your config.cfg file in you BZFlag directory... it is in the folder 2.0 . It will be recreated when you start the app (if there isn't one there). I have seend config file corruption cause strange behavoir, such as not being able to spawn, the app not starting, being unable to kill/be killed. Like I said, it is a long shot, but it looks like you have been trying out the normal solutions with little luck

Ck_asdf · Post by **Ck_asdf** » Mon Jul 03, 2006 5:18 pm

Hah, that'd be cool... unable to kill or be killed. Like an observer who can move around on your own...

Post by **joevano** » Mon Jul 03, 2006 8:16 pm

An Observer can move around on his own... I think you switch the mode with F8 until you get to "Roaming" (watch the top of the screen). Then you can move around the map at will. Use your arrow keys in combination with shift and ctrl. Unmodified you move forward/back/left/right, Shift allows you to move up/down/spinleft/spinright, Ctrl lets you tilt up/down/left/right (or something like that). I always have to mess around with the keys because I can never remember... imagine that

Official forums for BZFlag.org

Others not responding in observer mode

Others not responding in observer mode

Solution, I think

From Bad to Worse