I have an update to share…I’m still messing around with gamemode, as suggested, but I’m struggling a bit. I haven’t tried anything else just yet…still googling at this point…in the meantime if anyone has any additional suggestions it would be much appreciated! Let me know if there’s any more info I should provide…thanks!
Vulkan Installable Client Driver (ICD) ~]$ ls /usr/share/vulkan/icd.d/
Vulkan Installable Client Driver (ICD) Loader (32-bit) Below is my output for pacman -Qs vulkan : local/lib32-nvidia-utils 470.63.01-1 Googling those last 2 lines brought me to suggestions to ensure I had lib32-vulkan-icd-loader as well as vulkan-icd-loader installed, which I do. Info: Required Vulkan extension VK_KHR_surface not supportedĮrr: DxvkInstance: Failed to create instance I had a log file created in hopes that it would output at least something that I could search for…Output of Doom3BFG_dxvi.log: info: Game: Doom3BFG.exe The game actually launches with or without this variable present…it doesn’t seem to make any difference at all though. The proper colors render, but it either crashes after cutscene or I am only able to see my HUDĪdding launch option PROTON_USE_WINED3D=TRUE %command%. Switching between older versions of Proton (all the way down to 4.2) doesn’t seem to help. OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 21.2.1 OpenGL shading language version string: 1.30 OpenGL core profile profile mask: core profile OpenGL core profile context flags: (none) OpenGL core profile shading language version string: 3.30 OpenGL core profile version string: 3.3 (Core Profile) Mesa 21.2.1 OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) OpenGL vendor string: Intel Open Source Technology Center Vendor: Intel Open Source Technology Center (0x8086)ĭevice: Mesa DRI Intel(R) HD Graphics 3000 (SNB GT2) (0x116)
Output of ls /usr/share/vulkan/icd.d/ nvidia_icd.jsonĮxtended renderer info (GLX_MESA_query_renderer): Recently though (last 2-3 days) using older Proton version launches game with with completely black screen. Older versions of Proton (pre 6.3) will launch the game with correct colors but it still crashes after opening cutscene.
Issue: Doom 3 BFG Edition will launch using Proton Experimental or Proton 6.3, but everything is different shades of red and black…no other color…and after opening cutscene the game crashes and I’m back to my Steam library. Changing usecache to 1 obviously uses the cache, and cacheMink, I have no idea what it does, but if it isn't as high as what I mentioned earlier you need to change usecache back to "0" or your game will crash.Having a bit of trouble getting Doom 3: BFG Edition to work on Steam…hoping someone can lend a helpful hand. By raising cachemegs you are leaving more room for Doom to work with. card can't store all the textures it needs, it will use some of your system memory to store them. called Texture Thrashing, basically what this means is if your vid. If anyone else wants to post any other tweaking tips or ask questions / make suggetions feel free.īrief Explanation of what you changed in DoomConfig.cfg:ĭoom3 uses a tech. Now I run on high quality at 1024 (havent tried a higher res yet but will) with awesome framerates and no stuttering ever. but by doing so you should also change image_cacheMink to "20480".īefore I was running at 1024x768 medium quality and still getting tiny bits of chop when i went through certain doors etc. If you want you can also change image_useCache to "1".
Now, change image_cacheMegs to 1/4 of your physical memory. Scroll down until you get to the following fields:
Special Catalyst 4.9 Drivers have been released ESPECIALLY for use with Doom 3. Okay, here are a few quick tips to make sure you are running doom at the best quality with the best framerate your rig can handle.įirst, Radeon users.