-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Game won't launch #25
Comments
Just chipping in. I have got the same problem. I have got GOG 1.4 hotfix version of Far Cry. Installed OK, VR mod installed OK, even shows up in the list of MODS (CryVR) in 2d game screen. I have got Oculus Quest 1. Windows 11, DX12, GPU AMD RX6600. The integrated card Hybrid toggle is always switched off i.e. High Performance discreet GPU i.e. AMD6600 in on at all times. When starting the game from Steam, or Oculus Home, with FarCryVR.bat file the screen goes black and then nothing happens. And on the Desktop toolbar there is like a "double icon" one of which says Fallout 2006 and the other half says something like...Exception Failed Violation, Critical error, Memory 00000000C see below, and there is a button in the bottom right saying ABORT. It happens within 3 seconds of starting the game. The LOG txt file says Direct3D9 initiating, failed no suitable device found. If I try to run FarCryVR.bat as administrator I get an instant message "FarCry. exe cannot be located". I have tried everything, reinstall, try 0.5.2 VR mod, same thing. I've tried removing "erase direct9...dll or something like that...." in FarCryVR. bat, nothing. Please help? Never had any problems with any VR game before... This is the same problem that was solved and closed by another user, I just don't know how and what was done. Call Stack Trace: function=0x0** END OF LOG Physics initialization Exception: 0xC0000005, at Address: 0x0023:0x38010FA3 Thank you for the efforts. I just want to be able to appreciate your wonderful VR Mod))). |
Please provide the full contents of both the In general, make sure your graphics drivers are up to date. If you have any monitoring software running, like fpsVR or Afterburner/Rivatuner, try disabling them as they can sometimes interfere. |
Thank you ever so much for trying to help, I have lost all hope. AMD drivers up-to-date, no other VR apps running. As requested please find the logs below: Log Started at Thursday, August 24, 2023 22:50:05 --- CPU detection --- Processor 1: Processor 2: Processor 3: Processor 4: Processor 5: Processor 6: Processor 7: Processor 8: Processor 9: Processor 10: Processor 11: OS User name: 'Dimster'
|
This is your issue, your graphics driver does not support Vulkan 1.3. Given that your card absolutely should, that suggests that your graphics driver is not up to date (or that you have Vulkan extensions or layers installed that prevent it from detecting Vulkan 1.3). Please try redownloading and installing the latest AMD Adrenaline driver from https://www.amd.com/en/support/graphics/amd-radeon-6000m-series/amd-radeon-rx-6000m-series/amd-radeon-rx-6600m. If necessary, use Display Driver Uninstaller first to do a clean reinstall of the driver. |
Thank you. Does it matter if all my other VR games with mods work perfectly, meaning that "Vulcan" (whatever it is)" is installed and working correctly. Or is it just FarCry is the only game that uses Vulcan? I am seriously confused, because Vulcan 1.3 support was already included standard in AMD driver release 22.1.2. Why is FarCryVR not detecting it, when all other VR games with 3D Mods do? Thanks again. |
Most VR mods, or even native VR games, for that matter, do not use Vulkan, and few, if any, require Vulkan 1.3. Yes, your driver should support it, which is why I recommend reinstalling it fresh. And make sure that nothing interferes with Vulkan - like I said, if you have monitoring tools like fpsVR or Afterburner/Rivatuner running, that can cause issues. If you have installed Vulkan extension layers like Reshade or others, those might cause issues, as well. There is nothing I can do on my end, I'm afraid. Something is interfering with your driver's Vulkan support on your end, so I recommend you go through the steps outlined above. |
Thank you so much for your help! |
Check your |
What about similar crashes with only warning of this line on latest drivers: |
Please always provide both logs in full. I can't really tell anything otherwise. That line is most likely irrelevant. |
Sorry. Game launches and loads through normal desktop mode. error.log: Exception Code: 0xC0000005 The memory could not be "read" Call Stack Trace:
log.txt: --- CPU detection --- Processor 1: Processor 2: Processor 3: Processor 4: Processor 5: Processor 6: Processor 7: Processor 8: Processor 9: Processor 10: Processor 11: Processor 12: Processor 13: Processor 14: Processor 15: OS User name: 'Smoils VR' Init Shaders 127 Shader files found. Construct Shader ''...ok The memory could not be "read"
info: Game: FarCry.exe |
I encountered the same issue, using AMD 5700 XT. I tried to load save I have created in desktop mod and the game just crashes with no error message. Trying to start new game in VR mode also crashes game after loading. |
Make sure your GPU driver is up to date and disable any overlays or performance monitors like fpsVR, Rivatuner/Afterburner, ... |
Thank you, I finally solved it. Simply updating the GPU driver wasn't enough, though. After completely uninstalling using DDU and then reinstalling the latest drivers, as well as reinstalling the game/mod, it fixed the issue for me. Additionally, I think it's worth mentioning that the first time I launched the game was without the mod installed. I just configured the settings, started the game, and then quit. Then mod installed -> no more crashes. |
I think I have all the files loaded and in the right place. Quest headset is recognized in Steam VR, through Visual Desktop. But when I launch from the bat file, it sits in the Steam VR "waiting room" and goes no further. Im a Windows newbie, but would appreciate the opportunity to play your mod. It looks fantastic.
tj
The text was updated successfully, but these errors were encountered: