Store Page
Lords of the Fallen
All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

Lords of the Fallen

Store Page
View Stats:
Global Achievements
Abysswalker Oct 21, 2023 @ 3:20pm
Shaders dont pre compile correctly anymore after driver update?
I updated to the latest NVIDIA driver as the game wanted me to do and even warned me about before starting it. The shader cache was deleted as a result. Usually it gets rebuild after I start the game again but not in LOTFs case apparently. Cause now I have terrible shader stutters all the time. I even went back to the older driver 537.58 but its still not compiling the shaders correctly and still stuttering.

When I first started the game on release day, I noticed that the shaders were pre compiling correctly because of the very high CPU usage and the longer load time. The game ran butter smooth as a result. This doesnt happen anymore, it loads up pretty quickly without compiling shaders. I have deleted the UPIPELINECACHE file in AppData/Local/LOTF2 multiple times. No change. My guess is one of these patches messed something up.

I hate Unreal Engine with a passion. Always issues. Only a few games running well on this engine. Sure it looks great but other than that, its trash. I have a 4090, 13900K and DDR5 7200Mhz CL34 RAM. Also yes, the game is on an NVME SSD (990 Pro). The FPS are fine. Its just the shader stutters that are pretty noticeable now. Has anyone managed to find a fix?

EDIT: Apparently the latest, or one of the latest patches broke the shader compilation step. I guess we have to wait for the devs to undo their mistake. You would notice an issue like that instantly if there was QA testing, but since we sometimes get two patches a day, QA testing falls flat.
Last edited by Abysswalker; Oct 22, 2023 @ 2:04am
The author of this topic has marked a post as the answer to their question.
Click here to jump to that post.
Originally posted by Volf:
Ok so first things first, make sure you save your save files. They're in your local appdata location like other games. If you're not sure where this is, please check online on how to get it visible. I didn't need to do anything with it myself but I figured it would be safe to do.

Next please follow the below, I might miss something so please do the best you can at piecing things together. Also a grain of salt as this might not fix your issues.

-Do a fresh driver install
-delete LOTF2_PCD3D_SM6.upipelinecache in your local appdata location
-we're then going to download an old version of the game through steam. You'll want to read the guide on how to do this here, https://www.makeuseof.com/how-to-downgrade-steam-games/
-You can experiment with any version you want for the manifest but I went with the below 3 numbers for appID, depotID and manifest ID.
-1501750 1501751 6588456889037667214

-after these download ~30gb, you'll want to drag them over to your main game install folder and replace all files with them. I would also recommend right clicking the game and telling it to only update when you want/open.
-Funny thing here is that it doesn't look like the game devs have implemented any form of check on which version you're running the game with. I installed this version to boot up the game to see if it worked and sure enough it was 1.1.19 in the bottom right corner, it also gave me the message saying crossplay was working when I logged in.

-Anyways, once you load in if things worked you should see the shaders compile as they should before loading into the main menu and you can exit the game when finished.
-Normally you could just right click the game and change the update to always keep the game up to date BUT as I mentioned above. There is no check on this from the devs so the game will keep launching in the old version...so....

-Now you have to download the current most live version to avoid any potential issues on their next update. So you'll want to follow the above steps again but use the most recent manifest below.
-1501750 1501751 2308268746285644881
-This will be another 30gb download and you'll want to replace all your main files again...
-Once this is complete you should have had your shaders compile and you'll be back to version 1.1.21.

Sorry there may be ways to streamline this but I certainly don't want to invest more time into fixing this. Best of luck to you all and hopefully it helps
< >
Showing 1-15 of 33 comments
elstirthibaut Oct 21, 2023 @ 3:31pm 
I think you can try deleting the cache file in in C:\Users\ldlc\Yourname\Local\LOTF2\Saved
it's LOTF2_PCD3D_SM6.upipelinecache. delete it and launch the game.
#1
Volf Oct 21, 2023 @ 11:31pm 
Anyone figure this out? I'm also having issues and I've tried all nonsense posted on this forum with no luck. I need to know how to force another shader build before the main menu...
#2
Goodfella Oct 21, 2023 @ 11:43pm 
Same thing happened to me since the update, making the game rather unpleasant to play now.
#3
Barf Oct 22, 2023 @ 12:44am 
It isn't the new driver as I experienced this issue on the previous patch on the 537.xx drivers. The previous patch apparently has broken the Shader compilation step. Deleting the file above is a placebo, it does nothing.
#4
Abysswalker Oct 22, 2023 @ 1:57am 
Originally posted by Giant Feeble Lard Baby:
It isn't the new driver as I experienced this issue on the previous patch on the 537.xx drivers. The previous patch apparently has broken the Shader compilation step. Deleting the file above is a placebo, it does nothing.
Yeah they really need to fix this asap. Cause I guess lots of people have updated their drivers (which deletes the shaders) because of the warning you get when playing with an older driver. I dont know how you could mess a patch up this bad and break one of the most important steps that could prevent stuttering, the shader compilation.

