Search Results for 'Fallout'

[bjr84]

I have the same sort of issue. Fallout 3 GOTY and Fallout NV. Weird thing tho, every once in a while it works fine… (i.e. controller is default). I tried different sequences leading up to opening the game, but cant replicate. It simply works sometimes and does not others… it only started for me about 3 weeks back. Also when this started to happen, Half-life 2 stopped working properly.

[bjr84]

Hi,
Im having issues on startup with Fallout 3 GOTY, and Half-life 2. If I have SteamVR running or not, the game/computer decides to launch with keyboard/mouse primary over the controller for some reason. This, therefore, results in non-functionality of some controller buttons and/or non-functioning of the game… I cant replicate the issue as it seems sporadic (as in sometimes the controller is the primary…). I believe a late update just crushed it becauase it was working not a few weeks ago. I now have to alt+tab to select the game window for some reason and this may have something to do with it?

[mr_spongeworthy]

I’m running a Pimax 5k + and I have brainwarp turned off, and I have both Async and Fluid Sync turned off. As I delve into VR I’m finding that I really, really dislike all forms of injecting fake frames (that shouldn’t surprise me, I’m definitely hyper – sensitive to that type of thing, I can’t stand the Soap Opera Effect, for example, which on some modern TVs actually makes me feel slightly queasy).

I will say that the vorpX Fluid Sync (locking to 45 and then doubling to 90) is the best I’ve yet seen by far, but I still prefer the game running at “x” fps and my hmd running that same rate. (Also, your Z-Buffer 3D is really, shockingly good. I’ve used a LOT of 3D processes in the past, and I have to say I’m deeply impressed with the quality of vorpX).

But I digress: So I have all those functions turned all the way off, but both FO3 and FO4 will still frequently lock to 45fps. For testing purposes I’ve already tried completely disabling vsync and leaving the games totally uncapped (but I don’t run that way due to game-engine issues), or capping the FPS with Riva Statistics Tuner (this is what I generally use for games) or in the case of FO3 locking it with a FOSE utility called Fallout Stutter Remover. In all cases I’ll see the games lock to 45, and then eventually unlock again.

Any thoughts on how I might remedy this?

[rainykawa]

