Suppress FX When Close and Cloak Of Darkness
By
Ice_Cube_Maker,
Posted on: 2010-02-08 16:49 in ALL ACCESS Gameplay Technical Issues Bugs
[Cloak of Darkness] and [Shadow Cloak] set your Translucency to 0 for the duration of the power. That makes your avatar completely disappear and you only see the Auras. If you suppress the auras.. you wouldn't see anything. That seems to be by design.
Hero side I have a Dark Melee / Dark Armor scrapper, and respecced him into Cloak Of Darkness, and I have no worries at all, can see his outline just fine, and I don't have to Suppress Close FX. I guess hero side Cloak is different from villain side?
Quote:
Does your Hero have some kind of other aura on his costume that is actually making the outline? That might not be suppressed by the command because it's not a power. If your Villain does not have a similar aura, then that might be why the results differ. As far as I can tell, the Translucency is the same for both Scrapper and Brute versions of the power.
|
Originally Posted by Ice_Cube_Maker
Hero side I have a Dark Melee / Dark Armor scrapper, and respecced him into Cloak Of Darkness, and I have no worries at all, can see his outline just fine, and I don't have to Suppress Close FX. I guess hero side Cloak is different from villain side?
|
A friend suggested I try the Tailor to fix my problem. There is an option for Cloak Of Darkness to not fade, I selected that, and I can active that power now and still see body outline. I guess I did that with my hero a while ago and have since forgotten what I did. Thanks for the help all, take care and keep playing and having fun 
I did a respec this morning to include Cloak Of Darkness in my Electric Melee / Dark Armor build, expecting Suppress FX When Close to allow me to still see a body outline in the murky fuzzy darkness, but it is all fuzzy cloud, no body outline. When I set the distance to 30 for the camera, nothing is visible at all except for a floating name. Is there a setting to still see the body outline while having Cloak of Darkness active, or is this a "known" bug?