Have issues with scene share/hub when I open in AR mode and load or reload scene and sometimes when scrolling and using hand tracking the menu becomes stuck to hand and will not release unless exit and refresh and reload game. I have been able to get this glitch to repeat multiple times simply by scrolling and loading others scenes/positions.
Hmm. I just saw a similar symptom in AR + Hand Tracking. In my case, the menu went too far out so it was not possible to click it. I’ll try to fix this today.
(it’s fixed now)
Last edited 1 year ago by RockHardVR Admin
Blixeree
1 year ago
Good improvement, thanks!
Blixeree
1 year ago
Being able to update a scene seems hit or miss. I’d usually expect to be able to push an update when I either open up a previous file from my private collection or download a file from the public share that I’dcreated previously. I do notice that the system appears to know my ID since it pre-populates it on a new share. This isn’t to say that it doesn’t work at all. I think it gets triggered after I’ve initially uploaded a new file and then I can update it, but only during that session. I’ll see if I can get more specifics. I suspect this is why we still see what appears to be duplicate poses being submitted to the gallery or people may just be saving versions in private.
That’s right. Update is activated either when the current scene has been downloaded from the server, or at the moment it has been uploaded.
I didn’t think about what happens if a user downloads a scene from server, and load a private collection. (consider server having an old version, and private having a new version) This should be able to update. I’ll check.
I’ll implement a method to check for duplicates from a user, and block them like it does in Body Share.
I rather not prevent someone downloading a scene and uploading it under his nickname, because it is meant to be a storage first.
Even if the pose gallery becomes total chaos like Body Share, registered users can always bump their scenes. 😉
Got it. I think it’s ok to have the public and private versions separately updating but yeah, some change should have occurred to trigger the ability to do an update, otherwise it’s not an update. Unless I guess someone just wants to update the screenshot. On the other hand, if someone downloads someone else’s scene, they shouldn’t be able to update the file until they fork their own new version. Then, of course, they should be able to push public updates on that one or if it’s in their private collection. Anyways, in the end, probably not the biggest deal of its fixed or not, but would be nice since it definitely creates a certain amount of redundancy.
I’m upgrading the private collection now. I better take care of the update function in private collection this time.
If current scene is loaded from private, private will be updated. If it’s from scene share, scene share will be updated. That looks like the simplest way.
Have issues with scene share/hub when I open in AR mode and load or reload scene and sometimes when scrolling and using hand tracking the menu becomes stuck to hand and will not release unless exit and refresh and reload game. I have been able to get this glitch to repeat multiple times simply by scrolling and loading others scenes/positions.
Hmm. I just saw a similar symptom in AR + Hand Tracking. In my case, the menu went too far out so it was not possible to click it. I’ll try to fix this today.
(it’s fixed now)
Good improvement, thanks!
Being able to update a scene seems hit or miss. I’d usually expect to be able to push an update when I either open up a previous file from my private collection or download a file from the public share that I’dcreated previously. I do notice that the system appears to know my ID since it pre-populates it on a new share. This isn’t to say that it doesn’t work at all. I think it gets triggered after I’ve initially uploaded a new file and then I can update it, but only during that session. I’ll see if I can get more specifics. I suspect this is why we still see what appears to be duplicate poses being submitted to the gallery or people may just be saving versions in private.
That’s right. Update is activated either when the current scene has been downloaded from the server, or at the moment it has been uploaded.
I didn’t think about what happens if a user downloads a scene from server, and load a private collection. (consider server having an old version, and private having a new version) This should be able to update. I’ll check.
I’ll implement a method to check for duplicates from a user, and block them like it does in Body Share.
I rather not prevent someone downloading a scene and uploading it under his nickname, because it is meant to be a storage first.
Even if the pose gallery becomes total chaos like Body Share, registered users can always bump their scenes. 😉
Got it. I think it’s ok to have the public and private versions separately updating but yeah, some change should have occurred to trigger the ability to do an update, otherwise it’s not an update. Unless I guess someone just wants to update the screenshot. On the other hand, if someone downloads someone else’s scene, they shouldn’t be able to update the file until they fork their own new version. Then, of course, they should be able to push public updates on that one or if it’s in their private collection. Anyways, in the end, probably not the biggest deal of its fixed or not, but would be nice since it definitely creates a certain amount of redundancy.
I’m upgrading the private collection now. I better take care of the update function in private collection this time.
If current scene is loaded from private, private will be updated. If it’s from scene share, scene share will be updated. That looks like the simplest way.
Thanks, that sounds like a good approach.
I waited this option! Good work! Pose simulator is amazing, very funny to play