Doesn't affect slave cameras mode ( -prop:/sim/vr/mode=SLAVE_CAMERAS), as slave cameras are positioned correctly.Affects default / scene view mode ( -prop:/sim/vr/mode=AUTOMATIC), as stereo callbacks position cameras.Spotlights (taxi/landing lights) are relative to camera in default mode.Sun position is fixed relative to head, presumably because shadow maps are rendered based on master camera, but osgXR only moves slave cams.When shadows are enabled, the FlightGear window doesn't appear to refresh even though buffers are swapped, but VR output works.Performance could be better so crank down the graphics if frame rate is low.Splash screen is rendered directly onto the left eye viewport which isn't very pleasant in VR.Get started on other controller interaction and controller rendering.Continue to polish controller flight support, add haptics etc.Improving platform support (Monado in particular).Rendering of controllers (as basic cuboids).Controller pointing support with some mouse emulation.Controller support for flight (helicopter collective in left hand, helicopter cyclic in right).Configurable VR mirror (see View->VR Settings) shown in default camera view (blank, left, right, side-by-side left & right).Motion tracking updates HMD views (but doesn't move main camera).Enable/disable at startup via -enable-vr / -disable-vr command line options, or from GUI (View->VR Options).Highly experimental, partially in next, partly out of tree. OR explicitly pass `-DENABLE_VR=OFF` to CMake to disable VR support altogether.OR depend on OpenXR and GLX, and explicitly pass `-DSYSTEM_OSGXR=OFF` to CMake so the built-in osgXR is built statically.preferably depend upon an osgXR package providing the osgXR dynamic library.To avoid implicit dependencies when packaging, packagers may need to do ONE of the following: In any case it will print a message along the lines of - VR support enabled/disabled. If no OpenXR is found it will disable VR support.If no osgXR library is found it will check for OpenXR and if found it will build its own static built-in copy of osgXR to use.Look for the osgXR library, and if found it will link against that (same as -DSYSTEM_OSGXR=ON).When CMake runs for FlightGear (next or osgxr/osgxr_clean branches), by default it will attempt to enable VR on Windows and Linux (same as -DENABLE_VR=ON). More FGData changes can be found on James Hogan's osgxr branch (non-rebased branch), or osgxr_clean branch (clean history, may be rebased).More SimGear changes can be found in James Hogan's osgxr branch (non-rebased branch), or osgxr_clean branch (clean history, may be rebased).A mirror is available on github for issue tracking. More FlightGear changes can be found on James Hogan's osgxr branch (non-rebased branch), or osgxr_clean branch (clean history, may be rebased).On Windows, you can use the Windows nightly builds.flightgear-git, simgear-git, flightgear-data-git. On ArchLinux, you can use the -git AUR packages, i.e.Some VR code can now be found in FlightGear's next branches (see below for details).On ArchLinux, you can install the osgxr AUR package to get the version needed by FlightGear's next branches.osgXR source can be found on github, or the version included in the flightgear 3rdparty directory can be used.The portable OpenXR API now seems to be getting widespread adoption, which will allow FlightGear to support a variety of VR devices across multiple platforms. A previous attempt to support some form of VR is described in OculusImplementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |