Jump to content

actually_fred

Members
  • Posts

    124
  • Joined

  • Last visited

1 Follower

About actually_fred

  • Birthday 03/01/1987

Personal Information

  • Flight Simulators
    FSX, DCS World
  • Location
    Austin, TX
  • Interests
    VR
  • Occupation
    Software Engineer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah; their hardware is good, excellent value, and link/airlink are great - better than VD for me - when they work. On the other hand, Oculus frequently push out updates that break Link/AirLink features I depend on, or just break it entirely. I still use them when I can, but I also regularly use virtual desktop as a backup when link is broken yet again.
  2. This is a hardware limitation; with the possible exception of the Varjo XR4 (the advertising material is... advertising material, not clear functional descriptions), no generally available headset is capable of rendering anything at multiple focal planes.
  3. They seem to be moving stuff around a lot; googling for "leap motion download old versions of gemini" gets you a few links to pages with it.
  4. Most of the replies in help threads contain factually incorrect advice, which makes setting up VR more confusing for everyone. I'm going to address a few common ones: - SteamVR + OpenXR: SteamVR supports OpenXR (it's an "OpenXR runtime") - if you want to use SteamVR + DCS, you want to start by setting SteamVR as your OpenXR runtime. You do not want to 'disable OpenXR' to use SteamVR, unless for some very rare reason you specifically want to use OpenVR. If you do this, no games that require OpenXR will work unless you change your settings back. - "OpenXR Tools for Windows Mixed Reality" is specifically for Windows Mixed Reality headsets. If you have a quest, rift, pimax, varjo, beyond, or any other non-WMR headset, do not install this software, and especially do not click the button to set WMR as your OpenXR runtime. If the tutorial you're watching or the guide or reading says to do this and doesn't say "just for G2" or "just for WMR", find a better guide. If you just want to see information on openxr, https://github.com/maluoi/openxr-explorer/releases/latest is a better tool, in combination with https://github.com/fredemmott/OpenXR-API-Layers-GUI/releases/latest if you have several OpenXR API layers (roughly 'plugins') installed*. - "OpenXR Toolkit" is not the same thing as "OpenXR Tools for Windows Mixed Reality" - "OpenXR Toolkit" is not the same thing as "OpenXR" - "OpenXR Toolkit" is never required. It's a great tool, install it if there's a specific reason you want it, but it's not necessary. - "Set WMR/your headset/SteamVR to OpenXR": this is the wrong way around and can confuse people: "Set OpenXR to SteamVR/WMR/your headset" is correct. It's a single OpenXR setting for all OpenXR hardware manufacturers and games - you are changing if OpenXR games use WMR, oculus, steamvr, or whatever, not a headset setting. Specifically these buttons in steamvr/wmr/manufacturer-specific stuff all change `HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1\ActiveRuntime` - SteamVR can simultaneously be your selected OpenVR and OpenXR runtime. Games will only use one at a time. - If WMR is set as your OpenXR runtime, your G2 can be used by openxr *or* steamvr-via-openvr *or* classic (deprecated) Windows Holographic *or* opencomposite-via-openvr* without any settings changes. Games will only use one at a time. - If Oculus is set as your OpenXR runtime, your quest/rift can be used by openxr, *or* steamvr-via-openvr *or* opencomposite-via-openvr *or* the classic (deprecated) libovr without any settings changes. Games will only use one at a time. - If you need to change your OpenXR runtime and the buttons in the various vendor-specific tools aren't doing what you want, https://github.com/rpavlik/xr-picker/releases/latest is a good tool * OpenXR-API-Layers-GUI can also be used to fix issues, but I'm recommending it here because layer (plugin) order matters, and the current version of OpenXR-Explorer sorts them alphabetically - this means that OpenXR-Explorer is not currently useful for troubleshooting API layer issues. This should be fixed in the next version of OpenXR-Explorer.
  5. A quick repair will bring it back if needed. Check that Leap Motion support is disabled in DCS if you want to use leap motion via openxr instead.
  6. > If using controller emulation That change is unneeded and has no effect when using touch screen/tablet emulation. If it has an effect with HTCC, you're using oculus touch controller emulation, which will not work correctly with this ring; it would need new firmware, and some changes to HTCC. I'm interested, but hoping to find a supplier for the batteries that can deliver to the US faster than March
  7. Even if you're not using HTCC, https://htcc.fredemmott.com/hardware/ultraleap/README.html#pimaxs-hand-tracking-module - this will *only* affect OpenXR hand tracking, not classic leapc.dll integration, so you may need to delete leapc.dll from your DCS bin and bin-mt folders for it to apply (and re-do that every DCS update)
  8. The easiest way to deal with that would probably be to add them to an aircraft tab's folder in saved games - you can see the paths it looks for those in the tab settings. If there's an X by the one in saved games, that just means that it doesn't exist yet, and you can create it if you want to. I'm probably going to add some level of lua scriptability at some point; this would include fully-lua-defined tabs, but I probably will also add 'lua-assisted' tabs - e.g. a folder tab where you can write lua code that changes which folders it's looking for based on which aircraft you're flying. I could also add 'custom prefix' to aircraft/terrain, e.g. "My Documents\Controls\<aircraft>", though this might be a bit too niche to be worthwhile, especially once it's possible with lua scripting. Might also add JS scripting - it's my preference, but OpenKneeboard already deals with some lua, and it fits better with the current DCS modding community.
  9. No, there’s no simple way for that, its 99% the same technical problem as bookmarks.
  10. You also need to set Oculus as your active OpenXR runtime; this is in the Oculus PC app settings, or you can use a tool like https://github.com/rpavlik/xr-picker
  11. While it would be relatively straightforward for OpenKneeboard to run Lua (and it will probably support some level of Lua scripting in the future), that wouldn't help here: the problem is getting access to the internal DCS/module features that these lua kneeboard pages depend on to work. It would probably require per-module DCS patching, and likely have problems with IC and need frequent per-module updates to keep up with changes in DCS.
  12. Probably not that difficult, it's just not seemed the most interesting way to spend my free time yet. That said, there are some minor complications: before bookmarks can be persistent, it needs to understand and track which kinds of content are persistent - and they can move. For example: - if you add a PDF, and bookmark page 5, the bookmark should be persistent - what if the PDF is modified or replaced? Trash the bookmarks or assume the page numbers still make sense and keep them, assuming the page count is >= the bookmark? Change tracking for PDF is not usable for this. - what if the bookmark is a text file and the text file is modified? The ideal would probably be to erase the bookmark if the modifications are *before* the bookmarked page, but otherwise should preserve it - radio log bookmarks should not be persistent as the radio log itself is not - mission briefing bookmarks should only be persistent within the same mission - if you have a folder tab and you bookmark `b.png` within that folder, close openkneeboard, add `a.png` to that folder, then re-open OpenKneeboard, the bookmark should still point at `b.png` - even though the page number for that bookmark has been increased by one
  13. There are currently no known crashes except when running as administrator which can only be fixed by Microsoft and is generally a bad idea anyway; if you’re not running as administrator sorry it’s complex, but if you follow the steps at https://openkneeboard.com/troubleshooting/crashes-and-freezes.html I might be able to fix whatever you’re encountering, or point you in the right direction.
  14. The one big gotcha is eye-tracked dynamic foveated rendering. This is possible on the QPro - not the Q3 - and can lead to *huge* GPU savings in DCS (and Pavlov, but not as much in other games where quad-views can't be used so DFR is implemented with other techinques). Personally the QPro's eye tracking latency was too high for me (I love it on the Pimax Crystal though) - but the majority of people don't seem to have a problem with it and it *really* helps with DCS framerates. Q3 is definitely a better all-round headset, QPro is probably a better DCS headset.
  15. I've spent the last few days making https://github.com/fredemmott/OpenXR-API-Layers-GUI ; this is a tool for managing your installed OpenXR API layers and removing old/corrupt ones - it won't install them for you. OpenXR API layers extend OpenXR games/apps; some popular layers include: - HTCC - Liv Stabilization - OpenKneeboard - OpenXR Motion Compensation - OpenXR OBS Mirror - OpenXR Toolkit - Quad-Views-Foveated - Ultraleap's OpenXR support - Varjo-Foveated - XRNS This tool lets you enable/disable any of these that are installed, re-order them, and can automatically detect and fix common problems: Separate versions are included for: - 64-bit API layers installed system-wide (most common, using HKEY_LOCAL_MACHINE) - 64-bit API layers installed per-user (Liv stabilization, extremely old versions of OpenKneeboard; using HKEY_CURRENT_USER) - 32-bit API layers installed system-wide (HKLM in the 32-bit registry) - 32-bit API layers installer per-user (HKCU in the 32-bit registry) For help, see https://github.com/fredemmott/OpenXR-API-Layers-GUI#getting-help ; I'm often unable to respond in threads, and I'm not able to respond to support DMs on any platform.
×
×
  • Create New...