Search Results for 'Black The Fall'

[wm79]

I do not know what happened – but nothing works any more without being able to tell you if and what I changed. Genuine Oculus supported games still work fine (Assetto Corsa, Projects Cars etc). As soon as I start VorpX Control and try to start Vorpx Control supported games it does not work any more:
Fallout 4: Image on just one eye.
Battlefield 4: Image on just one eye – picture is headfirst. Engaging virtual cinema brings normal image.
CS: Global Offensive: Black screen. Alt-Tabbing out and then into the game shortly shows sandwatch in oculus lower right.
CS: HL2 Engine: See CS: Global Offensive.

Any suggestions on how to fix these problems?

[agamer]

Trying to get two steam games that are on the supported list to work and they are failing to start. I have both vive and oculus rift cv1 head sets to test with and both give the similar results. The games in question start ok without vorpx running. Read through the troubleshooting options in vorpx and the post on the forums, disabling antivirus, aero and other windows services, no other overlay apps running, no steam overlay, tried changing many settings in game outside of vorpx to see if that helps, swapping out of cinema mode and cycling between the 3d modes – geometry/z/z adapt doesn’t help. Recently upgrade from a GTX780 to 1080 but same results on both video cards.

Risen – this starts ok in cinema mode but shows all black screen. Never renders game. Switching out of cinema mode and cycling between the 3d modes – geometry/z/z adapt doesn’t help, display stays black.

Dark Messiah of Might & Magic – this crashes to desktop on start consistently after showing the main game menu scene with the character rendered, seems to want to work but then just crashes.

System info:
Windows 7
ASUS nVidia GTX1080 Founders Edition
Intel i5 2500k
24GB RAM
Windows defender / Microsoft security essentials

Games that I have tested to work for me currently:
Fallout4
Skyrim
Oblivion
Dirt 3
Torchlight 2
Bastion

[Fredthehound]

You sure you arent Yoda? Because you just got me to lift the proverbial X wing out of the swamp…or at least the wool from my eyes ;)

With the multicore/affinity thing unfortunately ruled out, I dove back into the numbers and thanks to finally getting Skyrim Performance monitor working CORRECTLY with VorpX and showing me good data, I made one hell of an interesting discovery.

In the picture linked below…
http://s931.photobucket.com/user/NormLenhart/media/Ram%20limit.jpg.html
…the framerates arent registering but this run was in the upper teens to lower 20s in Skyrim in Markarth. That is with EVERYTHING turned up full. Maximum possible load with the intent of making the system work as hard as possible. The 4790K @ 4.7 Ghz is the red line in the lower chart. CPU bind is not the problem. The Titan is the black line that never hits 60% usage. Clearly it isn’t the problem.

But look at the green line on top. Thats Bill gates freaking 4 gig DX9 cap in windows 10 ruining the party. ENBoost is reserving the other 500ish meg thats not being shown. It’s a memory problem. Memory appears to be the only thing stopping VorpX/Geometry from running this config far above 45FPS and likely well above 90.

All the dips are when looking at high detail areas. Things that I had believed to be a draw call problem. But look at the CPU. It’s not remotely stressed.

When I looked at this before, it was with the really big texture packs installed and hit that cap, which I expected with the Antialiasing/weather/lighting mods. But my current load is on stock size textures. When I switch back to monitor, Skyrim is barely over 2 gig of memory use. Between the ram requirements of Skyrim and VorpX though, it’s hitting Billy’s asinine limit.

So it looks like from what I can tell, Geometry mode/draw calls arent the main issue. An 8Ghz CPU and 4 titans would be meaningless. It’s purely a memory wall.

Skyrim Remastered cannot get here fast enough. Well, if nothing else, this has been a learning experience for me.

I’m redownloading Fallout 4 now for a stock reinstall. Since it seems there’s nothing more I can do for Skyrim till the remaster releases, I might as well start digging into Fallout to see what I’ll be in for when it releases.

[TenaciousJ]

