Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spawner copies created too far from user #5634

Open
qiangjiadong opened this issue Aug 3, 2022 · 1 comment
Open

Spawner copies created too far from user #5634

qiangjiadong opened this issue Aug 3, 2022 · 1 comment
Labels
bug needs triage For bugs that have not yet been assigned a fix priority P3 Backlog

Comments

@qiangjiadong
Copy link

Description
When making copies of any Spawner objects, the copied object is too far from the user and the original position of the Spawner object

To Reproduce
Steps to reproduce the behavior:

  1. create a default new scene
  2. Add 'default Spawner'
  3. Publish the scene with a room
  4. Interact with the Spawner
  5. See error (or use this room to test https://hubs.mozilla.com/Pb3unvq/striped-majestic-picnic)

Expected behavior
the copied object is close to the user and the original position of the Spawner object.

Screenshots
微信截图_20220803124203

Hardware

  • Device: [Desktop
  • OS: [Windows, iOS, Linux]
  • Browser: [Chrome]

Additional context
This error might also relate to bug #5620

@qiangjiadong qiangjiadong added bug needs triage For bugs that have not yet been assigned a fix priority labels Aug 3, 2022
@emclaren emclaren added the P3 Backlog label Aug 3, 2022
@BabeleDunnit
Copy link

I did some tests.

first of all, everything works like a charm on the Quest (default browser), both grabbing object and materializing them from distance with the in-world cursor works perfectly.

On desktop (macOS, Chrome):

I made several test about objects geometry and the issue seems unrelated with it. I scaled objects, reset their transformations by "apply all transform" in Blender, moved their origin, changed the scale applied from the spawner node itself. I now have some mugs which are spawned with a null spawner transformation and sometimes they work, sometimes they don't. I cannot see any pattern, it seems completely random.

It SEEMS that the spawner works better with BIG objects (before scaling them my mugs were 1 mt high), but I am not sure if this is just an effect of the object being bigger and less prone to be translated out of the walls, etc. Maybe it is translated exactly of the same amount but you do not notice it just because is bigger.

On mobile devices (tested on Chrome on an iPhone and Safari on iPad Pro): the spawner works as expected.

I made these tests from a Blender scene, exporting with the Hubs Blender Add-on, with both gravity enabled and disabled, and loading the scene in spoke (via the "add new scene" glb direct upload, NOT importing the GLB in spoke and publishing from there).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage For bugs that have not yet been assigned a fix priority P3 Backlog
Projects
None yet
Development

No branches or pull requests

3 participants