LM Ultimate VR thread

oldgamergazza said:
Im thinking of upgrading to a Amd 9800x3d to run my Pimax Crystal Light, currently running a 13600k.
Is any one running the amd with the pcl and are there any issues or does it run satisfactory?
Click to expand...
first day: memory is not correct yet (because my ddr5 are xmp1 only, no expo ready, so 3000 men speed only now.
Same settings as before:(gpu TUF 5090)
Pimax :quality: 1.0, quad views balanced, no NIS
game: msaa 4x, post low, first four ultra, aniso 16x, from shadows and lower all low, cars 20
with the 13900K had 68-74 average, sometimes 90 fps
now with 8950x3D 90fps fixed, sometimes +6 +15 percent free gpu

soo yes, already better faster and smoother, jump for it
 
I have Pimax Super UW , can't start this sim with OpenXR Toolkit anymore, tried many Pimax clients always the same bug after april LMU patch.
Is anyone getting this?


1776019742301.png
 
Last edited:
Yata_VR said:
I have Pimax Super UW , can't start this sim with OpenXR Toolkit anymore, tried many Pimax clients always the same bug after april LMU patch.
Is anyone getting this?


View attachment 14169
Click to expand...
No. Have the same pimax S UW, using the openXR toolkit 1.3.1(I think) all works good, have not see if I got the emu patch, but I think I have to get it. Had this kind of error in the beginning, when NOT the pimaxOpenXR was the default. Today was downgrading the toolkit to 1.2.1 (for experimenting some issues) but all works good here. Bad news for you, sorry. Try to clean reinstall the 2.0.0 pimax client maybe to have a proper openXR
 
A question to mr.Yata VR: if you CULL the mid and the outer ring (so all black in openXR Toolkit, does the left and right center focus points are the same? For me the left is on the middle, and the right is about 30-40 degrees (a lot) to. the right. weirdo.
 
szaboviktor said:
A question to mr.Yata VR: if you CULL the mid and the outer ring (so all black in openXR Toolkit, does the left and right center focus points are the same? For me the left is on the middle, and the right is about 30-40 degrees (a lot) to. the right. weirdo.
Click to expand...
I didn't have had a problem with it, but I won't share my settings right now because I can't use the toolkit; previously, it worked perfectly in 1.3.8 with crop2fov enabled for performance. I ahve reinstalled it and problem still persist. Maybe its open composite issue
 
Is there any plan to render the UI in 3d space so that it's not so jarring to go from looking at the UI to game while racing?
 
szaboviktor said:
No. Have the same pimax S UW, using the openXR toolkit 1.3.1(I think) all works good, have not see if I got the emu patch, but I think I have to get it. Had this kind of error in the beginning, when NOT the pimaxOpenXR was the default. Today was downgrading the toolkit to 1.2.1 (for experimenting some issues) but all works good here. Bad news for you, sorry. Try to clean reinstall the 2.0.0 pimax client maybe to have a proper openXR
Click to expand...
I have figured out that enabling eyetracker in Pimax Client 2.0 beta is crashing openxr tool. Disabled and is running as before
 
AF seems to not work. Textures are muddy. I have set it to 16x. If I activate AF in nvidia control panel, GPU (5090) goes from 30% headroom to 100% usage and FPS drops off 15-20 from 75fps to 55-60fps. Anyone knows how to get ingame AF working?
 
Sele1981 said:
AF seems to not work. Textures are muddy. I have set it to 16x. If I activate AF in nvidia control panel, GPU (5090) goes from 30% headroom to 100% usage and FPS drops off 15-20 from 75fps to 55-60fps. Anyone knows how to get ingame AF working?
Click to expand...
The ingame setting seems ok to me, maybe check the texture streaming to be set as off. Couriously, differently from what you report about AF, AA in nvidia control panel cannot be injected anymore, a nicer addition compared to stock msaa.
 
Sparviero said:
The ingame setting seems ok to me, maybe check the texture streaming to be set as off. Couriously, differently from what you report about AF, AA in nvidia control panel cannot be injected anymore, a nicer addition compared to stock msaa.
Click to expand...
Yes, I've seen this (screenshot) on reddit and tried. But it seems to not work. Still tanks the GPU. I had like half the FPS. But I didn't know the injection doesn't work at all.

Openxr toolkit does still work for me. I cropped the top down to 60% and use foveated rendering. Also with the sboys3 driver we now have sharpening filters available on the Meganex and the Luma sharpening improves the image so much. From blurry to very clear.

I don't understand why the game devs don't implement such simple filters.

Edit: I've asked GPT. So it seems like it's not an AF issue but LOD or mip bias. Got to check that. Normally I have all on high and ultra.

Textures look blurry and muddy and only pop up shortly before I drive past it. Like road textures or ads.

Edit: it's solved. Track details were at medium. Maybe that was it. Not sure.
 

Attachments

  • IMG_9102.png
    IMG_9102.png
    173.1 KB · Views: 28
Last edited:
75Vette said:
Lol, looks like you changed your mind before you even finished writing that.
Click to expand...
Yes Hahah I think I was in VR, writing it with the virtual keyboard. Which is a pain to do.

I deleted LMU from Nvidia control panel and amped up track details to high. And textures are fine now. Maybe some settings in the NCP were messing it up.

I then added it to NCP again and only activated MFAA. Don't know if it works but it seems to not cost performance either.
 
I was away two weeks ago, came back last week, and ever since then I’ve been plagued by massive lag in VR. Every 10 to 50 seconds, the FPS drops from 72 to around 60 when I’m on the track with opponents. The problem doesn’t occur at all on the track itself, or at least it’s less frequent. I still need to monitor this. I’m using a 7800x3d and a 4070ti Super with the Quest 3. I’ve actually always used Virtual Desktop with the Ethernet adapter, but that hasn’t been working properly either since I got back from vacation. so i tried Meta Link but it makes the same problems I’ve already disabled culling and reinstalled the game tried different drivers.. I’m out of ideas now, and I’m pretty annoyed. Does anyone here have any other suggestions?
 
Last edited:
Andregee said:
I was away two weeks ago, came back last week, and ever since then I’ve been plagued by massive lag in VR. Every 10 to 50 seconds, the FPS drops from 72 to around 60 when I’m on the track with opponents. The problem doesn’t occur at all on the track itself, or at least it’s less frequent. I still need to monitor this. I’m using a 7800x3d and a 4070ti Super with the Quest 3. I’ve actually always used Virtual Desktop with the Ethernet adapter, but that hasn’t been working properly either since I got back from vacation. so i tried Meta Link but it makes the same problems I’ve already disabled culling and reinstalled the game tried different drivers.. I’m out of ideas now, and I’m pretty annoyed. Does anyone here have any other suggestions?
Click to expand...
Turn off live screens in the graphics settings. That solved it for me. That was half a year ago. But you can give it a try.
 
Oops said:
Can I ask how you get this to work? I tried it before, but couldn't quite get my head around it :rolleyes:
Click to expand...
USb-c network adaptor connected to the Quest 3. ( i use usb-c extension cable to connect the network adaptor to the Quest). Disable wifi in your QUest 3 and it will connect automatically with your wired network. Start VD
PS: try to find a usb-c network were you can daisy chain usb-c device. You will be able to connect the usb-c network to charge the quest at the same time
 
Last edited:
mledour said:
Hi,
I've made a small OpenXR layer to crop the FOV and you can add a helmet overlay to get better immersion :)
Performance was a priority on both sides — the helmet overlay costs ~1% GPU when enabled and 0 when off, the FOV crop actively saves GPU by reducing the rendered pixel count, and per-frame CPU overhead is negligible.

The DLL and installer are signed, tested live online in LMU on a Pimax Crystal Light, no anti-cheat issues

Testers and feedback very welcome — and if anyone wants to contribute helmet PNGs, I'd happily ship them in the installer

Have fun ;)

https://github.com/mledour/OpenXR-Layer-crop-fov
Click to expand...

I'll test this out.

How does it interact with OpenXR Toolkit, and especially things like Crop2Fov or the Virtual Desktop Fov Stencil or Horizontal and Vertical FOV Tangents?

Your github page could do with a screenshot to show what it looks like when implemented :)
 
mledour said:
Good point on the screenshot — I'll add one to the GitHub page!

Regarding OpenXR Toolkit: this layer is intended to replace Crop2Fov and the H/V FOV Tangents features from OXT. Running both simultaneously would stack the crops and produce unexpected results, so if you're using my layer, disable those OXT features. The Virtual Desktop FOV Stencil operates at the compositor level and doesn't conflict, so that one is fine to keep.
Click to expand...

Tested with Quest 3 via Virtual Desktop. Ran the manual install (PS from an elevated terminal).
  • LMU menu UI and all in-game hud elements were displaced several meters in front of my centered view point.
  • In cockpit view the crop appeared to work, but there was no helmet overlay. I don't have Crop2Fov on so this shouldn't have impacted.
  • The cropped areas override my OpenXR Toolkit FPS display placement, which I have high and right. I guess there is no way to have this in unrendered space.
  • All of my Racelab overlays were gone.
I have a feeling your install method conflicts with Racelab. Any way to make them play nicely together?

"file_format_version": "1.0.0",
"api_layer": {
"name": "XR_APILAYER_app_racelab_Overlay",
"library_path": ".\\XR_APILAYER_app_racelab_Overlay64.dll",
"api_version": "1.0",
"implementation_version": "50331648",
"description": "Overlay API layer for https://racelab.app",
"functions": {
"xrNegotiateLoaderApiLayerInterface": "RacelabApp_xrNegotiateLoaderApiLayerInterface"
},
"disable_environment": "DISABLE_XR_APILAYER_app_racelab_Overlay"
}
}
Click to expand...

