LM Ultimate VR thread

I cant find anything VR specific in the 1.0 changelog and still it feels and looks different? I know that I always was thinking "looks a bit blurry, even on Virtual Desktop on Godlike". I havent played since before the update the teams feature came with. Did something change lol? It looks somehow sharper and .. overall better. More clean.
Can't say I noticed anything different from 1.0 to just before. I do think it looks decent enough but definitely not great. Yes, some places look blurry (Q3, 4090 card, most settings turned up high or max). It's weird. Some' just a bit blurry, others really blurry. The start of those last multiple fast turns at Le Mans looked really blurry for some reason while most of the rest of track was just a bit blurry in the distance.
 
Has anyone done any CPU related tests with VR and LMU?

In ACC I got a decent boost going to a 5800x3d, mainly resolved issues when being close to other opponents, otherwise it didn't do much.

I'm running a 4080 and a 5800x3d and wondering of going to a 9800 say would be of any benefit.

I still find VR looking pretty terrible compared to AC/ACC/iRacing and just about anything else on a Quest 3.
I upgraded from a 5800X3D to 9800X3D and its huge jump for VR. Check out this dudes VR Benchmarks. https://www.youtube.com/@BenchmarkOdysseys Amazing work.
 
Anyone have issues with bad stutters even though headroom is 40+ during said stutters? Talking Imola full Hypers field of AI.
 
Got to the bottom of the stuttering issues hopefully this helps somebody. Context: X870, 9800X3D, 4080, Quest 3 (native link cable).

Upgraded CPU/MOBO/RAM over the last few days, noticed bad stutters even though headroom was ~40%, also game would launch on any random number of attempts (DCS, AC, ACC launch no issues) anything from 2-20 attempts to get the game to execute.

Digging into it I started playing with Link bitrate in the debug tool which I had previously set to 900 (5800x3d X570) which on that platform worked fine. Had to drop bitrate to 350 at which point it seemed OK but not really, appears OK but still stutters in terns and sim would still not launch on first attempt. Scratching my head here because I'm supposed to get faster no? More lanes USB4 and all that...

Ended up going into BIOS and manually configuring all the PCIe lanes, I set x16 to Gen4, the M.2 to Gen3 (my drive is gen3) and all seems well now.

Leaving all PCIe configs at Auto/Gen5 according to AI is causing bandwidth contention and link training overhead.

Bottom line, whatever your platform, if you are running a Quest3 with a link cable perhaps best to just get a discrete USB controller, above fixed my issues but if I had the space I'd throw a controller in there to make sure my million USB devices don't cause issues.

On a positive note with the x870 Quest3 no longer looses charge on the link cable when in use and just works every time with Link loading on boot if the cable is plugged in or as soon as you plug it in if the headset is on already. Before I had to do a bit of a rain dance at times of plugging unplugging from the PC itself for it to pickup the link connection.
 
Last edited:
Got to the bottom of the stuttering issues hopefully this helps somebody. Context: X870, 9800X3D, 4080, Quest 3 (native link cable).

Upgraded CPU/MOBO/RAM over the last few days, noticed bad stutters even though headroom was ~40%, also game would launch on any random number of attempts (DCS, AC, ACC launch no issues) anything from 2-20 attempts to get the game to execute.

Digging into it I started playing with Link bitrate in the debug tool which I had previously set to 900 (5800x3d X570) which on that platform worked fine. Had to drop bitrate to 350 at which point it seemed OK but not really, appears OK but still stutters in terns and sim would still not launch on first attempt. Scratching my head here because I'm supposed to get faster no? More lanes USB4 and all that...

Ended up going into BIOS and manually configuring all the PCIe lanes, I set x16 to Gen4, the M.2 to Gen3 (my drive is gen3) and all seems well now.

Leaving all PCIe configs at Auto/Gen5 according to AI is causing bandwidth contention and link training overhead.

Bottom line, whatever your platform, if you are running a Quest3 with a link cable perhaps best to just get a discrete USB controller, above fixed my issues but if I had the space I'd throw a controller in there to make sure my million USB devices don't cause issues.

On a positive note with the x870 Quest3 no longer looses charge on the link cable when in use and just works every time with Link loading on boot if the cable is plugged in or as soon as you plug it in if the headset is on already. Before I had to do a bit of a rain dance at times of plugging unplugging from the PC itself for it to pickup the link connection.
Huh...I wonder if that's why I had such a horrible experience with the Link cable! Just resorted to using Virtual Desktop. In the end, decided to just go back to playing on a monitor. Loved the feeling of VR on my Quest 3 but the clarity of the image just wasn't doing it for me...plus the random stutters was driving me nuts.
 
Has anyone done any CPU related tests with VR and LMU?

In ACC I got a decent boost going to a 5800x3d, mainly resolved issues when being close to other opponents, otherwise it didn't do much.

I'm running a 4080 and a 5800x3d and wondering of going to a 9800 say would be of any benefit.

I still find VR looking pretty terrible compared to AC/ACC/iRacing and just about anything else on a Quest 3.
I'm fine with 4080 + 7800x3d + q3 @VD godlike res 72hz and all max except PP and reflections, so 9800x3d is ok
 
