CPU：i9 13900K
Otherwise , problem will gone if I set shading rate to 1X,any numbers above this settings will cause the issues~~~anyone face the same issues？
Why would you put the shading rate to 2x? It doubles your internal rendering resolution, which puts way more strain on the GPU.
CPU：i9 13900K
MB：z690 apex with 2103 bios/newest ME version
RAM：G·skill 6000 cl36 works with XMP1
GPU：rtx4090 suprim X default clock no OC
OS：windows11 22621.900
Driver：527.37 whql
Playing metro exdous PC enhanced edtion with too much micro stuttering and inconsistent frametime jaggy like hell in the begining menu(shading rate set to 2X) , but in game footage that's OK and fps is stable . Otherwise , problem will gone if I set shading rate to 1X,any numbers above this settings will cause the issues~~~anyone face the same issues？
You probably should, it will give you much longer to diagnose all the issues you seem to get until the next driver release. What a waste of a 4090.
What you mean What a waste of a 4090.? I dont have issues dude.
I resolved my previous random crashing in loading screen in Watch Dogs L and Metro EE by restarting Msi Afterburner before launching game. ITs ok now.
What you mean What a waste of a 4090.? I dont have issues dude.
I resolved my previous random crashing in loading screen in Watch Dogs L and Metro EE by restarting Msi Afterburner before launching game. ITs ok now.
Developer:
Striking Distance Studios
Publisher:
KRAFTON, Inc.
But I guess you mean publisher has some sort of marketing deal with AMD? Well, so what? This somehow allows Nvidia to pretend the game doesn't exist and keep us in radio silence? How childish is that and what message does this send to customers? "Here at Nvidia we never of this so called Callisto Protocol, sorry everyone, better luck next time".
Yes. You knew exactly what I meant, the Calisto profile has been in the driver for weeks.
Its AMD sponsored so Nvidia will not flaunt it on their drivers.
What about any Destiny2 players, how is it?
I used 522.xx for a while, but then those random crashes returned, so I returned to 517.48 and it has been fine since then.
Destiny 2 runs fine as usual, never had random crashes with drivers before 🙂
Updated new nvidia drivers.527.37
I launched Watch Dogs Legion after 5 minutes game minimalized with message from Battleye.
[INFO]Blocked loading of file:"C:\Program Files\Nvidia Corporation\NvTelemetry\NvTelemetryBridge64.dll
I just closed this window and the game just ran without any issue.
But why it pos up?
i.postimg. cc/ZK1Czygq/te.jpg
Game not crashed,just minimalized with that Battleye message. Any ideas?
Updated new nvidia drivers.527.37
I launched Watch Dogs Legion after 5 minutes game minimalized with message from Battleye.
[INFO]Blocked loading of file:"C:\Program Files\Nvidia Corporation\NvTelemetry\NvTelemetryBridge64.dll
I just closed this window and the game just ran without any issue.
But why it pos up?
i.postimg. cc/ZK1Czygq/te.jpg
Game not crashed,just minimalized with that Battleye message. Any ideas?
So no issues eh? Honestly, not the sharpest tool in the shed are you.
Get a score in Speedway bench 9 960 on 4090. On previous drivers had 10 000 🙂
Graphics Score
9 960
Checked: Far Cry 6, Watch Dogs Legion,Control,Metro EE the same fps like was on previous drivers.
But i will stay on that one.
You probably should, it will give you much longer to diagnose all the issues you seem to get until the next driver release. What a waste of a 4090.
Maybe you have issues with your system? Where i post i have any issues like you thinking?
Not that one with Watch Dogs Legion minimalized because its battleeye thing. Before.
What you mean ?"What a waste of 4090" ? Really dont know why you complain about now.
@jmmy23, @PapaJohn
DUDES!!!
Does a Mod have to come along & 'Bitch Slap' some sense into the pair of you for this bickering nonsense? Do you realise that this WHOLE page so far is about you two spitting your dummies out at each other. Seriously o_O
Profile "The Callisto Protocol" ShowOn GeForce ProfileType Application Executable "the callisto protocol/phoenix/binaries/win64/phoenix-win64-test.exe" Executable "thecallistoprotocol.exe" Executable "the callisto protocol/phoenix.exe" Setting ID_0x105e2a1d = 0x00000004 Setting ID_0x10f9dc81 = 0x00000011 Setting ID_0x10f9dc84 = 0x01000000 Setting ID_0x80857a28 = 0x00000001 EndProfileNot mentioned in the release notes however.