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

Sprite 3D doesnt work with Viewport texture on android. #80636

Closed
KeiMuriKoe opened this issue Aug 14, 2023 · 6 comments · Fixed by #81607
Closed

Sprite 3D doesnt work with Viewport texture on android. #80636

KeiMuriKoe opened this issue Aug 14, 2023 · 6 comments · Fixed by #81607

Comments

@KeiMuriKoe
Copy link

KeiMuriKoe commented Aug 14, 2023

Godot version

4.1.1

System information

Windows 10, Godot 4.1.1 Latest, Vulkan API 1.3.206 - Forward Mobile.

Issue description

I was trying to make ProgressBar for 3d Object. I used Sprite3D with SubViewPort as a texture. In edit page it works correctly, in run page too. After exporting to android device its not. It works not only with ProgressBar, with all textures to sprite3D with SubViewPort as a texture.

Steps to reproduce

  1. Create godot(4.1.1) project Mobile.

  2. Add 3D Node and any 2d stuff, for ex, ColorRect, u can choos button, progressbar, sprite2d etc.
    3.Join it as a child to SubViewport
    4.Create Sprite3D and pick texture to it as SubViewport, and choose SubViewport with 2d stuff as a child.
    5.place camera 3D so when u run scene u can see our 2d stuff in 3d space.
    image
    image

  3. As we can see, all works properly. Then export it to android, and check. We see nothing.

Minimal reproduction project

@KeiMuriKoe
Copy link
Author

git_issue.zip

UPD : Minimal reproduction project

@Calinou
Copy link
Member

Calinou commented Aug 14, 2023

What device model did you test this on? Can you reproduce this after switching the rendering method to gl_compatibility in the Project Settings (specifically for the .mobile override)?

@KeiMuriKoe
Copy link
Author

What device model did you test this on? Can you reproduce this after switching the rendering method to gl_compatibility in the Project Settings (specifically for the .mobile override)?

android 13. Google Pixel 7 pro. And yes, i reproduce this on Compatibility. And Still...

@EIREXE
Copy link
Contributor

EIREXE commented Sep 6, 2023

After some investigation this issue doesn't happen to me on the compatibility renderer, however both forward plus and forward mobile are affected. I also seem to have some template_release exclusive glitching together with the viewport bug, perhaps they are related.

What I get:

imagen

What it should look like:

imagen

@EIREXE
Copy link
Contributor

EIREXE commented Sep 7, 2023

after testing, it appears like viewport update mode VIEWPORT_UPDATE_WHEN_VISIBLE is the cause of the issue, switching it to VIEWPORT_UPDATE_WHEN_PARENT_VISIBLE fixes the issue, is this a bug or an intentional design?

@KeiMuriKoe
Copy link
Author

after testing, it appears like viewport update mode VIEWPORT_UPDATE_WHEN_VISIBLE is the cause of the issue, switching it to VIEWPORT_UPDATE_WHEN_PARENT_VISIBLE fixes the issue, is this a bug or an intentional design?

Yeah, you right switching to VIEWPORT_UPDATE_WHEN_PARENT_VISIBLE helped. Intuitively, it's not clear because with the VIEWPORT_UPDATE_WHEN_VISIBLE mode enabled in the viewport (which is the default setting), everything appears to be working correctly, but after rendering, it's not the case. But in principle, yes, the issue was indeed with this.

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.

4 participants