daMarek Posted March 7, 2012 Share Posted March 7, 2012 This may be known issue, but not sure, so here goes: Last night I queued for WZ and got put into... guess... Huttball. So we are just pew pew and my teammate gets the ball and makes a run for it. I follow him until he runs straight into the flames. I'm like NOO MOTHER****ER THAT DUMP **** *** *** *** only to see him emerge on the other side with full health. Then half a second later flames go down. I'm like ok minor glitch whatever back to pew pew. Then guy on the other team gets the ball and makes a run for it, and I see the floor planels turn red but he goes in, and for sure flames turn on, i'm like got you dumb **** but he comes out alive with full health. So mine thinking, the graphics on the flames are either lagged at times or show differently for each player. What gives? Link to comment Share on other sites More sharing options...
wtfnonamefree Posted March 7, 2012 Share Posted March 7, 2012 (edited) The problem is clientside and due to either bad connection or hardware on your end. After the lower graphics option in 1.1.5 this problem totally vanished on my low end machine. Now I have to relearn the timing and refrain myself from running into the flames too early, as I could safely do before.^^ Edited March 7, 2012 by wtfnonamefree Link to comment Share on other sites More sharing options...
Egobia Posted March 7, 2012 Share Posted March 7, 2012 Possable they had a sorc or sage bubble on which can save them from damage Link to comment Share on other sites More sharing options...
Mrip Posted March 7, 2012 Share Posted March 7, 2012 There is an exploit... That's all I'll say. Link to comment Share on other sites More sharing options...
wtfnonamefree Posted March 7, 2012 Share Posted March 7, 2012 (edited) There is an exploit... That's all I'll say. No, Mr. tinfoil hat. What the OP describes is simply a late rendering of the flames, so they appear to be still off, when they just went on and vice versa. This is caused by bad latency or unsufficient specs and I experienced it on both ends. I don't know about speedhackers - maybe they get one tick, maybe they don't - but this is clearly not what went on in the above scenario. Apart from that there is no exploit, that I know off (and I check up on those boards frequently to know my enemy!). Also, there are bubbles, undying rage, etc., leading to less or no damage depending on situation and movspeed. But, again - what the OP experienced is the typical late rendering of the flames. Edited March 7, 2012 by wtfnonamefree Link to comment Share on other sites More sharing options...
Mrip Posted March 7, 2012 Share Posted March 7, 2012 (edited) No, Mr. tinfoil hat. What the OP describes is simply a late rendering of the flames, so they appear to be still off, when they just went on and vice versa. This is caused by bad latency or unsufficient specs and I experienced it on both ends. I don't know about speedhackers - maybe they get one tick, maybe they don't - but this is clearly not what went on in the above scenario. Apart from that there is no exploit, that I know off (and I check up on those boards frequently to know my enemy!). I know for a fact that there is an exploit. This here might be late rendering, or it could be the exploit. Edited March 7, 2012 by Mrip Link to comment Share on other sites More sharing options...
daMarek Posted March 7, 2012 Author Share Posted March 7, 2012 ok, thanks for the info. Time for a new gfx card i guess Link to comment Share on other sites More sharing options...
wtfnonamefree Posted March 7, 2012 Share Posted March 7, 2012 Just try the new 'lowest' option in shader complexity. I went from 5 to 25 fps! Link to comment Share on other sites More sharing options...
daMarek Posted March 7, 2012 Author Share Posted March 7, 2012 Don't have fps problems, but that certain things don't render in time didn't occur to me. Link to comment Share on other sites More sharing options...
Recommended Posts