Will Eastcott
Will Eastcott
I agree with this 100%. `playcanvas-sync` should definitely be distributed and work as you describe IMHO.
@zachpeterpaul Not on Windows, it doesn't.
@Casval111 Just a note that the [Texture Tool](https://playcanvas.com/texture-tool) has been updated to allow you to generate the `envAtlas` texture.
Great! Thanks for this @LeXXik. Some comments: 1. Why has `package-lock.json` changed in this PR? 2. `_updateDynamic` and `_getEntityTransform` are very sensitive to performance changes. I'm wondering if it would...
The message no longer appears in the console with 1.57.1. Closing.
So presumably you can do this from a script with: ```javascript const button = this.entity.button; button.on('hoverstart', () => { document.body.style.cursor = 'pointer'; }); button.on('hoverend', () => { document.body.style.cursor = 'default';...
Sorry - hit close by mistake 😉
Don't you make your buttons as template assets? Would that make managing them all easier?
Those original near and far clip planes seem very reasonable to me. I do wonder whether something else might be at play here. For example, can you verify your camera...
So if async defaults to true, won't this change the behavior of existing PlayCanvas projects out there? There'll be meshes popping into view instead of the main thread blocking until...