UV coordinates ignored by MeshOBJLoader #3012

Activity

1. ScheiklP

   added

   issue: bug (minor)Bug affecting only some users or with no major impact on the frameworkBug affecting only some users or with no major impact on the framework

   on Jun 7, 2022
2. ScheiklP commented on Jun 7, 2022

   

   ScheiklP

   on Jun 7, 2022

   Last edited by ScheiklP

   ContributorAuthor

   More actions

   Did some more digging.

   In the code above texcoords=loader.texcoords, is not valid, because the loader did not actually read any data yet.

   

   Changing it to

   loader = visual_node.addObject(
           "MeshOBJLoader",
           filename="mesh.obj",
           handleSeams=True,
   )
   
   loader.init()
   
   visual_node.addObject(
           "OglModel",
           texcoords=loader.texcoords,
           texturename="texture.png",
   )
   

   fixed the issue. Is this still valid behavior?
3. epernod commented on Jun 7, 2022

   

   epernod

   on Jun 7, 2022

   Contributor

   More actions

   yes you need to use handleSeams = true if you want to use the vertices buffer + texcoords.
   But this mode can't be used as input of a mechanical mesh because some vertices are duplicated for the UV coordinates.
4. ScheiklP commented on Jun 7, 2022

   

   ScheiklP

   on Jun 7, 2022

   Last edited by ScheiklP

   ContributorAuthor

   More actions

   handleSeams = True was set in both cases. The main problem was that the loader was not initialized.
   It worked best (also without the init) when passing the LinkPath, and not the data container itself.
   So I guess this is more a thing of having example code than a bug.

   Where would be the best place to document an example like this?

   loader = visual_node.addObject(
           "MeshOBJLoader",
           filename="mesh.obj",
   )
   
   visual_node.addObject(
           "OglModel",
           texcoords=loader.texcoords.getLinkPath(),
           texturename="texture.png",
   )
   
5. damienmarchal commented on Jun 9, 2022

   

   damienmarchal

   on Jun 9, 2022

   Last edited by damienmarchal

   Contributor

   More actions

   Hi @ScheiklP

   Thanks for reporting and you are right in your conclusion (it is because that the object does not need to be initialize when created in python).

   Actually getting rid of the need to init the data is a long standing issue: see sofa-framework/SofaPython3#173

   This PR is probably the place to have future discussion on that topic and I close the issue,

   👍React with 👍1Reacted by Paul Maria Scheikl
6. damienmarchal

   closed this as completedon Jun 9, 2022