Open SeanCurtis-TRI opened 10 months ago
Note: back when the only visualizer was drake_visualizer
this wasn't a problem as both visualizers used VTK as their rendering back bone.
For reference -- are the primitive texture coordinate conventions documented (promised) in any of our API materials anywhere?
What happened?
We allow texture maps to be applied to primitives. These textures appear in the render engine implementations. Effort was made to have the same set of texture coordinates between
RenderEngineGl
andRenderEngineVtk
(and we getRenderEngineGltfClient
for free as it inherits fromRenderEngineVtk
). For historical reasons, the VTK texture coordinates (where provided) have been the de facto definition of Drake's primitives' texture coordinates.However, the texture coordinates defined by three.js for the primitives does not match VTKs (as they both make arbitrary decisions). It would be better if Drake presented a unified world whether rendering or displaying in meshcat.
The practical solution is to transform the textures in one domain to match the others. Several thoughts:
RenderEngine
s implementations to be simpler as they live in the Drake process.Version
No response
What operating system are you using?
No response
What installation option are you using?
No response
Relevant log output
No response