Search Results for 'Just Cause'

[Boblekobold]

I’m currently playing Atomic Heart. 110 FOV is Ok in my Reverb G2. I’m used to a little more too but It’s probably the right FOV.

I would recommand to set at least the resolution you want in Virtual Monitor before launching the game. There is a FOV slider ingame, so it’s really easy to configure (it takes 30s).

This game works really well with an RTX4090 with 3840×2880 resolution (so not as sharp as Metro Exodus Standard Edition, which is more optimized and beautiful). HUD resize / offset could have been useful (for subtitles at least, because HUD is not really needed otherwise).

Z3D is very impressive in this game. I find it sharper with 3D strenght at 0 but when you raise it, it really works, almost like G3D. There are some artefacts in cutscenes sometimes if 3D strenght is too high (you just have to lower it temporarily).

I tried UEVR too (and it runs smoothly) but I prefer VorpX on this game, like usual, especially to play the entire game (I could not with UEVR, even if it’s impressive too with this game, especially during cutscenes). Animations are cleaner in VorpX, image is sharper/clearer, especially at medium/long distance.
UEVR has good HUD, free camera rotations during cutscenes and impressive G3D (which allow you to understand more easily fighting cutscenes) but not very comfortable, especially when you’re swimming in polymer (and with flat fire effects, etc.) compared to VorpX 3D, and there are some really annoying glare effects you don’t have in VorpX.
And raytracing works with VorpX (and FOV seems narrower in UEVR).

[Boblekobold]

Virtual Monitor is really useful. With Quest 3 and Reverb G2, it also helps you to get 4:3 resolution.

Most useful resolutions are already predefined (I just had to add a 4:3 3200p resolution).

On Reverb G2, Metro Exodus works with 2880p, 3200p and even 3840p (5120×3840) resolution (at least in Z3D) with an RTX4090 ! With ultra raytracing and no DLSS (with Cloud Profile Ennchanted Edition and renamed excecutable). Even official G3D allow very high resolutions (especially if you turn off G3D shadow in VorpX). You can play fullscreen and adjust ratio in game video settings in this particular game.

Metro Last Light Redux (in G3D) is less optimized and 2880×2160 is already high resolution on RTX4090.

Metro 2033 original can reach easily 2880p in DX9 G3D (but if you go too high, your’ll have some glitches, 3D should be perfect in this game, which is like perfect native).

Bioshock 2 reach stable 90fps at 2880p G3D but you can’t really go above because it could crash. It’s still one of the best looking native like VR games.

Bioshock Infinite handle very high resolutions (more than 2880p, even on a GTX1080) and you don’t even need Virtual Monitor because windowed mode allow you to use any resolution/ratio you want !

I’m currently playing Atomic Heart and 2880p is smooth. 3840p works but it’s harder to fight.

Immersive screen seems sharper to me. You need higher resolution in full VR.

Of course with non 4:3 headset, you’ll have more megapixels, so 4:3 is better I think.

[Detective_Yoshi]

Thabks for your answer, Ralf. I really dont know what happened here.
After Titanfall 2 and Mirror edge, I tried Fallout 3 (wooooow!!! It worked!!!), Deus ex human revolution (bad;psvr 1 like resoulution and distúrbing tiny hands) and Dishobored 1 (good visuals but had to use direct scan sometimes during gameplay because it messes up in game) and all of them hooked first time maybe just changing in hook helpers.
Maybe these games didnt had any issues because were started in Steam, while Mirror and Titan needed Ea play to start? But why then Mass effect original 1 worked with ea play on (and then stopped working) and The Witcher 1 Steam wont start? Well ots a bit frustating but I cant be happier playing these games in VR and very afraid that Rdr2 and Cyberpunk maybe wont hook too if I try. Im very happy with your work and that you still want to improve in future releases.

[Benedict81]

Hi!

Just bought Vorpx and I’ve only played with it for two evenings. Got some questions that I didn’t find answers for.

Vorpx works and I’ve played Metro Last Light Redux with it for abit. Setting the game resolution is problematic, granted that this game has problems of its own with setting the resolution in windowed mode but heres what happens :

– If I just start the game with Vorpx running and use the automated settings, it wants to use a very low resolution (1600×1200 or something like that). I can change the resolution in-game, but that garbles the graphics (this is because of the windowed mode, not because of Vorpx, the graphics go weird even in flat mode if the game is not fullscreen). So not a Vorpx problem, it is the game not liking windowed mode.

– If I run the game through Vorpx Desktop Viewer, the resolution goes up, but now I can’t choose the resolution at all (the game locks the resolution to something weird like 5124×1440 (is that an ultrawide reso or something?), can’t remember the exact resolution but it was about that). Ok, the game is playable with this resolution, but I am still wondering why I can’t change the resolution in desktop viewer situation. I tried to turn the automatic resolution thing off, but that didn’t seem to do anything. I have created a plethora of custom resolutions into Nvidia control panel and if I understand correctly, it is recommended to run games in 4:3 aspect ratio or close to that for best results. And ofcourse I feel like I’d want to up the resolution a bit (getting near constant 120fps according to the Vorpx FPS thingy with this reso) cause the graphics still look a bit pixelated in the distance. Yes, I am new with Vorpx and I might be doing something wrong here, but thats why I am here :)

-Another tech question not related to resolution – is the ALT+L thing something that should be done once you are in-game and in full vr? I ask this because if i tap ALT+L once in-game, it reduces mouselook to just horizontal movement and if I don’t tap ALT+L I have full mouselook in both axis. Using the ALT+L also seems to remove the Y-axis options completely from the Vorpx menu (delete key), again, if I don’t tap the ALT+L, the menus have all the Y-axis options (and I do want full mouselook, especially in first person games).

Im running Win 11 (all the latest updates), RTX 4080, Pimax Crystal HMD.

Thanks!

[Ralf]

Games often render weapons at a different FOV than the rest of the world to make them look good on the monitor. That, besides moving the weapon out of sight unless you shoot, gets resolved by the auto weapon handling…

If the fully automated setup (usually manual tweaking causes more harm than good in highly automated profiles like this one) doesn’t work with either 23.1.5 or 24.1.0, wait until the next vorpX release. Maybe something changed recently.

I‘m sure it‘ll work in the next vorpX release though, I incidentally just tweaked the weapon handling stuff two or three weeks ago.

[Ralf]

The current version of the mod works fine with 2.13 normally. Occasionally game updates break the mod, hence the warning. Currently however the warning really just is a warning and everything works as expected under normal circumstances.

The most likely cause for your problem is some other mod getting in the way or some background program you may have running that also hooks into games, e.g. a GPU/CPU tool, a messenger, a game recording app or whetever else may display overlays in games and thus may cause a conflict.

[Boblekobold]

I never tried Titanfall 2 with VorpX but I know it works very well from others.

Maybe try to launch it without VorpX, and set it on DirectX11 or DirectX9 (VorpX doesn’t like DX10 and DX12 because it can’t render G3D, so sometimes official profiles only works with DX9 or DX11).

Did you try the hook helper, and alternate hooking ?

Some unofficial profiles requires to create a direct shortcut instead of launching VorpX (right click on VorpX in taskbar > create shortcut).

Sometimes you just have to wait and it works again (auto-update I presume), or use another version of VorpX (but I never had to and I tried a lot of games).

[Boblekobold]

It’s just a guess but i think…

If the image is out of proportion, it’s probably because your FOV (field of View) is too low (narrow), so you’re zoomed in.

It seems you can adjust FOV with this mod :
https://www.nexusmods.com/newvegas/mods/55085

Or simply with console command :
https://steamcommunity.com/app/22380/discussions/0/522730700808149795/
(But beware the achievements in this case, if it matters for you).

I suppose world Field Of view should be setted arround 120, then you lower it until it’s perfect for you.

Remember your perfect FOV value, it won’t change that much between games (except when games use vertical FOV, in which case you have to use lower value – multiply by 0.75 in 4:3 ratio).

I assume you use a 4:3 headset (Quest 3, Reverb G2 ?). Did you choose a 4:3 resolution ?
You should choose your resolution ratio and adjust zoom before adjusting FOV if you want a perfect experience.
You can raise resolution up to 2880×2160 or 3840×2880 (or more) if you want a very detailed image, but start with something low, as long as it’s 4:3.
Don’t forget using ClarityFX and raise sharpness before raising resolution (because it could be enough).

If you use an Aero, Pimax or other headset, it’s not 4:3.

Remember you can bind VorpX shortcuts (edgepeek, VorpX menu, recenter).

[tjpblue]

First off many many thanks,

The running in the foreground issue was something I had considered, though not exactly sure of the cause and effect. Though frustrated , I’m also amused right now because it did this as after I did the CET update and Microsoft framework update as well. I figured I didnt know what I was doing, reinstalling, rereading one word at a time and making sure I didnt misinterpret or miss anything. In essence it was probably good to go, just perpetuating this weird issue – but I am still incredibly grateful for your standalone update as it allows for me to narrow things down…. and you make good software :)

As far as clicking on the window , Im assuming you mean- the game on the actual desktop , to ensure Cp2077 is in the foreground. Will look into this as well.

