Видео

haha thanks buddy

😂

I followed the steps in the pinned comment on the flat2vr discord. Only thing i had to download was the Tim burten profile that is pinned. I use a link cable. There might be different steps to take if you use VD. Just make sure you have UEVR 1.04 or later. Don't download anything extra like the hitfix loader. Make sure TAA is off in game and launch it with the openXR mode checked in uevr. If using VD, you might need to use VDXR? I'm not sure on that one but try whatever options VD provides if using it.

Your welcome, glad it helped you. Thanks for the nice comment. 😃

It is really amazing! Most fun i have had in VR outside of sim racing

Glad it was helpful

😃

hahahaha I was bored

That big ole rear view mirror in the stock cars was begging to be used for something

lol yeah, i'm a noob. Hope it helps. I later realized i went a little extreme with the value and i am still making some changes. Good place to start though, lots of file edits can be made. To bad we even have to do this but i like a bit of tinkering now and then

@@racinvr true story, to fix the brightness is the job of Codemasters, no clue what they are doing 🙂

oh thanks, i was not sure what that setting did

Greetings. Could it be a bloom effect? There are more ini file edits to disable that if it is whats causing the issue. You could also try turning Post Processing to ultra low in game to see if that helps, or the opposite

Also you're running at 3200x1728. Why not drop down to 72hz and run (x1.3) 5408x2736. It'll run smoothly and have a much sharper and cleaner image.

@@proxlamuz4591 Not true, 60 fps with ASW is much smoother then a locked 72 or even 90. The wheel rotation is smooth and not all stuttery, as well as the windshield wipers. It all looks and feels much smoother like this I agree with you and for other games its much better to do what you have suggested, but same with Dirt Rally 2, even 90 locked feels like crap in the car view because of that bug

But the input latency goes to sky... ​@@racinvr

@@William3143 Quite the opposite actually. The higher the hz rate, the lower the latency. Pretty sure anyways...

I recorded the oculus mirror. I'm quite new at this

I tried setting the AA to low and cranking up the resolution on the oculus app but it was to much for my GPU. It did help make things a little less muddy but the shimmering was still much worse with bad FPS for my setup.

It is incredibly blurry for me if using any upscaler+AA, no upscaling game actually looks nice but the fps is bad... DLSS is super blurry, it works great in other games, heck DLSS was working great using the UEVR mod... this VR update is just barely better than using UEVR.

@@MrBeerscuits Yes UEVR looked much cleaner for me. With the WRC 1.7 update, this enabled shadows to work in native stereo mode using UEVR but menus were only usable outside the headset. I have not tested the WRC 1.8 VR update with UEVR yet, maybe it fixed the menus and could be a good idea to check it out

oh good idea. I will have to try this thanks for the tip

Can you have different quest 3 debug tool profiles/settings depending on which game you’re playing?

From what I can tell the FOV will go back to Zero if you reboot or change your rendering size . All the other setting usually stay put .

@@Flexium_GG I don't see any options for that, so i don't think so

Thanks my friend 👍

Its not bad, not great though either. I am forced to not use shadows because of rendering issues. The official VR support will be much better. Plus i also recently found out that my Fanatec V3 pedals are causing a massive FPS drop when plugged into PC with USB. Something EA and Codies need to fix. I set my VR headset to 120 / 60. I only used the performance overlay a couple times and i never dropped below 60 fps i think. As far as quality goes, it looks very clear to me. As long as AA is set to at least HIGH, the image looks pretty good. My most recent video that shows the Fanatec FPS bug has the oculus mirror active and is recording what is seen in the headset if you want to check it out.

Yeah its definitely a bit large. I wanted to show off the replay views in VR.

Have you cycled through the different wheel options that show up in game in the controller section? Try the Direct custom input option and then back out to main menu, go back into controls and map your axis. Are your pedals plugged into the wheel base or plugged into PC via USB? If plugged in seperatly, use seperate pedals in the control options I don't know if this will work. I don't have the wheel but it is worth a shot

Yeah its a pain in the butt. Even after download, windows defender keeps deleting the dll. There are ways around that. I hope it is a false positive but i don't know. I'm still using it though.

Yeah, it was a good time hanging out and doing this video. Looking forward to the next one as well.

Pretty sure that was you pal...

​. Busted.. 😢

no worries, i have plenty for all of us

Thank you. I blame the tree

It feels nice and smooth to me for the most part. I don't know if it is the mod or my VR software but i have to run the VR headset at 120hz. I tried 90 and it was very stuttery

It is just a in game option. Gameplay options i believe its the one where you chose steering wheel animation or show driver.....Somewhere in game play options

Awesome! That's great you have the toolkit running with it. Some folks were reporting crashes because of it, so if you start to encounter a issue like that, the toolkit may be the culprit. Enjoy!!! Some of these locations look fantastic in VR.

@@racinvr I've had a few crashes related to hot swapping settings, particularly SS. It usually runs fine with those settings after the crash though.

Hai ragione, in questo video ho anche notato il continuo sussulto della telecamera ma non succede negli altri video. Non sono sicuro di cosa sia successo qui.

a me viene male anche solo giocarci su monitor se mi va a scatti !! con il vr invece mi da ancora troppo fastidio giocare a rally come dirt 2.0!! @@racinvr

It does have trackir support. For the rest of your question, i'm not sure.

Oh thanks for the tip. I will try this for sure

Not sure what you mean.

Yeah the crosshair makes it a bit confusing since it moves with your head. I try to use the ship to aim

Hey bud. Thanks for stopping by. Thought i might mix it up a bit.

Not sure what my FPS is. It feels smooth with some hitches here and there. I have my Quest 2 headset running on 120 hz mode. So a very smooth 60 reprjected into 120 perhaps? Feels like i am getting at least 90 most of the time. I also don't remember the resolution. I did make a video of my UEVR settings that shows the overlay with the resolution. I don't have access to that data at the moment sorry. The title of the vides was UEVR wrc settings or something like that

I actually am not sure what DX version it is using. Whatever the default is. I've been thinking and perhaps HAGS is the reason for your crashing. Try disabling Hardware accelerated GPU scheduling

@@racinvr where do you disable that?

@@sveininge 1 Open windows Settings, and click/tap on the System icon. 2 Click/tap on Display on the left side, and click/tap on the Graphics settings link on the right side 3 Click/tap on the Change default graphics settings link under Default settings at the top. 4 Turn on or off (default) Hardware-accelerated GPU scheduling for what you want

Hello again. Did you figure out the problem? Many folks are saying that OpenXR toolkit is causing crashes

have not tried anymore, :)

No config on my end. Here is my process... start oculus PC app, connect via link cable, make sure that is all up and running. start uevr injector. Start wrc Inject with Openxr and it is up and running. In game AA must be at least high. Shadows and post processing must be at ultra low, those effects are not rendering in both eyes. Not using any upscaling. Not using any openxr toolkit. Also since you have a 3080, hardware accelerated gpu schedualing could be the culprit.