Open source social vr platform, Godot matrix/mastodon client, XR collaborative creation tool! (WIP)
  • GDScript 94.8%
  • GDShader 5.1%
  • Shell 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-10-26 00:36:18 -04:00
.github built automated build and release deployment with git workflows 2026-02-12 11:42:07 -08:00
.vscode MOVED TO 4.3 RC3, various small changes to ui and small bug fixes. started preparation of voip. many in-progress changes put on hold because of issues with gdextensions. this build may not work but i will fix it soon. 2024-08-09 20:24:32 -06:00
addons updated godot xr vendors plugin 2026-10-26 00:36:18 -04:00
android added searchbox for attributes 2026-08-29 15:21:56 -04:00
barkvr-system proto: added some controls for touch screens 2026-10-24 12:08:13 -04:00
exports Add .gdignore to exports directory to avoid Godot from importing files from exports directory 2026-08-30 14:46:59 -03:00
webrtc - removed an is_instance_valid check because returning false for nodes that arent actually invaid. its unclear if this is an engine problem or if the nodes are somehow getting marked as free? fixes #42 2025-11-14 20:08:35 -08:00
.gitattributes Add GitAttribute File 2025-11-23 16:13:39 +01:00
.gitignore just learned i wasn't supposed to exclude the .import files -_- 2025-01-17 07:44:01 -07:00
.gitmodules moved voxel and file drop imports to use WorkerThreadPool instead of explicit threads, added output/input audio device selectors, extended local ui a bit, added passthrough button (for headsets that support it), added some beginnings of hand tracking interaction, various other small changes/fixes 2024-07-14 18:13:27 -06:00
default_bus_layout.tres massively reduced base CPU load by reducing the quality of the audio effect used to get local mic volume and fft information, minor project settings tweaks, added new generated openxr_action_map 2026-05-30 16:30:53 -04:00
export_presets.cfg add web export option 2026-10-10 19:17:12 -04:00
LICENSE updated license to include contributors, minor changes 2025-03-10 21:39:35 -06:00
LICENSE.txt * moved helpers to library folder since now there are two library or helper like global function sets. it just makes sense 2025-11-14 23:52:51 -08:00
openxr_action_map.tres added new xr action map with all the profiles enabled so we can support all the platforms 2026-09-02 13:27:34 -04:00
project.godot disable emulate mouse from touch, enable xr frame synthesis, enable mobile sensors 2026-10-23 19:05:14 -04:00
README.md docs: Fix formatting style of contribution guidelines 2026-09-16 14:01:51 -05:00


Discord | Matrix

BarkVR is an open-source and decentralized social XR creativity tool, built upon the solid foundation of Godot 4.x.

Warning

Please keep in mind that this software is not secure in its current state. It is a completely open tool that exposes Godot functionality to you and any other user you connect to. This will likely remain true until the first alpha. The first alpha will contain security and network sync exclusions to allow you to prevent users from pushing code to your device unless you clearly and explicitly allow it. But those features are not ready yet.

Status:

The project will be releasing an alpha build shortly. Please feel free to support the project however you wish, or not at all.

Core Focus:

  • Accessibility: Making BarkVR welcoming to everyone, regardless of background or ability.
  • Decentralized Design: Giving users the freedom to create without borders and no reliance on a login system.
  • User Empowerment: Providing users with complete control over their creations.
  • Open Design: Welcoming collaboration, transparency, and teaching to evolve BarkVR together.
  • Social VR: Creating a space where connections thrive beyond physical limits, fostering shared experiences and boundless imagination.

We are working to incorporate technologies like Activitypub (and matrix) for user management, ppfs or any other static file hosting, and WebRTC/QUIC for the peer connections for our storage solution. This means the whole platform is completely open and capable of being run/hosted without any reliance on the maintainers.

Features:

  • Real-time networked scene editing of any object in the shared Godot scene
  • Real-time voice over IP, using the gdopus utility
  • Real-time GDScript loading (a virtual scripting environment is planned for the future for security)
  • Runtime import of any asset supported by Godot with some extensions (vrm, gltf, fbx, images, audio)
  • Full-fledged chat and call system through matrix (calling features are still partially WIP)
  • Spatialized VoIP using Opus
  • Full peer-to-peer mesh networking with WebRTC with PAXOS state resolution (PAXOS library WIP)
  • Generative audio tools (can load samples, act as a modular synthesizer/FM-synth | WIP)
  • Full modeling, rigging, and texturing tool-set (supports voxel based mesh drawing | WIP)

Contributing

All contributions are welcome, whether that's through GitHub issues, messaging contributors (especially zodiepupper, so I can organize things correctly) directly, emailing the support email barkvrsupport@pupper.dev, or submitting PRs!!

Rules:

  • Contributions should be presented, and handled in all aspects with respect and compassion for all involved.
  • Contributions and statements made by contributions should:
    • MUST NOT be hateful, or made with the intention of causing harm
    • MUST NOT be discriminatory against any specific type of person
    • MUST NOT be in support or in the interest of any Nazi ideals, hateful rhetoric, or suggesting ill fate on any group

Important

This is not a place for politics that are unrelated to this project, and it is not a place for people to be hateful. If you contribute here, you are expected to treat others with kindness, love, and respect in all ways. If you don't give it, you don't deserve it.

Guidelines:

  • In-Code Documentation:
    • SHOULD be clear and concise
    • SHOULD NOT expect the reader to have prior knowledge about the project (within reason)
  • Commit Messages:
    • SHOULD be straight to the point
    • SHOULD reasonably say what was done (and if applicable, why)
  • Pull Requests:
    • SHOULD be concisely state what is being changed as the title
    • SHOULD have a description that is as detailed as an Issue regarding the same topic would be
    • SHOULD contain 1 commit per discrete change
    • SHOULD focus on a single bug/issue/feature request and solving it quickly
  • Issues:
    • SHOULD be concise and explain the problem
    • SHOULD explain the expected end result
  • GenAI Usage:
    • Contributions MUST NOT contain LLM generated content. For further discussion along this topic, please contact zodiepupper directly.

Tip

It is recommended that Issues be conversational and informal, but formal is also fine. Don't be shy!

for support, help, or anything really:

email: barkvrsupport@pupper.dev fax: +1-208-848-3252

Thank you for being here, thank you for being interested

Let's make something cool together!!

For latest, look at the "dev" branch!