Cloak Doesn't Work on Grenade 3

Agreed. And that thing always scares me a bit, making me think it's an enemy. :lol:

Definitely, for me, I can't hear friendly sin hums either. The bots seem to hum even louder now, but that's probably just my imagination.

I have confirmed that the Assassin cloak can work perfectly well on Grenade III Arena (and all maps).
I just got out of a game with a friendly and 2 enemy Assassins and it was plenty hard to see them even while moving.

So when it happens it is just a random glitch, and it can happen on any arena.

It is most likely the same bug that causes particles/coins/smoke to appear black. Wrong shader is active or shader uniforms are not being updated correctly.



I also listened for friendly hums and this time did not hear any. It is most likely also a bug that sometimes you can.


L. Spiro

Okay let's do this again: The cloak does not work correctly on Grenade III.

It was prooven and without a counterproof your word means nothing. Maybe you just can't see them? I can see them perfectly fine there.

Yes, the water mark is present and they are quite visible.

I think you need to read again.
It has the capability of working fine on all maps, and sometimes, on any map, it has a watermark effect.

Just like black smoke or the coins at the end of the game. They work fine or appear black 50/50.

Its a shader bug. Case closed.


L. Spiro

A shader bug actually appears as such, i.e. black. The cloak thing is not a shader bug.

Did you actually look at the screenshots or are you just writing whatever you feel like at the time? It happens everytime on Grenade III. Everytime, not random, not a 50/50 chance, everytime.

Show us some screenshots where it happens on for example LazerRazor.

It feels like I'm talking to a ******* wall.

He was an enemy Assassin.
Shortly after I snapped the screen shot, he was completely gone. Cloaking worked perfectly.
At the same time, it did bug in one of my earlier games today. 50/50 or so chance of happening. Once it begins happening, in continues until you restart your game.

Additionally, the thing that takes the model vertices, normals, etc., and puts them together is called a shader (since the fixed-function pipeline is dead). In this case, there is no texture on the model (or the texture is ignored within the shader, either way is the same) except for a cube-map texture used for the Fresnel refraction (which could also get the incorrect results if it is corrupt), so it is not a texture bug (barring the possibility of the cube-map texture).
Most likely one of the shader uniforms has been cached out and is not being detected as reset, and is therefore not being updated. If the normal matrix, texture matrix, eta, or fresnel powers are wrong, if if the cube-map texture is corrupt (less likely), you could end up with the result shown in the bad screenshots.


But dont mind me, Im just a wall.


L. Spiro

Put him against the wall.

It isn't so much putting them against a wall. I doubt it will even be noticeable in the distance L-Spiro took that screen shot from. Assassin's cloak works fine on grenade III if you are close up it just shows up as a watermark from long distance.

It requires you look at the assassin from the opposite side of the map. You basically are required to go sniper an actually zoom in on the assassin to see the issue. You can barely see it with the naked eye if you know exactly what you are looking for, however, zoomed she sticks out like a sore thumb.

So, retest and take a screenshot based on what we actually said. As sniper from the opposite side of the map.

My tests show that it depends on what is behind him, at any range. Specifically the blue shadow color.

He doesnt have to be in it, but if he is in front of a shadowed area, even in the unreachable background areas, you can see him easily.

It seems to have been fixed on other arenas, as I noticed this constantly in the past, but not since the latest update.


L. Spiro

Thanks for finding this. It's a fairly simple issue, and my fault for it's existence.

Short explanation is the way the Assassin's shader worked the distance fog was getting applied twice. Prior to the lighting change the distance fog in our maps didn't cover the play area so it hadn't exposed the issue.

This will be fixed in our next patch.