These aren’t all FPS games, but are excellent picks:

The Vanishing of Ethan Carter is AWESOME in VR if you’re into mystery adventures
Elite Dangerous if you like space exploration games
The Elder Scrolls Series – primarily Skyrim.
Fallout 4
The Batman Arkham Series
Metro 2033
Call of Duty Black Ops 1-3, Battlefield 3-4 and even Hardline, Any Splinter Cell or Crysis game
Alien Isolation
Quake I-III
Half Life 2
Portal
The Witcher 1 and 2 if you like extended campaign games that will suck all your time, not sure if Witcher III is manageable at acceptable graphics levels
Bioshock: Infinite
Borderlands
GTA IV and V
and to tickle your fear of heights check out Mirror’s Edge

Essentially if your computer can run it, and it’s built on a major game engine like Unreal, Unity, and quite a few others – it’ll play in VorpX. The less popular it is the more tweaking you’ll have to do though because it won’t have been done already by someone else. Once you get used to the Vorpx in game menu you’ll be able to get games to run. Whether you get a true stereoscopic experience depends on how the game was coded though.

I’m sure that’s clear as mud now.. lol. But hopefully there are a couple of games on there you can check out that are well established as compatible.

VorpX Supported Games

[maximus2k16]

I managed to finally get Vorpx working with ReShade. I tested it with Fallout 4, but in Geometry mode whilst having ReShade injected the right eye goes black, this could look incredible with ReShade, but another bump in the road, any idea why it would make the right eye view go blank?

Regards

[Fredthehound]

Actually before getting to the INI stuff/while I’m in rant mode and thinking about this, I feel that man has ruled the world as a stumbling dem… Oh wait. Wrong rant…
Skyrim modding for VR… Oh yea!

I’m far from the first to say it but the truth is that modding Skyrim is all about compromises. That is doubly true for VR. I aluded to it earlier but the engine of skyrim simply cannot be forced to do a lot of things we’d like it to do. And perhaps the new Remaster on DX 11 will open a lot of them up, but it will still take raw power. It’s just that the raw power will be actually usable.

My Crossfired 390s left a lot of power on the table. together, they have the same TFLOPs as a 1080, but a 108 will leave them in the dust in any game or benchmark, so what gives?

Coding. In the case of Skyrim, thats the old engine code never being designed for the things we have managed to come up with since. Things like a Titan X or scripted weather mods or even efficient use of multi-core/Hyperthreaded processors.

Last summer I had a relative, an old code monkey from back in the punch card days out here in AZ from back east on vacation. I was showing him the crap we go through to make Skyrim do what it does and he was just dumbstruck that pwople have extended this software this far and that it works at all, much less works well when done right.

It’s kind of like VorpX itself in a way. We have something that can turn regular games into 100% playable VR games. Thats black magic stuff when you really think about it. Games like Skyrim or Fallout or Doom or any other game on the compatability list sere NEVER designed for what Ralf made them do. SO hats off to you sir ;)

As for Skyrim and the Creation engine, think of the INI tweaks in general like taking your car to a skilled mechanic. He can adjust a few things and suddenly your car drives, runs etc. a lot better than when you dropped it off. He didn’t bolt on a Turbo kit and a bottle of Nitrous Oxide. He simply tightened a few things, changed the plugs and rotated the tires, but the whole car just works and feels better.

Maybe, if you’re really lucky, he’ll find something that the factory botched pretty badly and with some duct tape and bailing wire, he can work a small wonder. And in our case, the Bethesda ‘factory’ badly botched the multi threading/multicore utilization and thanks to updated code and INI tweaks, we can improve on whats there significantly. It’s not a panacea, but it will help performance/framerates/loading/smoothness CONSIDERABLY. Which will soon matter a LOT.

A friend of mine I grew up with had a father who was an old racer from back in the 50s-70s that used to preach on the details when building his vehicles. None of them ever had the biggest engine etc., but the guy had a ton of trophies all over his house. His vehicles weren’t the prettiest things. But they won. Often.

