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

meshName property doesn't affect rendering

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P3: Somewhat important
    • None
    • 5.12.3
    • Qt3D
    • None
    • macOS 11.2.1
      Qt 5.12.3
    • macOS

    Description

      It looks like the meshName property is ignored when loading a Wavefront file with Mesh and it ends up loading all the vertices/faces of the model:

      Mesh {
          id: carMesh
          meshName: "13914_Taxi_car"
          source: "qrc:/Taxi/13914_Taxi_v2_L1.obj"
          onStatusChanged: { console.log("Taxi: status=" + status); }
      }

      Upon inspecting the 13914_Taxi_v2_L1.obj , I can see it defines named groups using the g tag, as in:

      ...
      
      g 13914_Taxi_car
      usemtl 13914_Taxi_car
      s 2
      f 37559/39651/36283 37560/39652/36284 37561/39653/36285 37562/39654/36286  
      ...

      So I would expect Mesh to be able to load just this part of the model. Am I right to assume this?

      Unfortunately, using a meshName that doesn't exist in the wavefront file also doesn't generate errors/warnings/problems and the entire mesh gets loaded instead.

      I attached a small, reproducible and compilable example to this ticket that also contains the 3D model to facilitate testing.

      Am I using it wrong? The documentation is almost non-existent on this topic.

      Attachments

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

        Activity

          People

            seanharmer Sean Harmer
            karlbuhr Karl Buhr
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes