CV1 arrived today

[Wrongway]

I had a DK2 which got sold on eBay last week. I didn't even think the CV1 had been despatched yet until the UPS chap turned up this afternoon.

I un-installed the drives for the DK2 to get a fresh install then ran through the installation. Firstly I seem to be getting the odd HDMI disconnected message. Should it do this when the sensor in the device doesn't sense a head in place. Also the head sensor seem very sensitive and easily loses detection if moving the CV1 around a little.

Other than setting 3D/speakers or headphones in ED's options do I need to do anything else. I noticed the refresh stayed at my 59.95Hz which was the default for my monitor. The CV1 looks a lot sharper than the DK2 was but still is quite shimmery. I have had a good search but can't find any postings advising how to get the best out of it and what settings may need changing. I keep seeing references to SDK tool, supersampling and pixel density etc. Any help would be appreciated. I am using an Nvidea 970 card. Also how do you get framerate displayed with a Rift.

 

[JerryLove]

I un-installed the drives for the DK2 to get a fresh install then ran through the installation. Firstly I seem to be getting the odd HDMI disconnected message. Should it do this when the sensor in the device doesn't sense a head in place. Also the head sensor seem very sensitive and easily loses detection if moving the CV1 around a little.

Nope. You should not be seeing that. I've had zero such errors.

There's another thread in this forum about someone getting frequent HDMI disconnects and it being a problem with the cable connection to the CV1.

Play with the cable near the headset and see if you can trigger it with "normal motion". If so: contact Oculus.

Other than setting 3D/speakers or headphones in ED's options do I need to do anything else. I noticed the refresh stayed at my 59.95Hz which was the default for my monitor.

The displayed refresh is for your monitor. The Rift should be trying for 90fps. You can pull up the in-VR display from the rift tool to see what you are getting.

The CV1 looks a lot sharper than the DK2 was but still is quite shimmery.

Moire patterning. If you figure out how to get rid of it, let me know. I've also seen flashing textures (which you can mostly eliminate with super-sampling).

I have had a good search but can't find any postings advising how to get the best out of it and what settings may need changing. I keep seeing references to SDK tool, supersampling and pixel density etc. Any help would be appreciated. I am using an Nvidea 970 card. Also how do you get framerate displayed with a Rift.

