Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

fetch_snapshot of a textured mesh

See original GitHub issue

Hello, this project is so great. Especially, fetch_snapshot is wonderful.

I enjoyed snapshots and found that the texture of a mesh is not dumped. The following code successfully presents a textured rectangle,

    plt_texture = k3d.mesh(
        vertices=[[0,0,0],[img_shape[1],0,0],[img_shape[1],img_shape[0],0],[0,img_shape[0],0]],
        indices=[[0,1,2,],[2,3,0]],
        uvs=[[0,0],[1,0],[1,1],[0,1]],
        texture=open(img_path,'rb').read(),
        texture_file_format=splitext(img_path)[1],
    )
    plot += plt_texture

but an error occurs when opening the dumped snapshot.

The length of the snapshot is only 125 for this object, so I think texture data is not dumped at all. I really appreciate it if it is supported.

Issue Analytics

State:
Created 2 years ago
Comments:5

Top GitHub Comments

1reaction

artur-trzesiokcommented, Jul 8, 2021

K3D@2.9.7 is released on pypi (and soon on conda-forge) - https://pypi.org/project/K3D/2.9.7/ . Please check a new version that should contain fix for this issue.

1reaction

artur-trzesiokcommented, Jun 28, 2021

Ok. This change https://github.com/K3D-tools/K3D-jupyter/commit/61ff4f81ba8b5fc19d0840f86de617d5f4d07138 provide new serialization behaviour of Bytes but we adapted it only for STL. Right now that will be quick to fix it ! 👍