Its one of the downsides when pushing out this many patches. Basically no QA testing.

Originally posted by Volf:
Anyone figure this out? I'm also having issues and I've tried all nonsense posted on this forum with no luck. I need to know how to force another shader build before the main menu...

I am not sure if it would work if someone could upload the shaders which were loaded in correctly before the patch broke it and we just copy paste them into the AppData/Local/LOTF2 folder. But apart from that, I think we have to wait and see if the devs fix it as fast as they broke it.
Last edited by Abysswalker; Oct 22, 2023 @ 2:08am
#5
Goodfella Oct 22, 2023 @ 2:48am 
Originally posted by Giant Feeble Lard Baby:
It isn't the new driver as I experienced this issue on the previous patch on the 537.xx drivers. The previous patch apparently has broken the Shader compilation step. Deleting the file above is a placebo, it does nothing.

I just uninstalled the latest driver and installed the previous one, 537.58. Fixed it for me. Hilarious that the game tells you it has issues, even though the later driver is the one that causes the issues.
Last edited by Goodfella; Oct 22, 2023 @ 2:49am
#6
Blacksmith77K Oct 22, 2023 @ 3:17am 
Originally posted by Abysswalker:
IThis doesnt happen anymore, it loads up pretty quickly without compiling shaders. I have deleted the UPIPELINECACHE file in AppData/Local/LOTF2 multiple times. No change. My guess is one of these patches messed something up.



EDIT: Apparently the latest, or one of the latest patches broke the shader compilation step. I guess we have to wait for the devs to undo their mistake. You would notice an issue like that instantly if there was QA testing, but since we sometimes get two patches a day, QA testing falls flat.

Ive no problems with nVidia 545.54. I just clean up the driver with DDU only to see what your problem can be.
So after REINSTALLING 545.54 there is NO problem. Shader will be created how it should be.
Maybe you have to find your problem on your system. (C++ up to date, etc...)
#7
Abysswalker Oct 22, 2023 @ 4:10am 
Originally posted by Blacksmith77K:
Originally posted by Abysswalker:
IThis doesnt happen anymore, it loads up pretty quickly without compiling shaders. I have deleted the UPIPELINECACHE file in AppData/Local/LOTF2 multiple times. No change. My guess is one of these patches messed something up.



EDIT: Apparently the latest, or one of the latest patches broke the shader compilation step. I guess we have to wait for the devs to undo their mistake. You would notice an issue like that instantly if there was QA testing, but since we sometimes get two patches a day, QA testing falls flat.

Ive no problems with nVidia 545.54. I just clean up the driver with DDU only to see what your problem can be.
So after REINSTALLING 545.54 there is NO problem. Shader will be created how it should be.
Maybe you have to find your problem on your system. (C++ up to date, etc...)

I always use DDU to uninstall drivers. I have reinstalled the driver two times now. I am not sure if you understand what I mean. The shader loading "bar" is still present. It just doesnt create nearly enough shaders anymore for a 100% smooth experience. At launch my CPU usage was at 99% for almost a minute and the game created a ton of shaders (how its intended at first launch or after driver updates). That is broken right now.

Maybe you just dont notice it. Its not stuttering all the time but its definitely noticeable and not right. C++ has nothing to do with it. In any other game (UE), shaders are being created correctly.
Last edited by Abysswalker; Oct 22, 2023 @ 4:12am
#8
Gameo Oct 22, 2023 @ 4:14am 
Originally posted by Abysswalker:
Originally posted by Blacksmith77K:

Ive no problems with nVidia 545.54. I just clean up the driver with DDU only to see what your problem can be.
So after REINSTALLING 545.54 there is NO problem. Shader will be created how it should be.
Maybe you have to find your problem on your system. (C++ up to date, etc...)

I always use DDU to uninstall drivers. I have reinstalled the driver two times now. I am not sure if you understand what I mean. The shader loading "bar" is still present. It just doesnt create nearly enough shaders anymore for a 100% smooth experience. At launch my CPU usage was at 99% for almost a minute and the game created a ton of shaders (how its intended at first launch or after driver updates). That is broken right now.

Maybe you just dont notice it. Its not stuttering all the time but its definitely noticeable and not right. C++ has nothing to do with it. In any other game (UE), shaders are being created correctly.
Sounds like a driver issue, you can set the shader cache size in the nvidia control panel, if thats actually whats happening
#9
Abysswalker Oct 22, 2023 @ 4:34am 
Originally posted by Gameo:
Originally posted by Abysswalker:

I always use DDU to uninstall drivers. I have reinstalled the driver two times now. I am not sure if you understand what I mean. The shader loading "bar" is still present. It just doesnt create nearly enough shaders anymore for a 100% smooth experience. At launch my CPU usage was at 99% for almost a minute and the game created a ton of shaders (how its intended at first launch or after driver updates). That is broken right now.