Download (if you don't already have) and open the Oculus SDK and run the RiftDebugTool.

You can toggle the perfmon on and off there. You can also set super-sampling there.

There are two approaches to SS.

Approach one: change the SS in the configuration in Elite dangerous (1.0 should be default: raise for quality, lower for speed)
Approach two: Start Oculus. Start the debugtool. Set your SS rate in the debug tool (you aren't going to be able to usefully get above 1.5, if there). Start Elite. In elite, try lowering your SS (0.65 for example).

I get the best results with the debug tool on 1.6 and Elite on 1.0; but I;m tunning a 1080: YMMV

 

[Chaz]

I un-installed the drives for the DK2 to get a fresh install then ran through the installation. Firstly I seem to be getting the odd HDMI disconnected message. Should it do this when the sensor in the device doesn't sense a head in place. Also the head sensor seem very sensitive and easily loses detection if moving the CV1 around a little.

Try a different HDMI port, sometimes that works for those that have had the same problem. The sensor should not lose any detection at all, it's generally pretty robust at keeping a track of you. Just make sure you don't have it too close, keep it about 3 feet away and make sure it has a completely unobstructed view. Your best bet is to have it at about head height when standing with it tilted down slightly so that it will see you when both seated and standing. If it's all up and working properly then it shouldn't lose tracking at all. Try and keep everything plugged in the USB 3 ports that are on the motherboard at the rear rather than the case ports and don't use USB hubs.

 

[Wrongway]

Try a different HDMI port, sometimes that works for those that have had the same problem. The sensor should not lose any detection at all, it's generally pretty robust at keeping a track of you. Just make sure you don't have it too close, keep it about 3 feet away and make sure it has a completely unobstructed view. Your best bet is to have it at about head height when standing with it tilted down slightly so that it will see you when both seated and standing. If it's all up and working properly then it shouldn't lose tracking at all. Try and keep everything plugged in the USB 3 ports that are on the motherboard at the rear rather than the case ports and don't use USB hubs.

By sensor I meant the small sensor inside the mask itself at the top that detects your face in place. I found it was flicking on and off initially. I might have improved it by fitting the mask better.

- - - - - Additional Content Posted / Auto Merge - - - - -

Nope. You should not be seeing that. I've had zero such errors.

There's another thread in this forum about someone getting frequent HDMI disconnects and it being a problem with the cable connection to the CV1.

Play with the cable near the headset and see if you can trigger it with "normal motion". If so: contact Oculus.


The displayed refresh is for your monitor. The Rift should be trying for 90fps. You can pull up the in-VR display from the rift tool to see what you are getting.


Moire patterning. If you figure out how to get rid of it, let me know. I've also seen flashing textures (which you can mostly eliminate with super-sampling).


Download (if you don't already have) and open the Oculus SDK and run the RiftDebugTool.

You can toggle the perfmon on and off there. You can also set super-sampling there.

There are two approaches to SS.

Approach one: change the SS in the configuration in Elite dangerous (1.0 should be default: raise for quality, lower for speed)
Approach two: Start Oculus. Start the debugtool. Set your SS rate in the debug tool (you aren't going to be able to usefully get above 1.5, if there). Start Elite. In elite, try lowering your SS (0.65 for example).

I get the best results with the debug tool on 1.6 and Elite on 1.0; but I;m tunning a 1080: YMMV

Much appreciated Jerry. Initially it looks like I need the SDK as I think that contains the Rift too and debug tool? I have downloaded the SDK but cannot find any installation instructions. Does it have an installer or do I just plonk the contents of the directory somewhere. The shimmering for want of a better word in the station is terrible.

 

[JerryLove]

By sensor I meant the small sensor inside the mask itself at the top that detects your face in place. I found it was flicking on and off initially. I might have improved it by fitting the mask better.

I believe he's referring to the cylinder on a stick when he says "sensor"; and obviously the mask when discussing HDMI.

Much appreciated Jerry. Initially it looks like I need the SDK as I think that contains the Rift too and debug tool? I have downloaded the SDK but cannot find any installation instructions. Does it have an installer or do I just plonk the contents of the directory somewhere. The shimmering for want of a better word in the station is terrible.

Just extract it somewhere. The debug tool is an executable in the "tools" subdirectory.

 

[Wrongway]

It seems to have settled down a lot now. The proximity sensor in the mask seems ok. It was probably just the mask wasn't fitted right. I ran the in VR tool to see what the framerate etc was. In just its own desktop it was quite happy at 90fps with about 50% headroom I think it was called on the graph adjacent to the FPS bit. What I went into ED it really suffered. FPS went down to 60-70 in the station and the other graph was showing red.

Whereabout is this SS setting in the configuration in ED. I can't seem to find it. I couldn't find the SS setting in the debug tool either.

 

[dogbite]

If your headset light flickers try reseating hdmi cable. Turn off AA in game. Set SS to .65 in game. Start Oculus home before the debug tool. Set pixel density in debug (try for 1.5 with a GTX 970) hit ENTER. You may need to lower PD around stations or busy areas and or lower some in game settings. Leave the debug tool running. Launch ED. Hope that helps.
SS is in graphic settings in game options -hit the + to expand the list.

 

[Wrongway]

Thank's Dogbite I am sure that will be very helpful, I will try it soon as I get back hope. I retired for a pint to give my head a rest and study a bit. I did try and locate the SS setting in game before without any success. I think I saw PD in the debug tool, I will check when I get back.

 

[Zieman]

Whereabout is this SS setting in the configuration in ED.

Options - Graphics - Quality

 

[dogbite]

Thank's Dogbite I am sure that will be very helpful, I will try it soon as I get back hope. I retired for a pint to give my head a rest and study a bit. I did try and locate the SS setting in game before without any success. I think I saw PD in the debug tool, I will check when I get back.

"per pixel density override" is 2nd on the list
Have a pint for me. lol

 

[Wrongway]

Thank's to the folks in this thread for all the advice and help in getting things going. The CV1 seems nice and stable now. I have had no HDMI disconnects or fun with the little proximity sensor in the mask. I don't think I ever had a hardware problem with it. I put it down to my PC and software. I have had a tweak at the settings as advised here and it has helped without doubt. I still get shimmering on sharp the contrasting edges in stations but I suspect it's right and me expecting a bit much for my hardware.

I put the PD setting in the debug tool. I noticed when I ran it again I had to enter the PD value again, it doesn't seem to save. Is that correct and am I supposed to run the debug too every each time before running ED.

The vastness once you get out with different ships is so amazing. Jaw dropping. I never really got this far with the DK2.

 

[dogbite]

yes the PD resets after each time you close it. You can use it in other games as well. Some, like DCS and IRacing have built a density control into their games. Hoping ED will do this as well. Glad your enjoying your new toy. Warp speed

 

[Wrongway]

Hmmm, started getting HDMI disconnects again as I mentioned earlier in this thread. It seems to happen by tapping the headset. I contacted Oculus support who told me how to re-seat the HDMI cable in the headset. Doesn't seem to have cured it though. Tapping the headset brings up "cant find your headset" in the notifications window of the Oculus app quickly followed by "HDMI cable disconnected" notification, which then shows as expired. The display blanks and sometimes returns but usually needs the app restarting. I am now waiting for support to come back to me. I am sure somethings loose in the headset and it's not the cable.