Project Cars 2 VR? Is it OK?

Just-Dave said:
Waiting to hear back about the burning smell off oculus, but it was just that once, used it after and it has not repeated,
Not using the official cable no, got the anker one every one recommended, speed was 2.6 gbps,
Not tried virtual desktop or side quest, I dont have a good enough router I think so I've not thought much about Virtual desktop,
I've tried the encode width thing and tbh, I cant tell a difference,
I have put time into this, looked around for solutions tono avail sadly,

The only thing that the quest 2 beat the cv1 when I tested was the resolution, but that extra resolution ain't no good lf the compression of the link cable makes the game look worse, this is at least the conclusion Ive come to, or maybe yeah I just have a really defective headset when attached via link
Click to expand...

The burning smell may have been due to a defective fan, the Quest 2 has fans which are very slightly audible and the unit requires a bit of juice to be able to decode. At least this is the case with Virtual Desktop when running under 'boost mode' which is needed for anything over 100mbps.

One thing you may wish to try is the Oculus Debugger tool, they've now added an option to change the bitrate of the Link. See here:
https://www.reddit.com/r/OculusQues..._v23_is_out_improving_oculus_link_resolution/

That said, I've tried Project Cars 2 on the Rift S and felt it really wasn't good enough. Super-sampling helped smooth out the image but there just wasn't enough detail to see into the distance which is pretty important in a racing sim. I appreciate the Quest 2 has a higher resolution but Link hasn't had an official update yet (the render target res is based on Quest 1) and has been left behind by Virtual Desktop. Worth playing with the bitrate now though as this has only just been made available.
 
Last edited:
Just-Dave said:
Waiting to hear back about the burning smell off oculus, but it was just that once, used it after and it has not repeated,
Not using the official cable no, got the anker one every one recommended, speed was 2.6 gbps,
Not tried virtual desktop or side quest, I dont have a good enough router I think so I've not thought much about Virtual desktop,
I've tried the encode width thing and tbh, I cant tell a difference,
I have put time into this, looked around for solutions tono avail sadly,

The only thing that the quest 2 beat the cv1 when I tested was the resolution, but that extra resolution ain't no good itself the compression of the link cable makes the game look worse, this is at least the conclusion I'm come to, or maybe yeah I just have a really defective headset when attached via link
Click to expand...

There is one thing that stands out there, if you can't see the difference with the Higher Encode width, that means your headset is borked. It makes a big difference. It stays at the higher encode width even without the Link cable attached, so you should see a difference even in the home screen. The encode width resets when you restart the headset.

You should download Sidequest and try it out, it makes it easy to switch to 90hz and change the encode width. It's a very useful program to have.

Also, I think if you have a 5ghz router, you should try Virtual Desktop, it might rule out a cable issue. You might get a bit of Latency, but, it's just for testing out the visuals.
 
Kashinoda said:
The burning smell may have been due to a defective fan, the Quest 2 has fans which are very slightly audible and the unit requires a bit of juice to be able to decode. At least this is the case with Virtual Desktop when running under 'boost mode' which is needed for anything over 100mbps.

One thing you may wish to try is the Oculus Debugger tool, they've now added an option to change the bitrate of the Link. See here:
https://www.reddit.com/r/OculusQues..._v23_is_out_improving_oculus_link_resolution/

That said, I've tried Project Cars 2 on the Rift S and felt it really wasn't good enough. Super-sampling helped smooth out the image but there just wasn't enough detail to see into the distance which is pretty important in a racing sim. I appreciate the Quest 2 has a higher resolution but Link hasn't had an official update yet (the render target res is based on Quest 1) and has been left behind by Virtual Desktop. Worth playing with the bitrate now though as this has only just been made available.
Click to expand...
Cheers for that, will look at that bitrate settings when I'm back home tomorrow
 
melmac said:
There is one thing that stands out there, if you can't see the difference with the Higher Encode width, that means your headset is borked. It makes a big difference. It stays at the higher encode width even without the Link cable attached, so you should see a difference even in the home screen. The encode width resets when you restart the headset.

You should download Sidequest and try it out, it makes it easy to switch to 90hz and change the encode width. It's a very useful program to have.

Also, I think if you have a 5ghz router, you should try Virtual Desktop, it might rule out a cable issue. You might get a bit of Latency, but, it's just for testing out the visuals.
Click to expand...
Will have a look at side quest tomorrow,
Hopefully oculus will offer me a swap,
Didn't directy buy from them, got it from argos, but hopefully if they tell me it needs swapping I can take it in a get a different one, or tbh I may even just get a refund and wait for my g2 order to come,

Did you get chance to try p cars 2 throught the link yourself?
 
Just-Dave said:
Will have a look at side quest tomorrow,
Hopefully oculus will offer me a swap,
Didn't directy buy from them, got it from argos, but hopefully if they tell me it needs swapping I can take it in a get a different one, or tbh I may even just get a refund and wait for my g2 order to come,

Did you get chance to try p cars 2 throught the link yourself?
Click to expand...

Oculus have just released a new Beta. Might be worth trying, you can up the encode bitrate of the Link cable to 500Mbs. You should try 200Mbs and see if it make any difference.

