Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-114769 Multiview and related in the Qt graphics stack and Quick 3D XR
  3. QTBUG-124842

Multiview: Screen textures in custom materials (and effects)

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: P2: Important P2: Important
    • 6.8.0 FF
    • Quick: 3D
    • None
    • 6f2e533c6 (dev)

      The depth and screen textures both become texture arrays when the main render target is multiview. Consequences for the shader code, incl. user-provided? (one cannot probably just write the GLSL code 'texture(SCREEN_TEXTURE, uv)' anymore, once we fix up the shader generator so the sampler is correctly a sampler2DArray...)

      Source compatibility and portability concerns: e.g. if SCREEN_TEXTURE is simply not a sampler2D anymore in multiview mode, what if users want to write custom materials and effects that work both in regular and in XR mode? Also is this sensible even; how would the shader know that now it has to do things twice, first by sampling layer 0 and then repeating the same for layer 1? More uniforms?

       

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            lagocs Laszlo Agocs
            lagocs Laszlo Agocs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes