This SFF load problem

[Krypto 'SAM' saiyaN]

Click the spoiler to see the problem.

Error detected.

Cannot find parameter: nameCan't load Custom_SSFIV_Oni.sff
Error loading chars/SSFIV_Oni/SSFIV_Oni.def
Error loading p1

Clipboard tail:
Versus screen init
End of versus screen loop
Game loop deinit
Gameflow 11
Loading match assets...
Loading stage...
  Loading BG...OK
Stage loaded OK
  Allocating helpers...OK
Match RNG seed: 2075607641
Reset persist vars team 0
Reset persist vars team 1
Loading character chars/SSFIV_Oni/SSFIV_Oni.def...
  Loading info...OK
  Loading cmd command set Custom_SSFIV_Oni.cmd...OK
  Loading cns Custom_SSFIV_Oni.cns...OK
  Loading cns Custom_SSFIV_Oni_normal_chains.cns...OK
  Loading cmd state entry Custom_SSFIV_Oni.cmd...OK
  Loading common states common1.cns...OK
  Loading sff Custom_SSFIV_Oni.sff...Character SSFIV_Oni.def failed to load

 

So, why this is happen actually? This one of the example, happen when using mugen 1.1. How to solve it?
 

[NotAGoodName]

Mugen is bad at managing its own RAM usage and will happily run out for some reason.  There's not any actual solution that I know of.  PlayerCache = 0 seems to delay it, but "seems" is probably the key word.  It's just one of those things.

[Ryon]

it cant find parameter "name"

 

strange issue, I think I had a issue as well loading up Oni.

[Alex S.]

Sometimes it happens to me too, it's like it says: "hey, I'm not loading all of this stuff this time" and quits. Probably because it's heavy. It happens also with Cody or Gouken by Orbinaut, who are heavy characters; and with heavy stages too.

 

But this happens to me in 1.0. I think it's for the same reason though.

[Krypto 'SAM' saiyaN]

Yea, it usually happen when choose the character along with some heavy stages too. But it only happen in 1.1. For me, i can open all this heavy chars/stages on mugen 1.0 without any problem. Is this has anything to do with mugen 1.1 is still a beta?

[NotAGoodName]

No.  I had this happen all the time on 1.0, too.  Mugen just doesn't flush after itself very well.  If you check your error log, it probably stopped on something like releasing resources.  If I had to guess, I would say that Mugen tries to load new resources at the same time that it tries to release old ones.  Obviously, when the math doesn't work out, this happens.  Not surprisingly when you're dealing with SFFs that are >100MB.

[Krypto 'SAM' saiyaN]

Not surprisingly when you're dealing with SFFs that are >100MB.

Yea, it always happen when the sff file was near 100mb or more. This is my first time encounter with this problem after i'm using 1.1. I never had this problem before when i'm using 1.0 and winmugen.