VR Discussions, Questions & Feedback

Hi

I'm having a problem with my Pimax Crystal Light.

In-game, I have two transparent screens right in front of my eyes (these are the ATH layers), even when I remove the ATH.

It's from Open XR because I don't get them through SteamVR.

Any ideas?

I can get a third one if I display the FPS, It moves with my head.


CPU i7 13700kf GPU 7900XTX

 

I get the best results using Pimax-OXR runtime at 90Hz (Lab) setting, buttery smooth. Image quality is a bit on the fuzzy side but, with your stronger GPU, you could try running 120Hz for improved image quality.

 

I suspect you have some conflict with software. When you say OpenXR, are you using the Pimax integrated version and bypassing Steam VR altogether? Be sure you have the Steam VR switched to OXR mode. I had some visual artifacts initially and uninstalled Steam VR to insure it wasn't conflicting with PimaxPlay. Steam may have reinstalled it again but, no issues since then.

 

Mine updated and I didn't even notice or notice that option was now there. Thanks for the heads up!

 

Thanks for helping me !

I bypass steamVR with opencomposite and use openXR toolkit .
I open the game on steam .
Sorry, I was a console player, I'm not good on computer

 

I never got on very well with OXR toolkit but, it's not needed when using the Pimax CL imo.
I would just be sure the OpenComposite switch is set to bypass Steam VR and use PimaxPlay's integrated OXR support. It's much easier and provides very good results. Pimax has some good tips and videos on their site that can help you set it up properly.

 

Thanks, after many tries and lots of testing, best option , was using openXR with resolution around 6k, and limiting vertical FOV to gain performance, and enabling foveated render in the OpenXR toolkit, MSAA off.

 

Hi, hope someone has some tips for a weird 'bug' I have.
My setup: 7800x3d,7900xtx, Pico4@72fps wired using VD.

Recently I've been seeing my GPU headroom drop from +50% to -10% while racing, or when starting a session. The fix is to look down at the floor of the car for several seconds, and then the headroom goes back to +50% and stays there. So for instance when you start a session in the pit, occasionally I'll be at -10% and asw will kick in. Then look down, wait for it to recover and look back up. Now it's at +50% and alls well. Nothing in the external view has changed, but some massive load has clearly disappeared.
I've tried various setting changes in game, but don't see anything that could have this massive impact (and be invisible)

Any ideas???
Ian

 

It sounds like SSW is activated during VD and then deactivates too slowly. Do you have SSW set to automatic? Try disabling it if that's the case.

 

That might be it, . I tried a quick 30min online and it stayed rock solid. Clearly something was confusing the ASW trigger?
Thanks Xenix

 

If you set your VR setup right at the performance limit, this happens with SSW and ASW. Generally, you should turn off SSW and ASW when driving with force feedback. This will halve the frame rate, and you'll only feel half of your steering wheel inputs and outputs on your PC and in your hands.

 

To be fair with sim software in general, I believe the simulation and FFB included runs at a MUCH higher frequency than FPS output.

EDIT: but not Madness Engine, because low FPS impacts a lot FFB.

 

What is SSW?

 

Synchronous SpaceWarp. Is your headset set to 80 hz ? Then if your framerate drops to 79, 68 or 57 instead of the 80 you set it to ? Then your FPS is cut in half at 40, and those missing 40 are interpolated frames so that it makes it look as if it was running at 80.

 

If you enable Turbo mode in OpenXR Toolkit that will permanently stop ASW

 

That doesn't matter. If you have a steering wheel with a lower frequency, you might just notice it less. Pay attention to the latency when you enable SSW. The game will run slower and/or skip frames. These frames will also be skipped on the steering wheel.

 

Even a G29 can run at 400Hz.

But you are right and I was wrong. This thing runs the FFB at least at the same frequency of FPS. Tested at 20 FPS and 300.

And this is stupid as hell in software design. Really pathetic.

Tested now in AC and works MUCH better. Madness Engine link - I don't know why - FFB to FPS heavily.

I never felt this before because I usualy play at 90-120Hz, and at 120 to 60 FPS this impact in FFB isn't so noticeable. But If FPS goes to less than 60 FPS, it's terrible.

 

72/36 is bad.
120/60 is much better.
I'd rather have a stable 72 than 80/40 90/45 That's just my opinion with my system.

It's only at 120/60 that the difference becomes blurred. But you can still feel it. I would say (with my system) that at a stable 80, I can no longer tell the difference.

 

I would definitely not recommend 120/60 ever because at the 120 FPS mode the battery is getting absolutely hammered. I personally just stick to 72 with SSW off. It gives me more performance headroom and when i tried higher framerates i felt no difference. I notice different framerates immediately on a TV / monitor, but not in VR.

 

Thanks, thought this cutting in half was ASW? What is ASW then?