Skip to content

Open source social vr platform, Godot matrix client, XR collaborative creation tool! (WIP)

License

MIT, MIT licenses found

Licenses found

MIT
LICENSE
MIT
LICENSE.txt
Notifications You must be signed in to change notification settings

zodiepupper/barkvr

Repository files navigation

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 power to shape BarkVR's world through decentralization.
  • User Empowerment: Providing users with complete control over their creations for a sense of ownership.
  • Open Design: Welcoming collaboration and transparency 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 the Matrix messaging API for user management, ppfs or any other static file hosting, and WebRTC 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

Tip

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

Thank you for being here, thank you for being interested

Let's make something cool together!!

For latest, look at the "dev" branch!

About

Open source social vr platform, Godot matrix client, XR collaborative creation tool! (WIP)

Topics

Resources

License

MIT, MIT licenses found

Licenses found

MIT
LICENSE
MIT
LICENSE.txt

Stars

Watchers

Forks

Sponsor this project