I noticed the same.
Layer count is now around 48-52 instead of 81 or 82 and the new limit is raised to 200?
And can the color be adjustable? That dark green is really hard to see.
Maybe not show colors if it’s good. Change colors only when the number of active layers approaches the limit?
1 Like
I can adjust the colors and yes things have changed. Beta upped their layer maximum to 200 which is now on prod. This is why I changed how it was calculated. instead of a static value. So if it ever changes again. It will see it on the fly. WME has less active layers now thanks to the devs. So the number should show less for active layers.
Lots of changes here with the new version of WME. The WME developers changed the “zones” that layers can be in so that the zone that user script layers are in can now accommodate 200 layers. This script is now only counting layers set as visible, which is why the count is lower now. I’m not sure this is appropriate because if a script creates a layer, even if its not visible, it is still taking one of those layer “slots”.
The colors are supposed to indicate how much of the available space you are using. Green means you are using less than 25% of the available space. I think its much less important now that the space available has been extended.
If you go to line 62 in the script and change “green” to “lightgreen” that makes it much more readable. The background shading is not consistent for me. It is often just a white background.
Update 2024.7.9.1
-Removed Colors.
So the way I understand this the total layers being used and available for use different than what this script is saying?
Currently it says I’m using 42 but in the previous WME it said 72. Is the number closer to 72?
Probably doesn’t matter because 200 seems like a lot and I don’t think I have enough scripts to get there. 
For me, it is currently showing 46 layers (visible), but the actual number of layers created is 79. Like I said, it might be best to show the total layer count, not just those that are set visible.
From my understanding. Only when layers are visible are when they effect WME. If they aren’t visible then they “shouldn’t” effect WME performance.
200 is a hard limit on the number of layers that can be created/allocated. Whether it is visible or not, when a script creates a layer, it is allocated and takes up one of the slots.
It sounds like you don’t understand what creates the eventual issue.
Visibility has no impact on the object selection issue (with the possible exception of the final layer that is passes into the Feature space - but I have not tested that, and with the extra possible layers I don’t want to dedicate the time to). The layer count increases due to layers being added regardless of if they are visible or not, and the eventual passing of a layers zindex into the Feature space is what creates the issue.
With the available space that we have now, especially with recent changes to many scripts to minimize layer usage, I’m not sure I see a value in taking up WME real estate with a display like this. With the likelihood of hitting the issue being so low, moving this to a tab to be referenced would make more sense to me.
Update 2024.7.9.4
- Moved to tab section.
- Shows Active, Created, and Max Layers
- Active layer counter can still be displayed on top right.