A guess as to why we cannot download stadiums from 24 and 23
-
I recall the first few days after the pre-release of MLB 25 was made, one of our noteworthy stadium designers commented that he noticed the memory bite on the props was measurably larger than they were for MLB 24 and 23. I only dabbled in the latest SC for long enough to confirm no new props were added, and then left it cold. However, I did notice in that brief time that the textures appeared to change on the stand props. It was subtle, but noticeable.
Now, let's consider the reality that no self-respectable stadium designers creating works for MLB 24 and earlier are going to release a stadium that has memory meat left on the bone. Heck no! All stadium designers are going to use up every drop of memory available to create stadiums that looks as nice as can possibly be rendered.
So, if the lion's share of vault stadiums were created for MLB 24 and earlier consumed 99% of memory, and there is merely a two percent increase in memory consumption for the stand props, then by definition it means props as large as the stands would push the memory used for MLB 25 well over the 100% mark.
What happens when memory exceeds the limit? You are not allowed to save the stadium within your console and you are thereby not allowed to upload it to the vault. So, if a stadium that got in there now exceeds the memory cap, it isn't going to download and load into your console game experience.
Instead, it will most likely default itself right back to the stadium that originally occupied that one slot out of thirty, and that is precisely what folks are reporting. When they can actually get a stadium to download, then what they end up with is nothing more than the image of the custom stadium but when they try to load it in SC for additional editing, or play it in the game, they instead get the default stadium that occupied that save slot and doesn't exceed the memory cap.
To confirm this, I wonder if anyone who created a brand new stadium within MLB 25 and uploaded it to the vault would be kind enough to share that with the community here at Reddit and we can see if that stadium successfully downloads and plays. If it does, and we confirm it's only the legacy stadiums that are "the problem," and if that's the case, then I think we likely have the cause.
-
Then sds just needsto say that they can not be imported and delete all previously created stadiums from the vault
I started over, and now my stadium is 68%, and I can't finish it because of the save issue. Stadium Creator is not usable, at least for me. SDS owes its customers an explanation. A void of information is the real issue on both fronts: import and save issues. -
The nutzo thing is I created a so-called test stadium with minimal props just to test out my theory, and I saved it and then exited SC. Went in to upload it to the vault, and it wasn't there in my save slot! Like so many others have reported, what was there was the blank template stadium! LOL!!
-
@PriorFir4383355_XBL this would be owness on MLB the show developers to come out and comment on this.
They have not.
-
So pathetic that they haven’t even issued a “we’re working on it” response.