{
"file_format_version" : "1.0.0",
"api_layer": {
"name": "XR_APILAYER_MLEDOUR_fov_crop",
"library_path": ".\\XR_APILAYER_MLEDOUR_fov_crop.dll",
"api_version": "1.0",
"implementation_version": "2",
"description": "Narrows the effective field of view and swapchain resolution to reduce GPU load.",
"functions": {
"xrNegotiateLoaderApiLayerInterface": "xrNegotiateLoaderApiLayerInterface"
},
"disable_environment": "DISABLE_XR_APILAYER_MLEDOUR_fov_crop"
}
}
Click to expand...

Didn't test OpenKneeBoard with Tiny Pedal yet.

Your uninstall script worked fine, menu UI and hud distances returned to normal and Racelab overlays returned.
 
75Vette said:
Tested with Quest 3 via Virtual Desktop. Ran the manual install (PS from an elevated terminal).
  • LMU menu UI and all in-game hud elements were displaced several meters in front of my centered view point.
  • In cockpit view the crop appeared to work, but there was no helmet overlay. I don't have Crop2Fov on so this shouldn't have impacted.
  • The cropped areas override my OpenXR Toolkit FPS display placement, which I have high and right. I guess there is no way to have this in unrendered space.
  • All of my Racelab overlays were gone.
I have a feeling your install method conflicts with Racelab. Any way to make them play nicely together?





Didn't test OpenKneeBoard with Tiny Pedal yet.

Your uninstall script worked fine, menu UI and hud distances returned to normal and Racelab overlays returned.
Click to expand...

I tried the layer with the Crop2VR mod and they do not work well together. You can get them to work together but the simplest way is to just reinstall the original OpenXR Toolkit dll.

For the helmet overlay not displaying, this is because you used the manual installer which doesn't install the helmet image files. You can use the installer for simplicity, it will install default settings and helmet files.

For the overlays not displaying, this is because the fov_crop layer needs to be loaded before other overlay layers. You can use this tool to achieve this: https://github.com/fredemmott/OpenXR-API-Layers-GUI

I have updated the readme and added a screenshot with the helmet overlay.

Thank you very much for your feedback 😉
 
Last edited:
I´ve found this on reddit but cant ask there the post is disabled to replies.

Where can I find these settings mentioned in the post? Because my game is too dark in VR.

Post Processing (appearance tab):

Post Processing = On

Contrast = 52.5

Brightness = 47.5

Exposure = 47.5

Saturation = 50

Vibrance = 0

Highlights = 100

Shadows = 0
Click to expand...
 
You must log in or register to reply here.
Back
Top