Search Results for 'grid'

[JDogDaBoy]

I’m no longer getting the open XR instance creation failed message anymore but vorpx still doesn’t seem to want to hook into the game. And I don’t know if the home screen you’re talking about has recently become the default, but I’ve never had to go to that space before. The game always started up with just a blurred background and I can’t get that to happen anymore. And with the home screen, the game is not the center screen it’s a very small screen off to the left. The center screen which is fairly large is just a man with a VR with a question mark. I only use one VR controller to click on things and I don’t really have the ability to use both VR controllers. When the game starts with that screen I can press delete on the keyboard and the menu will pop up, but none of my buttons will work for the game and I can’t even get off of the start screen from the game because the controller and the keyboard become inactive as soon as I enter that space. I really only use vorpx as an aiming assistance for things like Call of Duty and so mostly I just need the head tracking capability. But when I enter that gridded room there doesn’t seem to be any sort of head tracking. I don’t even know how to get that big gray box with the man in the VR to go away and how to get the game to Center.

[moblackny]

I have had vopx for about 10 days now and have yet been able to get it too work. I have contacted support and have followed all of the suggestions they gave but no luck. seeing if anyone here can help. the errors I get is no oculus headset found I have the meta quest 3. Also getting the failed to attach exe. I have check to make sure nothing that can interfere with it is running. these are the steps I am doing. please let me know if they are not correct as I am new to this.
1. opening vorpx config selecting oculus as device
2. going to local profiles and selecting the profile for the game I am trying to use and clicking apply and close
3. powering on the meta quest 3 which is connected via link cable to pc meta quest link software loads and says connected (although I have read that I should close the meta quest software because vorpx will detect without it so I have tried both ways)
4. Then clicking on the shortcut on my desktop for the game I want to use. (although I have read that I shouldn’t and I should start the game through vorpx but have yet to see a option to do so)

I get attaching said exe then attaching exe failed then the menu option comes up where I can choose to install helper or preferred helper which I have tried both then I get no oculus headset found.

this is a 6 week old powerhouse windows 11 pro computer with more then enough hardware to run any game at max settings $2000+ 48GB ram RTX4060 TI MSI b760 4TB Samsung 990 pro with heatsink

I do have dual monitors which I just read this morning that this can be a possible issue so I have yet to try disabling one of them about to leave for work so don’t have time to try this. if anyone can assist it would be greatly appreciated. Games I have tried are Dirt 3, all GRID games, WRC Generation and Call of duty modern warfare.

Also just checking when they say to make sure there are no conflicting software running they just mean to stop there processes in task manager not uninstall them. I know that is a no brainer but I have spent over 30hr in 10 days trying to get this to work so I want to make sure Im not missing anything. I consider myself to be a above average computer technician and troubleshooter but this has me stumped to say the least.
Please HELP someone

[moblackny]

I have had vopx for about 10 days now and have yet been able to get it too work. I have contacted support and have followed all of the suggestions they gave but no luck. seeing if anyone here can help. the errors I get is no oculus headset found I have the meta quest 3. Also getting the failed to attach exe. I have check to make sure nothing that can interfere with it is running. these are the steps I am doing. please let me know if they are not correct as I am new to this.
1. opening vorpx config selecting oculus as device
2. going to local profiles and selecting the profile for the game I am trying to use and clicking apply and close
3. powering on the meta quest 3 which is connected via link cable to pc meta quest link software loads and says connected (although I have read that I should close the meta quest software because vorpx will detect without it so I have tried both ways)
4. Then clicking on the shortcut on my desktop for the game I want to use. (although I have read that I shouldn’t and I should start the game through vorpx but have yet to see a option to do so)

I get attaching said exe then attaching exe failed then the menu option comes up where I can choose to install helper or preferred helper which I have tried both then I get no oculus headset found.

this is a 6 week old powerhouse windows 11 pro computer with more then enough hardware to run any game at max settings $2000+ 48GB ram RTX4060 TI MSI b760 4TB Samsung 990 pro with heatsink

I do have dual monitors which I just read this morning that this can be a possible issue so I have yet to try disabling one of them about to leave for work so don’t have time to try this. if anyone can assist it would be greatly appreciated. Games I have tried are Dirt 3, all GRID games, WRC Generation and Call of duty modern warfare.

Also just checking when they say to make sure there are no conflicting software running they just mean to stop there processes in task manager not uninstall them. I know that is a no brainer but I have spent over 30hr in 10 days trying to get this to work so I want to make sure I’m not missing anything. I consider myself to be a above average computer technician and troubleshooter but this has me stumped to say the least.
Please HELP someone

[Spinelli]

Ralf wrote:

Sorry for the spam detection troubles you encountered. The alternative to having spam detection on in the forum software would be a 3:1 spam:content ratio unfortunately, extra bad since the beautiful invention of drivel bots like ChatGPT etc.

Your actual issue:

Maybe some weird issue related to Pimax’s software that puts itself in between vorpX and the headset. Reversed eyes are conceptually impossible with vorpX’s G3D method (at least unless the profile author intentionally inverted them, which obviously isn’t the case here).

Possibly related to the time vorpX hooks into the game (before or after Pimax initializes its stuff). Enabling alternative hooking in the config app may be worth a shot. That aside maybe check whether there is some stuff in the Pimax software you can turn off. Haven’t checked a Pimax headset in a long time, but a few years back they had some custom reprojection that could change the IPD and make things appear cross-eyed occasionally.

vorpX does not change the power plan. Some VR runtimes do howewer. At least the Meta (Oculus) runtime does. Not sure about Pimax.

OK, update.

Starting Game Consistently

It looks like I have VorpX, rFactor, and SteamVR consistenly playing good with eachother. I just try to start them in the following order: PiTool, VorpX, SteamVR, and reversed order for closing, and also I make sure to always close SteamVR (not Steam as a whole) once I’m out of any game along with starting the games from PiTool (which automatically opens SteamVR). Some of those steps may not be neccessary but the formula seems to work every time. I also make sure not to alt-tab out of the game. This caused issues last time with the SteamVR grid-environment being superimposed in the rFactor game and led to other issues too (had to end up closing game from task manager and then restarting all VR-related programs/services).

Parallel Projections

I forgot that Pimax’s Parallel Projections is a requirement for VorpX. It says right in the VorpX Pimax guide (which I’ve read multiple times). 3D is fine now

Remaining Issues

1. I still can’t get the head-movement to work without the entire game’s screen being locked to my head (unless I run in 1 of the interactive movie screen modes or whatever which). If I enable head-tracking, the entire screen is still locked to my head but, mixed with that, there’s a teeny, tiny but of proper head movement relative to the locked screen but it’s like 3% of the entire head movement compared to the locked-screen’s head movement.

If I enable the game’s mouse free-look setting, the camera / driver’s head suddenly looks upwards while spinning and falling to the ground.

If the game supports TrackIR / head-tracking (like rFactor and all games based on it’s engine), do we just rely on VorpX’s head-tracking being enabled? Or is the game’s mouse free-look setting supposed to be activated instead (via a game’s hotkey)? Or are they supposed to simultaneously be enabled/activated?

2. The 3D is basically perfect – the ISImotor (commonly referred to as the ISI GMotor) engine that rFactor runs on has always been one of the best native Nvidia 3D Vision games anyways so I’m not surprised – however there’s one issue. Lots of the vehicles’ in-car dash’s gauges (or on the car’s dash, steering wheel, etc.) are almost impossible to look at as they’re being rendered in only 1 eye but not the other (or sometimes only partially in the other eye). It’s extremely disorientating and headache inducing even if you don’t look at it.

This issue used to only occur with games running on the ISImotor engine if the particular game didn’t have a 3D Vision profile assigned to it. The fix is incredibly easy. With Nvidia Inspector in the Stereo section, make sure “StereoProfile” is set to “Yes” and “Stereo TextureEnable” is set to “0x00000001 COMMON_STEREO_TEXTURE_ENABLED”. After that, all the games’ cars’ dashes, gauges, display screens, etc. were fixed and PERFECT.

The problem is, there’s no more “StereoProfile” setting in Nvidia Inspector, and the “Stereo TextureEnable” setting only has literally one option to choose from: “0x00000001” (no writing after it). I know Nvidia removed 3D support from their drivers but I thought simply enabling these “bits” in Nvidia Inspector would still be available.

[drowhunter]

There’s a profile for this game that does full G3D and FullVR and it’s really, really good. Even 6Dof works (kind of)

Only thing I needed to do was map the headtracking to to right joystick with an anti-deadzone of about 0.3

The issue is while the yaw works well enough the pitch is totally whack.

When moving head up or down the world moves with you.

There is an option to lock pitch but it doesn’t work.

If there was a way to simply tell Vorpx to simply ignore the tracking data for pitch altogether it would be perfect.

Ralf since Vorpx is obviously in control of receiving the pitch from the headset could you add an option to ignore it please?

I also tried turning the Y sensitivity on the joystick to 0, but it doesn’t do anything, in guessing because it doesn’t actually seem to be moving it’s not the in game joystick that is causing the actual problem.

E.g even looking down in the game if you push to the absolute bottom it switched the camera to look behind. and when pushing the joystick all the way up the have only moves your head like 2 degrees this is just how the game works.

it seems that in full VR Vorpx is the one causing this world movement on pitch.

[papakapp]

Desktop viewer works fine. Witcher 3 does not. (only game I tried)

When I go in game, SteamVR launches, and I get the SteamVR loading screen with the grid pattern drawn on the ground. Then, when the view in the headset starts streaming the sound from the game, the screen goes black.

any help?

I am also unable to run any game that I purchased from the Steam store in VR, Although I could yesterday, before I installed Vorpx. Now when I try to launch a game from the steam store, Vorpx tries to hook into it, and prevents it from launching.