It worked prior to update 19.3.0. Now it launches like it used to and on the monitor says VORPX and the view moves around with the headset, but it wont launch into the HMD :(

[mr_spongeworthy]

Ok, thanks! I’m having significantly more issue with Fallout 3 than I have had in the past, despite modding it incredibly lightly this time and having the reliable GOG version. Good to know I don’t have to worry about vorpX changing my actual .ini files.

[Ralf]

Config app: you should be able to solve that by using by one of the High DPI compatibility options Windows provides. Right click the .exe > Properties > Compatibility.

vorpX does not change the bLoadFaceGenHeadEGTFiles option in Fallout 3. Some mod managers or similar tools may also change .ini files. So if you are using something like that, that’s a potential candidate. The .vpxbak file is not used unless you restore settings in the vorpX config app.

PipBoy: IIRC shaders in the game are used in multiple places, so enhancing/scaling the PipBoy breaks other things. EdgePeek is you best friend here. The save an extra mouse click you can bind the EdgePeek key to your PipBoy key.

[mr_spongeworthy]

Completely Vanilla Fallout 4 install – no mods, no tweaking of any kind, and I’m having the following problem:

When I enter VATS, the screen will shudder and hop between two different views of the scene. It kind of zooms in and out and sometimes I’ll see the highlighted target way off in the distance somewhere. Then the target will pop back into place. Back and forth. This in running Fallout 4 at 1080p in Lounge mode (haven’t tried other modes yet).

[mr_spongeworthy]

I promise, I am using the built-in forum search function to look for answers before posting questions here:

Is there a place where you clarify what game .ini settings vorpX will change automatically? For example, I’ve tried to add “bLoadFaceGenHeadEGTFiles=1” to my Fallout 3 .ini files and it keeps getting removed. I suspect vorpX might be seeing a line it does not understand and is removing it? Also, if I add lines to the “FalloutPrefs.ini.vorpxbak” file will that take care of this issue

[TheBalt]

mr_spongeworthy wrote:

I hope it helps. As far as I can remember all of the same basic fixes work for FNV and FO3 (although, you will have to download the proper versions of the Script Extender and Stutter Remover etc.)

ya, i figured this wouldnt be that hard to extrapolate over to new vegas. if it doesnt, all good – i still need to give fallout 3 a full vr playthru anyhow, played it back in the day but not all modded out and in vorpx yet, so i got a whole game just sitting there, just was gonna do new vegas first cause never finished it – so either way, ill be taking your advice for an eventual playthru lol..

if any wicked crazy mods like motion tracked controllers comes out in these games like doom 3 bfg edition got – please point them out lol

[mr_spongeworthy]

After really delving into vorpX for the first time with FO3 I’m very impressed overall. The lounge mode is a godsend for those of us who are playing games that don’t suit full VR well. Plus I can play games that way for hour without issue, whereas a full-VR game like Skyrim VR I’m only at about 15 or 20 minutes before nausea sets-in (I’m absolutely fine with seated racing-sims however).

One observation: Parts of the Configure vorpX app do not comply with scaled-screen settings. I run a 1080p display at 4K resolution and then scaled to 250%. I have specific reasons to do this and don’t want to have to switch back to regular 1080p. However, it makes parts of the Configure vorpX app unreadable as they appear not to scale at all (IIRC it is all of the “help” text sections which do not scale).

A Question: Is it possible for me to turn off specific notifications? When running the vorpX Desktop app I get a message flashing in the upper-left corner that I have to dismiss every time with a key-combination. And when I’m showing the FPS with the built-in vorpX utility it continually nags me that I’m not getting 90fps. I would really like to be able to turn those notifications off if possible, but without using the “Hide Less Important Notifications” function.

Last Question: If I turn on the “G3D Shader Authoring” function will I be able to tweak fundamental settings to try and fix things like the Fallout 3 Pip Boy and Terminal screen issues? Or are the provided profiles simply as good as they can possibly get? I’m used to having to fiddle with profiles with other products and might put in some time if there is a reason to do so, but I don’t want to just bang my head against a wall if the reality is that I’m not going to be able to correct issues like those.

Thanks!

[mr_spongeworthy]

I finally had time to sit down and really tackle getting Fallout 3 to work properly with vorpX. For those who don’t know, titles based on that engine (so at least FNV and Skyrim, plus probably others I don’t know about) had all kinds of fundamental game-engine-based frame-rate and stuttering issues, even on vastly overpowered rigs. So I thought I would put my finding here in case other vorpX users want to get it running well.

For reference, my rig is a Quad-core i7 overclocked (and liquid cooled) to 4.4 ghz, 16GB ram, all SSD storage, and an RTX 2080 Super card. So pretty capable, but definitely not top-end by VR standards. This is running a Pimax 5K+ HMD, so I have to run relatively high resolutions to really make use of the Pimax.

I’m only shooting for acceptable lounge-mode performance here with – not full VR. If you want to achieve true 90fps you might have problems anyway, as the FO3 engine will experience significant issues when pushed above 60fps. So everything here will probably apply to you but you’ll likely need to to use one of the various fake-frame methods (brainwarp, async, fluid sync etc.)

I’m not going to give step-by-step instructions here, because if you need a true step-by-step for any portion you can easily find it already written-up online many times over. I’m also not going to cover what FOV settings to use etc., because those are all going to depend on your HMD and personal preferences anyway.

Here are the key things you will need to do to make FO3 run smoothly:

1) Disable Vsync in your .ini files. Don’t rely on the launcher option to do this, it doesn’t actually work. You have to set the iPresentInterval value to 0 manually in the ini files.
2) Install FOSE: https://fose.silverlock.org
3) Install the Fallout 3 Stutter Remover: https://www.nexusmods.com/fallout3/mods/8886?tab=description
4) Edit the stutter remover .ini file (sr_Fallout_Stutter_Remover.ini file in the Data\FOSE\plugins folder) and set the maximum fps to 60 (you can use other settings if you wish, that one works very well for me. If you rarely get 60fps you might want to limit your fps to a value that works better for you. Even clear down at 30fps the game isn’t too bad in Lounge mode).
4b) If you are using Windows 10 also edit the stutter remover .ini file with these necessary Win10 fixes:

turn off the features in these 2 lines:
bHookCriticalSections = 1
bHookLightCriticalSections = 1
by changing the 1s to 0s:
bHookCriticalSections = 0
bHookLightCriticalSections = 0

5) Disable any driver level fake-frame features (brainwarp, motion smoothing, etc.)
5) Launch your game using the FOSE launcher app.
6) Disable all vorpX fake-frame features (this isn’t technically necessary, but to my eyes they just make things look uneven. If you absolutely have to get 90fps I suggest trying the Fluid Sync mode and limiting the fps to 45 in the stutter remover .ini file. That’ll give you a game engine running at a solid 45fps, doubled to 90. To my eyes that looked like the best of the fake frame methods in FO3).

Using those settings I’ve got absolutely silky-smooth framerates with zero stuttering at very high resolutions (2560×1440+) and quality maxed across the board for FO3 (plus many high-rez texture mods and ini tweaked to ugrids=7), even with all of my “VR Quality” settings set to 100%.

