Don't use Created stadiums for vs CPU...
-
The game always ends up crashing. I was just up something like 17-0 with a bunch of homeruns and several strikeouts with Ubaldo Jimenez in less than four innings. But I don't get credit for any of that due to the crash! I am 2 for 2 in having a vs CPU game crash within a few innings played.
-
There are reports that SDS performed operations on the existing props that may have increased their assigned memory consumptions. If that is indeed what they did, then it is possible that stadiums that worked just fine in MLB 24 may be causing issues in MLB 25. Unfortunately, if SC isn't improved, then I'm not working with SC any longer and so I cannot confirm the situation.
-
@PriorFir4383355_XBL I built this stadium in 25, because I couldn't download my other stadiums from previous years. So all my props (which were only a handful and about 60 % memory usage) are all from 25. Also, I do know that SDS removed that really small field that a lot of people liked to use. Now there isn't any little league type fields available.
-
Thanks for the clarification. Yes, it seems SDS has performed a myriad of little things to make using SC more of a headache than it's worth -- at least right now.
Zero new props added so far.
Zero changes to how the designer can setup the stadium -- still stuck with the jewel box and the bullpens on the field of play.
Memory creep.
Poor vault performance.
Custom stadiums causing CTD's.Hey! What's not to like about the latest and "greatest" version of Stadium Creator! LOL!!
-
Thanks for starting this thread. At least now I know it's not just me crashing using a created Stadium
-
@DivineFury75_PSN Were you playing in vs CPU or another mode with the created stadium?
-
@dap1234567890_PSN VS cpu
-
Something is really messed up with created stadiums. Most of the created ones I see state is has a seating
capacity of 50,000,000. Unless that's just my vault.
