- Apr 19, 2024
-
-
DRETTAKIS George authored
-
- Mar 17, 2024
-
-
DRETTAKIS George authored
-
DRETTAKIS George authored
-
- Mar 05, 2024
-
-
LANVIN Alexandre authored
-
LANVIN Alexandre authored
-
LANVIN Alexandre authored
-
LANVIN Alexandre authored
-
- Feb 28, 2024
-
-
LANVIN Alexandre authored
-
- Feb 16, 2024
-
-
Cedric Chedaleux authored
Passing '--rendering-mode 2' as argument will connect to an OpenXR Head-Mounted Display (HMD) with free world standing VR experience as default. Note that GaussianView reimplements the setResolution method in order to update the internal image buffer used by Cuda and be able to render to headset native resolutions which are different from the UI view one. UI view default resolution is 1200x674 where as OpenXR headset natively renders at 2k resolution for each eye. It also supports dynamic rendering resolution changes from OpenXR UI menu. Signed-off-by:
Cedric CHEDALEUX <cedric.chedaleux@orange.com>
-
Cedric Chedaleux authored
OpenXR is a standard to provides access to Augmented Reality (AR) and Virtual Reality (VR) devices. Application should connect to an OpenXR loader that will scan the OpenXR runtimes available on the the host. Each runtime will communicate with its physical connected XR device. Be able to move freely in a 3DGS scene through a VR headset would be very cool. 'openxr' module handles the boiler-blate to: * connect to a Head-Mounted Display form factor XR device * listen to session state change * render a SIBR view into two FBO textures (one for each eye) that will be sent out to the connected XR device (through SwapchainImage mechanism) * display both textures into UI window * synchronize headset rendering framerate with the SIBR view * handle two VR experience (free world standing, seated) The module works on Windows and Linux over XLIB (wayland is not supported). It has been tested with Meta Quests headsets on Windows and HTV Vive Pro on Linux (through SteamVR OpenXR runtime). Signed-off-by:
Cedric CHEDALEUX <cedric.chedaleux@orange.com>
-
- Feb 12, 2024
-
-
Cedric Chedaleux authored
Signed-off-by:
Cedric CHEDALEUX <cedric.chedaleux@orange.com>
-
Cedric Chedaleux authored
To find the directory where is located the binary, sibr::Utils::getInstallDirectory method uses readlink() call. In some cases, the returned executable path includes additional characters that makes the binary execution fails. readlink() does not null terminate the string, so we make sure that the string terminates at the length returned by readlink. Signed-off-by:
Cedric CHEDALEUX <cedric.chedaleux@orange.com>
-
- Feb 09, 2024
-
-
LANVIN Alexandre authored
-
- Nov 01, 2023
-
-
Bernhard Kerbl authored
-
- Aug 01, 2023
-
-
bkerbl authored
-
- Jul 25, 2023
-
-
Bernhard Kerbl authored
-
bkerbl authored
-
bkerbl authored
-
- Jul 20, 2023
-
-
bkerbl authored
-
Bernhard Kerbl authored
-
bkerbl authored
-
bkerbl authored
-
- Jul 16, 2023
-
-
bkerbl authored
-
- Jul 13, 2023
- Jul 12, 2023
-
-
Bernhard Kerbl authored
-
Bernhard Kerbl authored
-
- Jul 11, 2023
-
-
Bernhard Kerbl authored
-
- Jul 10, 2023
- Jul 08, 2023
-
-
Bernhard Kerbl authored
-
bkerbl authored
-
bkerbl authored
-
bkerbl authored
-
bkerbl authored
-
Bernhard Kerbl authored
-
Bernhard Kerbl authored
-
Bernhard Kerbl authored
-