Also, when you make change in the debug tool, you have to lock and unlock your Quest 2 for the changes to take effect.

Here's the info

https://www.reddit.com/r/OculusQues..._v23_is_out_improving_oculus_link_resolution/

EDIT: Sorry :) missed your question. Nope, haven't got around to it, will try in a few minutes.
 
Just-Dave said:
Did you get chance to try p cars 2 throught the link yourself?
Click to expand...

Mate, sorry there is something wrong with your Quest, or maybe it's the cable.

Just tried out Project cars 2 and it looks really good on the Quest 2 over the Link cable. It's a little bit soft, but, there is no way you would think it looked like a Playstation 1 game.

On Virtual Desktop it looks almost as good as the through the lens video of the Reverb G2. The Signs are clear, I can see far out to the distance, the number plates are readable from roughly the same distance.

When they update the Link cable It will look as just as good as the Virtual Desktop with less latency.

EDIT: Just want to add, that I left the link cable at the default settings, didn't change the refresh rate or anything else through the debug tool.
 
melmac said:
Mate, sorry there is something wrong with your Quest, or maybe it's the cable.

Just tried out Project cars 2 and it looks really good on the Quest 2 over the Link cable. It's a little bit soft, but, there is no way you would think it looked like a Playstation 1 game.

On Virtual Desktop it looks almost as good as the through the lens video of the Reverb G2. The Signs are clear, I can see far out to the distance, the number plates are readable from roughly the same distance.

When they update the Link cable It will look as just as good as the Virtual Desktop with less latency.

EDIT: Just want to add, that I left the link cable at the default settings, didn't change the refresh rate or anything else through the debug tool.
Click to expand...
Yeah dont sound good for mine does it,
I cant see the number plate of the car in front on me on the grid let alone in the distance,
Maybe I should order a new cable while I wait for oculus support to get back to me, but dont want to keep spending money on it, especially if its knackered
 
Just-Dave said:
Yeah dont sound good for mine does it,
I cant see the number plate of the car in front on me on the grid let alone in the distance,
Maybe I should order a new cable while I wait for oculus support to get back to me, but dont want to keep spending money on it, especially if its knackered
Click to expand...

Even on Reverb G2 you will only be able to read the number plates when you are about a car's distance away.

I don't have any of the recommended cables, I am just using a cable that I was using to charge my phone. It's a USB to USB C cable. Some cables don't work, but, surely you have a couple of USB to USB C cables lying around just to test it out.
 
melmac said:
Even on Reverb G2 you will only be able to read the number plates when you are about a car's distance away.

I don't have any of the recommended cables, I am just using a cable that I was using to charge my phone. It's a USB to USB C cable. Some cables don't work, but, surely you have a couple of USB to USB C cables lying around just to test it out.
Click to expand...
Sadly no lol,
I had to order this one, my phone is usb c to usb c in the plug,
I will ask some friends see if they have one
 
I use a Rift S for PC2, and it looks good - but admittedly on long straights stuff in the distance can be a little lacking.

I've never really tried supersampling to make a difference. What's the best way to do so? Is it using the Oculus Tray Tool still?
 
The new beta link software is a big improvement. Still slightly soft and washed out image, but far less compression visible when set to 200mbps encode rate.
 
Ravenger said:
The new beta link software is a big improvement. Still slightly soft and washed out image, but far less compression visible when set to 200mbps encode rate.
Click to expand...
Will give it a whirl tomorrow

bazzabear said:
I use a Rift S for PC2, and it looks good - but admittedly on long straights stuff in the distance can be a little lacking.

I've never really tried supersampling to make a difference. What's the best way to do so? Is it using the Oculus Tray Tool still?
Click to expand...
There is a supersamlping setting in game pal,
Also you could try the sharpening hack,
That's a file in the pcars documents folder,
The Info in in this thread over the last few pages where the guys have been trying to help me out
 
melmac said:
Mate, sorry there is something wrong with your Quest, or maybe it's the cable.

Just tried out Project cars 2 and it looks really good on the Quest 2 over the Link cable. It's a little bit soft, but, there is no way you would think it looked like a Playstation 1 game.

On Virtual Desktop it looks almost as good as the through the lens video of the Reverb G2. The Signs are clear, I can see far out to the distance, the number plates are readable from roughly the same distance.

When they update the Link cable It will look as just as good as the Virtual Desktop with less latency.

EDIT: Just want to add, that I left the link cable at the default settings, didn't change the refresh rate or anything else through the debug tool.
Click to expand...
Ok mate, after some good testing this morning i can confirm making changes in the debug tool does have a effect, i was restarting everything each time to be sure,
Problem i ran into was when i started making changes it soon showed the potato effect on my 1070 lol,
I will wait for my 3080, when i can start to crank these things before making finial judgment but i have to say Automobilista 2 does a far better job of vr,
The AA is barely noticeable compared to Project car 2,
So im going to be spending time using AMS2 Rather than Pcars 2 in vr, I always preferred that title anyway so its no loss,
Cheers for all your advice and help btw
 
You must log in or register to reply here.
Back
Top Bottom