Page 1 of 1

[Fixed][16.05.2013] shields in extremely poor quality.

Posted: 17 May 2013, 13:09
by dreammyw0w
Hi,

Most competitive players use low settings to get an extra performance boost/fps so well yeah... so did I and I love my settings.
However now all the shields are completely blurred and this shouldnt be happening. Everything else is supercrisp and nice ( like spawns, poles, the GUI ), but shields look horrible! Clublinks are finnaly working now so it'd be cool if i could see other clans' logos or at least the default shields without the blur.

So can anyone help me or tell me what setting it is? ( Just look at the screenshots, you'll understand what I mean. )
Or maybe its a bug? I dont like changing my settings tho :/


Image

Re: shields in extremely poor quality.

Posted: 17 May 2013, 13:11
by tcq
Looks like a bug for me. Please use this sub forum to report bugs.
http://forum.maniaplanet.com/viewforum.php?f=469

Re: shields in extremely poor quality.

Posted: 17 May 2013, 13:20
by viperozza
Same happens to me since early beta stages. :teub:

Re: shields in extremely poor quality.

Posted: 17 May 2013, 13:35
by jonthekiller
It's not a bug, it's when the texture quality is in low quality.

Re: shields in extremely poor quality.

Posted: 17 May 2013, 13:58
by Omnixor
you don't say? let's make an exception for shields then, ffs. for some reason, signs in TM don't become shitty quality when textures are set on low.

Re: shields in extremely poor quality.

Posted: 17 May 2013, 14:54
by dreammyw0w
its just an image placed on the spawn & scoreboard. How would this affect performance?
Like omnixor said, pls make an exception :)

Besides , parts of the GUI shouldnt be shitty-looking because of a setting. Name one other game where this happens? :)

Re: shields in extremely poor quality.

Posted: 18 May 2013, 07:18
by eyebo
You're right. The shields in the UI shouldn't look this bad. I'll move this to the reports forum.

Re: [16.05.2013] shields in extremely poor quality.

Posted: 20 May 2013, 16:38
by LuckyBoy
Fixed for next version.
Thanks