VB-Audio's Forums

Well that is the thing there is a device for my Headset but if I use that my Buttkicker does not work.. what I am saying there was another ASIO device before that was the headset and I used that..

But I had a problem with Windows and I reinstalled and since I did that I no longer see the other ASIO device.. either way it really don't matter I just thought it would be an easy solution I have it working fairly good like this..

Once I get some money I will be donating some money towards your Programs I have found it usefull so thank you for the help and the Program..

I have a similar setup to you O+, Buttkickers (SimCommander) alongside a DD wheel and an SFX-100 Motion platform

It's a real pain in the ass, there are so many quirks with it that I have to have a specific startup routine powering on different devices and launching different applications at specific points in the startup chain.

If I don't then the audio won't work with the headset and the force feedback on the wheel doesn't work.

One thing to note is that with the O+ is USB Audi Device is actually disabled when Windows Mixed Reality is not running, I had all sort of issues with Voicemeter hanging due to this behaviour. This was because the device actually wasn't present in the system until WMR started.

Thought I would mention it as it may explain why your not seeing the device. I got around this by either launching voice-meter after WMR had launched (and the device gets enabled ) or restarting voicemeter after everything has started up.

Also another thing to note is that I'm having big issues since the WIn10 1903 issue with Voicemeter Potato. after about 30-40 mins of usage the audio output for the O+ will crash. You know it's coming as if your in game you will get massive lag/stuttering in game for about 10-15 seconds (almost guaranteed to put you in the barrier in any racing sim) and then you will just get white noise thrown into the O+. I've actually resorted to not using the audio on the O+ and mapping my sound-cards headphone output instead. this seems to put a band aid around this issue for me so far.

if you have strange audio problem with Voicemeeter after WIN10 update, it's recommended to re-install Voicemeeter
more info there: viewtopic.php?f=6&t=442