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

PanoramaSky created using Viewport texture is always rendered pink. #68088

Open
RicardRC opened this issue Oct 31, 2022 · 4 comments
Open

PanoramaSky created using Viewport texture is always rendered pink. #68088

RicardRC opened this issue Oct 31, 2022 · 4 comments

Comments

@RicardRC
Copy link
Contributor

Godot version

master (f013315)

System information

Windows 11, Nvidia 1070

Issue description

This test subviewport:
image
Looks like it's not having any effect once passet as viewport texture, like this:
image

Notice that this happens even if I use both PR #64138 and #64152

Also, repro project shows no error or warning in any console or output.

Steps to reproduce

Open repro project, run, observe the pink where there should be a procedural sky.

Minimal reproduction project

ViewportBug.zip

@Calinou
Copy link
Member

Calinou commented Oct 31, 2022

Is the viewport's update mode set to Always?

@RicardRC
Copy link
Contributor Author

I've tried setting it to all combinations of update and clear mode.

@Calinou Calinou added the bug label Oct 31, 2022
@Rindbee
Copy link
Contributor

Rindbee commented Nov 20, 2022

If a resource's sub-resources have local_to_scene enabled, that resource also needs to have local_to_scene enabled.

If there is such a resource chain Node-R1-R2-R3(local_to_scene)-R4, it is required that R1, R2, and R3 all need to enable local_to_scene, and R4 does not have to be enabled.

ViewportTexture requires local_to_scene to be enabled, so both its parent resource and its ancestor resources need to enable local_to_scene.

@RicardRC
Copy link
Contributor Author

RicardRC commented Aug 1, 2023

Doing as @Rindbee says solved my problem. I think that the editor should complain when something needs a certain "local chain" and does not get one, or one resource is marked as local and it's not having any effect because there is a lack of a link on the locality chain. I know that viewport does ask for "local", but it did not hint at the chain Rindbee mentioned.

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

No branches or pull requests

5 participants