Got to the bottom of the stuttering issues hopefully this helps somebody. Context: X870, 9800X3D, 4080, Quest 3 (native link cable).

Upgraded CPU/MOBO/RAM over the last few days, noticed bad stutters even though headroom was ~40%, also game would launch on any random number of attempts (DCS, AC, ACC launch no issues) anything from 2-20 attempts to get the game to execute.

Digging into it I started playing with Link bitrate in the debug tool which I had previously set to 900 (5800x3d X570) which on that platform worked fine. Had to drop bitrate to 350 at which point it seemed OK but not really, appears OK but still stutters in terns and sim would still not launch on first attempt. Scratching my head here because I'm supposed to get faster no? More lanes USB4 and all that...

Ended up going into BIOS and manually configuring all the PCIe lanes, I set x16 to Gen4, the M.2 to Gen3 (my drive is gen3) and all seems well now.

Leaving all PCIe configs at Auto/Gen5 according to AI is causing bandwidth contention and link training overhead.

Bottom line, whatever your platform, if you are running a Quest3 with a link cable perhaps best to just get a discrete USB controller, above fixed my issues but if I had the space I'd throw a controller in there to make sure my million USB devices don't cause issues.

On a positive note with the x870 Quest3 no longer looses charge on the link cable when in use and just works every time with Link loading on boot if the cable is plugged in or as soon as you plug it in if the headset is on already. Before I had to do a bit of a rain dance at times of plugging unplugging from the PC itself for it to pickup the link connection.
Max CAS in virtual desktop AND in openxr toolkit plus codec AV1 @200, and you got alot of improvement
 
Last edited:
Running Pimax Crystal Light and removed opencomposite from LMU so the game runs on openVR and then just use SteamVR to play the game.

I have to try this. So just to be clear, we have to change PimaxXR routine for OpenVR and avoid using OpenXR Toolkit, right?
I'll give it a shot.

Meanwhile I did some test with my new system:
9800x3d/DDR5 6000CL30 - 4090 - Pimax 8KX

So far I settled on this settings

Setting LMU VR.jpg

with Normal Fov, High Render Quality and 90hx in PiPlay.
I also tweaked the json with some minor stuff like ambient occlusion and rearwiev mirrors.

It's almost 90FPS rock solid around SPA with daytime race and Hypers+P2s, but ideally I would tune down a bit render quality in PiPlay to have some GPU hearoom for more impredictable online racing. CPU is barely feeling it, with 40/50% headroom in AI racing.

While I was at it I took the chance to compile a quick and dirty screenshot comparison about CAS and the other sharpening tweaks as per Pimax video on the subject (this)

CAS.jpg

I need to test further, but looking at this I think CAS disabled or with very low values would be the sweetspot for me personally.
The settings from the Pimax video, with the Nvidia panel tweaks, seems to do more harm than good to me. I tried also NIS but it seems to produce a jagged image with just marginal benefits frametime wise.

All in all, coming from a Reverb G2 and a slower PC, I'm quite happy about the upgrade and the game is perfectly enjoyable without sacrificing image quality. Also the big FOV of the 8KX is a blessing for Simracing, and I can't see me going back to anything lower than 120°/130° Horizontal.
 
Hey guys.
I have a big difference in performance between offline Race and the online daily race with my PC and the psvr2. The offline weekend works great, absolutly no performance issues. But in the daily race its all slow, it lags a little bit and feels not responsive, by playing with a lan cable. Is it the same for you? Is there a setting to change that?
 
I’m yet to do any online laps, what’s the word on online performance? I currently have the game tuned for 30-40% headroom at Imola with a full hypers field at the back of the grid. Is online that much more taxing that I need to aim for more headroom?
 
Buenas tardes acabo de comprar las pico 4 el caso es que los circuitos y coches rivales se ven muy mal, anteriormente tuve las reverb y se veía bien, las gafas las tengo por cable con el pico connect y mi equipo es un i5 12600k con una Gráfica rtx 5070/12gb y Ram 32gb a 3200, sabrías decirme una configuración óptima para solucionar el problema?
 
No, eye tracking eork a bunch of games, quad view is possible for supported games too. I am on holiday too, but openxr toolkit could work with dfr, i hope somebody will try it.
Absolutely

I am flying back this weekend so if no jet lag I will give it a try
 
Buenas tardes acabo de comprar las pico 4 el caso es que los circuitos y coches rivales se ven muy mal, anteriormente tuve las reverb y se veía bien, las gafas las tengo por cable con el pico connect y mi equipo es un i5 12600k con una Gráfica rtx 5070/12gb y Ram 32gb a 3200, sabrías decirme una configuración óptima para solucionar el problema?
 
Good afternoon, I just bought the pico 4, the thing is that the circuits and rival cars look very bad, previously I had the reverb and it looked good, I have the glasses by cable with the pico connect and my computer is an i5 12600k with an rtx 5070/12gb graphics card and 32gb RAM at 3200, could you tell me an optimal configuration to solve the problem?
 
Hi
So I started racing online again over the last week. When I join a session and load into the pits my dash is blank. It doesn't matter what car I use its just blank the entire time. I have had to turn the speedo widget back on. Does anyone have any ideas or work arounds?
 
Back
Top