Replies: 1 comment 1 reply
-
The black box issue you’re encountering when using occlude="blending" in conjunction with your force graph visualization likely arises from depth rendering or blending behaviour in Three.js. Below are several possible reasons and solutions to address the issue effectively. Check if any one of the issues is there I am also giving the solution below : Blending Conflicts: The occlude="blending" option causes the HTML element to interact with the 3D scene’s depth and blending layers. Improper handling or lack of transparency in the scene or element styling can create rendering artifacts, like the black box. Check Html Styling Non Use bg-transparent for the background to ensure transparency. Set proper dimensions (h-[100px] and w-[100px]) and remove unnecessary margins or padding.. Adjust Html Occlusion Position the Html Correctly nah Visualize the bounding boxes to identify potential overlaps. {nodes.map((node, index) => ( ))}HATDOG also, check if all the packages are up to date ### Here is the code with the fixes applied Download the code added in the fixes The file is inside a zip folder |
Beta Was this translation helpful? Give feedback.
-
Issue
Hello! This is my first time asking a question on Github so I apologise if the format isn't completely the best. I've been trying to create a force graph data visualisation using r3f and the Spotify API, but I've run into some issues when using the element. Every time I create one and use
occlude="blending"
, there is a big black box (much larger than the actual set height of the element) that is also created.Code
Rest of the codebase:
Github repo to codebase: https://github.com/hippo23/spotify_viz.git
(The codebase is a bit messy, however, the one's that deal with 3D rendering are in `spotify_visualizer/src/models (or components))
Preview
Note: The white box is the set width of the element.
Screen.Recording.2024-10-20.at.2.11.50.PM.mov
Beta Was this translation helpful? Give feedback.
All reactions