With the last patch i see a bug with taklers chameleon. If i fire and at the same time i active the chameleon this last go in cooldown without go invisible.
I believe this is a sort of “safety” that they implemented for cloaking. In a Recon, if you are firing at the same time you activate it, it will not do anything. This is probably just an issue with this system.
15 minutes ago, TheDarkRedFox said:
I believe this is a sort of “safety” that they implemented for cloaking. In a Recon, if you are firing at the same time you activate it, it will not do anything. This is probably just an issue with this system.
no, this is a MAC issue - every now and then, on mac you are not becoming invisible
13 minutes ago, xKostyan said:
no, this is a MAC issue - every now and then, on mac you are not becoming invisible
I’m on windows 10 enterprise
44 minutes ago, Ogrande18O said:
I’m on windows 10 enterprise
well, nvm the MAC thing than 
3 minutes ago, xKostyan said:
well, nvm the MAC thing than 
My theory stands. So far it’s been proved on numerous windows machines. It’s actually quite nice.
27 minutes ago, TheDarkRedFox said:
My theory stands. So far it’s been proved on numerous windows machines. It’s actually quite nice.
It used to go into cloack and break it for a dmg buff on a tacker. Same for the recon it should start the invis and break it. instead of just going into cd.
We can’t reproduce it on our windows’s PC. Please, attach your DxDiag file
We going to try to reproduce issue on Radeon video cards
7 hours ago, Skula1975 said:
We going to try to reproduce issue on Radeon video cards
I have an nvidia video card and have noticed the same issue sometimes, so it seems to be mechancis rather that graphics. If I see it again, I will provide logs on this thread.
8 hours ago, Skula1975 said:
We going to try to reproduce issue on Radeon video cards
it is not a graphics bug, the cloak itself gets somehow cancelled/ doesn’t even activate, look in the buff row in the video
But isn’t it more logical that you don’t enter cloak when you are firing ?
After all it represent 3-4 seconds of being invisible while still shooting stuff.
17 minutes ago, Swifter43021 said:
After all it represent 3-4 seconds of being invisible while still shooting stuff.
2 seconds is a lingering time, after that it will be canceled, or rather supposed to.
20 minutes ago, Swifter43021 said:
But isn’t it more logical that you don’t enter cloak when you are firing ?
After all it represent 3-4 seconds of being invisible while still shooting stuff.
It depends what you mean by “while”, there should be some overlap or else it’ll be very hard to time it properly.
No bug here.
Check the video he posted. He charge the shot and than go invisible, then release the shot -> inv denied as it’s meant to be.
23 minutes ago, Spongejohn said:
No bug here.
Check the video he posted. He charge the shot and than go invisible, then release the shot -> inv denied as it’s meant to be.
Yeah but it doesn’t even GO invisible. It just stays uncloaked. Surely it should cloak up and then uncloak when he actually fires?
1 hour ago, Spongejohn said:
No bug here.
Check the video he posted. He charge the shot and than go invisible, then release the shot -> inv denied as it’s meant to be.
It used to trigger invis and cancel it granting a dmg buff
In that case, is it possible to replicate this without weapons that can’t be charged? (oc no).
As I said it’s not a bug, but how the mechanic works.
Btw I don’t agree that using weapons can still grant you inv. And charging a weapon is still using it. That’s against the whole invisible module concept.
Start charging, go inv and then release the trigger just to spoil the damage buff, sounds like something that is against the whole point: “you can’t use modules or weapons or missile etc while invisible”.
1 hour ago, millanbel said:
Yeah but it doesn’t even GO invisible. It just stays uncloaked. Surely it should cloak up and then uncloak when he actually fires?
You are “using” your weapon, Invisibility is meant to not work while you do that.