Note that there appears to be some sort of a bug in the Fluid Sync setting – after an area transition and at other times it will still lock my FPS to 45 for a period of time. You can either toggle Fluid Sync on and off again, or just wait a while, and in a short while (usually less than a minute) Fluid Sync will disable itself again and your FPS will shoot back up to whatever your maximum value is. (P.S. Would *love* to see this Fluid Sync issue fixed!)

Hope that helps a few people!

Things I haven’t been able to fix: Incorrect focal-depth for PipBoy display and terminal screens. (If anyone knows how to fix this PLEASE LET ME KNOW!) This causes a double-vision effect for those items. (P.S. Would also *love* to see this fixed!)

Here is a “solution” of sorts:

1) Bring up the vorpX in-game menu and set a dominant eye.
2) Close your non-dominant eye when using the PipBoy or Terminals.

[bjr84]

Hey,
Love Vorpx Thank you!
Im having trouble with Fallout 3 where VATS isn’t working (RB on Xbox One controller) but its “intermittent”. Let me explain “intermittent” – I noticed after trial and error that if I start the game and the controller is defaulted (i.e. no mouse pointer, just use controller at the start-up screen) then all works fine. But if the mouse pointer is there (i.e. mouse and keyboard default?) then VATS doesn’t work with RB (im thinking its being overridden by the keyboard/mouse setup).
(I have the controller option in Vorpx set to “Auto”).

I cant seem to replicate these two different scenarios – i.e. controller vs. keyboard/mouse ‘default’ (or so that’s what I’m calling it). I’ve tried to force the game to run in Big Picture mode (as the controller should be default that way) but I get an error – something isn’t playing nice – Big Picture or Vorpx. Anyhow.

I deleted the .INI file (and had it autogenerate at startup) and that seemed to work the first time I ran the game after deletion (i.e. VATS worked fine) but then when I edited the .INI file to fix that Windows 10 freeze issue, it ‘went back?’ to keyboard default. I will replicate again by deleting the ini file and this time not modifying the file to deal with the freeze issue, and will report back. But either way, I feel like this level of troubleshoot shouldn’t be necessary to correct the problem im experiencing. Gotta be something in the game/controller settings or Vorpx settings to default the Xbox One controller instead of Auto?

Ben

[Kurt91]

I’ve been trying to figure out how to get two games working, as the title of the thread says. Both of them are fully playable as-is, but I’d like to try and iron out the last little details. I also am kind of stuck having to ask rather than experiment for now because I’m a Computer Science major and I lent my headset to one of my instructors. (I’m taking a VR/Haptics class)

First off, when I play Portal 2, I have an issue where I’m facing the wrong way when going through a portal. I know that this is a known issue, but I was wondering if anybody has figured out a fix for it. One thing that I had read was to turn off DirectVR. What do I lose if I do that? Could I turn it on when I start the game, then turn it off and keep the FOV and turning my head to turn in-game? What benefits does keeping DirectVR have?

Second, I wanted to ask about Fallout: New Vegas. I can get the game working out-of-the-box, but as anybody will tell you, the game doesn’t shine without mods. In particular, graphics/lighting overhauls and ENB/Reshade/NVReloaded. Since it’s such an old game, fixing up the graphics seems like a pretty big priority when trying to get it working in VR.

I’m having difficulty using VorpX alongside an ENB. The ENB adds a D3D9.dll file, which apparently VorpX doesn’t seem to like very well, and it refuses to hook into the game. Is there a way around this so that I can use both? There’s an injector version of ENB that doesn’t include the dll file, but it requires being manually started before starting the game, and that would not only be a pain (since I’d constantly forget, and the game is a pain to get started), but I’m not sure how well it would work alongside using Mod Organizer 2 and NVSE Loader. (MO2 has to assemble the mod folders when starting the game, NVSE Loader is a different launcher for the game that is needed for a very large number of mods.)

Anyways, I’ve been trying to look up answers for both of these by myself, but to no avail. The last Portal 2 thread was quite a while ago, but I’ve been seeing videos over 5 years old of the game working in VR flawlessly. As for my New Vegas issue, everywhere I look just has people say to use the wrapper version of ENB (the one with the dll file) since it’s automatic, not taking programs like VorpX into account.

[buckjohnston]

These guys made fallout new vegas, looks like a great game. It’s called “the outer worlds”

anyone know what graphics engine it uses and any luck with vorpx?

[Adil3tr]

Bradwell Conspiracy, new control bindings for Fallout NV so I can play with just my index controllers