Jump to content

Recommended Posts

Posted

I have been using Openkneeboard successfully and I was also able to use HTCC individually. Both worked really well and then I loaded both and that when the problems started. Mostly HTCC will stop tracking my hands, but the ring-mice (Slugmouse) still worked, I just had to aim with the Q3. It almost works better since I'm not fighting both head and finger movements but some switches are difficult to lock on to.

At other times OKB will stop responding to keyboard commands and the Wacom pen. It's still active as when I lean forward it zooms in, I just can't change pages.

I used the OXR tool also by the dev and it flagged HTCC as needing to move to the bottom. Since then the tool has no warnings. Only HTCC and OKB are active in the OXR layers. Additionally when OKB stops working, I can close it but it won't leave memory and takes a 3 finger salute to terminate it.

Any ideas? Seems like handtracking from Q3 might be the issue. All setting in the 2 apps are per the Devs instructions.

Meta Quest 3, Intel i9-10900K, EVGA 3080Ti FTW3, Corsair 64GB DDR4 3200, ASUS ROG Strix z-490-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted

Yea, I thought I would start here as he gets pretty busy. I'm going to figure out if there are logs first and set OKB back to default.

Meta Quest 3, Intel i9-10900K, EVGA 3080Ti FTW3, Corsair 64GB DDR4 3200, ASUS ROG Strix z-490-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted

All appears to work as expected for me. HTCC tracks, Open Kneeboard responds to Wacom pen and buttons.

Are you sure your Wacom tablet was still awake/connected?

Are you using the latest OKB build v1.8.2?

HTCC: Are you sure you haven't parked it (Fred calls it hibernate) by raising your hand above your head? You may not have done that deliberately, but merely having your hand in view and then lowering your head could put HTCC to sleep. I think I turned this off and instead reduced the working FOV through the registry settings so that the cursor only reacts to hand movements if it is in that FOV. That way I am able to reach out and grab the mouse without HTCC taking control.

Registry Settings | HTCC (fredemmott.com)

Posted

I haven't been able to check yet as I had a busy day. The Wacom was active as I checked and could move and write, it just didn't show that I wrote in VR.

I use a Razer Tartarus Pro for the OKB commands, and that was working in DCS for other commands. 

I thought about the parking issue and will look more closely at it, but with OKB not active it didn't happen. 

I'll reset settings and look again. 

Meta Quest 3, Intel i9-10900K, EVGA 3080Ti FTW3, Corsair 64GB DDR4 3200, ASUS ROG Strix z-490-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted
On 5/29/2024 at 4:13 AM, Maddaawg said:

it flagged HTCC as needing to move to the bottom

Clarifying from discord: this is absolutely not a requirement of HTCC.

XR_NeckSafer currently must be above HTCC for an unknown reason. The tool does not aim to put HTCC at/near the bottom, it just aims to put XRNS higher than it.

My projects:

OpenKneeboard - VR and non-VR kneeboard with optional support for drawing tablets; get help
HTCC - Quest hand tracking for DCS; get help

If you need help with these projects, please use their 'get help' links above; I'm not able to track support requests on these forums.

 

Posted
11 hours ago, actually_fred said:

Clarifying from discord: this is absolutely not a requirement of HTCC.

XR_NeckSafer currently must be above HTCC for an unknown reason. The tool does not aim to put HTCC at/near the bottom, it just aims to put XRNS higher than it.

Thanks for the clarification. I worked on this for hours last night. I removed both OKB and HTCC after losing any tracking with HTCC even with OKB disabled. I might be having a Q3 hand tracking issue. When I got out of Quest Link and tested hand tracking with the auto switching and controller tapping it would only stay on for a few seconds. When I switched to manually turning it on, it worked fine. I might try VD today and see if the issue persists. 

 

Meta Quest 3, Intel i9-10900K, EVGA 3080Ti FTW3, Corsair 64GB DDR4 3200, ASUS ROG Strix z-490-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

  • 2 weeks later...
Posted

Ok, so I got this working. I had to go one more step backwards in the Wacom software to 6.4.4-3 from v6.4.5

Meta Quest 3, Intel i9-10900K, EVGA 3080Ti FTW3, Corsair 64GB DDR4 3200, ASUS ROG Strix z-490-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted

I tried that version first, the problem was still there and the pen and tablet settings did not have the option to be set at application defined.

The Github page for OKB says to use older versions because of that feature removal. I was having the symptoms described in his troubleshooting area that are driver related.

Meta Quest 3, Intel i9-10900K, EVGA 3080Ti FTW3, Corsair 64GB DDR4 3200, ASUS ROG Strix z-490-E Gaming, Samsung 990 Pro 2TB M2 NVME Windows 11 Drive, Samsung 970 EVO Plus 2TB M2 NVME Game Drive

Posted (edited)

Perhaps it keeps the setting if you turned it on in an earlier version of the driver? They have completely removed the option for 'application-defined' tablet versions in recent versions, and they've confirmed it was intentional. It can't be set in the app, which makes it impossible to add the bindings in OpenKneeboard. Pen buttons may still work.

I'm fairly likely to remove wintab support in a future version and require OpenTabletDriver: currently *no* manufacturer has a 'good' driver, and one manufacturer has a driver that reliably crashes unless the app uses a specific version of .net (neither DCS nor OpenKneeboard use .net at all). If I do this, I'll probably make an OpenTabletDriver plugin to actively block wintab, so that both drivers can be installed at the same time for people who actually do drawing with their drawing tablet 😛

Edited by actually_fred

My projects:

OpenKneeboard - VR and non-VR kneeboard with optional support for drawing tablets; get help
HTCC - Quest hand tracking for DCS; get help

If you need help with these projects, please use their 'get help' links above; I'm not able to track support requests on these forums.

 

Posted
6 hours ago, actually_fred said:

Perhaps it keeps the setting if you turned it on in an earlier version of the driver?

I wonder if there is a registry setting that could be added. It seems odd, though, but not improbable. I'd expect it to go entirely in the future or not fully work.

6 hours ago, actually_fred said:

I'm fairly likely to remove wintab support in a future version and require OpenTabletDriver

Thanks.

6 hours ago, actually_fred said:

for people who actually do drawing with their drawing tablet

That would be me. So, thanks once again.

Posted
On 6/12/2024 at 12:25 PM, actually_fred said:

Perhaps it keeps the setting if you turned it on in an earlier version of the driver? They have completely removed the option for 'application-defined' tablet versions in recent versions, and they've confirmed it was intentional.

That's odd as I still have it on my tablet GUI.

image.png

 

image.png

Posted (edited)

On 6.4.6-2 (-1 is no longer available for download), it shows up if you selected it on an earlier version, but vanishes from the menu the moment you change it to something else:

 

6.4.6-a.png

6.4.6-b.png

Edited by actually_fred

My projects:

OpenKneeboard - VR and non-VR kneeboard with optional support for drawing tablets; get help
HTCC - Quest hand tracking for DCS; get help

If you need help with these projects, please use their 'get help' links above; I'm not able to track support requests on these forums.

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...