QoS & netspeed might be the cause of trigger lag. | Forums

[XyZspineZyX]

Read the following text I found on a Danish website, I did this:

This is for broad band connections using windows XP PRO.

1.make sure your logged on as actually "Administrator". do not log on with any account that just has administrator privileges.

To log in as an administrator:
click on start->logoff->logoff
in the logon screen hold Ctrl+Alt+Del.
in the user field type 'Administrator' <-case sensitive.
in the password field type the password for the administrator (if you dont have any leave blank. click ok.
2. start - run - type gpedit.msc
3. expand the "local computer policy" branch
4. expand the "administrative templates" branch
5. expand the "network branch"
6. Highlight the "QoS Packet Scheduler" in left window
7. in right window double click the "limit reservable bandwidth" setting
8. on setting tab check the "enabled" item
9. where it says "Bandwidth limit %" change it to read 0-- Click apply,

OK, exit gpedit.msc
10. go to your Network connections (start->my computer->my network connection->veiw network connections). right click on your connection, choose properties then under the General or the Networking tab (where it lists your protocols) make sure QoS packet
scheduler is enabled. 11. reboot , now you are all done.

This is more of a "counter what XP does" thing. In other words, XP seems to want to reserve 20% of the bandwidth for its self. Even with QoS disabled, even when this item is disabled. So why not use it to your advantage. To demonstrate the problem with this on stand alone machines start up a big download from a server with an FTP client. Try to find a server that doesn't max out your bandwidth. In this case you want a slow to medium speed server to demonstrate this. Let it run for a couple of minutes to get stable.

The start up another download from the same server with another instance of your FTP client. You will notice that the available bandwidth is now being fought
over and one of the clients download will be very slow or both will slow down when they should both be using the available bandwidth. Using this "tweak" both clients will have a fair share of the bandwidth and will notfight over the bandwidth.

Then I changed the following in the Ravenshield.ini file.

[Engine.Player]
ConfiguredInternetSpeed=10000

My trigger lag is gone.

You can also remove QoS scheduler as suggested by this text:

When you select your connection type, UT2003 sets a connection speed that it expects will work well with this connection type. Selecting a connection type faster than what your connection can support will result in extremely poor network performance, as UT2003 will attempt to use more bandwidth than is available, causing packets to back up.

The most common reason for laggy, unresponsive gameplay on-line is that somewhere in the connection between your client and the server, there isn't enough bandwidth available to handle the connection. This can happen if you are playing on a server that has too many players connected for the speed of its internet connection (a common problem with servers running on a cable modem). If the game plays well until a certain number of players have joined, the server connection is the problem.

Its also possible that your connection does not have as much bandwidth as UT2003 expects, even if you set the connection speed properly. For example, a cable modem's available bandwidth may be significantly reduced if many other people are using a cable modem in your area, or if your provider caps the bandwidth at a lower level than UT2003 expects. Here are the default settings which UT2003 uses for available data bandwidth. Note that there is additional network and protocol overhead, so these values will be lower than the theoretical maximum speed of the connection:

Modem: 2600 bytes/sec
ISDN: 5000 bytes/sec
Cable/ADSL: 10000 bytes/sec
LAN/T1: 20000 bytes/sec

UT2003 almost never actually uses more than 7500 bytes/second of data for connections. You can tweak the bandwidth cap used by your client using the netspeed console command. For example, typing netspeed 4000 at the console will change your bandwidth cap to 4000 bytes/second. The actual bandwidth cap is also limited by the client bandwidth cap set by the server to which you are connected. If you are seeing poor network performance, experiment with lower netspeeds.

If this doesn't address your network play problem, type stat net at the console to bring up network statistics in the top left hand corner. Several lines of text will be displayed, looking something like:

- Net ---------
59 Ping
60 Channels
In: 0, Out: 0 Unordered
In: 0, Out 0 Packetloss
In: 19, Out 41 Packets
In: 76, Out 40 Bunches
In: 3212, Out 2623 Bytes
5000 Speed
0 Reps
1 RPC
0 PV

Ping is the round trip time between your client and the server, including game packet processing time on the client and the server. Ping is also shown for each player when you bring up the scoreboard (by pressing F1). Since the ping displayed includes game client and server overhead, it will be greater than the network ping shown in the server browser before you connect. The higher the ping, the more delay there will be before the server processes your commands.

This will be evident to you as lag before the projectile comes out when you press fire, for example.[img]/i/smilies/16x16_smiley-surprised.gif[/img]

Very high pings (above 500) indicate either a distant server, or that your network connection is saturated (in which case you should reduce your netspeed as described above).

You will very rarely see unordered packets. These have the same effect as lost packets, since they have to be thrown away. Packet loss of more than 10% (divide the packetloss + unordered total number by the packets number) can cause severe degradation of the connection. This is a network issue - there isn't anything you can do about it except connect to a different server.

The number of bytes in and out will typically be significantly lower than the speed (your max connection speed) unless you have a very low netspeed selected (for example a modem). However, they should always be over 1000 bytes/second. If not , this may indicate a problem with the server (unless its a very quiet server with no action).

Typing stat net again at the console will make the network statistics display go away.

We've also seen this advice posted on the UT2003 forums, to address problems with very high (999) pings:

In Windows, go to Start > control panel > network connections >

Now here you should see

- Client for Microsoft Networks
- File & Printer sharing
- QoS Packet Scheduler
- Internet Protocal (TCP/IP)

Click on QoS Packet Scheduler and click "remove". Then reboot and play.

As you can read from the above text trigger lag can also be present in UT2003.

My trigger lag is reduced by 99.9% and RvS is sweet again.[img]/i/smilies/16x16_smiley-very-happy.gif[/img]




Cheers TT

OS: Windows XP Professional SP1 DX 9.0a
CPU: Athlon XP 2400+
Motherboard: ASUS A7N8X
RAM: Corsair CAS 2 512MB PC2700 DDR
Video Card: ATI Radeon 9700 Pro Rev 3.0 Omegadive Modified CAT 3.4
Sound Card: Sound Blaster Audigy : aud_betadrv_030417
Mouse: Logitech MX700 : Mouseware 9.76

[XyZspineZyX]

Read the following text I found on a Danish website, I did this:

This is for broad band connections using windows XP PRO.

1.make sure your logged on as actually "Administrator". do not log on with any account that just has administrator privileges.

To log in as an administrator:
click on start->logoff->logoff
in the logon screen hold Ctrl+Alt+Del.
in the user field type 'Administrator' <-case sensitive.
in the password field type the password for the administrator (if you dont have any leave blank. click ok.
2. start - run - type gpedit.msc
3. expand the "local computer policy" branch
4. expand the "administrative templates" branch
5. expand the "network branch"
6. Highlight the "QoS Packet Scheduler" in left window
7. in right window double click the "limit reservable bandwidth" setting
8. on setting tab check the "enabled" item
9. where it says "Bandwidth limit %" change it to read 0-- Click apply,

OK, exit gpedit.msc
10. go to your Network connections (start->my computer->my network connection->veiw network connections). right click on your connection, choose properties then under the General or the Networking tab (where it lists your protocols) make sure QoS packet
scheduler is enabled. 11. reboot , now you are all done.

This is more of a "counter what XP does" thing. In other words, XP seems to want to reserve 20% of the bandwidth for its self. Even with QoS disabled, even when this item is disabled. So why not use it to your advantage. To demonstrate the problem with this on stand alone machines start up a big download from a server with an FTP client. Try to find a server that doesn't max out your bandwidth. In this case you want a slow to medium speed server to demonstrate this. Let it run for a couple of minutes to get stable.

The start up another download from the same server with another instance of your FTP client. You will notice that the available bandwidth is now being fought
over and one of the clients download will be very slow or both will slow down when they should both be using the available bandwidth. Using this "tweak" both clients will have a fair share of the bandwidth and will notfight over the bandwidth.

Then I changed the following in the Ravenshield.ini file.

[Engine.Player]
ConfiguredInternetSpeed=10000

My trigger lag is gone.

You can also remove QoS scheduler as suggested by this text:

When you select your connection type, UT2003 sets a connection speed that it expects will work well with this connection type. Selecting a connection type faster than what your connection can support will result in extremely poor network performance, as UT2003 will attempt to use more bandwidth than is available, causing packets to back up.

The most common reason for laggy, unresponsive gameplay on-line is that somewhere in the connection between your client and the server, there isn't enough bandwidth available to handle the connection. This can happen if you are playing on a server that has too many players connected for the speed of its internet connection (a common problem with servers running on a cable modem). If the game plays well until a certain number of players have joined, the server connection is the problem.

Its also possible that your connection does not have as much bandwidth as UT2003 expects, even if you set the connection speed properly. For example, a cable modem's available bandwidth may be significantly reduced if many other people are using a cable modem in your area, or if your provider caps the bandwidth at a lower level than UT2003 expects. Here are the default settings which UT2003 uses for available data bandwidth. Note that there is additional network and protocol overhead, so these values will be lower than the theoretical maximum speed of the connection:

Modem: 2600 bytes/sec
ISDN: 5000 bytes/sec
Cable/ADSL: 10000 bytes/sec
LAN/T1: 20000 bytes/sec

UT2003 almost never actually uses more than 7500 bytes/second of data for connections. You can tweak the bandwidth cap used by your client using the netspeed console command. For example, typing netspeed 4000 at the console will change your bandwidth cap to 4000 bytes/second. The actual bandwidth cap is also limited by the client bandwidth cap set by the server to which you are connected. If you are seeing poor network performance, experiment with lower netspeeds.

If this doesn't address your network play problem, type stat net at the console to bring up network statistics in the top left hand corner. Several lines of text will be displayed, looking something like:

- Net ---------
59 Ping
60 Channels
In: 0, Out: 0 Unordered
In: 0, Out 0 Packetloss
In: 19, Out 41 Packets
In: 76, Out 40 Bunches
In: 3212, Out 2623 Bytes
5000 Speed
0 Reps
1 RPC
0 PV

Ping is the round trip time between your client and the server, including game packet processing time on the client and the server. Ping is also shown for each player when you bring up the scoreboard (by pressing F1). Since the ping displayed includes game client and server overhead, it will be greater than the network ping shown in the server browser before you connect. The higher the ping, the more delay there will be before the server processes your commands.

This will be evident to you as lag before the projectile comes out when you press fire, for example.[img]/i/smilies/16x16_smiley-surprised.gif[/img]

Very high pings (above 500) indicate either a distant server, or that your network connection is saturated (in which case you should reduce your netspeed as described above).

You will very rarely see unordered packets. These have the same effect as lost packets, since they have to be thrown away. Packet loss of more than 10% (divide the packetloss + unordered total number by the packets number) can cause severe degradation of the connection. This is a network issue - there isn't anything you can do about it except connect to a different server.

The number of bytes in and out will typically be significantly lower than the speed (your max connection speed) unless you have a very low netspeed selected (for example a modem). However, they should always be over 1000 bytes/second. If not , this may indicate a problem with the server (unless its a very quiet server with no action).

Typing stat net again at the console will make the network statistics display go away.

We've also seen this advice posted on the UT2003 forums, to address problems with very high (999) pings:

In Windows, go to Start > control panel > network connections >

Now here you should see

- Client for Microsoft Networks
- File & Printer sharing
- QoS Packet Scheduler
- Internet Protocal (TCP/IP)

Click on QoS Packet Scheduler and click "remove". Then reboot and play.

As you can read from the above text trigger lag can also be present in UT2003.

My trigger lag is reduced by 99.9% and RvS is sweet again.[img]/i/smilies/16x16_smiley-very-happy.gif[/img]




Cheers TT

OS: Windows XP Professional SP1 DX 9.0a
CPU: Athlon XP 2400+
Motherboard: ASUS A7N8X
RAM: Corsair CAS 2 512MB PC2700 DDR
Video Card: ATI Radeon 9700 Pro Rev 3.0 Omegadive Modified CAT 3.4
Sound Card: Sound Blaster Audigy : aud_betadrv_030417
Mouse: Logitech MX700 : Mouseware 9.76

[XyZspineZyX]

how the hell did you find all that out?

[XyZspineZyX]

never mind, i dint rEd the 1st sentence.

[XyZspineZyX]

hmm interesting info,... ill have to check this out

thanks

========================================
---]>Ravenshield - TEAM WAR<[--
http://www.rakkasanwarriors.com

[XyZspineZyX]

A small update.

For some strange reason RvS keeps resetting my netspeed to 5000 in Raveshield.ini [img]/i/smilies/16x16_smiley-surprised.gif[/img]

So now I have changed it back to 10000, and made Ravenshield.ini Read Only[img]/i/smilies/16x16_smiley-mad.gif[/img]

[Engine.Player]
ConfiguredInternetSpeed=10000




Cheers TT

OS: Windows XP Professional SP1 DX 9.0a
CPU: Athlon XP 2400+
Motherboard: ASUS A7N8X
RAM: Corsair CAS 2 512MB PC2700 DDR
Video Card: ATI Radeon 9700 Pro Rev 3.0 Omegadive Modified CAT 3.4
Sound Card: Sound Blaster Audigy : aud_betadrv_030417
Mouse: Logitech MX700 : Mouseware 9.76

[XyZspineZyX]

Please submit a link as to where I can download the Omega Drivers specified in your signature.

Edit: I found the Omega Drivers.

I'm still in doubt as to whether or not I should download one of the BIOS Updates for my ATI Radeon 9800 Pro 128MB and wich one to use!

I'd also like to know where you found the drivers for your Creative Audigy card, I've search on their homepage but to no prevail.

Message Edited on 07/14/0312:07AM by DNW2279

[XyZspineZyX]

hi, my friend nitojon showed me your 1000 ping resolve, but how do ya sort this with Nortons firewall ? & surely everyone who play doesn't turn their firewall OFF. If they do then why have one? Who knows who's looking in their PC's

[XyZspineZyX]

This stuff works 100%

First I tried the top part, lowering only the % to 0 but that did not help at all.

So I just simply uninstalled teh Q&S feature from my network and voila!


Rig:
Using WinXP on:
ASUS P4XP-X MoBo with 533Mhz FSB Using SoundMAX AC-97 Dolby Digital Onboard sound (5.1).
P4/Celeron 1.7 Ghz CPU
256MB DDR Samsung PC-266 Ram
GeForce 4 MX440 SE AGP8x With 64 MB DDR
Sony VAIO USB Mouse

[XyZspineZyX]

this doesnt help...

i got into a server, 30 ping... 30!!!!!!1 wooo wow...

same trigger lag as id get if i had a 200 ping

so bah, im SO lookin forward to 1.4 which says "REMOVAL OF TRIGGER LAG" so bring it on =D