Quote:
Originally Posted by wildwillie
What do you mean by "null errors" ? Like this one:
Code:
[07:17:17] =================================================
[07:17:17] System.NullReferenceException: Object reference not set to an instance of an object.
[07:17:17] at LYqSxVUb301LL4jGavw.ZwH7F0UuLB23PuC9oo5.dU5QQyWtLl(r07HI3T3F1600G48A6t , GFLK6d8aKf0VrJKYuLT )
[07:17:17] at Nxt3iJYHuBeNh7InIPp.SiM9x2YyQLXTcHxQFWH.hrLQbkJSkFm(ZwH7F0UuLB23PuC9oo5 , Int32 )
[07:17:17] =================================================
I started our server last night at 9:30 and it is still running without problem.
I have 4 missions in rotation and the Dedicated server uses between 700mb and 950mb of memory.
I just found one issue I have been tracking where the player is not removed after they have disconnected. Which is why you see 85 players ingame on our stats page when it actually is only 1.
Attached is the new exe for that fix.
Also you will need to download the latest GeoCityLite.dat file from http://www.maxmind.com/app/geolitecity and unzip it to the IL2ClodCommander folder.
Willie |
That error message, is sadly normal (currently). What I'm talking about is the steam stats tracker in my sig. Sometimes you'll see a player labeled as (null). This is a player that attempted to join the server yet failed authorization. So this (null) will stay on the on the steam stats and the player will not be able to join until the server is completely restarted. So if you have a null in your listing and kept your server up 24/7 that particular player can never join again. This extra player does not show up in the console, so it's not like you could kick him out either. They are just stuck failing auth. So if you had 25 players according to steam and 1 of those being a null, your in-game server will only show 24.
That's why we restart the server at the end of each mission. We used to rotate missions, but found leaving the server up will significantly increase the amount of players that can't join (nulls) to well in the 20's in a 24 hour window. And this null thing is completely random. It's happened to the majority of players I've talked to at least 1 time.
Another reason why we really need dedi files for the server.