![]() |
|
|
|
#1
|
|||
|
|||
|
Cheers AndyJW, thats a relief! Sounds like the problem and reason is 'ping'. I always check the 'brief' and make sure that my ac has correct markings, weapons loadout, etc - this particular server didn't specify any conditions. So once kicked you can never rejoin that server?
Last edited by SEE; 06-07-2010 at 05:42 PM. |
|
#2
|
|||
|
|||
|
You should be able to rejoin at some point - again, if the server has a forum, I'd take a look there - it may be an hour or two. Meanwhile, a few questions:
(a) Which server? (b) Where are you based (country)? (c) If you run this: http://www.pingtest.net/, what results do you get? (d) Are you using WiFi to connect to the net, or a cable? (e) Are you sharing your connection with anyone? This might give a clue as to the problem. |
|
#3
|
|||
|
|||
|
Once inside the Server and once in the cockpit on the tarmac, press "S" key and you can see your ping value.
This is the stock key to show the list of players and statistics, their pings (in miliseconds) and points. If you can't see anything, you'll have to go into the "Controls" section and configure the key for "Online Rating" in the "MISC" area. This is the real ping you have against the Server in that moment. Sometimes, a high ping can be caused not by yourself but simply if the Server has not a good connection, there too many people connected, or just if the Server is on the other side of the World ! PD: and do not forget , when going on line, to close any other program in your PC which can be using part of your Internet connection like P2P programs, etc. It is advisable to leave all our bandwith for IL-2 and related programs as Teamspeak, HL, etc. EDIT: If you want to know who is causing the message "Cheating has been detected!" to show, go to the game's folder, then subfolder "i18n", and open with Notepad the file "netmessages.properties". Look at the beginning of the file for the lines: user_cheating1 cheating has been detected user_cheating2 cheating has been detected user_cheating3 cheating has been detected (I am not sure about the exact build of these phrases in the stock game because I changed them long ago) and write them as : user_cheating1 {0} is causing lag! user_cheating2 {0} is causing lag again! user_cheating3 {0} is causing lag 3 times! save the file, and you'be able to see the name of the pilot who is causing lag. Of course keep a safe copy of the stock file "netmessages.properties" before modifying it in case of any problem. Last edited by FAE_Cazador; 06-07-2010 at 10:25 PM. |
|
#4
|
|||
|
|||
|
Thanks for all the replies and info, (so much to learn- phew!).
In reply to AnndyJW questions:- The server was SD_TotalWar I'm in the uK I use cable to my router not Wi fi and no other programs were running other than HL and my Saitek flightstick software profile. I will check the ping and take a peek at the files mentioned. Thanks guys! |
|
#5
|
|||
|
|||
|
Thanks, SEE.
HL gives me a ping of 48, according to the server selection screen, and I'm UK based too. That should be fine. If the ping is erratic, rather than persistantly bad, I'd suspect a problem with the phone line, or just a crappy internet service provider (BT have a lousy reputation on this, for example). And yes, there is a lot to learn if you want to get the most out of IL-2. Don't forget you are doing it for fun though, so don't feel obliged to learn everything straight away (it can't be done, I don't think anyone knows everything anyway...) |
|
#6
|
|||
|
|||
|
It may have been a inter/squad match or even a co-op and you being kicked may be because an admin realised that you should not be there
Unfortunately not all online games are open to everyone. I am sure it is nothing you did. If it was a ping issue some servers have an auto kicks. You are normally warned repeatedly regarding your ping being too high or believe it or not, too low! |
|
#7
|
|||
|
|||
|
I doubt if that was the problem, Bobb4. SD_TotalWar looks like a furball dogfight server from the HL details. I'd hope that anyone running a closed match on HL would password protect it, or at least explain before kicking someone.
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|