All actions can be invoked from a 3D environment; this includes loading other scenes, more/new 3D objects, changing lights, skyboxes, colours, textures, etc. Note that exploration and movement through an environment would involve one of more 3D objects, rather than a skybox.

The post What’s the best way to create an environment that can be navigated? appeared first on MetaVRse.

With a mouse and keyboard, or a touch-enabled experience (somewhat like Fortnite). All avatars can be animated and controlled in our web Editor. We can also build out those feature sets as per client requirements.

The post How can a user control an avatar in the environment? appeared first on MetaVRse.

Our system supports two different rendering modes: Blinn-Phong and physically based rendering (PBR). Diffuse, Reflections, and Specular are all part of the Blinn-Phong shader, which does not support PBR; as a result, it has an alternate set of standards when referring to the naming conventions of the texture files. The MetaVRse Engine is able to toggle between these two standards.

Once PBR is turned off the names of the Drag and Drop windows will change to Diffuse, Reflections, and Specular. Our system is also capable of interpreting the Blinn-Phong textures as PBR and can be applied in the following way:

• Diffuse = Albedo
• Reflections = Roughness
• Specular = Has no equivalent and is therefore not utilized

The post What should I do if the texture settings are different from what I expect? appeared first on MetaVRse.

Absolutely, our platform is fully modular and flexible, ready to adopt custom HUDs and frontend solutions. Everything from the frontend perspective is fully customizable and client-oriented. If you require a custom solution, please contact us.

The post Am I able to create a frontend editor on top of your solution? appeared first on MetaVRse.

Our platform is modular and fully customizable to the needs of our clients. If there are missing features or capabilities, we would be happy to do a custom integration. Please let us know your requirements and challenges by contacting us.

The post What should I do if we need capabilities that the MetaVRse platform doesn’t provide? appeared first on MetaVRse.

MetaVRse Engine rendering takes place on the local host device (phone, laptop, tablet etc.). Our cloud services are modeled around the seamless hosting and serving of 3D experiences to all devices. We have discussed hybrid rendering to offload some of the heaviest tasks to the edge; however at this time it is not our primary focus, as the 5G infrastructure required is still in its infancy.

On a broader level, there are advantages and disadvantages to both approaches. Rendering on local devices is a more reliable and stable solution that is not so dependent on a steady super-fast connection. As personal devices get more powerful every year, their capabilities to render complex 3D experiences increases exponentially. Cloud rendering, on the other hand, has limitless computing potential, and with a stable and fast 5G connection can render life like experiences. The downfall is that it is still prohibitively expensive for the average user to pay for continuous access to cloud-enabled high-power GPUs, and stable 5G-connected devices and infrastructure are still very scarce.

The post Why do you use device-based rendering rather than cloud-based rendering? appeared first on MetaVRse.

We currently do not have the ability to perform body and facial tracking. That being said, our system has the capabilities required to perform both tasks, and an out-of-the-box integration is part of our mid-term roadmap. Our development priorities are responsive to customer needs.

The post Do you provide integration with face and body tracking? appeared first on MetaVRse.