Stuck to low quality assets in match

[Sangral]

Anyone else having this problem? I have set everything to max settings but something seems broken on PC. In a match everyone has low quality hair and body textures but if I choose Highlight Reel then everything is how it should be and transforms into high quality.

I heard from someone that did not have this problem but I am sitting here with my 4090 and 7800X3D and have this.

How about you guys?

In match:
https://c.l3n.co/i/Yb6wfD.png

Highlight Reel:
https://a.l3n.co/i/Yb6bp0.png

You can also see this problem here in this video from someone (Look at Cody's hair)
https://www.youtube.com/watch?v=DrMK7JYvTRI

EDIT:

I nailed the problem a little bit down. I did lot's of more comparisons. Found out that low asset models seems to glitch through the attire very often like Tonga Loa here:

https://b.l3n.co/i/YbqmQq.png

Which doesn't happen on the high quality assets.

And then I found out that it's probably LOD based, and therefore an LOD problem. If I go very close to the model with the third person camera, it changes to high quality. So this is what's actually broken. The LOD is so short that the normal gameplay camera can't reach it and everything is low asset models in normal gameplay.

https://www.youtube.com/watch?v=RoR0vBt3EaI

Edit 2:

Here are 2 more examples of this issue. Every PC version has this and yes, it's indeed because the LOD distance for High Quality assets is set too close to the models so it never triggers. This leads to moments like this where the bell rings and the second the match starts, all 4 characters turn into lower asset characters.

https://youtu.be/VrkcnuQpQ_Q

Or, problems like this, where I am sure that 2K doesn't wan't this to be a huge topic on social media.
Because you are only seeing lower asset models in gameplay, these models have slightly changed bodies and these don't react well anymore to the attires they are wearing. So you are constantly having smaller or bigger parts of the body glitching through the clothing, like here.

https://youtu.be/On6Kp_oZQ8o

I am sure it's in 2Ks interest to get this fixed.

UPDATE:

https://c.l3n.co/i/oVcuQa.jpg

The LOD issue is now officially in the Tracker of 2K for current problems! Please upvote to make them fix this.

https://support.wwe2k.com/hc/en-us/community/posts/39519897677075-Play-Graphic-Quality-Randomly-Appears-Low-in-Gamplay-and-Highlight-Reels

They still got the description half wrong here tho. 🤦🏻‍♂️ The issue is always in gameplay and always because of a very simple and instantly noticable reason (The LOD "trigger" being too close to the characters) and not random and it is not appearing in Highlight Reel at all, that's why you can use Highlight Reel to compare.
It's like you explain things to them like they're 5 and they still throw every information together like AI 1.0 and make something confusing out of it. 😂


But still, upvoting would be nice.

[Ja'Crispy]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von Highway:

Would be funny if was as simple as that to fix. Also using driver 572.75 if that matters.

Also occurs to me theres is also a camera setting for the FOV defaults... havent changed that but might also be a thing if on ultrawide like me... anyway testing Cody vs DDP since both have specific haircuts now see what happens

Okay thank you good sir and yes it wouldn’t suprise me if clamp was causing it , I was pulling my hair out over that setting not long ago haha

[Highway]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von Highway:

Would be funny if was as simple as that to fix. Also using driver 572.75 if that matters.

Also occurs to me theres is also a camera setting for the FOV defaults... havent changed that but might also be a thing if on ultrawide like me... anyway testing Cody vs DDP since both have specific haircuts now see what happens

Well on default camera and default nvidia profile, in a default 1v1 I'm only seeing LOD drop when reasonable distance from the outside the ring view, seems normal LOD until camera is about zoomed out floating halfway to the barriers in a live match not replay. So guess can eliminate my filtering settings and negative LOD settings as a fix lol as same with them off.

Will now try the camera FOV setting I heard about, see if thats a cause.

EDIT thats only for the 3rd person view so probably not the issue.

[Highway]

Yea tried few different modes and cant reproduce this issue on mine, even on a live bot match with manual camera i can zoom out from action without pop-in hair LOD changes people having issue with, mine degrades nigh on the barriers if they on opposite side of ring.

[Ja'Crispy]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von Highway:

Also occurs to me theres is also a camera setting for the FOV defaults... havent changed that but might also be a thing if on ultrawide like me... anyway testing Cody vs DDP since both have specific haircuts now see what happens

Well on default camera and default nvidia profile, in a default 1v1 I'm only seeing LOD drop when reasonable distance from the outside the ring view, seems normal LOD until camera is about zoomed out floating halfway to the barriers in a live match not replay. So guess can eliminate my filtering settings and negative LOD settings as a fix lol as same with them off.

Will now try the camera FOV setting I heard about, see if thats a cause.

EDIT thats only for the 3rd person view so probably not the issue.

Okay , tbh it doesn’t bother me that much cuz I only notice the hair model looking really rough outside of entrances , it’s definitely a weird one

[Highway]

Ursprünglich geschrieben von Ja'Crispy:

Ursprünglich geschrieben von Highway:

Well on default camera and default nvidia profile, in a default 1v1 I'm only seeing LOD drop when reasonable distance from the outside the ring view, seems normal LOD until camera is about zoomed out floating halfway to the barriers in a live match not replay. So guess can eliminate my filtering settings and negative LOD settings as a fix lol as same with them off.

Will now try the camera FOV setting I heard about, see if thats a cause.

EDIT thats only for the 3rd person view so probably not the issue.

Okay , tbh it doesn’t bother me that much cuz I only notice the hair model looking really rough outside of entrances , it’s definitely a weird one

Starting to think this in more a cache issue as recall the previous games all have a 8gb floating cache file... something my gen4 NVME doesnt struggle with maybe? which always defaults to C: which might not be everyones fastest storage etc

C:\Users\(USERNAME)\AppData\Local\WWE 2K25\PrebakeCache.bin

back in the days before i moved to NVME I did a linked folder to move that temp file to faster drive to fix things, helps enormously for creative tools etc loading times. This file is generated every time launch a match to load the resources (so safe to delete as will regenerate it every time play). The game also stores all the PSO shader cache there as well... so if C: is a sluggish drive that could be reason?

[Gretschory]

Can confirm it is definitely a thing. Wow that is new low.

Edit: Correcting myself: Not a new low. Going through my files for bug reports I found that glitch in at least 2 other WWE games. It was later resolved according to my own notes.

Confirms the suspicion they take an older version of the game to build on that. Can somebody confirm that bug was in 2k19? This would be the last version with chain wrestling active and I think I remember reporting this issue on the forums and they fixed it in a later patch. It is actually looking like the same glitch I had on an older version. I did not name the screens accordingly (silly me) but yeah it quite looks like that.

[JamappleKirk]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von JamappleKirk:

100% this is happening to me too, make me laugh the people saying it's op's specs and calling it user error, this will be happening for everyone there is no setting the end user can change that would fix this.

*that you know....

Fact is there are so many variables to glitches due to the sheer variation of PC builds and drivers, background apps, hardware variations, bios settings, video settings, windows settings and patches, and game updates too, that its very hard to have two identical setups show identical issues, and even might be intermittent (this is why console issues tend to be picked up easier cos they are all the same setup, but it's not infallible as quality control on the silicon is not factored into that)

If 100 people bothered to come here and say they have the issue, what about the tens of thousands of others might not or didnt notice, and because they didnt turn up to comment, it doesnt validate your statement of everyone having the problem. Sample size matters on stats, but the stats can still be wrong unless every single person is polled.

So until officially confirmed by devs as a heavily reported issue to the bug report, this is just a tiny vocal minority. If you believe its a fact, then encourage people to submit bug tickets on the support site, not just moan here as that solves nothing.

Would you be willing to post ingame screenshots of you not having this issue? posting tickets to 2k support is somthing we should all be doing yes, however I can see why people wouldn't bother as we normally get nothing passed a copy paste canned response from agents.

P.s I have a gen 4 NVME too and I'm getting the issue every single match.

[WestJake]

Ursprünglich geschrieben von JamappleKirk:

Ursprünglich geschrieben von Highway:

*that you know....

Fact is there are so many variables to glitches due to the sheer variation of PC builds and drivers, background apps, hardware variations, bios settings, video settings, windows settings and patches, and game updates too, that its very hard to have two identical setups show identical issues, and even might be intermittent (this is why console issues tend to be picked up easier cos they are all the same setup, but it's not infallible as quality control on the silicon is not factored into that)

If 100 people bothered to come here and say they have the issue, what about the tens of thousands of others might not or didnt notice, and because they didnt turn up to comment, it doesnt validate your statement of everyone having the problem. Sample size matters on stats, but the stats can still be wrong unless every single person is polled.

So until officially confirmed by devs as a heavily reported issue to the bug report, this is just a tiny vocal minority. If you believe its a fact, then encourage people to submit bug tickets on the support site, not just moan here as that solves nothing.

Would you be willing to post ingame screenshots of you not having this issue? posting tickets to 2k support is somthing we should all be doing yes, however I can see why people wouldn't bother as we normally get nothing passed a copy paste canned response from agents.

P.s I have a gen 4 NVME too and I'm getting the issue every single match.

Several people including me already sent a ticket. The more people do so, the higher chance they will fix it.

[Highway]

Ursprünglich geschrieben von JamappleKirk:

Ursprünglich geschrieben von Highway:

*that you know....

Fact is there are so many variables to glitches due to the sheer variation of PC builds and drivers, background apps, hardware variations, bios settings, video settings, windows settings and patches, and game updates too, that its very hard to have two identical setups show identical issues, and even might be intermittent (this is why console issues tend to be picked up easier cos they are all the same setup, but it's not infallible as quality control on the silicon is not factored into that)

If 100 people bothered to come here and say they have the issue, what about the tens of thousands of others might not or didnt notice, and because they didnt turn up to comment, it doesnt validate your statement of everyone having the problem. Sample size matters on stats, but the stats can still be wrong unless every single person is polled.

So until officially confirmed by devs as a heavily reported issue to the bug report, this is just a tiny vocal minority. If you believe its a fact, then encourage people to submit bug tickets on the support site, not just moan here as that solves nothing.

Would you be willing to post ingame screenshots of you not having this issue? posting tickets to 2k support is somthing we should all be doing yes, however I can see why people wouldn't bother as we normally get nothing passed a copy paste canned response from agents.

P.s I have a gen 4 NVME too and I'm getting the issue every single match.

is your C: drive for OS also on NVME gen4? or just the game install ? (i have 10 drives in my rig, and the Gen4 OS drive isnt used for games, I have seperate gen4 for steam etc, so just helps to eliminate if the bin cache is causing this).

[WestJake]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von Ja'Crispy:

Okay , tbh it doesn’t bother me that much cuz I only notice the hair model looking really rough outside of entrances , it’s definitely a weird one

Starting to think this in more a cache issue as recall the previous games all have a 8gb floating cache file... something my gen4 NVME doesnt struggle with maybe? which always defaults to C: which might not be everyones fastest storage etc

C:\Users\(USERNAME)\AppData\Local\WWE 2K25\PrebakeCache.bin

back in the days before i moved to NVME I did a linked folder to move that temp file to faster drive to fix things, helps enormously for creative tools etc loading times. This file is generated every time launch a match to load the resources (so safe to delete as will regenerate it every time play). The game also stores all the PSO shader cache there as well... so if C: is a sluggish drive that could be reason?

This is definitely not a shader cache issue. It's a set value for LODs by devs. It's issue on PS5 as well and other consoles.

[Highway]

Ursprünglich geschrieben von WestJake:

Ursprünglich geschrieben von Highway:

Starting to think this in more a cache issue as recall the previous games all have a 8gb floating cache file... something my gen4 NVME doesnt struggle with maybe? which always defaults to C: which might not be everyones fastest storage etc

C:\Users\(USERNAME)\AppData\Local\WWE 2K25\PrebakeCache.bin

back in the days before i moved to NVME I did a linked folder to move that temp file to faster drive to fix things, helps enormously for creative tools etc loading times. This file is generated every time launch a match to load the resources (so safe to delete as will regenerate it every time play). The game also stores all the PSO shader cache there as well... so if C: is a sluggish drive that could be reason?

This is definitely not a shader cache issue. It's a set value for LODs by devs. It's issue on PS5 as well and other consoles.

not really bothered about consoles and their out of date hardware, they need to do stuff for performance on island mode lol, PC doesnt. If it's a real issue for you, report on a ticket and they will patch it, but for now, mines fine.

[Ja'Crispy]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von Ja'Crispy:

Okay , tbh it doesn’t bother me that much cuz I only notice the hair model looking really rough outside of entrances , it’s definitely a weird one

Starting to think this in more a cache issue as recall the previous games all have a 8gb floating cache file... something my gen4 NVME doesnt struggle with maybe? which always defaults to C: which might not be everyones fastest storage etc

C:\Users\(USERNAME)\AppData\Local\WWE 2K25\PrebakeCache.bin

back in the days before i moved to NVME I did a linked folder to move that temp file to faster drive to fix things, helps enormously for creative tools etc loading times. This file is generated every time launch a match to load the resources (so safe to delete as will regenerate it every time play). The game also stores all the PSO shader cache there as well... so if C: is a sluggish drive that could be reason?

I have a wd s850x gen 4 drive myself but I haven’t messed the file or anything , i have a 4080 and a 7800x3d atm so I’m good on that side of things

[JamappleKirk]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von JamappleKirk:

Would you be willing to post ingame screenshots of you not having this issue? posting tickets to 2k support is somthing we should all be doing yes, however I can see why people wouldn't bother as we normally get nothing passed a copy paste canned response from agents.

P.s I have a gen 4 NVME too and I'm getting the issue every single match.

is your C: drive for OS also on NVME gen4? or just the game install ? (i have 10 drives in my rig, so just helps to eliminate if the bin cache is causing this).

Ursprünglich geschrieben von Highway:

is your C: drive for OS also on NVME gen4? or just the game install ? (i have 10 drives in my rig, so just helps to eliminate if the bin cache

Both drives are WD sn850x 4th gen NVMe a 1tb and 4tb

[WestJake]

Ursprünglich geschrieben von Highway:

Ursprünglich geschrieben von WestJake:

This is definitely not a shader cache issue. It's a set value for LODs by devs. It's issue on PS5 as well and other consoles.

not really bothered about consoles and their out of date hardware, they need to do stuff for performance, PC doesnt. If it's a real issue for you, report on a ticket and they will patch it, but for now, mines fine.

I already did and you have the same problem as well, you just don't see it or don't want to see it. Unless you send a gameplay video with third person camera and Cody, I can't believe it's not present in your PC.

[Highway]

Ursprünglich geschrieben von Ja'Crispy:

Ursprünglich geschrieben von Highway:

Starting to think this in more a cache issue as recall the previous games all have a 8gb floating cache file... something my gen4 NVME doesnt struggle with maybe? which always defaults to C: which might not be everyones fastest storage etc

C:\Users\(USERNAME)\AppData\Local\WWE 2K25\PrebakeCache.bin

back in the days before i moved to NVME I did a linked folder to move that temp file to faster drive to fix things, helps enormously for creative tools etc loading times. This file is generated every time launch a match to load the resources (so safe to delete as will regenerate it every time play). The game also stores all the PSO shader cache there as well... so if C: is a sluggish drive that could be reason?

I have a wd s850x gen 4 drive myself but I haven’t messed the file or anything , i have a 4080 and a 7800x3d atm so I’m good on that side of things

well probably safe to say isnt hardware side issue there... are you also forcing on RebAR for all games? I do... bypassing the default mode on that.