Maybe you just dont notice it. Its not stuttering all the time but its definitely noticeable and not right. C++ has nothing to do with it. In any other game (UE), shaders are being created correctly.
Sounds like a driver issue, you can set the shader cache size in the nvidia control panel, if thats actually whats happening
I have set the size to unlimited and still no change. Its 100% the game since it doesnt happen with other UE games. I just fired up Lies of P and the shaders were created correctly with high CPU usage. Here is a screenshot of the ingame frametime graph. I was just walking a little bit in skyrest brigde and the shader stutter was already very noticeable:

https://steamcommunity.com/sharedfiles/filedetails/?id=3057695837
#10
Blacksmith77K Oct 22, 2023 @ 4:36am 
Ah okay. IF you install a fresh driver, THEN the shader will compiled complete and you will see your CPU on 100% for 10-20sec or so.

After that, IF you relaunch your game, you can see the "shader create bar" too, but THAT is only a shader CHECK and need less time.

Your reported stutter are traversal (hardcoded loading-points) and autosave stutter (all 25sec)
#11
Abysswalker Oct 22, 2023 @ 4:42am 
Originally posted by Blacksmith77K:
Ah okay. IF you install a fresh driver, THEN the shader will compiled complete and you will see your CPU on 100% for 10-20sec or so.

After that, IF you relaunch your game, you can see the "shader create bar" too, but THAT is only a shader CHECK and need less time.

Your reported stutter are traversal (hardcoded loading-points) and autosave stutter (all 25sec)
The thing is, it didnt happen at launch up until I updated my driver (did a DDU fresh install) yesterday (which deleted shaders). That CPU on 100% for 20s didnt happen either. The bar filled up just as fast as usual. Thats the issue here. Its not traversal stutter (if it were, it would still be bad on the games side though). I have already reported the issue to the devs hoping they look into it.
Last edited by Abysswalker; Oct 22, 2023 @ 4:44am
#12
Gameo Oct 22, 2023 @ 4:46am 
Originally posted by Abysswalker:
Originally posted by Blacksmith77K:
Ah okay. IF you install a fresh driver, THEN the shader will compiled complete and you will see your CPU on 100% for 10-20sec or so.

After that, IF you relaunch your game, you can see the "shader create bar" too, but THAT is only a shader CHECK and need less time.

Your reported stutter are traversal (hardcoded loading-points) and autosave stutter (all 25sec)
The thing is, it didnt happen at launch up until I updated my driver (did a DDU fresh install) yesterday (which deleted shaders). That CPU on 100% for 20s didnt happen either. The bar filled up just as fast as usual. Thats the issue here. Its not traversal stutter (if it were, it would still be bad on the games side though).
Are you DDUing in safe mode? That parts important. Do that and go back to a previous driver likw 537.34 i think it is, ( from sept ) and see if the issue persists
#13
Abysswalker Oct 22, 2023 @ 4:48am 
Originally posted by Gameo:
Originally posted by Abysswalker:
The thing is, it didnt happen at launch up until I updated my driver (did a DDU fresh install) yesterday (which deleted shaders). That CPU on 100% for 20s didnt happen either. The bar filled up just as fast as usual. Thats the issue here. Its not traversal stutter (if it were, it would still be bad on the games side though).
Are you DDUing in safe mode? That parts important. Do that and go back to a previous driver likw 537.34 i think it is, ( from sept ) and see if the issue persists
I use DDU always in safe mode. I already mentioned that I went back to the previous driver in the opening post...
Last edited by Abysswalker; Oct 22, 2023 @ 4:48am
#14
Barf Oct 22, 2023 @ 6:31am 
Originally posted by Gameo:
Originally posted by Abysswalker:
The thing is, it didnt happen at launch up until I updated my driver (did a DDU fresh install) yesterday (which deleted shaders). That CPU on 100% for 20s didnt happen either. The bar filled up just as fast as usual. Thats the issue here. Its not traversal stutter (if it were, it would still be bad on the games side though).
Are you DDUing in safe mode? That parts important. Do that and go back to a previous driver likw 537.34 i think it is, ( from sept ) and see if the issue persists

I am with Abyss on this. The last patch or patch before has broken the shader comp step. Somewhere between the 17th and the 20th as I have a post back on the 19th noticing this change. For testing purposes I decided to launch Lies of P since I had updated my drivers after the last time I had played, and sure enough it performed a shader comp step as expected. This proves to me that it isn't the driver and more to do with the patch breaking it.
#15
< >
Showing 1-15 of 33 comments
Per page: 1530 50

Lords of the Fallen > General Discussions > Topic Details
Date Posted: Oct 21, 2023 @ 3:20pm
Posts: 33

Discussions Rules and Guidelines