Formerly I had a setup of range indicators for the target, 40 yards, 30 yards, 8 yards, and so on, specific to the class/spec. 

 

Each range icon was a "Unit Condition Icon". The range icons were fed to a meta icon.

 

Since 8.5.5-1 (don't nail me on that, but I think it was 8.5.5-1) this doesn't work anymore.

 

For testing I disconnected a range icon from the meta icon, then it worked sometimes, but still far from reliably.

 

However, I solved the problem now by converting all the "Unit Condition Icon" range icons to "Condition Icon" icons, that is, the range condition is now set in the icon's condition, and no longer in the "Unit condition" subcondition.

 

I'm reporting this because I'm not sure if this is an intended behavior change or rather a symptom of some underlaying bug. 

 

If it is an intentional change, just close the ticket.

 

Posted by CurseForge user Portalbendarwinden | Imported from CurseForge issue #1621 | Raw

Should be fixed now with https://wow.curseforge.com/projects/tellmewhen/files/2643292 

 

It was indeed recently broken with 8.5.5-1. Sorry about that!

Posted by CurseForge user Cybeloras

@Cybeloras, since I already have changed all my range icons to "Condition Icon", should I revert them back to "Unit Condition Icon"? In other words: Is "Unit Condition Icon" less expensive than "Condition Icon"?  (CPU-wise) 

Posted by CurseForge user Portalbendarwinden

No, a regular Condition Icon is generally always going to be more performant. A unit condition icon is used for cases when you want to know which units (from a large number of units) satisfy some conditions. For example, making an icon for each healer in the raid that is below 20% mana (You'd make the icon as a Group Controller).

 

If you're only checking a single unit, then a regular Condition Icon will be better and simpler.

 

Posted by CurseForge user Cybeloras