3D Vision fix for Yooka-Laylee with extra graphics options.
Update: the fix has been updated for the current version of the game (July 2017). The download link is in the installation steps as always.
Fixed
- Haloing issues (smoke, water, fire, etc).
- Lighting.
- Shadows.
-
Installation
- Download this file and extract its contents in the root folder of the game.
- Launch the game through a shortcut that forces exclusive fullscreen. For example: "C:\GOG\Yooka-Laylee\YookaLaylee64.exe -window-mode exclusive".
Hotkeys
- F1: two convergence presets.
- F2: HUD depth presets.
- F3: bloom toggle. Not disabled by default.
- F4: depth of field toggle. Not disabled by default.
- F5: post process antialiasing toggle. Not disabled by default.
- F7: depth of field strength presets. Initial strength by default.
- o: HUD toggle.
Notes
- Future game updates may break the fix. I will fix the game again if that happens (probably not immediately if there are going to be more updates soon).
Thanks !!!!!!!!
ReplyDeletewow thank you so much! now I'll take this game in steam.
ReplyDeletethx so much this is fantastic in 3D
ReplyDeletewouaaah!!! great this patch
ReplyDeletevery googd job
A french fan
Hey there. I add the "-window-mode exclusive" to the icon from GOG, but nothing. Do I have to obligatory have an Nvidia card? I can only hear two low beeps and the app doesn't even start.
ReplyDeleteStart explaining everything. What do you want from the fix? If it's only for the graphics mods (depth of field, AA and bloom toggles), you don't need to run the game in exclusive fullscreen or an Nvidia GPU, in theory. That's just for 3D, and if you don't have an Nvidia GPU, you can't play with 3D Vision.
DeleteThe beeps are definitely not normal and it shows that something is wrong with the fix in your case. But I don't have an AMD GPU to test that. This fix doesn't use the Nvidia profile section, so it shouldn't be trying to access your registry, for example.
Open "d3dx.ini" and set "calls=0" to "calls=1". Then, when you try to boot the game it will generate a "d3d11.log" file. Show me its contents after your game crashes.
Hi. Sorry for not specifying it in the first place: I'm interested in the graphics mods (I'm on AMD)
DeleteHere is the log: https://pastebin.com/3fkjnvtB
Try deleting or renaming "nvapi64.dll" in the game folder (it came with the fix). I faintly recall that if it's present, it's what makes a Nvidia GPU mandatory.
DeleteDoes it support top and bottom or SBS? I tried the former, but I only get a black screen when I activate 3D mode.
ReplyDeleteProbably will work. Uncomment the line ";run = CustomShader3DVsion2SBS" in the d3dx.ini by removing the semicolon. Then you can use F11 to change 3D modes.
DeleteYou need to solve the black screen in 3D mode first though (before installing the fix). We can't do anything unless 3D is working properly. Try reinstalling your driver using DDU.
Hi, 3D is working properly. I can play in normal 3D Vision mode, no issues there. I only get the black screen if I uncomment the line ";run = CustomShader3DVsion2SBS" and select Top and Bottom or SBS mode. Also, today I noticed that when I activate 3D, I briefly see a message at the top that reads "Unrecognized shader customshader3dvsion2sbs".
DeleteFixed! I tried several things, like tinkering with the game's nVidia profile and using 3D Fix Manager to update the libraries, but what finally fixed the issue was removing the "-window-mode exclusive" option.
DeleteGreat! Thanks for letting us know the solution, that's an interesting tweak I haven't seen before.
DeleteThis comment has been removed by the author.
ReplyDeleteI loved your fix!! Played through the whole thing in 3D in 1440p and I was blown away.
ReplyDeleteIs there anyway to fix the "Portals" to other areas rendering wrong? (I'm not the only one who sees this right?)
Crashse on current steam version.
ReplyDeleteI enabled logging but no log was created. Here is game crash log:
https://www.dropbox.com/s/physsvdolfwpvdx/YookaCrashLog.zip?dl=0
The crash log suggests that you are using a Radeon card? 3D Vision is an nvidia specific technology.
DeleteOK
DeleteI was not trying to use 3D vision. I wanted to remove processing effects.
That should be OK. As a general idea, the 3Dmigoto tool will work on Radeon cards and does not require 3D Vision. You don't want to use the entire fix file though, that includes a lot of stuff to fix 3D effects and modifies a lot of shaders. Go to the Github for 3dmigoto and on the Release page download the 1.3.16 directly. Run just with that and see if you still get a crash.
DeleteIf you set calls=1 in the d3dx.ini file, that provides a 3Dmigoto log that I can look at.
The game does not crash with 3Dmigoto. Can I use it to disable postprocessing effects?
Deleted3d11_log: https://pastebin.com/9hxDMSU2
Yes, should work to disable effects. Use the hunting overlay to find the pixel shaders that you want to disable. Pixel shaders are usually better than vertex shaders, because vertex shaders can impact more parts of the image. You want to cycle through the shaders, we call 'hunting'. Once you find the shader, mark it, and you'll get the hash code for it. You can then setup a [ShaderOverride] section with handling=skip.
DeleteYou can find the default keys used for the hunting in the d3dx.ini file, and if search around a bit you'll find examples of how to do the handling=skip.
Since it doesn't crash with 1.3.16 this should work.
Thank you, it is very useful, i like it!
DeleteI managed to get this working in SBS with Quest2 using virtual desktop, 3D fix manager, and Geo 11. It looks so gorgeous! Thank you! <3
ReplyDelete