search

vasturiano / 3d-force-graph-ar

3D force-directed graph component in AR
https://vasturiano.github.io/3d-force-graph-ar/example/async-load/
MIT License
93 stars 21 forks source link

Three.SpriteText throws raytracer error, sprites seems malfunctioning... #14

Open alexanderevgrafov opened 1 year ago

alexanderevgrafov commented 1 year ago

Three.SpriteText lib seems not compatible with current 3d-force-graph-ar due THREE.Sprite: "Raycaster.camera" needs to be set in order to raycast against sprites. error

To Reproduce GoTo examples https://vasturiano.github.io/3d-force-graph-ar/example/text-nodes/ or https://vasturiano.github.io/3d-force-graph-ar/example/text-links/ and check dev console.

Permanently reproducible at least on MacOS Catalina with Chrome Version 111.0.5563.146

but sure this is not platform-dependent story

vasturiano commented 1 year ago

@alexanderevgrafov thanks for reaching out.

This is a known issue related to aframe.

Please see: https://github.com/vasturiano/3d-force-graph-ar/issues/10 https://github.com/vasturiano/3d-force-graph-vr/issues/31#issuecomment-1043570188 https://github.com/aframevr/aframe/issues/5042

vid commented 1 year ago

Is there a way we can help resolve this ,or work around it? I always come back to this library because it seems so great at making information clear, but there seem to be a lot of unresolved issues with important functionality. Should we pile on to an issue, fund something? Thank you!