It comes down to that whole building a house on sand idea. Do it and you’re gonna have a bad day. But build your foundation right/well, and you aren’t going to have those issues. And thats something to keep in mind as we move ahead in this insanity because its those little things that are going to enable us to make this game do things Todd Howard never intended. Thats not new. Skyrim modders have done it for years.

What they have NOT done is many of these things in VR, which as we know, is a more demanding environment. So lets see what happens when we try.

[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)

[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.

[digitalid]

I’m using an HTC Vive and I was able to get Fallout 4 to run and tried the original Doom game, which isn’t listed as a supported game but still worked. But I cannot get Black Mesa to work. I tried to search the web and these forums but couldn’t get any information. The game runs normally when I launch it so I assume that vorpX isn’t injecting any files in the game. Does it simply not work at all and I should stop wasting my time trying, or is there a solution? Any help is greatly appreciated!

[gnet2000]

I cannot play Amnesia Dark Descent at all. Both eyes get flashing flickering of the game and the frame rates is so low it would be less than 1 frame per second. Im running win 10 64 bit. AMD fx-8350 Black edition and an R9 390x video card. Quake 2 does the exact same thing. I have tried many settings to no avail. Games like Skyrim and fallout 4 run just fine. It seems to be a possible issue with Open GL not really sure. Any help would be greatly appreciated.

[Hassassin]

Thanks alot for the tip Hannes.
I tried using the war hammer profile as you suggested and imported the ESO.exe, it gives me the geometry option, but my right eye is black when i use it. The HUD shows but none of the actual in game environment. Please let me know if there is any way I can fix that. However the Z3D options work and do provide a slight 3D effect, so it will do for the time being I suppose. I really wish they would add the full 3D back to ESO, I never even got to experience it :(

Can any one tell me how is the Fallout 4 vorpx experience. Im looking forward to playing that full in VR as well. I’m just loving Skyrim in VR after I got all the proper mods and settings right. Unfortunately I only get 30 fps with a GTX 970. A few more frames would be nice, but I haven’t tried to go below ultra setting yet. Gonna be playing all the good Location Quest mods in VR, any recommendations?

[crios222]

Hi, I just bought Vorpx recently and it has worked well with some games and not so well with others, in Fallout 4 I have launched successfully and tweaked parameters but I can’t get Arma 3 to launch in my Oculus, it only displays on my T.V. I have my Oculus hooked into the HDMI port and my TV running on an adapter from a display port, and I am running windows 7. I tried to make the rift my primary display, but my computer only sees my T.V. as a display option, not the oculus. I don’t have this problem with Mount and Blade, Chiv, or Fallout 4, so I deleted every Arma 3 folder on my computer and did a fresh install to no avail. All I see in the oculus is a white gridspace with my sensor while the game loads and plays on my monitor. The only thing that happens is once the arma3 client begins to load, the oculus flickers to black for a split second but then returns to the white empty space. I have read through the trouble shooting and I have no idea what the problem is.

*edit – I have also tried running the game both with steam VR on and with it off, neither seems to help.

I also was able to optimize the settings with the config optimizer but it doesn’t seem to help the game launch on the oculus either. If you could suggest some solutions or places to check I would appreciate it as I would really enjoy playing Arma 3 and Vorpx has worked fine out of the box with other games I own. Thanks.

[anon123456]

Bought the vorpx beta last night. Windows 10, nvidia titan X. Installed vorpx, restarted my computer. I’ve tried every possible combination of things I can think of to get this to work. Disabling all apps running in my taskbar. Restarting steam VR, restarting my computer, restarting vorpx, running everything as administrator, steam VR direct mode vs not direct mode. Creating a shortcut via taskbar vorpx icon to fallout 4 downloaded through steam. Everytime I try to run it I just get a black screen. Vorpx desktop mode does not work at all. I can see the process has started but in my HMD I still see my steam VR background.

I once received a white screen with multiple color lines, almost like 2 rainbow colored barcodes. I don’t remember what combination of things I tried when that occured though because I’ve tried so many different ways to get it to work. I also received a solid red screen, and have also seen a red screen with some sort of background image, I don’t remember what it was and I can no longer get the red screen or red with background image or white with rainbow barcode to display.

Any help is greatly appreciated. I have created a vorpx troubleshoot.zip file. Do you want me to send it to you?

[peteostro]

Playing fallout 4 and it looks zoomed it. Used game optimizer and checked the ini file and it says FOV 120. Tried a bunch of voprx settings but can not get it to no look zoomed in. Also when playing the screen is flicking black allot (Does not happen in Theater mode)

[grodenglaive]

Here’s the debug report. It’s trying to launch but doesn’t quite make it.
I tried a second time and did not get an error; but there was no picture, only sound. Main screen was black, Vive was grey.
Note that I had disabled the Oculus runtime, since it was also launching along with steamvr and that didn’t work out.

`’Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\Fallout4.exe’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\ntdll.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\kernel32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\KernelBase.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\steam_api64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\advapi32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\msvcrt.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\sechost.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\rpcrt4.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\shell32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\shlwapi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\gdi32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\user32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\lpk.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\usp10.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\ole32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\X3DAudio1_7.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\xinput1_3.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\setupapi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\cfgmgr32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\oleaut32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\devobj.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\libScePad.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\winmm.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\hid.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\bink2w64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\IPHLPAPI.DLL’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\nsi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\winnsi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\winhttp.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\webio.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\msvcp110.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\msvcr110.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\flexRelease_x64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\cudart64_75.dll’. Module was built without symbols.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\flexExtRelease_x64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\nvToolsExt64_1.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\ws2_32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\GFSDK_SSAO_D3D11.win64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3d11.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\dxgi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\version.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\dwmapi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘F:\Games\SteamApps\common\Fallout 4\GFSDK_GodraysLib.x64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\apphelp.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\AppPatch\AppPatch64\AcGenral.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\sspicli.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\sfc.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\sfc_os.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\userenv.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\profapi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\mpr.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\imm32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\msctf.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\GameOverlayRenderer64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\psapi.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Users\Pete\AppData\Local\Temp\vorpx\4f8ebd4e-0.tmp’. Module was built without symbols.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\msvcp120.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\msvcr120.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3dx10_43.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3dx11_43.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3dcompiler_47.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3d10.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3d10core.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3d9.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\d3d8thk.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\D3DX9_43.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\opengl32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\glu32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\ddraw.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\dciman32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\dxgidebug.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\steamclient64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\crypt32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\msasn1.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\imagehlp.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\tier0_s64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\vstdlib_s64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\secur32.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\cryptsp.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\rsaenh.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\cryptbase.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\uxtheme.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\System32\wintrust.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Animation Labs\vorpX\Devices\OpenVR\win64\openvr_api.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\SteamApps\common\SteamVR\bin\vrclient_x64.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\SteamApps\common\SteamVR\drivers\lighthouse\bin\win64\driver_lighthouse.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Program Files (x86)\Steam\SteamApps\common\SteamVR\drivers\lighthouse\bin\win64\aitcamlib.dll’. Cannot find or open the PDB file.
‘Fallout4.exe’ (Win32): Loaded ‘C:\Windows\winsxs\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\comctl32.dll’. Cannot find or open the PDB file.
The thread 0x2d4 has exited with code 0 (0x0).
The thread 0xee0 has exited with code -1073741819 (0xc0000005).
The thread 0x1094 has exited with code -1073741819 (0xc0000005).
The thread 0x1090 has exited with code -1073741819 (0xc0000005).
The thread 0x108c has exited with code -1073741819 (0xc0000005).
The thread 0xa1c has exited with code -1073741819 (0xc0000005).
The program ‘[2984] Fallout4.exe’ has exited with code -1073741819 (0xc0000005) ‘Access violation’.