Post by (HOB)Wolfage on Aug 11, 2024 9:29:41 GMT -8
Some of you still don't know so here is again. Because the game was released in 2002 and internet connections where not as they are now , It's best you change few things. I will also try to share some information that some of you may not have heard of. But the players you think are cheating, they definitely know. So before complain check it your settings.
You may still get a high ping but the quality will improve. That's why some players better with higher ping cause they get a really smooth 'ride'. So take some time and fix it your settings.
1. Game rate
- The most important setting is the rate, it will improve your connection ( ping ).
- When you installed the game this feature is set to 2500 as standard rate.
- This setting is calculated for a 56 K connection .
How you change this ?
- You can change this directly in your sof2mp.cfg ( located in Base / Mp ).
- Open the sof2mp.cfg with a text editor and find the line : seta rate "2500"
change the 2500 to a higher number.
- Or you change it in the game itself by opening the console (hit the '~' key or the one directly under the 'Esc.' key on your keyboard). and write : rate 15000
Note:
1000=~1KB/s.
Broadband and cable users recommended to 25000.
The best rate settings are in a range from 15000 to 25000.
If you have low rate but you have broadband or cable internet connection you might have lag.
Also if players using a low rate, their movement will be very strange (possibly forces some warping)
which makes them very hard to hit.
2 cl_maxpackets
cl_maxpackets sets how many packets are sent to client (yourself).
Usage:
/seta cl_maxpackets 100
Values: 15 to 100
Default: 30
Note:
If your cl_maxpackets are higher, more data is sent to you as the client and when these packets are
smaller they arrive more frequently to you. If you see more data about your environment,
you can decide more precise how or where to move.
Players on a low rate setting should have their cl_maxpackets setting lower.
But, because the packets go both ways (to client and to the server),
players on low maxpackets might have problems, because other players will find this player’s
movements weird which can make them hard to shoot and also this player can see other players movement weird.
3. Snaps
Snaps determines how many times the server sends you updates
(snapshots) per second about the game state.
If the default value for snaps is not appropriate for you, you can increase/decrease anytime
the amount of the updates sent to the Client (for yourself).
If your updates are poor just lower your snaps value (view lagometer to check your updates). More info at bottom section.
A good value to begin with is 30.
- This feature improves your connection as well.
- The standard snaps setting by the game is 20.
- You can change this in the range from 20 to 50 ( Do not go higher then 50 ).
- You can change this directly in the sof2mp.cfg ( same way as for the rate ).
- Or you can change this in the games console by writing : seta snaps 50
4. Com_maxfps XX
FPS seems to be the most important to reduce, you have to do this to decrease the demand the system's putting on your connection for the data
required to render at such high (off-line) fps rates. If you don't do this then your connection will keep locking up and choking as it
can't get enough data from the server to render the relative position of everything going on in a
online game - which is why players sometimes seem to 'jump/stutter' across your screen
(it's like trying to suckthe last drops of a cola through a straw, most of the time you hit air - packet loss - and occasionally
you hit cola - data). See the table below about the best rates/connection speeds.
- You can see what fps you reach while playing.
How ?
Open the gamesconsole (hit the '~' key or the one directly under the 'Esc.' key on your keyboard).
Write : cg_drawfps 1
On the right side top of your screen will appear the fps you have.
- You can set this in the main game settings menu from the game, but here the maximum
you can set is 125. ( you find this under the icon network settings ).
- You can change this in the game as well by opening the console. (hit the '~' key or the one directly under the 'Esc.' key on your keyboard).
and write : com_maxfps x ( x stands for a number )
- Where the x stands you can go in a range from 125 to 333. ( 333 is enough )
- You can set this higher if you want but this depents what videocard you have.
Soldier of Fortune was built around a modified version of the Quake II engine. In quake engine based games there are specific “key” fps steps exist: 43, 76, 125, 333.
If you set on one of these values, you somehow can move faster or jump higher, but you really cannot observe this as much.
Here is some idea for ideal settings:
LAN **
seta cl_maxpackets "100"
seta cl_packetdup "0"
* seta snaps "40"
seta rate "25000"
ADSL / Cable / Wireless **
seta cl_maxpackets "60"
seta cl_packetdup "1"
* seta snaps "40"
seta rate "25000"
ISDN Bonded **
seta cl_maxpackets "60"
seta cl_packetdup "1"
* seta snaps "40"
seta rate "(See Table Below)"
128000 BPS: seta rate "14000"
112000 BPS: seta rate "12250"
ISDN Single **
seta cl_maxpackets "60"
seta cl_packetdup "1"
* seta snaps "40"
seta rate "(See Table Below)"
64000 BPS: seta rate "7000"
56000 BPS: seta rate "6200"
Other settings maybe someone still need it:
cl_packetdup This setting determines if duplicate commands are sent, range is 1 to 5 and is 1 as default. if a packet gets lost then a 'backup' command may still be received. Set to 1 as default which is recommended if you have packet loss. If you have an excellent connection with very little or no packetloss at all then this could be set to 0 and cl_maxpackets possibly raised. However, as with all settings experiment to see which is best suited for your connection - See cg_lagometer for a guide on how to determine if you need to adjust this setting.
cg_lagometer Set this to 1 to monitor your connection - The first line is related to your graphics card updating displayed frames in time with received gameworld updates from the server. It will be blue if frames are being rendered in time with the world updates. If it has a lot of yellow then gameworld updates are not being displayed and are being dropped. In this case reduce your snaps or tweak your visual settings to raise your average framerate so it is always above your snaps setting. Another option is to increase cl_timenudge by a very small value, note that if you are using a negative value for cl_timenudge the first line of the graph may be mostly yellow.
The second line is netgraph in that green means packets are being received okay, yellow that capping is causing your client to reject packets and red that the packet was lost. In the case of yellow increase your rate or try lowering your snaps. If you have a lot of red then change ISP 😅or server.😒 If you have to play on the server or use the ISP then make sure that your cl_packetdup is set to 1 and try adjusting snaps and cl_maxpackets to compensate for the lost packets.
You may still get a high ping but the quality will improve. That's why some players better with higher ping cause they get a really smooth 'ride'. So take some time and fix it your settings.
1. Game rate
- The most important setting is the rate, it will improve your connection ( ping ).
- When you installed the game this feature is set to 2500 as standard rate.
- This setting is calculated for a 56 K connection .
How you change this ?
- You can change this directly in your sof2mp.cfg ( located in Base / Mp ).
- Open the sof2mp.cfg with a text editor and find the line : seta rate "2500"
change the 2500 to a higher number.
- Or you change it in the game itself by opening the console (hit the '~' key or the one directly under the 'Esc.' key on your keyboard). and write : rate 15000
Note:
1000=~1KB/s.
Broadband and cable users recommended to 25000.
The best rate settings are in a range from 15000 to 25000.
If you have low rate but you have broadband or cable internet connection you might have lag.
Also if players using a low rate, their movement will be very strange (possibly forces some warping)
which makes them very hard to hit.
2 cl_maxpackets
cl_maxpackets sets how many packets are sent to client (yourself).
Usage:
/seta cl_maxpackets 100
Values: 15 to 100
Default: 30
Note:
If your cl_maxpackets are higher, more data is sent to you as the client and when these packets are
smaller they arrive more frequently to you. If you see more data about your environment,
you can decide more precise how or where to move.
Players on a low rate setting should have their cl_maxpackets setting lower.
But, because the packets go both ways (to client and to the server),
players on low maxpackets might have problems, because other players will find this player’s
movements weird which can make them hard to shoot and also this player can see other players movement weird.
3. Snaps
Snaps determines how many times the server sends you updates
(snapshots) per second about the game state.
If the default value for snaps is not appropriate for you, you can increase/decrease anytime
the amount of the updates sent to the Client (for yourself).
If your updates are poor just lower your snaps value (view lagometer to check your updates). More info at bottom section.
A good value to begin with is 30.
- This feature improves your connection as well.
- The standard snaps setting by the game is 20.
- You can change this in the range from 20 to 50 ( Do not go higher then 50 ).
- You can change this directly in the sof2mp.cfg ( same way as for the rate ).
- Or you can change this in the games console by writing : seta snaps 50
4. Com_maxfps XX
FPS seems to be the most important to reduce, you have to do this to decrease the demand the system's putting on your connection for the data
required to render at such high (off-line) fps rates. If you don't do this then your connection will keep locking up and choking as it
can't get enough data from the server to render the relative position of everything going on in a
online game - which is why players sometimes seem to 'jump/stutter' across your screen
(it's like trying to suckthe last drops of a cola through a straw, most of the time you hit air - packet loss - and occasionally
you hit cola - data). See the table below about the best rates/connection speeds.
- You can see what fps you reach while playing.
How ?
Open the gamesconsole (hit the '~' key or the one directly under the 'Esc.' key on your keyboard).
Write : cg_drawfps 1
On the right side top of your screen will appear the fps you have.
- You can set this in the main game settings menu from the game, but here the maximum
you can set is 125. ( you find this under the icon network settings ).
- You can change this in the game as well by opening the console. (hit the '~' key or the one directly under the 'Esc.' key on your keyboard).
and write : com_maxfps x ( x stands for a number )
- Where the x stands you can go in a range from 125 to 333. ( 333 is enough )
- You can set this higher if you want but this depents what videocard you have.
Soldier of Fortune was built around a modified version of the Quake II engine. In quake engine based games there are specific “key” fps steps exist: 43, 76, 125, 333.
If you set on one of these values, you somehow can move faster or jump higher, but you really cannot observe this as much.
Here is some idea for ideal settings:
LAN **
seta cl_maxpackets "100"
seta cl_packetdup "0"
* seta snaps "40"
seta rate "25000"
ADSL / Cable / Wireless **
seta cl_maxpackets "60"
seta cl_packetdup "1"
* seta snaps "40"
seta rate "25000"
ISDN Bonded **
seta cl_maxpackets "60"
seta cl_packetdup "1"
* seta snaps "40"
seta rate "(See Table Below)"
128000 BPS: seta rate "14000"
112000 BPS: seta rate "12250"
ISDN Single **
seta cl_maxpackets "60"
seta cl_packetdup "1"
* seta snaps "40"
seta rate "(See Table Below)"
64000 BPS: seta rate "7000"
56000 BPS: seta rate "6200"
Other settings maybe someone still need it:
cl_packetdup This setting determines if duplicate commands are sent, range is 1 to 5 and is 1 as default. if a packet gets lost then a 'backup' command may still be received. Set to 1 as default which is recommended if you have packet loss. If you have an excellent connection with very little or no packetloss at all then this could be set to 0 and cl_maxpackets possibly raised. However, as with all settings experiment to see which is best suited for your connection - See cg_lagometer for a guide on how to determine if you need to adjust this setting.
cg_lagometer Set this to 1 to monitor your connection - The first line is related to your graphics card updating displayed frames in time with received gameworld updates from the server. It will be blue if frames are being rendered in time with the world updates. If it has a lot of yellow then gameworld updates are not being displayed and are being dropped. In this case reduce your snaps or tweak your visual settings to raise your average framerate so it is always above your snaps setting. Another option is to increase cl_timenudge by a very small value, note that if you are using a negative value for cl_timenudge the first line of the graph may be mostly yellow.
The second line is netgraph in that green means packets are being received okay, yellow that capping is causing your client to reject packets and red that the packet was lost. In the case of yellow increase your rate or try lowering your snaps. If you have a lot of red then change ISP 😅or server.😒 If you have to play on the server or use the ISP then make sure that your cl_packetdup is set to 1 and try adjusting snaps and cl_maxpackets to compensate for the lost packets.