*edit* nevermind about the last part. I was able to exclude steam games from whatever Vorpx tries to hook into. (trivially) still no witcher though.

[dlee]

A few tips:

Don’t like the extreme, crawly aliasing? You can force sparse-grid supersampling (SGSSAA) and it works with Vorpx. There is a performance hit but it’s less than I imagined it would be. It is extremely good at cleaning up aliasing. I would just disable the game’s ineffective anti-aliasing in the game’s menu.
https://www.pcgamingwiki.com/wiki/Dishonored#Anti-aliasing_.28AA.29

Eventually you will get to a NPC dialog that will not work properly in DirectVR mode. The dialog options will not appear. Disabling DirectVR for that conversation is a fix.

Also, after a successful DirectVR scan you may still not be able to look around. Try climbing an in game object to fix that.

[drowhunter]

+1 for this AFR works great for me and If it allows me to play more games in VR im all for it.

I really want GRID 2019 and GRID Legends to be in VR so bad.

[sikjar]

I am fine with 2D, I just want to be able to play in my headset using headtracking, and VorpX makes that possible.

I have tried to increase the quality without antialiasing, but even with very high supersampling there is stil a lot of aliasing and flickering on distant objects. Maybe I am especially sensitive to this, but I really find the game unplayable without antialiasing. The solution using NPI applies 4x Multisampling and 4x Sparse Grid Supersampling plus a few other setting changes, which almost totally eliminates those problems.
So I am still hoping for some solution that will allow me to use the NPI method in VR.

[mr_spongeworthy]

RJK_ wrote:

Just a quick note on the UGRIDS setting. The game crashed when saving with uGridsToLoad=7 and loading a savegame after resetting uGridsToLoad to 5. A value of 6 seems to work though.

Yes, that’s a know issue with UGRIDS; you can find a fix through console if you really want to, it’s not too hard. uGrids must be odd numbers, 5 works, 7 works, but 6 is actually the same as 5, that’s why you can have uGrids=6 and still load those saves if you set it back to 5. IIRC anyway. Bethesda games require so much tweaking to really get them right that it’s hard to keep track! uGrids can also cause other random problems, so if you aren’t used to that then probably don’t set it to anything other than the base 5.

Are you using G3D?

[RJK_]

Just a quick note on the UGRIDS setting. The game crashed when saving with uGridsToLoad=7 and loading a savegame after resetting uGridsToLoad to 5. A value of 6 seems to work though.

[RJK_]

Havent had one crash since i installed the multicore fix above. Now with Ralfs incredible new sharpening you can spot distant details you never belived they were there. ( both sliders all the way up to max ). Uhh year good Idea with the UGRIDS setting looks awsome. Here now 65/82 smoothly with 3840×2880 and maximum texture pack on my GTX1080ti.

[mr_spongeworthy]

Fallout 3 is definitely one of my top, if not my very top vorpX game. It just looks great and it runs very well in G3D at high resolutions. Thanks for the tip about the multicore fix. I’ll take a look at that. I’ve got a thread here somewhere that covers using the Fallout stutter remover etc, which may be necessary for many (Fallout 3 and NV had major stuttering issues when run at frame-rates other than 60 or 30, if I remember correctly). Other issues to avoid are frame-rates greater than 60, which will break the physics and can cause all kinds of problems (this issue persist through at least Skyrim and FO4). So you’ll want to use motion smoothing to double your frame-rate and lock your actual fps to 45/90, or 60/120 (for example). I lock it to 45/90 and that’s plenty smooth enough for me even in full VR mode (and it allows me to use UGRIDS=7, as that makes a HUGE difference to FO3’s otherwise extremely short draw distance.)

[Ralf]

Nothing draw distance releated is changed. Just the resolution and the dialog FOV. The game always had fairly severe pop-ins. It only loads a certain amount of ‘grids’ at once, no matter how high you set the draw distance.

There is an .ini setting named ‘uGridsToLoad’ or something similar that allows you to load more grids. Heavily impacts performance and memory consumption though, so be careful. If memory serves right 9 was what I settled for back in the day, beyond that the game supposedly becomes unstable. Probably earlier with mods that add more objects to the scenery.

[Ralf]

Can’t replicate any of that for the life of me. 2019 crashes on my main dev box on start currently (with or without vorpX), but I just checked 2020 and it runs as great as always. My usual test is starting a race event with full grid. Except for the start with everyone in front of me I pretty much get stable 90fps with G3D at 1440p and with roughly medium graphics details. Looks great, feels great as well.

That’s with a 3080 though, so obviously a fast machine. But on my 1080 test box the F1 games run also fairly well. Should be absolutely no problem to run these games at least with stable 45fps on a decent PC.

The only thing I can really recommend is resetting the vorpX profile to default and using either the low or medium detail presets provided by the game without adjusting anything manually. Also make sure to let vorpX audjust the game’s settings in case you disabled that.