Search Results for 'Crysis 3'

[OculusRiftRocks]

ah, can the same thing not be done with crysis 2/3 built in 3D, or was that built in 3D a cheap z-buffer.

[Ralf]

Update 2018/12/15

vorpX 18.3.2.2 has been released. This (hopefully) concludes the series of fixes related to issues with the most recent SteamVR version.

Changes/Fixes:

• Improvements for WMR headsets related to issues with most recent SteamVR.
• Fallout 76: FOV did not work since the game got official FOV change support.
• OpenVR updated to 1.1.3b

---

Update 2018/12/09

vorpX 18.3.2.1 has been released. This hotfix addresses the SteamVR head tracking swim/latency introduced with yesterday’s update. No other changes.

---

Update 2018/12/08

vorpX 18.3.2 has been released. This is a maintenance release mainly addressing frequent frame judder in SteamVR mode after the latest SteamVR update.

In addition to that some related changes originally intended for vorpX 19.1.0 have been backported to 18.3.2, most notably support for Motion Smoothing (SteamVR), respectively Asynchronous Space Warp (Oculus). vorpX 19.1.0 is still on track for a pre-Christmas release.

Changes/Fixes:

• SteamVR: Fix for frequent judder below 90fps with recent SteamVR versions.
• SteamVR/Oculus: Motion Smoothing/Asynchronous Space Warp support.
• SteamVR: Supersampling <1.0 is now taken into account (only important for Pimax 5k/8k).
• Oculus: Crystal Image setting takes user set super sampling into account.
• D3D11: several multithreading fixes and improvements
• The Witcher: better Geometry 3D profile, Z3D parameters tweaked
• The Witcher 2: G3D did not work anymore, Z3D parameters tweaked
• GTA V: scalable HUD added

---

Update 2018/11/15

vorpX 18.3.1 has been released. This is a maintenance release that mainly adds support for Fallout 76. The profile is a fully featured DirectVR profile with everything DirectVR can do in the best case including automatic resolution, FOV (two methods) and basic roomscale.

Additionally minor issues with the program itself and other profiles have been fixed.

In case anyone wonders: the Frostbite engine G3D support that sparked a bit of interest recently is still in development and will be made available with the next larger update 19.1.0 before the end of the year.

New profiles:

• Fallout 76: G3D/Z3D, full VR, DirectVR: head tracking, resolution, FOV, tweaks

Changes/Fixes

• Effects that look bad in VR (e.g. DOF blur) can also be disabled with Z3D.
• DirectVR scanner could time out with large scans in low memory situations.
• DirectVR menu page didn’t behave correctly if both memory scan FOV and .ini edit FOV are available.
• FOV scan was run despite .ini edit FOV being selected if both are available.
• Fixed an occasional G3D crash in Fallout 76 (and maybe other DX11 games).
• Arma III: DirectVR FOV was slightly too high.
• The Witcher 3: some objects were rendered at wrong depth.
• Crysis 3: reflections fixed, effect fixes.
• Fallout 4: minor gun decals and fire glitches fixed.

---

Update 2018/10/25

vorpX 18.3.0.1 has been released. This is a hotfix that addresses the issue below. No other changes.

• Black textures with Z3D in some D3D11 games (18.3.0 regression)

---

vorpX 18.3.0 released

After four maintenance releases for the 18.2 branch it’s finally time for a slightly bigger release with a bit of feature refinement and also more and enhanced game profiles. Most notable additions are: Dark Souls Remastered, Monster Hunter World, Shadow of the Tomb Raider and Assassin’s Creed: Odyssey.

Experienced users can now create much better custom profiles by defining HUD/shadow etc. shaders.

For details please check this blog post.

[Ralf]

This functionality is part of the DirectVR settings optimizer for Crysis 3 and only applies to the actual Crysis 3 profile.

When you make a copy of that profile to try an unsupported game, the routines doing the image zoom/fov calculations aren’t invoked.

[Ralf]

It’s capped on purpose in Crysis 3, the game does not allow to set the camera field of view high enough for the screen to be fully used vertically while maintaining a correct FOV. The alternative would be a fully used screen with a too low FOV, resulting in image distortion. You would definitely not want that.

[daggey]

Hi so I am using crysis3 and the image zoom setting within the vorpx menu maxes out at 0.75 for some reason – so the image is quite small and there is significant unused black screen around the edge of the image. If it would zoom in to 1.0 or 1.1 it would be much more immersive/look much better. Is there any way to edit the config file to change the max value of the zoom or to otherwise change it to be able to zoom further than the profile seems to want to let it ? Thanks.

[Ralf]

Lichdom is not supported, so it’s perfectly normal that you don’t get 3D. Judging from what I found on the internet it seems to be based on CryEngine 3, so making a custom profile based on the Crysis 3 or the Kingdom Come Delieverance profile is worth a shot. There is no guarantee though that this will work.

If it works, you will get basic stereo 3D. FOV adjustment for FullVR mode would have to be done manually though.

Same for Vermintide 2. That one will be looked into before the next update though, I just can’t promise anything yet.

Some general info: vorpX doesn’t automatically provide stereo 3D for every game you throw at it. For stereo 3D and Direct VR functionality game specific profiles are required. Normally you should see a message in the headset whenever you open an unsupported game to avoid any potential confusion in this regard.

To check beforehand whether there is a profile for a game you want to try you can use the “Local Profiles” list in the config app or the supported games list.

Team Fortress 2 (and other Source engine games): there might be an issue with a recent SteamVR version causing this. I can’t say anything more specific yet, but the issue will be looked into before the next update.

[haints]

morbidexpression wrote:

Just use the Crysis 3 profile and don’t rename anything

What are you talking about?

The Crysis 3 profile is locked down to the Crysis3.exe. You can’t add KCD to that profile because VorpX won’t let you. So you have to rename the KCD.exe.

If you are talking about making a COPY of the Crysis 3 profile and using that, I already said I tried that and it didn’t work for me.

morbidexpression wrote:

What’s to keep trying?

Like I already said, even when I got the Crysis 3 profile to work with KCD, ONLY the HUD was in 3D. Everything else was flat, with no depth at all.

[morbidexpression]

What’s to keep trying? Just use the Crysis 3 profile and don’t rename anything. Loads just fine and Geometry 3D works everywhere.

[haints]

Old post, I know, but I couldn’t get it working with cloned profile either. I renamed the game’s .exe to Crysis3 and that worked but only the HUD has 3D. Will keep trying.

[haints]

I just tried it by renaming the game’s .exe to Crysis3 (wouldn’t work with cloned profile) and it hooks and loads but only the HUD is in 3D. The HUD itself has depth but everything behind it is in 2D. Z3D doesn’t offer 3D either. Any work arounds?

Great news to hear there’s going to be (might be?) an official profile as I think this would be an awesome game with VorpX …

EDIT: KCD is running on Cryengine 4 and Crysis 3 is on the previous engine. Prey also runs on Cryengine 4 so I will try that next.

[steph12]

that’s great news !

thank you Ralf for looking into this soon :)

and thank you Baktus, i will try crysis 3 profile with kcd and see how it goes.

[Baktus]

Crysis 3 works for kcd very well with g3d

[bluepill]

Hi Ralf,

good news, Crysis 3 now works for me in Vorpx 17.3.0

I found out – sort of – by accident:
Origin suddenly would not start and showed this error:
“Origin.exe – System Error: the program can’t start because MSVCP140.dll is missing from your computer. Try reinstalling the program to fix this problem.”

To solve this, I had to install VC redist 2015 I found on some forum posts.
But 2015 refused to install because the *nice* Win 10 unstoppable auto update feature already installed VC redist 2017. (a newer version…)

So, to fix Origin I had to uninstall VC Redist 2017 x86/x64 and replace it with VC redist 2015 x86/x64.

Now Origin starts again, but Crysis 3 is also working fully in vorpx 17.3.0
(I had to use Z-buffer 3D though, because Geometry 3D caused artifacts in gun and character textures)

Maybe this could help out some other folks.

PS: Very nice experience in Crysis 3, almost Native VR game feel!

Bluepill

[bluepill]

Hi Ralf,

Good job on Vorpx 17.3.0!
Works very nicely with Mass Effect Andromeda. (framerate is ~50 FPS with my R9 290, so I am still tweaking a bit to get it higher – already disabled Vsync)

I just freshly installed Crysis 3 from Origin to try out this game in VR on my Oculus DK2.
I started a new game in recruit mode and skipped the training. (I am more a person for training on the job I guess:)
Seems Vorpx is correctly attaching to Crysis 3. Intro scenes are running fine in VR

But after the intro clip of helicopter flying to the dome, all I see is blackness in my headset and on my PC screen. I guess this is the point were the game really starts in 3D. I DO hear voices/action, so the game IS running.

I also added the custom resolution 1440 x 1080 in the AMD control panel, but that did not help. So I removed it again.

Also I seem to loose the mouse cursor repeatedly in Crysis 3 (in the menu structure of the game)
But maybe that is caused by the wired Xbox 360 gamepad I have connected. Its not the main issue, but maybe its related.

I’m running a fully updated Windows 10 Pro with fairly recent AMD driver 17.11.1 (most stable one now for me)
I already emailed you the trouble shoot zipfile with all detail data.

Additional info that is missing in the troubleshoot zip files:
I use RIFT software 1.20. (Not using the Core 2.0 beta, too unstable)

Thanks for your help!

Best Regards,
Bluepill

[onetoo]

I’ve only tried that resolution so far in 17.3.0 with Crysis and GTA V. Crysis works. It’s not just th commandline.txt file. This also happens in steam without that file when I set launch options (named it wrong in the previous post). This seems to be specific to GTAV, but I’ll try IV since it uses the same method.