Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-122429

QShaderProgram logChanged and statusChanged report nothing with Qt3DExtras meshes and custom meshes.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P2: Important
    • None
    • 6.6.1
    • Qt3D
    • None
    • Windows

    Description

      Both logChanged and statusChanged signals in QShaderProgram class report nothing in case the material this shader program exists on is applied on a mesh loaded by QMesh class.

      But when using any mesh from Qt3DExtras package, or if I made a custom mesh myself, and used that same material with that same shader program on it, those two signals report nothing at all.

      I provided a script that triggers this problem, it defines a Qt3DExtras.CubiodMesh and all the needed setup to load it with a QTextureMaterial, and it connects all shader program signals to a print statement, and sets their shader codes to a dummy ones to trigger errors.

      It has a commented out line to load a gltf file I provided for a cube using QMesh, you can uncomment it and comment the Qt3DExtras.CubiodMesh definition to see that those signals works only in that case.

      Attachments

        1. ShaderProgramLogTest.py
          2 kB
        2. DiffuseMap.png
          DiffuseMap.png
          43 kB
        3. Cube.gltf
          2 kB
        4. Cube.bin
          0.8 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            seanharmer Sean Harmer
            ahmedahmedeg Ahmed Ahmed Abd Al Maksoud
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes