No offensive, hateful, or low-effort comments.

Only submissions that are directly related to Dell & Dell Technologies are allowed.

Discord Filter Out Help Posts Only Show Help Posts Dell Website Meet the Dell Family For direct contact with Dell please see the 'General Support' section below. Please note this subreddit is 100% unofficial. Feel free to ask questions that are support related or otherwise on anything related to Dell Technologies & we'll do our best to help you. I haven’t been using it long, so can’t comment on whether the issue existed in previous versions.Welcome to /r/Dell. All NX plugins (Abbey Road, Nx Virtual Studio Collection) are 14.0.0.

Tracker firmware is 1.30v1.13 Waves Central is 13.3.2. Has this issue been identified and is it being worked on? It’s made the head tracker effectively unusable without having to close the tracking app every twenty or so minutes. I presume there is some real or perceived issue with using the Windows Bluetooth connection service that Waves is working around by implementing its own, using extremely aggressive polling that at least on some Bluetooth chipsets is so (CPU) expensive it becomes a DOS attack. Being connected to or not connected to a head tracker makes no difference. (This means I can’t use my Bluetooth mouse.) Turning ‘automatic connect’ on or off doesn’t make a difference. The only way of stopping the resource usage, outside of closing the tracking app, is to turn off Bluetooth, presumably so that all the requests fail in a non-resource-hungry way to fall back on camera tracking alone. It appears to be in the identification routine for trackers, which cannot be switched off in the app. It makes no difference whether the camera is turned on or off. It does this whether the tracker, camera, or both are being used for tracking. It does so somewhat gradually over time, but ending up at 60+% before crashing the PC through overheating. With the tracker app running, it indirectly makes increasing memory and CPU usage indirectly, through the of the Device Association Service ('Service Host: Device Association Service). This is happening on both Windows 10 and Windows 11 on two different computers, under both Reaper and Audirvana VST hosts. I’m observing a resource leak related to the head tracker app in Waves NX. I was hoping the head tracker would reduce my CPU use under NX, but it’s not.

Waves nx headtracker