Waw what a bad evening this turned out to be

(
TLDR: Does 0.6 run with CV1 - 90% no. Will say for the other 10% after I get my desktop PC living again.
Longer answer: Setup everything, plugged the headset in - runtime didn't notice it. Tried with the base station - same thing. Then tried a bunch of configurations - nope. Dug into Oculus files to find device IDs and tried some simple stuff - nope.
Then, finally, in a moment of supreme ignorance I decide there's a small chance the newer AMD Crimson display driver I installed may be causing the issue. Normally, I'd just grab my DK2 and just verify it gets seen by the runtime. But it's currently at a friend, cuz, you know, i have a cv1 with me.
As I was uninstalling Crimson, somewhere in the middle of the uninstaller, where usually it would unload the driver context, my display went completely blank. PC apparently was still running though. I hit the power of button, it politely shut down, then started it again and still get nothing on the display. Tried several simple things - nothing. Then I checked out if google knows anything about this and guess what ... I'm not the only one. Apparently it's a Crimson thing.. So expect a raging post in the AMD forums in a short while, right after i do what will probably be a windows reinstall.
And so I type this from my work macbook .. goddamnit!
Looking at it from the bright side - will have a clean testbed to try out stuff ... yey ?