Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
So to clarify: you're confirming firsthand (as in you've actually experienced this) that if you download enough CAWs then, like last year, eventually load times become progressively long until finally it just fails to load and stops responding or crashes again unless you delete some of them? (That's how it was last year.) If so, can I ask: does the issue from last year where eventually if you have too many things like images on CAWs and arenas just start disappearing during matches too?
While this undeniably helps, those issues were present last year irrespective of having a good NVMe. The issue simply took longer to become apparent cumulatively or required more downloads. It would still manifest before reaching the CAW slot cap. And would entail stability issues beyond simply slow loading. This was a software engineering issue on the game's end and not hardware dependent, merely hardware limitable. It was essentially the very same soft cap issue that 2K19 suffered from (a legacy codebase issue.) I'm trying to ascertain from people whether that's improved or eliminated this year or not.
but i got the standard edition so i cant test for myself yet but will make a followup comment when i do.
Bear in mind that the issue as it manifested last year was also dependent on what we downloaded, not just how many. E.g. 50 CAWs with max layers and tons of custom images and a ton of created arenas that were also highly detailed and full of images, could cause more problems than 100 simpler CAWs with few images and layers. So factor that in when testing.
Yes, this is why I mentioned earlier that having an NVMe didn't resolve the issue for some. It certainly helped, but several people I knew still had 20+ minute loads for 8 CAW matches in custom arenas.
I'm really hoping this has been substantially improved this year. Thus far reports are mixed, and the game likely isn't available to enough players yet (most don't do early access presumably) to truly see enough reports to get an idea.
you can check my yt to see the detailed caws im tallkig about https://www.youtube.com/watch?v=h7f2TW_HLr8&t=6830s
No doubt. It was a very difficult to quantify issue. Likely some specific combination of community creations caused it which, needless to say, means a ton of variability and difficulty in resolving the problem. All I can with certainty is that it happened across a large crossection of hardware configurations, including for people with more than adequate RAM and excellent NVMe's, as well as (most tellingly imo) on console where there's total hardware consistency from a QA standpoint. And that the only solution for those suffering from it was to delete a sufficient number of CAWs, arenas, and images.
And sadly this appears to be true this year as well. I'm seeing it from a lot of people. I'm hoping it's at least reduced, but that it's happening at all is disappointing. This is an issue that has been present in the series since 2K19. I won't buy these games until it's eliminated, if it can be. As I'm a heavy CAW user and that's the primary reason I play these games. CAW and Universe.