You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently developing my own modifications of this for my project, but I think having full native support for setting numDimensions to 2 would be nice, considering I've found it to be more performant than using the regular 2D Force Graph, at least with my medium-large dataset. By 'full support', I mean disabling rotation, using an orthographic camera instead of a perspective one, making zoom relative to mouse position rather than the viewport center, and similar functionalities that make it act more like the 2D version of Force Graph while also using ThreeJS.
This is the app I am currently using Force Graph in. It has a 2D mode that uses the regular Force Graph, and a 3D mode that uses the 3D one. On my phone, 2D mode is so slow it's unusable, while 3D runs just fine. Both could be further optimized, but I believe there are definitely some advantages to the way the ThreeJS implementation is rendered that can make it more performant for larger datasets.
The text was updated successfully, but these errors were encountered:
I am currently developing my own modifications of this for my project, but I think having full native support for setting numDimensions to 2 would be nice, considering I've found it to be more performant than using the regular 2D Force Graph, at least with my medium-large dataset. By 'full support', I mean disabling rotation, using an orthographic camera instead of a perspective one, making zoom relative to mouse position rather than the viewport center, and similar functionalities that make it act more like the 2D version of Force Graph while also using ThreeJS.
This is the app I am currently using Force Graph in. It has a 2D mode that uses the regular Force Graph, and a 3D mode that uses the 3D one. On my phone, 2D mode is so slow it's unusable, while 3D runs just fine. Both could be further optimized, but I believe there are definitely some advantages to the way the ThreeJS implementation is rendered that can make it more performant for larger datasets.
The text was updated successfully, but these errors were encountered: