Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Editor] setting the preview environment to all black still leaves the horizon #99701

Closed
hpvb opened this issue Nov 26, 2024 · 4 comments · Fixed by #99957
Closed

[Editor] setting the preview environment to all black still leaves the horizon #99701

hpvb opened this issue Nov 26, 2024 · 4 comments · Fixed by #99957

Comments

@hpvb
Copy link
Member

hpvb commented Nov 26, 2024

Tested versions

Reproducable on current master [d09d82d]

System information

Godot v4.4.dev (779fe8da4) - Fedora Linux 41 (Workstation Edition) on Wayland - X11 display driver, Multi-window, 2 monitors - Vulkan (Forward+) - dedicated AMD Radeon RX 6950 XT (RADV NAVI21) - AMD Ryzen Threadripper PRO 5975WX 32-Cores (64 threads)

Issue description

When setting the editor environment to all black, a white horizon remains.

Image

Image

Steps to reproduce

Set editor environment to all black, with 0% sun.

Observe that the editor still has a white horizon

Minimal reproduction project (MRP)

N/A

@hpvb
Copy link
Member Author

hpvb commented Nov 26, 2024

Note that this is not the grid going into the distance.

Image

@clayjohn
Copy link
Member

This isn't a bug per se. The horizon color was never exposed to this menu since the menu is just intended for quick edits to the overall color of the scene. That's also why it only exposes a few options from the WorldEnvironment.

@hpvb
Copy link
Member Author

hpvb commented Nov 26, 2024

@clayjohn I would argue that at the very least this is really surprising. I found this issue while doing my new hobby of "watching random Godot streamers", and one of them was trying to setup an editor environment they could use to test their particle system.

It looked like a reasonable thing to want to do to me.

@clayjohn
Copy link
Member

Sure. I'm just providing context so no one goes investigating to find the root of the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants