Search Results for 'fallout 4'

[Fredthehound]

Hi all,

I, and at least a couple others I know of, are curious about 1080s (and the new Titan once it ships). Is anyone here actually using a 1080 or 1080 SLI setup with Skyrim or Fallout 4 yet?

What are your Geometry mode framerates like? Stuttering? Issues? Supersampling? Granted, it’s a pretty specialized/expensive rig so I’m not expecting a ton of replies but I figured I’d ask. Reason being, I was originally going to jump on the 1080SLI wagon but their scarcity gave me time to think and consider waiting on a TI. Of course with the Titan about to release a TI may not be offered at all.

I have the Notify me thing set with Nvidia and will (barring something financially disastrous in the meantime) be committing a wanton act of wallet sodomy, but I’d love to hear about anyones 1080 experiences regardless.

And yes, you all will get a full report on the Titan’s VR performance in Sky and F4 if/hopefully when I get it.

[Ralf]

You can remap gamepad buttons on the gamepad page of the vorpX ingame menu.

Alternatively you can enable the *experimental* Direct Head Tracking on the head tracking page of the ingame menu, which currently is avalilable for Skyrim and Fallout 4. This enables native gamepad support. Be aware though that this is truly experimental. It might or might not work on your PC.

[Ralf]

What answer do you expect on the official vorpX support forum? You don’t loose the HUD in any game, but in games where vorpX can’t scale the HUD, you will need to use vorpX’s EdgePeek function to look at parts of the HUD in screen corners. EdgePeek let’s you briefly zoom out and back by clicking the mousewheel.

The games you are interested in run as follows feature wise (G3D means “true” 3D with two cameras, Z3D means Z-Buffer 3D, which doesn’ look as good, but is a lot faster).

1. Fallout 4: G3D/Z3D, positional tracking, FOV adjustable ingame, scalable HUD, as close it gets to a native game with injected VR.
2. Alien Isolation: G3D/Z3D, positional tracking, FOV adjustable via ini tweak
3. GTA V: Z3D, FOV adjustable via external tool (Flawless Widescreen)
4. Doom: not supported, but runs in unsupported mode (2D only), FOV adjustable ingame.

And BTW: don’t believe everything you see on YouTube. I am aware of at least one recent vorpX video there where the main complaint of the “reviewer” that he talks about most of the time (no 3d) is plain and simple not true. Kind of unbelievable the whole thing. Modern times, I guess…

[LotusBorn]

I was all excited when i learned about this program but after watching a couple videos that bash it im kinda on the fence about purchasing it. Mainly interested on playing GTA V, Alien, Doom 2016, and Fallout 4. Do these games run good? Do I lose the HUD? Is it worth it?

[paul.desilva]

I just installed Vorpx and when I try to run the config, it immediately crashes. I have uninstalled Vorpx completely and re-installed multiple times, restarted my machine, tried running it as admin or in compatibility modes.

Vorpx itself runs but when I try to start (in this case) Fallout 4, it says it cannot find the Oculus Rift. Unfortunately I’m on the HTC Vive. I opened the Vorpx file that’s in AppData and attempted to change “sDeviceName” which was set for the Rift by default but I don’t know if “HTCVive” is the proper name.

[General]
sOculusProfile=
sDeviceName=HTCVive

This allowed the game to open and I can bring up the in-game Vorpx settings, though nothing comes through the HMD, only onscreen.

Suggestions?

[Fredthehound]

I’m on a Sabertooth Z87 (I typoed it as 97 upthread but same basic thing really) with a 4790K overclocked to 4.7ghz and that may have an impact on frame rates compared to a non OC’d cpu, so bear that in mind. The OC may better utilize the faster ram.

I got a 5 fps boost on the worst of the worst minimums… Dragonreach staircase, where draw calls are pounding the hell out of the CPU. I can’t say for sure what my high FPS is with the 45 cap of VorpX but I can say the whole FPS range shifted up noticibly…meaning smoother overall and many places are now at 45 that were low 40s before at best.

Fallout 4 on a regular monitor took one hell of a leap forward as well (then again it is known to love fast ram.

I’ve read that anything above 2400/2666 on the Z series is rapidly diminishing returns because of the architecture so a Skylake 6700K OCd to 4.6 or 7/DDR4 rig would be the bext logical step beyond that to actually use DDR4 speed. But thats about $1K vs the $90 for the 2400 ;)

[Pudsley]

You might be right in some respects…I seem to have some other issue at the moment it seems.

I seem to be getting black screens even in games that previously worked (Fallout 4 for instance)

[Sandermander]

I noticed something else also. I cannot seem to create profiles under “Local Profiles”. When i click “Create now profile based on this one”, the dialogue pops up to name the new profile, but after that, the profile never pops up in the list. Also, the “Add” and “Remove” buttons for the .exe files in the existing profiles are greyed out.
If i “Reset profile to factory defaults” on any local profile, i get an error, saying if it keeps happening, i should reinstall Vorpx.
Having done that 4 times now, i dont think it helps.
Also, even when i run Vorpx Desktop Viewer, i get the “This game is not supported” dialogue box. I think something is wrong with the profiles and Vorpx is not detecting the .exe files. The “This game is not supported” box shows up in everything i run.
I have looked in my documents and settings folder and there is a Vorpx folder with all the settings and profile info, so i have no idea what is going on.

Note: If i look in my Vorpx.ini file, the:

sOculusProfile=

is empty. I dont know if this could be the problem.

I looked in the vorpx.log after running Borderlands Presequel and Fallout 4 and both says settings not available.

INF: App: Attaching to borderlandspresequel.exe (32bit)
INF: ProgSettings: System settings not available
INF: ProgSettings: User settings not available
INF: VorpControl Injector InjectVorpDll1: C:\Users\ALEXAN~1\AppData\Local\Temp\vorpX\78380cec-0.tmp injected (mode 1), reason: 1
———————————————–

INF: App: Attaching to fallout4.exe (64bit)
INF: ProgSettings: System settings not available
INF: ProgSettings: User settings not available
INF: VorpControl Injector InjectVorpDll1: C:\Users\ALEXAN~1\AppData\Local\Temp\vorpX\3547f567-0.tmp injected (mode 1), reason: 2
———————————————–

Here is my full log for you, Ralf: https://www.dropbox.com/s/fvyd5cd7djl9l36/vorpx.log?dl=0

Halp.

[ArticTiger]

kkkiwi wrote:

Would you care to share how you accomplish this?

Bit of a pain to set up, I use 3 monitors next to my vive to do it. My display mirror is showing on my 1440p monitor and I do a region capture on my OBS to stream it to my Twitch, and save it to disk as well.

Only problem is, in VR you can’t check if the recording is going well! I didn’t notice no sound on the fallout vid because of this :)

I’m gonna be checking out many VR games that weren’t intended for VR on my channel so this gives the best compatibility.

[borus]

That’s actually what I’ve been saying from the beginning of the thread — that my expectations might have been too high.

I’m loving the way the high-end VR stuff looks on the Rift — eg The Lab, Bullet Train — and by comparison Skyrim appears to be low-res with a “dirty” or messy quality. My immediate hunch was that this is just a function of taking a game intended for monitor play and blowing it up to VR… but people seemed SO pumped at their Skyrim VR experience that I just wondered if maybe I was missing something.

That said, I’m definitely curious to see what Bethesda does with Fallout 4 VR next year. Going native VR is bound to be pretty rad.

[ArticTiger]

So fallout 4 looks fine for me (It’s a bethesda game so similar enough)- don’t mind the start of the video I was having unrelated issues as well as the sound not recording: https://www.youtube.com/watch?v=CrQ2InamTJI

My settings for this game are 1280×1440 in a borderless window screen. I recommend playing around with the FOV, mine is actually set to 135. Also make sure to turn off all blur types.

If everything else fails, try some mods?

[Senatic]

So i spent probably about 20-30 hours trying to make vorpx the experience I want. I’ve tried 3 different games (life is strange, portal and fallout 4) and I can’t say any of them worked well. I have a HTC vive for the record.

The main issue, and the one that kills the First person experience and any sense of immersion, is the fish eye effect that I can’t for the life of me figure out how to get rid of. And it is really bad in fallout 4, the funny thing is it doesn’t happen when i move the camera with my mouse, only with my head. I’ve tried various resolutions suggested in threads here on the forum, I’ve tried multiple FOV settings, I’ve tried with and without geometry mode (without lessens it but doesn’t remove it completely), I’ve tinkered with pretty much all the settings the app has to offer (I knew it was a complicated app to get into before I bought it and that it’d require a lot of tinkering to get things working well) but I can’t seem to solve this issue.

Is this solvable, if so any concrete tips would be appreciated.

Also, have anyone found any games where you have at least some decent sense of presence, because even when I got things working fairly well I never actually felt like I was THERE the way you do in native vive games. Of course I knew this was likely the case before buying it but im curious if anyone has gotten any game to work THAT well with vorpx that you actually felt you were in the world.

[NipOc]

I found a fix for the buggy shadow, that appears around near objects in Geometry 3D
(looks like black Z-3D artifacts).

You have to turn

bComputeShaderDeferredTiledLighting=1
to
bComputeShaderDeferredTiledLighting=0

and the shadow is fixed.

[Ralf]

Switching off head tracking in EdgePeek mode introduces an issue where you regularly end up looking in a different direction in reality than in the game after leaving EdgePeek mode if you look around while it’s enabled. Especially in regard to the up/down axis this is very disorienting. An idea how to potentially avoid that is on the experiments list for a long time, so this *might* get adresses eventually, but no promises. Apart from that: in the future there will be more games that have Direct Head Tracking like Fallout 4. In these cases this will be avoidable.

There are two different frame rates because two different rendering processes are happening in parallel: the game itself and a second render thread that pushes the image to the headset.

Ideally both should show 90fps, but that will seldomly be possible with more demanding games. Primarily you should make sure that the game frame rate stays above 50fps for smooth gameplay. If that is the case, the direct mode frame rate usually also is OK automatically.

In Skyrim you will need to switch to Z-Buffer 3D and/or lower the game’s graphics settings for a significantly better frame rate. If you are prone to motion sickness, *always* prefer a high frame rate over image quality. Always!

[ld57]

Hi,

I create this post to give my 5 cents regarding my own experience with Vorpx and Comodo.

The main issue was related to all games execution 64 bits processes, and Vorpx would not hook these games. (Fallout 4, GTA V, …)

in fact, In Comodo, there are several modules :
– antivirus, defense+, firewall, file evaluation.

Regarding Vorpx, you run Vorpcontrol.exe (named Start Vorpx shortcut on your desktop), but it also launch Vorpcontrol64.dat (you see it in task manager).
These 2 executables target 32bits and 64bits games.

But one module in Comodo prevents vorpcontrol64.dat to be launched, this prevents the ability to Vorpx to detect you launched a 64 bits game (F4, GTAV,…)
If it is the case, you would not see vorpcontrol64.dat in task manager, and you will see application crash regarding vorpcontrol64.dat 0x000005 in your eventlog application (run eventvwr in windows).

This module is located in Defense+ in Comodo. In defense+ menu, you will see HIPS parameters, and in this configuration page, you can deactivate/activate HIPS, but you need to know that all others options below are not related to HIPS (that s why disabling HIPS keep crashing our Vorpcontrol64.dat).

And it is here : the last option is named “Detect shellcode injections”. and you can add exceptions.
you have to act here : add all Vorpx executables to this exclusion list.

Enjoy now the ability to keep your prefered security software and your prefered 3d wrapper :)

ld

PS : for more details regarding all options for comodo, here the link of manual comodo support