no se porque pero a mi me apsa lo mismo incluso teniendo los puertos abiertos. pero weno etos son:
Los puertos UDP y TCP a abrir en el router son 2 UDP y 3 TCP:
34297 / UDP
34397 / UDP y TCP
34447 y 34496 / TCP
y te dejo un manual que tenemos:
F1 Challenge 99-02
Online Multiplayer Guide
One of the most important aspects in F1 Challenge (F1C) that has been almost completely overhauled from F12K2 is the multiplayer code. In this short guide I would like to first describe the major differences between F12K2 and F1C netcode. I will then go over the multiplayer parameters in the plr file, explain what they mean and how to set them in order to unleash the full potential of F1C's new netcode.
The main weakness of F12K2 netcode is the inefficient bandwidth usage of the server (the upload speed of the server). For example, at a data rate of 12, a single player requires ~10Kbps (Kbit per second). If we run a session with 4 clients – the server will send ~40Kbps (4*10) to each client. Hence, for a session of 4 clients at a data rate of 12 the server will send ~160Kbps (4x40). In general, the required bandwidth for a session is equal to the number of players squared multiplied by the bandwidth of a single client (10Kbps in our example). You can now see how quickly bandwidth runs out as the number of clients' increases. For example – 4 clients requires ~160Kbps, if we now add 1 more client, we will need 250Kbps (5x5x10). If we double the amount of clients from 4 to 8 the needed bandwidth will jump from 160Kbps to 640Kbps!!
The second main problem in F12K2 netcode occurs when the load of the server exceeds its bandwidth. For example, when a server that has a 500Kbps upload speed host a session with 8 clients which require 640Kbps (at a data rate of 12). As a result, the whole session “explodes”, i.e. all the cars will badly warp and quality will drop significantly.
With the introduction of the throttling code in F1C, all of these problems are now in the past. The throttling code introduces a significant leap forward to the multiplayer experience, as it is much more advanced and “smarter” than F12K2 code in many aspects. Among many improvements here are the most significant ones:
a) The session will never “explode” – the code will always use the bandwidth available to the server and divide it into the clients. If there is not enough bandwidth to accommodate all of the clients at the defined data rate, the code will throttle down the data rate and reduce packet size to a value that is manageable by the server. In addition, if a client does not have enough bandwidth, the server will throttle down the amount of data sent to this particular client. This will enable players with sub-broadband connection to participate in larger sessions.
b) Efficient bandwidth management - there is really no need to render all of the cars at the same data rate (like in F12K2). For example, if there are 4 cars running on the other side of the track that you can't even see, F12K2 netcode will still render them at the full data rate taking away precious bandwidth for no real reason. The new code will throttle down the data rate based on the distance between your car and the remaining field. Thus, cars further away from you will be rendered at a lower data rate and therefore will consume much less bandwidth.
How does all of this come to play in the real world? In our testing we were able to run a session with 10 players on a 300Kbps server with overall better quality than F12K2!! We don't think that 10 is the upper limit, but due to a limited number of available beta testers at that time, we could not try a larger number of players. Furthermore, one of the clients was on a sub 56K modem connection!! Obviously he does not have enough bandwidth to transmit and receive data at high rates – but it was certainly playable. In F12K2 a client on 56K connection could only dream of participating in a 10 player session...
One has to remember though, that since the session will never “explode” as the number of clients increases, there is a tradeoff. The tradeoff is a reduced data rate that would be most obvious at the start of the race – when the field is heavily packed. You will have to experiment and determine your personal compromise between acceptable quality and field size for your specific network performances, since quality is very subjective...
The new code will also affect replay quality. As mentioned above, at the clients end, various cars will be rendered at different data rates, based on their distance to the client car. This will result in a low quality replay when watching those cars in the replay. Only the server will have the complete data for the full field and thus a high quality replay for all clients.
Finally, from a bandwidth stand point – I think that a full grid is at last a reality for powerful servers (T1 or even some more powerful ADSL servers). In my opinion, the current limiting factor for a session size is frame rate – both at the clients and especially at the server end. You really want to make sure that at any given time frame rate will not drop below 30, as this will cause glitches in the session quality. Based on your computer system strength, you will have to adjust (if at all) your graphic settings accordingly so that frame rate will always remain above 30. I think a good idea would be to create 2 player profiles – one for offline and one for online with a reduced graphic setting (if needed).
The plr file multiplayer options parameters
The new throttling netcode comes with several new parameters under the Multiplayer Options section in the plr file. Let's go over the important ones:
* Throttling=”0” – This is the heart and soul of the new netcode. This parameter will be enabled as a default, make sure it is indeed set to 1. Note: this parameter is only effective when you host. If you join a server that uses the throttling code, as a result you will get throttled data even if throttling is disabled at your end.
* Throttle upstream override=”-1” This is where you tell the code your server upload bandwidth. Based on this number the code will calculate the available bandwidth it has for each client, and when it needs to start throttling down data. I suggest you enter your “real world” bandwidth (in contrast to your ISP's “advertised” number), as this is your real bandwidth. There are several good websites out there that will measure it for you (for example
http://www.pcpitstop.com/internet/BandwidthUp.asp ). If the test result showed you have an upload speed of 280Kbps, your plr should look like this: Throttle upstream override = “280” .
* Collision Threshold=”0.300” – If the latency of a client is higher than this value (current setting 300 msec) collision will be disabled for that particular client, and as long as latency is at or above this value, collision will remain disabled. The effect will be that this particular car will not collide with other cars, and will be able to drive through other cars. You should adjust this value based on the quality of your connection and the typical latency values in your sessions. For example, if you run a session on a LAN network – you should decrease this value, if however, normally you get latencies higher than 300 msec – you should increase this value or car-car collisions will never occur. Note: As latency increases, cars positioning accuracy decreases and warping increases which may yield false collisions.
* ForcePhysics=”16” – The force physics parameter gets pushed onto the client when they join a game, so if the host has the value of 16 set in their player file, the collision threshold of the session (i.e. the servers setting) will be set and enforced on all clients. For example, if you wish to force collision threshold as well as half-rate physics you should set this value to 20 (16+4). I recommend that the server will always force collision threshold as neglecting to do so may provide an opportunity for cheating. If the server does not force collision threshold, each client can set his own threshold. A client can now set an extremely low collision threshold (for example 0.025). Unless you are running on LAN, latency will never be lower than 25 msec, and as a result, this player will be completely resistant to car-car collisions.
The next set of parameters modifies the BoneSpring smoothing characteristics. The BoneSpring is used to smooth cars positioning on the track. The rule of thumb is to set a stiff spring (high spring constant) for high data rate and low latency and soft spring (low spring constant) for low data rate and high latency. In addition, testing showed that the BoneSpring smoothing has a negative effect at relatively low latencies. Therefore a set of parameters is needed to generate optimal BoneSpring smoothing under different conditions:
* BoneSpring Threshold=”0.15000” – As mention above, BoneSpring smoothing should be disabled under low latencies. With this setting the BoneSpring smoothing is disabled when latency is below 150 msec.
* BoneSpring Min Constant=”25.000” and BoneSpring Max Constant=”109.000” – These values should be modified if you changed the BoneSpring Threshold and Collision Threshold values. The BoneSpring stiffness is variable and will be changed based on the client latency in the following way: if latency is below the BoneSpring threshold – the spring is disabled. When latency is at the threshold, the spring is as stiff as it can get determined by the BoneSpring max constant . As latency increases the spring becomes softer and softer. At latencies equal and above collision threshold the spring get as soft as it can get determined by the BoneSpring min constant . For example, if you reduced the BoneSpring Threshold, you may want to increase the BoneSpring Max constant.
Extra goodies
Cheating in multiplayer
– This area has been significantly improved in F1C. First, each time you hope into your car, the game checks and verifies that the relevant files (*.exe, terrain.ini and HDV) are authentic. If the game detects that a player modified one of those files, a mismatch error message will be sent to the server as well as to the rest of the players. Further, the game will always compare those crucial files to those found on the server. This will finally solve problems most online leagues encounter. Let me explain: many online leagues dictate single car physics for all cars or allow each player to choose any car physics (*.hdv file) as long as it is from the 11 authentic teams. As a result, in F12K2 each time those players joined a race the server showed a mismatch error, and it was impossible to verify if their hdv file is genuine. In F1C, if the server has the hdv file that the player is supposed to have (for example the server will have the Williams hdv file as well as the engine file * ) there will be no mismatch error. This applies also to other files such as the terrain.ini file – if a group of drivers wish to play with pre-determined modified parameters – they can now enforce that only those changes will be used. Again, if the server's modified terrain.ini file matches those of the players – no mismatch error! This will be particularly useful for finally having cheating free online races with various mods!
* In F1C, to drive a car with a different physics (for example: a Minardi with the Williams physics) one has to copy the engine file from the Williams to the Minardi folder in addition to the *.hdv file.
Name tags and latency – If you hit the tab key (you can assign any key you wish including buttons on your controller), each car will be shown with the player name and the latency between you and this particular player. Unfortunately, enabling this mode has a serious impact on frame rate when there are large amount of players in the session. When a player experiences serious packet loss – a blinking disconnected symbol will appear above his car – indicating that there is currently a problem with his connection. This is an extremely useful feature that helps identify the source of the problem when experiencing warping.
Password protected session – You can now create a password protected game which will be announced on GameSpy, but only those who have the password can join your session. There is no need to share your IP address and remember IP's in order to join private games!
To create a password protected session click on the blank area under the game name entry, and type the password in the new text entry area.
Formation and reconnaissance lap – Yes - we now have it fully functional in multiplayer!! (formation lap is now functional in offline races) To enable it make sure you have the following entries in your plr file: MULTI Reconnaissance="1" and MULTI Formation Lap="1" . You also need to set the following parameters to your liking: Recon Pit Open="300.00000" , Recon Pit Closed="150.00000" and Recon Timer="1" . These values are well explained in the plr file. This is how it works: When you move to the race session, you will start from your pit stall. You can go out and drive around the track, but remember: don't cross the start/finish line since the pit-girls are on the track as well as other cars that may be waiting on their grid position. To run another lap you must drive through the pits. Remember to leave the pits before they are closed, and park your car in the appropriate grid position (based on your qualification). A pit girl holding a flag with your car number and your national flag will help you identify your position. You will then get a message to start the formation lap. After you complete the formation lap park your car in your grid position. If your car is not properly aligned or in the wrong position you will get a message indicating so and the race will not start. Once all of the cars are aligned properly the race will start. Alternatively, if the server at any time hits the space bar the cars will be placed in their grid position and the race will start.
![[mad]](/images/smilies/nuevos/miedo.gif "loco")
![[Ooooo]](/images/smilies/nuevos/sorprendido_ani1.gif "Oooooo")
![[oki]](/images/smilies/net_thumbsup.gif "Ok!")
![[tomaaa]](/images/smilies/nuevos2/tomaa.gif "toma")
![[bye]](/images/smilies/nuevos2/adio.gif "adios")
![[plas]](/images/smilies/aplauso.gif "Aplausos")
![[idea]](/images/smilies/nuevos2/idea.gif "idea")
![[rtfm]](/images/smilies/rtfm.gif "Lee!")
![[fies]](/images/smilies/nuevos2/fiesta.gif "fiesta")
![[360º]](/images/smilies/nuevos/vueltas.gif "como la niña del exorcista")
![[ok]](/images/smilies/nuevos2/okis.gif "ok")
![[jaja]](/images/smilies/nuevos2/otrasonrisa.gif "otra sonrisa")
![[toctoc]](/images/smilies/nuevos2/rompiendo.gif "machacando")
![[sonrisa]](/images/smilies/nuevos/risa_ani1.gif "sonrisa")
jeje son solo sugerencias 
![[buuuaaaa]](/images/smilies/nuevos/triste_ani3.gif "a lágrima viva")
![[agggtt]](/images/smilies/nuevos2/infeliz.gif "uf")
pero weno
![[decaio]](/images/smilies/nuevos2/decaido.gif "decaido")
