Bug #591

Legacy issues with vanilla 2.60

Added by Mateos about 5 years ago. Updated about 4 years ago.

Status:Fixed% Done:

100%

Priority:HighSpent time:-
Assignee:Spyhawk
Category:Client
Target version:2.74
OS: Arch:

Description

Yesterday I played a LAN using ET 2.60b, and here are the issues I encountered under the Legacy mod:
- When you set yourself ready when the map has ended, the antilag icon used to show this fact is rotated by 180°.
- The kill messages have a strange issue: in the console they’re fine, but in the game the "by" word has no space after it, and thus you have "byPlayerName" displayed instead of "by PlayerName".

Confirmed by my friend, but we use the same binaries, compiled last Sunday morning.


Related issues

Related to ET: Legacy Development - Task #849: Find a solution for mod translations Fixed 24.07.2015
Related to ET: Legacy Development - Feature #859: Implement translation/unicode support for non legacy mods New 16.08.2015
Related to ET: Legacy Development - Bug #981: Some characters don't appear in chat Confirmed 31.01.2017

Associated revisions

Revision 7bd261a4
Added by Spyhawk about 4 years ago

general: skip UTF8 on non Legacy mods, refs #591

Revision 31c06df9
Added by Spyhawk about 4 years ago

general: fixed typo in conditional statement, refs #591

History

#1 Updated by Spyhawk about 5 years ago

When you set yourself ready when the map has ended, the antilag icon used to show this fact is rotated by 180°.

Do you mean the ready icon instead?
Is it "upside down", or vertically reversed?

The kill messages have a strange issue: in the console they’re fine, but in the game the "by" word has no space after it, and thus you have "byPlayerName" displayed instead of "by PlayerName".

Are you referring to the popup message area? Or the Center printed message? (next time, a screenshot would be welcome)

#2 Updated by Mateos about 5 years ago

Yeah, I forgot to precise I meant the antilag icon used to show the ready state; Upside down.

I mean the area at the left of the screen; I can up a screen if needed.

#3 Updated by Spyhawk about 5 years ago

Mateos wrote:

I mean the area at the left of the screen; I can up a screen if needed.

Yes please.

#5 Updated by RaFaL about 5 years ago

I can’t confirm any of those bugs for me there was space between "killed by PlayerName"
I didn’t saw AntiLag Icon anywhere after map ended
The only thing I noticed it was a fucking massive FPS drop everywhere and evertime. I tested it on legacy server (debug one ) with ET 2.60b client

#6 Updated by Mateos about 5 years ago

RaFaL wrote:

I can’t confirm any of those bugs for me there was space between "killed by PlayerName"
I didn’t saw AntiLag Icon anywhere after map ended
The only thing I noticed it was a fucking massive FPS drop everywhere and evertime. I tested it on legacy server (debug one ) with ET 2.60b client

1) OK
2) Have you pressed ready so the icon appears?
3) Don’t have this issue

#7 Updated by Spyhawk about 5 years ago

I’m somewhat unable to test 2.60b client right now, as I currently only have the 64bit tools chain installed.
I’ve had a look at the code, which seems correct.

If that bug doesn’t appear on etl client and only 2.60b client, then my best bet would be that is a color code issue, since that part is different from the etl and original client (engine). Mateos, could try with some other nickname (uncolored, plain white, various colors, etc.) and report the results here?

#8 Updated by RaFaL about 5 years ago

Mateos wrote:

RaFaL wrote:

I can’t confirm any of those bugs for me there was space between "killed by PlayerName"
I didn’t saw AntiLag Icon anywhere after map ended
The only thing I noticed it was a fucking massive FPS drop everywhere and evertime. I tested it on legacy server (debug one ) with ET 2.60b client

1) OK
2) Have you pressed ready so the icon appears?
3) Don’t have this issue

2) Yes I did

#9 Updated by IR4T4 about 4 years ago

  • Target version set to 2.78

#10 Updated by IR4T4 about 4 years ago

  • Priority changed from Normal to High
  • Target version changed from 2.78 to 2.74

#11 Updated by IR4T4 about 4 years ago

- test the vanilla client & legacy mod

#12 Updated by Spyhawk about 4 years ago

  • Category set to Mod generic
  • Status changed from New to Can't reproduce
  • % Done changed from 0 to 100

Tested and cannot reproduce. Both issues are mod related anyway, using the vanilla client shouldn’t make any difference here.

#13 Updated by Spyhawk about 4 years ago

  • Status changed from Can't reproduce to Invalid

#14 Updated by IR4T4 about 4 years ago

  • Category changed from Mod generic to Client
  • Status changed from Invalid to New

Reopened.

Entering ( & sending by return) new unicode chars in intermission chat disconnect the client from 2.60 servers with error "CL_ParseServerMessage: Illegible server message X"

I can reproduce this bug with german umlaute but I think other 'special’ unicode chars of other languages have the same effect.

#15 Updated by IR4T4 about 4 years ago

  • Subject changed from Legacy mod issues under 2.60b client to Legacy issues with vanilla 2.60

#16 Updated by Spyhawk about 4 years ago

  • Status changed from New to Feedback
  • Assignee set to Spyhawk

#17 Updated by IR4T4 about 4 years ago

  • Related to Task #849: Find a solution for mod translations added

#18 Updated by IR4T4 about 4 years ago

  • Status changed from Feedback to Fixed

#19 Updated by Spyhawk about 4 years ago

  • Related to Feature #859: Implement translation/unicode support for non legacy mods added

#20 Updated by Spyhawk over 2 years ago

  • Related to Bug #981: Some characters don't appear in chat added

Also available in: Atom PDF