The Talos Principle 2

The Talos Principle 2

View Stats:
TTP2 + Frame Generation bug
< >
Showing 1-15 of 31 comments
dB- Nov 2, 2023 @ 10:29am 
I have the same issue :(
G Nov 2, 2023 @ 10:44am 
Same... shadows are bugged
Angry Sith Lord Nov 2, 2023 @ 10:48am 
Same. Also Frame generation causes crashes. Disable FG for now.
Alex Nov 3, 2023 @ 2:01am 
Same. But it takes a while before the issues show up. Disabling Frame Gen then doesn't fix it. You must restart the game with FG turned off to fix the lighting issues.
It's definetly an issue caused by Frame Generation.

What a shame. Hope this can get fixed.
Tilen Nov 3, 2023 @ 2:36am 
Same here.
CodiFly  [developer] Nov 3, 2023 @ 2:47am 
Are you using DLSS for frame generation? Try updating your drivers, the issue should be fixed with the drivers that also released yesterday.
joridiculous Nov 3, 2023 @ 4:05am 
Originally posted by FireGate_13:
https://www.youtube.com/watch?v=kxoU5CtAt2w
studio driver 537.42. I don't have any of those issues at all (typo, should be 5xx not 4xx)
Last edited by joridiculous; Nov 3, 2023 @ 7:57am
the_mo101 Nov 3, 2023 @ 5:20am 
I'm using the latest driver. 546.01. Indoor areas still fade to blackness when FG is enabled. Areas like the museum are unplayable. Everything looks great when FG is switched off and the game is restarted. I didn't have this problem in the demo though I have updated my drivers since then,
Last edited by the_mo101; Nov 3, 2023 @ 6:08am
the_mo101 Nov 3, 2023 @ 5:27am 
Originally posted by joridiculous:
Originally posted by FireGate_13:
https://www.youtube.com/watch?v=kxoU5CtAt2w
studio driver 437.42. I don't have any of those issues at all

I think I may try a roll back. The last two updates destroyed my frame gen mod in Starfield too! I think 437.42 was the last time it worked properly.
the_mo101 Nov 3, 2023 @ 5:46am 
You're right, It works perfectly with 437.42. Thanks!
joridiculous Nov 3, 2023 @ 7:59am 
Originally posted by the_mo101:
You're right, It works perfectly with 437.42. Thanks!
ok well that's nice.. I had a typo in my post post it should be 537.42. But if the one you found works, keep it.
Mad Max Nov 3, 2023 @ 8:03am 
I confirm that I have the same problem on drivers starting from 545.84 to 546.08 beta. On drivers 537.58 the frame generation works fine.
Last edited by Mad Max; Nov 3, 2023 @ 8:05am
Alex Nov 3, 2023 @ 8:04am 
Originally posted by CodiFly:
Are you using DLSS for frame generation? Try updating your drivers, the issue should be fixed with the drivers that also released yesterday.

Yesterday? Yesterday was no driver relase. I'm using 546.01 released on october 31. This is the newest game ready driver available.

But according to previous comments maybe the newer drivers are causing the problems.
Nvidia introduced a new driver branch last month and in general people seem to have issues with those newer drivers from the current branch.

I really think you as devs should reach out to nvidia and clarify what's going on here.

Thanks for the effort!


Originally posted by Mad Max:
I confirm that I have the same problem on drivers starting from 545.84. On drivers 537.58 the frame generation works fine.

Oooh, this already confirms what I just wrote.

537.58 is the old driver branch (october 10th).
All drivers released after 537.58 are using the newer branch which seem to cause many issues for people in a lot of games (stutter issues, memory leaks, crashes - nvidia really messed up with the new branch).
Last edited by Alex; Nov 3, 2023 @ 8:09am
joridiculous Nov 3, 2023 @ 8:05am 
I'll quote this DEV post here:
Originally posted by Eagleshadow:
I just tested the recent driver versions:
546.01 - fail
545.92 - fail
545.84 - fail
537.58 - works
537.42 - works

So its looks like the bug was introduced in driver version 545.84, and 537.58 is the most recent driver version that does not have this issue.
the_mo101 Nov 3, 2023 @ 8:09am 
Originally posted by joridiculous:
I'll quote this DEV post here:
Originally posted by Eagleshadow:
I just tested the recent driver versions:
546.01 - fail
545.92 - fail
545.84 - fail
537.58 - works
537.42 - works

So its looks like the bug was introduced in driver version 545.84, and 537.58 is the most recent driver version that does not have this issue.

Thanks!
< >
Showing 1-15 of 31 comments
Per page: 1530 50

Date Posted: Nov 2, 2023 @ 8:58am
Posts: 31