ColorRect Alpha at 255 still showing transparency

Help
1

Godot Version

4.6

Question

Hi all, I’ve been trying to get my ColorRect to be a solid color (and non-transparent). However the end result when running the game looks like so:

image
image1459×359 1.79 KB

The cyan/turquoise box should be a solid color and the empty placeholders shouldn’t be visible inside of it.

The actual color selector looks like so:

image
image475×935 57.3 KB

With the alpha set to 255. My scene tree has a base CanvasLayer1 → Control → ColorRect, and the empty tile placeholders are rendered on a tilemap under CanvasLayer1 → CanvasLayer2 → Node2D → TileMapLayer. The Control and ColorRect both have a Z axis of 2, the Node2D and TileMapLayer have a Z axis of 0.

Given that setup, with the ColorRect and the TilemapLayer on the same canvas layer, I figured the ColorRect would render on top of the TileMapLayer, but that doesn’t appear to be the case.

Any help on this would be greatly appreciated!

2

Looks like the ColorRect is below the TileMapLayer. Could you send a screenshot of your scene tree?

3

Sure thing, here’s the scene tree:

image
image427×297 17.6 KB

The ActionCardHolder::ColorRect is the color rect in question, and the Atcgame node is what contains the TileMapLayer.

For what it’s worth, I have tried to move the ColorRect to different places in the scene tree with no success.

4

Actgame being a child of a CanvasLayer is most likely the reason it’s rendering above the ColorRect. Try decreasing the Layer property of the GameCanvas and see if that fixes the issue.

Some additional info: the z-indices of nodes stop mattering when they are children of different CanvasLayers. This is really useful when you have nodes that you need to render on top of everything else: just put them on a CanvasLayer!

5

So first things first, CanvasLayers have their own Z levels and you didn’t mention their setting yet. So that might mess up your other Z levels, if you are not careful. @neropatti was already mentioning that.

Secondly, I would put both CanvasLayers on the same parent and not nest them within each other. Unless you have a very good reason to do so. I cannot imagine any off the top of my head, but it might be that there is some reasons. Better avoid complications, if there is no reason for it.

You have this structure:

.
└── cl1
    ├── cl2
    │   └── node2d
    │       └── tilemaplayer
    └── ctrl
        └── colrect

But I recommend this structure:

.
└── parent
    ├── cl1
    │   └── ctrl
    │       └── colrect
    └── cl2
        └── node2d
            └── tilemaplayer
6

Thank you both! It was that, CanvasLayer overriding the Z-index.

I’m curious, what is the benefit of not having a parent CanvasLayer? I found that my rendering of various scenes wouldn’t resize correctly unless they were parented by the single canvas.