Vulkan: SubViewports not functioning unless update mode is set to "Always"

[Leakbang]

---

Bugsquad note: This issue has been confirmed several times already. No need to confirm it further.

---

Godot version

v4.0.dev.calinou [cf67f18]

System information

Linux KDE Neon, Vulkan, NVIDIA GeForce GTX 1050 Ti, Driver Version: 470.63.01

Issue description

I cannot seem to make Subviewports work in any shape or form. The error message Uniforms were never supplied for set (3) at the time of drawing, which are required by the pipeline is continuously popping up. I have tried with both 2D and 3D objects in the viewports, however none seem to work.
Are others able to reproduce this effect?

Steps to reproduce

1. Setup a basic 3D scene
2. Add a SubViewport node
3. Set nodes as its children (Camera, UI control, or others)
   The viewport display is black and rendering the viewport as a texture will also not work.

Minimal reproduction project

No response

[spindlebink]

Same here. I initially figured they just weren't implemented yet, but good to hear others are having the same issue.

[Calinou]

Other people have gotten SubViewports to work on master, such as in #40651 and #54122. It seems that it's mainly breaking in 3D: #50327, #50296

[navy-cap-echo]

@Leakbang I had the same problem (black display) until i switch the "update mode" in the "Render target" of the SubViewport to "Always". I'm not sure this fixes your problem, but maybe give it a try.

[Leakbang]

I did try setting the "update mode" to "Always" but it didn't make any difference for me.

[FluffyBunniesTasteTheBest]

Same here in 3D, except that the SubViewport shows only pink instead of black. Changing "Update mode" to "Always" fixed it. (Mono build running on Ubuntu 21.10)

[Leakbang]

I retried this on v4.0.dev.calinou [e31138958], and setting the update mode to Always does not fix the issue.

[KoBeWi]

I just discovered the existence of UPDATE_WHEN_PARENT_VISIBLE. This should be the default option in SubViewport probably. UPDATE_WHEN_VISIBLE makes sense only for Window viewports and won't work as expected for typical usage.

[KoBeWi]

Actually no, UPDATE_WHEN_VISIBLE uses render_target_was_used() method, which never returns true. UPDATE_WHEN_PARENT_VISIBLE checks parent Viewport actually.

[Duroxxigar]

Just wanted to chime in here as well - setting the update mode to Always doesn't fix the issue for me either. 28174d531b

[Zireael07]

In alpha 1, 2D subviewports seem to work, but 3D don't. The resulting texture is either all black or all magenta

[CrezyDud]

In alpha 1, 2D subviewports seem to work, but 3D don't. The resulting texture is either all black or all magenta

works for me

[kalysti]

Same issue by me, but render target mode is always. 3d is still not working.
Tested with HBox, VBox, HSplit and VSplit Nodes..

Node tree

Output

When i move it an split controller and change the offset of the split controllers it works.
U can see here:

[Zireael07]

Hm, so it seems forcing an update/resize might do the trick? Thanks for the tip...

[kalysti]

Yeah its looks like that the subviewport size are not setted right by the viewport container. if u do it manualy it works.

[kalysti]

Small hack which fix the issue:

public override void _EnterTree() { var origSize = this.GetParent<SubViewportContainer>().Size; this.Size = new Vector2i((int)origSize.x, (int)origSize.y); }

[kalysti]

I think the issues comes inside the code. The SubViewportContainer is set the size of the SubViewport (Vector2 to Vector2i) -> something here is broken

[seocwen]

The following line seems to do nothing:
render_target_clear_mode = SubViewport.CLEAR_MODE_NEVER

I've been trying to draw on top of my last frame to no avail. As a minimal test, I have a subviewpoint set to clearMode NEVER, with a single colorRect with the following script:

func _process(delta):
color = $"../../../resources".random_color()
color.a = randf()
position = Vector2(randi() % 384, randi() % 256)
size = Vector2(randi() % 64, randi() % 64)
update()

The result is a new rectangle every frame, rather than a rectangle being added to the render target every frame.

[Zireael07]

Thanks for the workaround, I'll try it, as I still have the pink issue on my mirror mesh.

[thoced]

IriaSomobu's solution works for me

[Zireael07]

Confirming the workaround works.

[darrylryan]

Just to update this - I'm still seeing weirdness with pink output like @sboron in the latest master as of time of posting. Setting update / clear modes doesn't seem to help.

[Rindbee]

I noticed that if I change the size property of the SubViewport, I won't have this problem. So it may be that the necessary steps in _set_size are not performed during initialization. Maybe we should set the size in the constructor of SubViewport.

[arcanis]

Expanding on @Rindbee's comment, the following seemed to work:

extends SubViewport

func _ready():
	set_size(size)

[someguynamedjosh]

For me what ended up working was deleting the shader and material off the filesystem, re-saving the scene I was working on, and ticking 'local to scene' on those same resources. Then I could assign a new viewporttexture (which was automatically local to the scene) in the shader's parameters and it worked!

[clayjohn]

Update on this issue, it appears that the resize workaround is no longer needed since #68358 The only issue that remains here is that the update mode "When Visible" is not working. I'm looking into this now. All other update modes are working.

[nvanfleet]

I am seeing this on Mac OS Arm64 4.0.3 version of Godot. It looks like setting the texture programmatically makes it work for me actually.

self.plane1.mesh.material.set_shader_parameter("portal_texture", viewport2.get_texture())

[RisingThumb]

I am seeing this on Mac OS Arm64 4.0.3 version of Godot. It looks like setting the texture programmatically makes it work for me actually.

self.plane1.mesh.material.set_shader_parameter("portal_texture", viewport2.get_texture())

Just adding that I am seeing this in Godot v4.2.1 stable version of Godot, on Arch Linux using the official binaries. What nvanfleet wrote seems to be a workaround for this, so it looks like the issue is something to do with using viewport textures from the scene compared to when it's programmatically added 🤷

[HeyNinety]

I'm getting this issue as well. Godot v4.2.1 stable. Using Debian 12 KDE X11.

[lunarcloud]

I am seeing this on Mac OS Arm64 4.0.3 version of Godot. It looks like setting the texture programmatically makes it work for me actually.

self.plane1.mesh.material.set_shader_parameter("portal_texture", viewport2.get_texture())

Can you provide the full script example? I put this blindly into a script on the subviewport and it clearly needs more setup to work...

[RisingThumb]

I am seeing this on Mac OS Arm64 4.0.3 version of Godot. It looks like setting the texture programmatically makes it work for me actually.

self.plane1.mesh.material.set_shader_parameter("portal_texture", viewport2.get_texture())

Can you provide the full script example? I put this blindly into a script on the subviewport and it clearly needs more setup to work...

Your mesh should have a material. That material should be a shader. That shader should have a uniform sampler2D with the name "portal_texture". The issue described here, is that setting it in the Engine GUI doesn't work(I.E. clicking the material and clicking the subviewporttexture youw ant), but if you pass it programmatically it does work. I haven't had the time(or a use case) to look into whether this affects other things you can pass a viewport texture to.

This line of code needs to be adapted to get the correct material, and set the correct shader parameter and get the viewport texture. More information needed to point out what you're doing wrong

[colonelzkiller]

I'm getting this issue as well. Godot v4.2.1 stable. Using Fedora 39 Gnome, none of the above suggestions are working for me.