BUG cries on Bugfarm Fortress and Sumo

[Lackadaisical]

I dont know who they are but i remember them being one and the same person.

[Your_mom]

Code: Select all

[7] Your_mom: BUG wall phasing

Where? When? Who? A debug plot showed nothig immediately obvious.

hmm. well the other teams goalie died and someone on my team and then myself passed thru the last part of his trail before it dissapeared. i think it had to do with the 2.5 wall/grid experiment code although im not sure.

[2020]

i recently updated with rc4
and lots of strange things are happening...
to do with views

when i die
i end up in cockpit view staring at the ground...

when in fixed independent camera view
(eg when i am looking at the zone)
it changes again to the inside cockpit view of another player
whereas before
it this view wasn't tagged to the player
and so i could keep viewing it till the end...

not sure if this is a problem because i have updated
or whether it is the new version...
any suggestions for me to check
i will gladly follow

[Z-Man]

Your mom: yes, it probably has. On a production server, that option shouldn't be enabled like it is on Fortress, letting "old" clients in by overriding the compatibility check. I'll consider resetting a dead player's rubber to zero, this makes the walls have the length they appear with on the clients.

2020: Sounds like client bugs; can I have a recording? There is a neat start menu entry to generate one, just start AA with it, play, and some seconds after something strange happens, quit and send the recording here.
Or start with "armagetronad --record bug.aarec" on a command line in Unix

What version have you upgraded from? I'd like to say "strange, no changes have been made to that system since XXX"

[2020]

the rec facility is amazing!
kind of weird to see the game

here's the recording:


and i upgraded from rc3
and it is mac

[dlh]

the rec facility is amazing!
kind of weird to see the game

here's the recording:


and i upgraded from rc3
and it is mac

I remember having this error some time ago (beta1 or beta2), and then it magically went away.

[Z-Man]

A good recording, I see the effect in debug mode at about T=90s. Indeed, a change from rc3 to rc4 is responsible: when the deathcam (focussing a bit on the spot where you died) switched back to normal watching camera mode, it reset to your favorite camera mode. What I did not think about: you'd also want to reset the settings so you don't look to the floor, and maybe you don't want to switch modes at all, maybe you want to go back to your previous mode. All requires more work, so I'll revert that code.
It went unnoticed by others because you're about the only one setting the camera to internal by default

[junglehungry]

Code: Select all

[5] WalkerTexsRangr: LTTRS DONT WOR NO MOR
[5] WalkerTexsRangr: IM SRIOUS
[5] WalkerTexsRangr: RBUG LTTRS  FUCD
[5] WalkerTexsRangr: phew!
[5] WalkerTexsRangr: BUG sometimes when i'm chatting letters just disappear

That, if it's not a prank, would be a client bug and I'd need a clientside recording.

I get something similar when i accidentally hit the function key and another key (I think up-arrow) on an Apple Powerbook G4 running OSX 10.4.1 - most of the keys get different values and it becomes rather difficult to play. Remedy is hitting function key again.

[dlh]

[...]
That, if it's not a prank, would be a client bug and I'd need a clientside recording.

I get something similar when i accidentally hit the function key and another key (I think up-arrow) on an Apple Powerbook G4 running OSX 10.4.1 - most of the keys get different values and it becomes rather difficult to play. Remedy is hitting function key again.

Are you turning num lock on? If you are, it's not a bug ;)

[junglehungry]

Are you turning num lock on? If you are, it's not a bug

don't think so - it seems to be random letters as well as numbers, and I don't go anywhere near the numlock key - will shout bug if it happens again. But I'm pretty sure it something specific to my system rather than the client (let alone the server).

[Z-Man]

will shout bug if it happens again.

Don't, it's no use, it'll only save the server side recording. Please send a clientside recording instead, if the problem is anywhere on our end, only that will show it.

[gnorty]

I get something similar when i accidentally hit the function key and another key (I think up-arrow) on an Apple Powerbook G4 running OSX 10.4.1 - most of the keys get different values and it becomes rather difficult to play. Remedy is hitting function key again.

I have also had something silimar recently. I swapped servers and suddnly the direction keys stopped working. I could still access the menu as normal. It occurs to me now that maybe the client reverted to default keys, but tbh I was out of there pretty quick - those fortress guys get quite twitchy when people dont do what they expect at the startup!

[Z-Man]

Hrm. Playing back recordings currnetly breaks pretty often, most of the time right after a new client joins. Some pretty serious looking incidends are thus unanalzyable. Sorry, I'm on it. If we're lucky, fixing the bug also lets me play back the old recordings, but I wouldn't bet on that.

[Z-Man]

We're lucky The breakdown happens because on save, the highscore tables get an additional, empty entry, and during playback, they're not saved. Darn, this one was hard to find.