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
{{ message }}
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.
I'm not sure if issues about HoloPlay Core JS go here or this is only for the old Three JS version.
With the current holoplay-core (0.0.8), every time a message is sent the word "message" is printed to the console, which results in thousands of prints if you are drawing an animation (one console.log for every frame).
I guess the message should only print if the debug option was enabled, but that is not the case now.
The text was updated successfully, but these errors were encountered:
Hi! You found the right place! That's less than ideal indeed. However, we're currently working on a major refactor of our entire API - as such, we're not making incremental improvements to this product at this time.
I'll keep you posted on updates to the new API as they're coming! Also - saw your work with p5 - very cool!
Hi, Thanks for your work!
I'm not sure if issues about HoloPlay Core JS go here or this is only for the old Three JS version.
With the current holoplay-core (0.0.8), every time a message is sent the word "message" is printed to the console, which results in thousands of prints if you are drawing an animation (one console.log for every frame).
I guess the message should only print if the debug option was enabled, but that is not the case now.
The text was updated successfully, but these errors were encountered: