2be87fe7dc
Fix for MyAvatar sometimes hovering off the ground after foot tracking was enabled. MyAvatar's body is now recentered when foot-tracking starts or ends (in MyAvatar::update). Repro: - Start without foot tracking, 'Allow my avatar to stand: Always'. - Crouch, and wait a few seconds for the avatar to pop back to the standing position. - Slowly stand straight so that the avatar raises off the ground without recentering (PS: is this a bug?). If it recenters, retry from previous step. - Calibrate foot tracking. Previously the avatar would remain hovering off the ground until MyAvatar::centerBody was called. Fix for MyAvatar popping to a standing position if the left foot lost tracking. The recentering now takes into account if either of the feet are tracked. Repro: - Enable foot tracking (and ideally hips tracking). - Sit on the floor. - Cover the left foot sensor so it loses tracking. Previously the avatar and viewpoint would pop to a standing position. Optimisation: MyAvatar::update now stores bools indicating which body parts are tracked (_isBodyPartTracked). This avoid unnecessary computations that came from using getControllerPoseInAvatarFrame to convert controller::Pose from sensor space to world space and then to avatar space, only to check if the pose was valid. |
||
|---|---|---|
| .github/workflows | ||
| android | ||
| assignment-client | ||
| cmake | ||
| debian | ||
| docs | ||
| domain-server | ||
| ice-server | ||
| interface | ||
| launchers | ||
| libraries | ||
| pkg-scripts | ||
| plugins | ||
| screenshare | ||
| script-archive | ||
| scripts | ||
| server-console | ||
| tests | ||
| tests-manual | ||
| tools | ||
| unpublishedScripts | ||
| .clang-format | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| BUILD.md | ||
| BUILD_ANDROID.md | ||
| BUILD_LINUX.md | ||
| BUILD_LINUX_CHEATSHEET.md | ||
| BUILD_OSX.md | ||
| BUILD_WIN.md | ||
| CMakeGraphvizOptions.cmake | ||
| CMakeLists.txt | ||
| CODING_STANDARD.md | ||
| CONTRIBUTING.md | ||
| hifi_android.py | ||
| hifi_qt.py | ||
| hifi_singleton.py | ||
| hifi_utils.py | ||
| hifi_vcpkg.py | ||
| INSTALLER.md | ||
| LICENSE | ||
| prebuild.py | ||
| README.md | ||
| README_hifi.md | ||
| VCPKG.md | ||
Vircadia
What is this?
Vircadia is a 3D social software project seeking to incrementally bring about a truly free and open metaverse, in desktop and XR.
Download
Releases
How to build the Interface
How to deploy a Server
How to build a Server
How to generate an Installer
For Linux - AppImage - Vircadia Builder
Boot to Metaverse: The Goal
Having a place to experience adventure, a place to relax with calm breath, that's a world to live in. An engine to support infinite combinations and possibilities of worlds without censorship and interruption, that's a metaverse. Finding a way to make infinite realities our reality is the dream.
Boot to Metaverse: The Technicals
Many developers have had personal combinations of High Fidelity from C++ modifications to different default scripts, all of which are lost to time as their fullest potential is never truly shared and propagated through the system.
The goal of this project is to achieve the metaverse dream through shared contribution and building. Setting goals that are achievable yet meaningful is key to making proper forward progress on the technical front whilst maintaining morale.
Why High Fidelity's Virtual Reality Platform?
Because of all the options, it is the only starting point that is open-source, cross-platform, fully VR integrated + fully desktop integrated with an aim for quality visuals and performance. It also provides a foundation to build from including components like entity management, full body IK, etc.
WebXR offers the open-source and decentralized aspect but does not have any of the full featured starting points such as avatars, IK, etc. which means that a lot of ground work will have to be laid to make something functional. Far more work will need to be done to create a truly seamless and extensive experience as well.
Platforms like NeosVR or VRChat are not viable from go due to their fundamental closed-source and centralized nature. A metaverse to live in cannot have the keys handed over to any singular entity, if any at all.
We need to do the best we can with what we've got and our best bet as open source developers is to not redesign the wheel if we can help it!
Contribution
A special thanks to the contributors of Vircadia.