Search Results for 'Fallout'

[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

[Ralf]

The injector version *might* work, but there is no guarantee. May be worth to try it with both regular and alternative hooking. Possible that one works better with the ENB injector than the other.

Fallout NV is a good way to experience vorpX’s full potential BTW. The profile pretty much has everything vorpX can offer in the best case, even basic roomscale support. Make sure to start with an unmodded game and add mods one by one later. Some mods may break certain DirectVR features.

[jjensson]

I’m looking into modding Fallout New Vegas, and of course i can’t imagine playing that without ENB. Those atrocious graphics (especially the lighting) need fixing, IMO, to be enjoyable.

What’s the situation ATM regarding ENB? Does it work? Does it need some kind of proxying? If i remember correctly, ENB for older DX games came with 2 different methods of hacking into the game (injecting vs. wrapping).

I’d appreciate some help on this topic.

[hemingwaysghost]

Never mind, it’s working again. I opened up a remote session and clicked on it from the desktop and it started working. Mist have the same sort of issue I had in Fallout 3 where it would freeze on the load screen until I hit alt tab.

[STREET_BLAZER]

Following a number of recent Vorpx updates, FNV consistently fails to boot when ran along side VorpX. Even with AV disabled/ exceptions created (I use Avast), the problem still persists. I’ve managed to get it to boot w/ Vorpx a handful of times since troubleshooting yesterday, but this success seems random at best (1 out of 5 boots were successful on average). I am also presented with an error from Steam: “Application load error S:0000065432”. I never experienced this issue prior to the recent vorpx updates, and have NOT once reproduced it while running the game in 2D without Vorpx (in essence, fallout new vegas boots fine when not used in conjunction in Vorpx).

Not sure if I’m missing something here but I would appreciate any help in resolving this matter.

[mr_spongeworthy]

I’ve been a long-time stereoscopic gamer – about 10 years now with TriDef and other tools, so I’m VERY familiar with the performance issues associated with stereoscopic gaming. Despite this, I’m having some huge issues with vorpX that I just wasn’t expecting.

For example, using TriDef and my old AMD R9 390 I was able to run Fallout 4 with all settings except shadows set to Max in true 3D mode (not ZPD, what TriDef called “Power3D”) at 1080p and still maintain a minimum of 30fps. Shadow distance had to be limited to 4000, but other than that, I had to make zero quality concessions, even with extensive high-quality texture mods.

Under vorpX, and with a totally fresh install (no mods at this point), running in “Lounge mode” and with a brand-new RTX 2080 Super card (approx 2x the performance of the R9 390), with FO4 set to 1080p I’m struggling to get even 20 fps in many cases! Note that I’m not trying to play the game in full-VR mode with massive FOV and huge rendering-resolutions, I’m just trying to get the game to run at 1080p in the virtual lounge mode, not even with head-tracking or anything like that.

I’m not having any problems outside of vorpX – native VR titles run just fine (this is on a Pimax 5K Plus).

Any idea where I could be going wrong with this?

[mr_spongeworthy]

Ralf wrote:

It‘s not supposed to be that way. If you have the game installed on a harddrive, try a SSD if possible to minimize hitches caused by streaming in new geometry/textures. Also try without any mods if you have mods installed and last but not least try to delete your fallout3.ini, the game will create a new one on start.

Thanks, but it isn’t any of those basic issues. And yeah it sure isn’t supposed to be that way, but the old engine used in FO3 was really, really awful about these sort of things. There have been major problems right since the beginning, and there are some solutions, such as FOSE plugins etc to try and correct it, but there can be hours and hour and hours of testing, and tweaking, and testing again, before you get it right, and “right” can be different for every configuration, video-card, etc. Throwing all the power in the world at it doesn’t make a difference, because they are fundamental game-engine issues. I was just hoping that maybe I wouldn’t have to go through all the trial-and-error and work of getting it to run correctly again; if maybe there was a new, easy, solution I didn’t know about. Maybe I should just wait for the Capitol Wasteland project to finish (or for Bethesda to finally release an “SE” version running on the FO4 engine, which has far fewer of these sort of issues).

[Ralf]

It‘s not supposed to be that way. If you have the game installed on a harddrive, try a SSD if possible to minimize hitches caused by streaming in new geometry/textures. Also try without any mods if you have mods installed and last but not least try to delete your fallout3.ini, the game will create a new one on start.

[mr_spongeworthy]

OK, it was time for a long-overdue full clean install of Win10 anyway, so I did that and things work working better now. Don’t know what the problem was.

Fallout 3 is working and looks good, but has all the original problems that Fallout 3 had (I’m maintaining nearly 90fps even with vorpX activated, but it looks more like 15 or 20 fps while playing Fallout 3, which has all kinds of weird frame-rate issues, stuttering, etc.)

Rather than start a new thread, does anyone have a good fix for Fallout 3’s bizarre apparent frame-rate issues?

[hemingwaysghost]

To add a little detail… it looks almost as if half the screen is missing or maybe that it’s only projecting to one eye. The movement is off too. When I press forward on the touch joystick it moves diagonally. I’ve tried reinstalling VorpX and bioshock. Fallout 3 is fine and New Vegas is now working.

[Ralf]

Technically that would work, but for a decent framerate you would have to use vorpX’s fast Z3D stereo method. For the better “true” Geometry 3D method your rig would be too slow in many games unfortunately, definitely in case of Skyrim SE, but probably also in case of Fallout NV.

I’m also not entirely sure whether the DK2 still works with the latest Oculus Home software, so please check that first. vorpX does not work anymore with the old 0.8 beta Oculus runtime.