Im fanatical about expunging bloatware, and do not over AV my system like at all, but one detail you mentioned caught my attention. I had programmed a steering wheel/pedal setup to work with the game while driving. And I am going to look into this today-Though its not being used at the moment (to simplify troubleshooting) Basically a driver and x360ce which at this moment im targeting as potential suspects.

Though my issue is probably one in a million, if I find out a solution I will post on the off chance someone else struck by a unicorn as well.

Thanks again,
TJP

[mr_spongeworthy]

Just feedback to report that newer versions of Pimax Client (1.29.01.01, as of this writing) seem to be working well. Win11, HAGS on, etc. No major issues beyond the usual Pimax PITA stuff (broken motion-smoothing, etc.)

Ralf, is there any way I we can override the resolution being sent to our Pimax HMDs through vorpX? Currently vorpX (current beta, virtual monitor disabled) sends fewer pixels to the HMD than it really requires for excellent clarity. I can compensate a bit by running a title at very high resolutions, but in effect that’s still getting downsampled to a lower resolution than ideal before being sent to my 8k-x (plus, it’s very GPU intensive obviously). I’m frequently leaving a lot of clarity on the table because of this: Running an older title, even at 5k, is doable, but that resolution is getting reduced considerably before it is pushed to my HMD, lowering the quality. It looks to me as if you push the same number of pixels to the 8k-x as you do to the 5k, but the 8k-x needs more than that. So far I’ve been unable to overcome this. Both Pimax resolution override and Steam SS do not result in a higher resolution. FPSVR shows this when one uses the “detect resolution” function.

[Zel1984]

A little more info, i was able to open the config app & turn off the virtual monitor which now lets me start VorpX without the black screen so it does indeed appear to be some problem with the virtual monitor for me which is weird because i have been using 24.1.0 for a while & the virtual monitor option has always been on & i never had this problem till just recently.

[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.

[zedja]

Hi, I hope what I bring is a simple problem with a simple fix. I’m using an HP Reverb G2, running WMR, launching SteamVR, then hooking VLC Media Player (launched as a non-steam game from the Steam library). It starts up just fine every time. But anywhere from 2-20 minutes into file playback, VLC and SteamVR crash with zero warning or error message. The two programs just close and I am dropped back into WMR Home.

I’ve read that SteamVR crashes can be solved by switching to DX11 using the Steam Overlay, but according to VorpX text displayed shortly after hooking (in the bottom left of the screen), DX11 is already set. I can’t check via Steam because the Steam Overlay refuses to open while SteamVR is running (something else I’ve been trying to troubleshoot to no avail). Besides VLC, no other programs crash SteamVR except occasionally Cyberpunk.

I am on Windows 11 23H2, with an AMD 5700X3D and an overclocked 1080ti. I’ve tried with the GPU overclocking turned off— the same issue persists.

Anyone run into a similar issue and have any advice? It would be much appreciated.

[JF]

Hello, all!

I’m beating a dead horse a bit here, but has anyone figured out how to run Mass Effect 3: Legendary Edition? There’s an official profile for 1, but none for 2 or 3.

There are a few suggestions:
* Rename MassEffect3.exe to MassEffect1.exe – Doesn’t work, because the Legendary Edition launcher needs to launch these files by name. There are many existing threads on this, with no solution.
* Use the original ME2 and ME3 games – not helpful, since saves aren’t compatible, and I don’t have those games (I just have the LE editions).
* Wait for an official Vorpx profile to arrive – It’s been 5 years.

I’d love to try and make custom profiles for ME2:LE and ME3:LE, but can’t, since those exe files names are already taken by Vorpx official profiles. I know this is a deliberate choice by Ralph, But I’m asking to please, please at least give us the option to mess around with this and get it working. If we mess up the profiles, that’s on – I’ll happily reset those, but it’s better than just not having the option.

[rogerty]

Hello,

Using TextureStreamingMemoryLimit=0.000000 and TextureStreamingDistanceLimit=800000.000000 is perfect for me. I don’t seem to have crashes anymore ! THANK YOU THANK YOU THANK YOU XD

I am curious about how did you get to test that specific change ? Had you some documentation about Bioshock 2 or was it just trial and error ?

I want to point at some remarkable aspects too:

– It works only in Windows 10, not in Windows 11 where I still get crashes (Dual boot saves the day)…

– I have just played the whole Bioshock 1 suffering lots of crashes on the way but I have finished it; It also happened that in Windows 10 I almost had no crashes at all (a few), but in Windows 11 it was almost non playable because of the amount of crashes… One significant point in BS1 was that after loading a saved game I had to press ctrl alt supr and after that, esc, to be able to view the game back, while in Windows 10 it never happened…

Regards,

Roger