Hi, did you ever figure out what was causing this? I just started noticing it in my own game in the last week! I've been running this game for a year now. I can't imagine I've done as much in this game over the last year and only JUST noticed that the GM view works this way. Honestly, I've tried to be careful in pinning down common issues and trying ideas others have had. My belief is this is a bug affecting GMs who are viewing a UDL-enabled map that has Explorer mode turned ON. It's Explorer Mode that is glitching here. Here's what I can assert about the bug I'm seeing: Objects on any layer other than the Map Layer appear semi-transparent, with the Map Layer visible through them. It does only affect the view of a GM looking at their game, not players viewing that game. It does not seem to affect the Map Layer, but affects all other layers (Object, GM, and Dynamic Lighting). It does not seem to be tied to the GM Overlay Opacity Slider in any way. It does not seem to be tied to whether a token on an affected layer is at the "Front" or "Back". Tokens on the same layer occlude one another as expected based on whether they are "Front" or "Back". Visibility of Map Layer beneath two tokens interacts with one token "behind" the other by showing only "Front" token, but still with semi-transparency showing map beneath. No visibility at all on the token "behind" the other, despite the "front" one being transparent to the map beneath. Affect only happens when UDL is present (which is the case on all of my maps) and when Explorer Mode is turned ON. Can use UDL with or without Daylight Mode, but as soon as you turn Explorer Mode ON, you see the weird transparency. Turning Explorer Mode OFF renders what I would call my normal, expected behavior as has been my experience as a weekly GM user for the last year running two campaigns. This affects image assets regardless of the asset's Dynamic Lighting settings. I have tested assets with Sight (e.g. player tokens), assets that emit Light (e.g. a token for a torch), and simple art that never has any lighting effects enabled (sight or emitting light) at all (e.g. an NPC portrait drug out of the library to the map). My current synthesis of the above is that this is a bug, because I've never noticed it before this last week. It affects maps that have UDL and Explorer Mode turned ON. And it seems that it's Explorer Mode, specifically, which is the culprit. It seems to be showing the map "beneath" the tokens on the other layers "through" those tokens as a way of showing the "parts of the map" that the GM has already explored. That's great and all, but as a GM, I of course always know what the entire map looks like at all times. I don't want to see it "through" the tokens I set on top of it. Or at the very least, I want a way to turn that "x-ray vision" OFF so that I can see what the opaque tokens on the Objects Layer look like against (and occluding) the Map layer behind them. Additional Details in case they help: Images on the Object Layer, GM Layer, and Dynamic Lighting Layer appear ~50% transparent. Items moved to the Map Layer from any of these other layers become 0% transparent. Items moved from the Map Layer to any of these other layers become ~50% transparent. Affects both newly-imported (i.e. dragged-and-dropped directly from computer to map) and already-imported images (i.e. dragged-and-dropped from Roll20 library to map). Affects items recently uploaded to my Roll20 library as well as items that have been in my library for a year and with which I've never noticed this transparency before. The GM Overlay Opacity Slider can dial a token with ~50% transparency all the way down to 100% transparent. However, moving the slider all the way to the opposite end (which would normally make items completely opaque), can only ever make the item ~50% transparent. This effect only seems to affect things when viewed by the GM of a game. I'm our group's Forever GM, so I have no other GM account I can test this on to rule out it being an account-specific problem. This strange transparency effect goes away when viewing the map as a player, rendering all player-visible assets at their expected transparency values (i.e. usually opaque). I have tested this both by swapping my own view to the "as a player" view, and by viewing the map on my wife's computer with her logged in as her player account. Tests included careful search for "hidden" or "barely visible" copies of tokens or maps sitting on unexpected layers (e.g. a copy of the map on the GM layer).