CVS test server
- Lucifer
- Project Developer
- Posts: 8640
- Joined: Sun Aug 15, 2004 3:32 pm
- Location: Republic of Texas
- Contact:
After spidey left, I saw in my console "Spidey has joined Team Blue". When we spawned, I saw Player 1.
I wish I had a recording, if it's going to be a client side bug.
So, here's what I saw (with the irrelevant stuff that I don't remember not included)
Spidey has left Team Blue.
Spidey has left the game.
Spidey has joined Team Blue.
*round starts, I see Player 1 and no spidey*
I think I only saw Player 1 has joined the game, but nothing about team. If your logs and stuff don't show it, then we should probably mark it as "Mysterious thing Lucifer saw that was probably his imagination".
I wish I had a recording, if it's going to be a client side bug.
So, here's what I saw (with the irrelevant stuff that I don't remember not included)
Spidey has left Team Blue.
Spidey has left the game.
Spidey has joined Team Blue.
*round starts, I see Player 1 and no spidey*
I think I only saw Player 1 has joined the game, but nothing about team. If your logs and stuff don't show it, then we should probably mark it as "Mysterious thing Lucifer saw that was probably his imagination".
Code: Select all
[1] --> : BUG I have a blank name
Code: Select all
[15] nemostultae: BUG I just kicked mom off gold (maybe)
Code: Select all
[9] mhoese: lovely, i can run through walls
[9] mhoese: two times
[9] mhoese: lol
[4] joda.bot: BUG mhoese thought he drive through walls
I'll be testing the new "Time out" mechanism on the next server restart. The round will not start until all players have finished chatting. Within reasonable bounds, of course. I'll add code to filter out permanent chatbots later.
I found 2 bugs... both client side.
1) New glancing mode does not work on VERY fast servers,
the camera does not show the cycle anymore.
Failed to record this bug with latest cvs (except that the camera zooms out really far, on "Global Network Spacezone"). Guess I had a bad cvs-snapshot build I used previously.
The camera zoom out might be a WONT_FIX .
2) If I switch between fullscreen mode on fortress I get a huge amout lag of afterwards (this might be correct as it takes sometime to switch).
But I guess it got worse since beta4. Can you disable lag measurement right before switching and turn it back on afterwards ? Or just damp it's impact on the lag prediction function as it's only temporary.
Recording attached. (close to server restart )
Windows Code fixes:
1) New glancing mode does not work on VERY fast servers,
the camera does not show the cycle anymore.
Failed to record this bug with latest cvs (except that the camera zooms out really far, on "Global Network Spacezone"). Guess I had a bad cvs-snapshot build I used previously.
The camera zoom out might be a WONT_FIX .
2) If I switch between fullscreen mode on fortress I get a huge amout lag of afterwards (this might be correct as it takes sometime to switch).
But I guess it got worse since beta4. Can you disable lag measurement right before switching and turn it back on afterwards ? Or just damp it's impact on the lag prediction function as it's only temporary.
Recording attached. (close to server restart )
Windows Code fixes:
Already fixed while testing: Changed visibility of eVoteItem::items_ to protected.eVoter.cpp:446 DoGetDetails() wrote: operator &&' is ambiguousCode: Select all
if ( se_votingPrivacy <= -1 && bool(suggestor_) )
- Attachments
-
- armagetronad.rec.collection.tar.gz
- 2 "BUG" on CVS Testserver Fortress (shortly before reboot :P)
+ extreme camera zoom out on network spacezone. - (929.48 KiB) Downloaded 93 times
Thats correct, right after that i told nemo the same thing.z-man wrote:As far as I can tell from the logs, mom issued a team change wish right before nemo.Code: Select all
[15] nemostultae: BUG I just kicked mom off gold (maybe)
I played tonight, and it can get a little annoying. Some players may just turn on chat just to annoy people and make them wait.z-man wrote:I'll be testing the new "Time out" mechanism on the next server restart. The round will not start until all players have finished chatting. Within reasonable bounds, of course. I'll add code to filter out permanent chatbots later.
You can also create a little spam by repeatedly going in and out of "chat" mode (the fastest method is to press the escape key), because the server reports how much time is left each time you do it. This covers up any real chat that may have happened during that time. It is really annoying when multiple players do it.
Code: Select all
[4] lag: BUG: Something is wrong with the code that gives points for deaths
[4] lag: I am dying on people's walls and they are not getting credit
The change also means that now, teamkills later in the round are recognized with better precision. Fight a little with the enemy, then crash into the front of a teammate's wall to find out.
Code: Select all
[2] joda.bot: BUG did not see death message for hyrulian
bug report: "netowork error"
Tonight I have been forcibly disconnected from the server rather frequently (Message: "netowork error" [1]. Immediately before that, the console writes "meriton leaves meriton" a few dozen times). Every time I disconnected from the server this evening after 11 pm CET it was due to this bug. I'll try again now, hopefully it'll let me play for while
[1] The typo is quoted from screen.
[1] The typo is quoted from screen.
meriton: Could you try to make a clientside recording? The client seems to get an invalid packet from the server (the typo localizes the code quite well, it's in Cheater() in nNetObject.cpp), but of course, the server does not know anything about it.
The message flooding is an unrelated cleanup bug, I fixed something like that some days back. It also happens when you hit the boss key.
The server seems to send a false rename message. I'll dig deeper. Edit: the name doublette detection was done in a wrong place where it was possible to bypass it temporarily. Will be fixed on the next restart.
The message flooding is an unrelated cleanup bug, I fixed something like that some days back. It also happens when you hit the boss key.
Code: Select all
[2] lag: BUG: Two users with same name, the '2' doesn't show up in Player Police
Code: Select all
[0] joda.bot committed suicide.
...
[6] joda.bot: BUG joda does not know how to suicide
Code: Select all
[9] received logout from 9.
[9] joda.bot left the game.
[9] joda.bot leaves Team gold.
[9] Killing user 9, ping 0.0634694.
[9] Received login from 84.61.3.156:6212 via socket *.*.*.*:4536.
[9] New user: 9
[9] joda.bot entered the game.
[9] joda.bot plays for Team gold.
[9] joda.bot: gah hate does network errors
[9] joda.bot: BUG network timeout error