Search Results for 'Just Cause 3'

[Del_Pierro]

I just installed Vorpx after a longer period of time to try my RTX 3080 and Reverb G2 Headset. I started RE7 and I got pink spikes in the SteamVR performance graph all over the place, maybe 10 frames per second at most. SteamVR games work fine with other games, 100% resolution 90 frames. GPU load is not even high but pink spikes everywhere with lost frames so unplayable.

Any idea what the cause might be? Thanks. Changing the ingame resolution didn’t help.

[stonivr]

I need a g3d Just cause 2 profile.

@AlexLogin0ff there is already a real Bad company 2 g3d user profile that you can found. works 100 %

[Eola667]

The only three things I’ve seen change how the image looks with the same settings are either physical headset adjustments (being closer/further from the actual headset screen via mechanical means which can change perception along with FOV), resolution which changes VorpX screen aspect ratio though you’ve already pointed it out (not sure if Nvidia scaling for example can affect the VorpX screen dimensions, but I’ve got it switched off just in case). And then finally your own eyes when it comes to things like 3D strength, how comfortable people are with different 3D strengths can vary from person to person from what I could gather, sometimes for me the correct 3D strength even varies between playthroughs, although very, very slightly. Edit: keep in mind though, the variance in perceived correct 3D strength per playthrough/person isn’t caused by VorpX, but by how the eyes/brain percieve all this in the first place.

[ViktorF]

nVidia GTX 1080, AMD 3800X CPU, X570 mainboard, HP Reverb G2 headset, WMR and Steam VR are set up and working properly.

With the default VorpX setup Space Engineers in not hooked, so does not show up in VR at all. I tried to change the options on the General settings, they did not help.

With the watcher disabled, the desktop viewer shows the game on the theater’s screen, but has horrible stuttering right when a game is loaded, but no such problems in the 2D menu. Lowering the game’s resolution and the HMD rendering resolution did not help. It seems to mix up frames back and forth, showing the wrong one for hundreds of milliseconds.

Yes, I’m aware of the Steam VR problems caused by the most recent nVidia drivers in the past few months. I reverted to the 446.14 (May 27, 2020) driver as suggested by Steam VR. It helped the desktop viewer to not crash after a few seconds of stuttering, but the main problem still persists.

I tried the Tron 2.0 game (bought it for just this test), that is hooked properly and works perfectly.

I tried a different game (Worlds Adrift Island Creator) in desktop viewer mode, there was no stuttering there, showing it in 3D on the cinema screen. Although the viewer lost the game when it loaded a world, so it is still unusable.

[Smoils]

You cant get a game working with vorpx in any 3d if its engine doesnt have any similarities to any profiles vorpx has. For example bannerlord can be 3d because of it. For everything else its just a matter of trying. Often a profile that has G3D will have Z3D not working, you cant do anything about it but sink more time trying things out, it might not work at all with any profile.

Ralf – the author of the program is practically only one that can code any unsupported special case game to have 3d.

[senoctar]

Same here. I don’t know if this is something to be expected. There are several could profiles with downloads so there should be plenty that tried this game. It’s odd no one else complained about the frame rate.
I spent a couple of hours with various settings but they don’t seem to make much difference.
In the end I just used Z3D instead of G3D. But even for that, because program association buttons are disabled on official profiles you have to jump through some hoops to get it working, mainly discussed here: https://www.vorpx.com/forums/topic/devil-may-cry-5/

[forlaunchcast]

Very interesting and enlightening discussion. Thanks, Ralf, for that insight.

For what it’s worth, I played through entire Doom 2016 with just desktop vorpx and had a blast. Yes, it wasn’t 3D, but having a dark movie screen in front of you with headphone spatial sound still was a treat. And because it wasn’t geometry, it was smooth as butter.

[Smoils]

Even without visual glitches and tech reasons sometimes you just convince yourself game has depth if you believe enough I even noticed myself sometimes accidentally pressing hotkeys switching z3d off and only noticing after some time.

There are several latest amnesia profiles claiming 3d too while there is none because people are convinced it has depth.

Even z3d when it works is obvious, you dont have to put any effort to see if there is depth, there just is.

[RJK_]

Omerta: City of Gangsters (G3D)

I decided to disable shadows on default because they just hurt my eyes. A bit of an unusual profile but a working one.

– Optimized for cinema modes
– Full VR not recommended
– Looking very well on high resolutions
– Profile available at the cloud

Game is currently 83% OFF Here

[panterarosa2]

Ralf wrote:

Sounds as if something is really off on your system, SteamVR having wrong colors also doesn’t really sound right. you can be sure that if issues like that would be some general problem, you’d see quite a few more posts like yours here. If ‘wrong colors’ means the image is too dark/bright, you can change that in the vorpX menu on the image page.

If you happen to have a HDR capable monitor, please make sure that HDR is off in the Windows display settings. No current VR headset is HDR capable, so using Windows in HDR mode may lead to wrong colors.

The error you see in Oculus mode is returned by the Oculus runtime when vorpX tries to initialize the headset. Apparently the runtime checks the digital signature of the main runtime component, which for some reason fails on your machine. That’s not something vorpX does, it happens entirely within the Oculus runtime, vorpX just shows the error it gets back from the Oculus runtime. So all I can really suggest here is reinstalling the Oculus software since the error message suggests that the Oculus runtime is broken.

Apart from that please also do a full vorpX factory reset in the vorpX config app (trouble shooting page).

Last, but not least: If you happen to run vorpX, Steam, or any of the games you tried in some sort of compatibility mode (e.g. Windows XP), make sure to revert that.

Thank you for your reply

Few test more
Rocket league – default – working
RE 3 – DX 11 – default – working (3d geometric)
RE 3 – DX 12 – default – working (3d geometric)
Control – default – oculus runtime error (i do not even know if it is compatible)

– Is possible that Oculus quest 2 controllers interfere with vorpX? (From myself I have activated link using hand tracking, and then launch everything using mouse)

– I have closed DS4 controller till game is launched. Just in case.

– The game was launched in the past with too much quality so headset has problem loading game? i have decreased quality from pc version before launch as VR.

– The game had enabled HDR and might have some problem launching game? I have set all to normal.

– I have alternated between DX11 – DX12 and test.

I already did a full vorpX factory reset before I opened this threat and tested everything.

After all these test, I do not think anything is off from my side. I have reinstalled oculus just in case, and did as above, and now:

RE 7 – working using default on Steam mode (colors were changed because of HDR I think)
RE 2 – it just works if I disable “try to block known game overlays” on steam mode. This time the vorpX menu is working and 3D geometric is enabled. (something that I did above fixed it)

So far I was able to sort out the issues, HOWEVER, this is not nice. I had to try a lot of configurations and modes, AND as I said above, if I use others configurations game will not work even all I did. So something is not working on the app.
If you say still is my computer, I think you should know where the issue is. I do not think I am the only person who gets error from oculus quest 2, is just, probably we are not playing same games on vorpX using oculus quest 2 as it seems it depends about the game.

Oculus runtime error still there after all these checks.

[Tazling]

Greetings to more experienced Vorpxers. I recently tried it out for the first time, hoping to use my Quest 2 to play Portal 2 (best game ever!) in true 3D. It was not a happy first test drive.

(Note: I’ve been successful in getting Virtual Desktop working and playing SteamVR games wirelessly, so I’m not a total Quest 2 n00b, just a Vorpx n00b. Win10, Steam, AMD 5700XT, i8700K, loads of RAM, Quest 2, official Link cable)

I used my Link cable to try Vorpx because I had read that it did not play well with VD. Vorpx installed and launched successfully and the Configure app seemed to work OK. I chose appropriate profiles from the games menu. Everything seemed to be going according to the readme.

But, whether I tried Portal or Portal 2, I had similar deal-breaker issues: really poor rez, my avatar seemed to be 8 feet tall, major crawl and jaggies (like no AA at all), and huge distortion in peripheral vision, like every time I turned my head the world was stretching and bending in a very disturbing way.

I got VRsick very fast, less than 10 minutes, just looking around and walking (never got to any portal-jumping!) and had to quit — and this is a new problem for me, I never get VRsick. After playing, my eyeballs hurt (also a new experience).

Instead of a seamless VR experience I seemed to be looking at a spherical projection screen (a rectangle wrapped around a sphere) floating in a big gray limbo. Maybe this is how it’s supposed to look? I could zoom in to this projection and then it (sorta) seemed like 3d, but with the awful distortion everywhere outside the central focus area. Also head turning seemed to be overmapped bigtime, like small head movements resulted in disproportionate camera rotation (also making me dizzy).

Anyway my Vorpx first test flight was a bummer. I’m hoping I just have missed some obvious configuration options (dumb n00b error) and it actually works much better than that, ‘cos I can’t understand how it got good reviews based on my fairly horrible experience. If anyone else has succeeded with Portal 2 in particular, I’d sure like to know what you did right.

[theself]

I just got vorpx- I have an htc vive and battlefield V but I can’t get BFV to run in vorpx at all- doesn’t show up on the Hmd (even though I get the notification on my desktop ‘attaching to bfv.exe’ and BFV is supposed to work stock)- any ideas what I need to do to get it to run? Since BFV is an origin title and not on steam do I have to make it run through steam as a non steam game to make it run in vorpx since I am using steam vr and not oculus or not necessary for non steam games? Is there something in the graphics settings I need to change before hand to make it work? Like stop directx 12 and make it direct x 11? (I managed to get Battlefield 1 and Just Cause 3 to work so far) -Thank you for any feedback

[Jesús D.]

I have tried hooking Vorpx to Resident Evil 7, but so far I have not succeeded and I have been trying for two days, it just shows me the game launching black screen then the “ataching re7.exe” icon appears and it closes the game almost instantly.

Ive killed all the non-fundamental processes in the background, I have disabled the intel graphics chipset in the BIOS options because for some reason I had it always on, I have run the game in windowed mode and enabled / disabled the boxes of the general Vorpx settings, I have deleted the file “re7_config.ini” to make the hook again, I have restarted the pc and some other alternatives that unfortunately I don’t remember right now, the strange thing is that it has worked for me in Resident Evil 3 Remake / Direct X 11 including the first person mod and with Alan Wake / Direct X 9 and have worked without problems. Any help would be appreciated please, it makes me very sad that I can’t play these games.

[Sairai]

Ralf wrote:

I have tested both the Steam and the GoG version for several hours now and am confident to say that there are no crash conditions in conjunction with using vorpX. The only vorpX related crash condition was a conflict on AMD Radeon cards in some nVidia code the game uses, which apparently does something else on AMD GPUs than it does on nVidia GPUs. That has been fixed with yesterday’s update.

The best advice I can give you is resetting the profile to default in the vorpX config app, using the latest GPU drivers, not cranking everything up to max in the game’s graphics options and checking for potential conflicts with interfering background apps on your PC that also hook into games.

Just in case: if you happen to overclock anything in your PC, try with default clock rates.

Hi guys,

I definitely have a VorpX related crash condition since the update to 21.1.1.
My Cyberpunk profile includes the following:
– Cinema Mode, curved with ambient background, no AA
– Custom resolution ingame wqhd 2516 x 1440, ingame settings all maxed out
– No 3D, Crystal clear: normal
– Removed hud scaling from default profile: Set scaling to 1:1
– VorpX may not change any game settings (didn’t work any better with this option enabled and I prefer having full control on my own)

My hardware scenario:
– 3 monitors with 1920 x 1200 resolution (thus needed to use custom resolution for wqhd support)
– Valve Index HMD
– RTX 3090 (support for maximum raytracing and dlss on)
– i7 5820k 6x 3,8Ghz HT 12 Threads
– GPU no OC
– CPU stable OC ~8% (for years already)

Now when I launch Cyberpunk it seems like I have a 30% chance that the game does not crash after displaying the CD Project Red Logo. I wasn’t able to find the root cause so far. Tried different vorpX settings, different hooking and stuff but to be honest, I just want to play and don’t want to waste my time with troubleshooting atm.

If it does not crash right before start screen, everything runs perfectly fine and I can play for hours without any issues.
The game never crashes when I reset the profile to default. I am able to setup all my preferences in this session and can also play without any issues but of course this is very annoying in front of every gaming session because after closing and restarting the game, the same issue reappears.

It most likely has something to do with my custom resolution or the VorpX PoV changes. The whole part with ingame resolution (VorpX resolution settings) was changed with this update and maybe there is some sort of bug with custom resolutions? All I know is that this issue immediately appeared right after updating to 21.1.1 and never appeared before.

The game also never crashes during startup when I am running it without VorpX.
Hope this information can help you identifying the issue.

Kind regards,
Sairai

[incongruent]

Hey so I heard about vorpx for a while.

Since I’m putting in so many hours of death stranding, I figured I’d pick it up and see if I enjoy it.

I don’t know if I loaded it correctly… I right clicked on the vorpx toolbar and clicked Create Desktop Shortcut then selcted the ds.exe file. It loaded in VorpX. I know this because I had to change the setting to SteamVR before it would work.

It loaded okay, but it just kind of looks like a 3D television floating in the void. The 3D isn’t totally pronounced, but it’s definitely not flat. Is that the effect I’m supposed to be seeing?

One more thing, because the head tracking is enabling the mouse, it seems to be conflicting with my Steam Controller mouse input when I use the trackpad. So if I figure out how to disable the head such that it doesn’t move the cursor then the problem goes away?