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
Hi @mwbeene,
Are your interested in transferring ownership of this repository to the c-frame organization so other maintainers like me can help with the PRs and issues? If you are I'll invite you to the c-frame organization so you can transfer the repository. I'll also need to have the owner permission on npm (username vincentfretin) so I can make new releases.
If you don't want to add new features to the component, I'll respect that. I'll just create a fork in the c-frame organization and release the fork as @c-frame/cursor-teleport, but I wanted to suggest the transfer first before doing so.
Some changes I have in my personal project that could be contributed here:
Raycast only on click, don't show the cursor on mousemove on desktop (could be an option, to be discussed)
If we have a raycaster on scene, ignore all objects of this raycaster (or a variant of it, to be discussed)
Disable simple-navmesh-constraint during teleport transition if it's used (we should do the same if you're using movement-controls with constrainToNavMesh:true)
Add new API teleportTo(position, quaternion), quaternion optional, with rotation y transition, also fix look-controls pitchObject.rotation.x if needed, to be used via buttons to change camera view
Other changes I was thinking:
Update the build dependencies (webpack)
Add a color property to change the color of the cursor.
The text was updated successfully, but these errors were encountered:
The repo was transferred in the c-frame organization and I have now the right to publish on npm.
Thank you @mwbeene!
I'll create separate issues for the above later.
Hi @mwbeene,
Are your interested in transferring ownership of this repository to the c-frame organization so other maintainers like me can help with the PRs and issues? If you are I'll invite you to the c-frame organization so you can transfer the repository. I'll also need to have the owner permission on npm (username vincentfretin) so I can make new releases.
If you don't want to add new features to the component, I'll respect that. I'll just create a fork in the c-frame organization and release the fork as
@c-frame/cursor-teleport
, but I wanted to suggest the transfer first before doing so.Some changes I have in my personal project that could be contributed here:
Other changes I was thinking:
The text was updated successfully, but these errors were encountered: