Page 2 of 3
Re: Bug Reports: Dedicated Server
Posted: 16 Jan 2012, 05:21
by fastforza
Worst documentation ever. Gogo write proper documentation Xymph.
Re: Bug Reports: Dedicated Server
Posted: 16 Jan 2012, 08:16
by Xymph
fastforza wrote:Worst documentation ever. Gogo write proper documentation Xymph.
Nah, this is actually in there, you just need to read carefully.
Re: Bug Reports: Dedicated Server
Posted: 23 Jan 2012, 22:51
by w1lla
When will the first post of this topic be updated?!
There are bugs that have never been tested properly
Re: Bug Reports: Dedicated Server
Posted: 26 Jan 2012, 14:02
by xbx
Ok..
litlle by little, some of the issues get fixed:
nocturne wrote:
[*]
XMLRPC connection closed when sending data larger than 512kb. <
link >
2011-11-03
[*]
/noautoquit Command Line Parameter nonfunctional. <
link >
2011-12-22
fixed in the latest server:
http://forum.maniaplanet.com/viewtopic. ... 019#p88019
nocturne wrote:
[*]
No method to limit/disable track-included mods. <
link >
pre-TM2/MP
It is possible (and has always been) - although a bit hackish...
Doesn't
SetForcedMods(True, [{"Env" : "Canyon", "Url" : "
http://127.0.0.1/nourl"}]) or something like this
do the trick?
nocturne wrote:
[*]
Different handling of ScoreTables CustomUI than in TMF. <
link ,
link >
2011-10-13
this one should also be fixed, but it's in client. (and the latest client to be exact: you need to enable optional updates in the playerpage)
<scoretable visible="false"/> should now be like in TMN/TMF versions, no automatic display, but TAB still works.
and <manualscoretable visible="false" /> is like in the new version, forced hidden even when pressing TAB.
Re: Bug Reports: Dedicated Server
Posted: 27 Jan 2012, 10:03
by nocturne
Arg.. I apologize, guys.. I had a bit of an ISP meltdown over the last week (or two, rather).. Though I was sort of hoping one of you 'mods' would have updated the top post (really, I don't mind). Admittedly, I could have made it here sooner.. but due to my limited connection I was already absorbed with other issues.
I still have yet to test the new server version, to see whether or not the bugs have been fixed; but I'll be updating the top post momentarily to include the other reported bugs.
Re: Bug Reports: Dedicated Server
Posted: 27 Jan 2012, 10:34
by nocturne
Seems to be fixed.. redacting from the list.
xbx wrote:nocturne wrote:
[*]
No method to limit/disable track-included mods. <
link >
pre-TM2/MP
It is possible (and has always been) - although a bit hackish...
Doesn't
SetForcedMods(True, [{"Env" : "Canyon", "Url" : "
http://127.0.0.1/nourl"}]) or something like this
do the trick?
That hasn't really worked in my experience... I attempted it in TMF, though it never had any real results. Guess I need to test it more..
If it actually worked, though... we'd have additional problems, specifically those servers that run SetForcedMods in order to run server-specific ad billboards or custom round transition screens..
xbx wrote:nocturne wrote:
[*]
Different handling of ScoreTables CustomUI than in TMF. <
link ,
link >
2011-10-13
this one should also be fixed, but it's in client. (and the latest client to be exact: you need to enable optional updates in the playerpage)
<scoretable visible="false"/> should now be like in TMN/TMF versions, no automatic display, but TAB still works.
and <manualscoretable visible="false" /> is like in the new version, forced hidden even when pressing TAB.
Well, if it's fixed on the server side (or never was a server-side issue) I'll remove it from the list, but being as it's still an issue for the 99.9% of clients that haven't enabled optional updates, it should at the very least be mentioned on the client bug report thread, specifically stating that it's part of an 'optional' fix, and not actually fixed in the version being pushed to all clients. After all, us server operators work on the good graces of the 99%, not the 1% that actually know what they are doing.
Additionally.. where did
<manualscoretable visible="false" /> come from..? Is this something new? Were you planning on outlining it in any other documentation, let alone the new server feature/fix list? Reminds me of the option to disable incoherence checks in lap mode, which seemed to be intentionally buried pages deep into an antiquated server thread without any mention in the documentation.
Not to mention.. documentation.. figured that would have been the easiest problem to fix. Come on, at least put one of your SM interns on it..
Re: Bug Reports: Dedicated Server
Posted: 28 Jan 2012, 10:22
by nocturne
[where is the delete post button.. combined everything into the post below]
Re: Bug Reports: Dedicated Server
Posted: 28 Jan 2012, 10:50
by nocturne
4lturbo wrote:There is a bug in lap mode, if you are first during the race, you never know the gap between others players and you (bottom right) and if you are not first you only see players in front of you, never see the players behind you.
Sorry I've ignored this... but it seems like a client issue, which has already been reported several times in the client bugs thread.
w1lla wrote:When will the first post of this topic be updated?!
There are bugs that have never been tested properly
Again, I apologize... Between a crap server account and a shoddy ISP, I've pretty much had my hands full the last several weeks. Still trying to get everything sorted at the moment, though..
As for poorly documented bugs, please elaborate.. Anything in left in the list are glaring defects, many of which we've been suffering for ages with no recourse from Nadeo. The cache bugs, for example, are entirely too obvious -- a problem we've all faced time and time again, leading any knowledgeable server op to disable the feature entirely. The description of the 'bug' pretty much stated all of the problems (including, as you stated in a previous post, no error handling); so I'm not going to waste my time doing 'research' to clarify a fact as obvious as stating 'the sky is blue'.
Again, I understand that I may seem a bit biased (or just irritable, rather), and often genuinely off-color.. Absolutely true, which is the exact reason I've repeatedly refused becoming a moderator -- I maintain my independence purely so I can offer an unfettered opinion, calling out Nadeo for the egregious affronts they have perpetrated against this community, such as them originally using the FreeZone plugin as a method to collect completely player-specific statistics including all chat messages. Some of those here continue to rely on their relationship to various entities -- while I honestly don't care. I've been around here (TM) a lot longer than most of you guys, so I don't exactly expect you to understand my level of frustration.
PS: There are several reported 'bugs' which I have failed to add to the list.. but they honestly seem like client issues (lacking any further info), which should be posted in the aforementioned client bugs thread.
Re: Bug Reports: Dedicated Server
Posted: 06 Feb 2012, 19:25
by matrix142
I think I found a bug in the Method
GetCurrentRankingForLogin.
The situation:
Two players are on the server and one of them finished the map.
Then look at my code and at the result of it.
Code: Select all
//$PlayerFinish[1] is the playerlogin of the Player who finished the map (Return of the Callback PlayerFinish)
//Then I call the method to get the current ranking for the specified login
$this->instance()->client->query('GetCurrentRankingForLogin', $PlayerFinish[1]);
$current_ranking = $this->instance()->client->getResponse();
//Now I print the login and the array with the data of the method
echo $PlayerFinish[1];
print_r($current_ranking);
Now look here:
Player1
Array
(
[0] => Array
(
[Login] => Player2
[NickName] => Player2
[PlayerId] => 237
[Rank] => 2
[BestTime] => -1
[BestCheckpoints] => Array
(
)
[Score] => 0
[NbrLapsFinished] => 0
[LadderScore] => 0
)
)
First it says that the login ($PlayerFinish[1]) is "Player1". This is the true login from the player who finished the map.
But in the print of the array it returns the data of the other Player who is currently on the server.
Re: Bug Reports: Dedicated Server
Posted: 12 Feb 2012, 20:51
by nocturne
I haven't experienced that... I assume you're building an array of finished players, in which case.. are you sure you shouldn't be using $PlayerFinish[0] instead of $PlayerFinish[1]..?