运行mugen出现错误

[qianmozhongheng]

运行一些pc端的mugen游戏

出现此错误

[CaptainDreamcast]

Strange that it's throwing that assert like that, it should show an error screen instead. Does this happen with all characters/stages, or just specific ones? Does it work with the default assets folder? If it's just specific characters/stages, could I get a link to them so I could take a look? Thanks!

[qianmozhongheng]

Strange that it's throwing that assert like that, it should show an error screen instead. Does this happen with all characters/stages, or just specific ones? Does it work with the default assets folder? If it's just specific characters/stages, could I get a link to them so I could take a look? Thanks!

this is game link: https://juegosdemugen.com/en/melty-blood-mugen-2

[CaptainDreamcast]

I'll check it out and will let you know what I find, thanks a lot!

[CaptainDreamcast]

I took a look at the game files, there were a lot of things going wrong, but most of them can be worked around and will be fixed for later Dolmexica versions:

1. The font crash
   This is probably the one that caused the message from your original post to pop up. Dolmexica crashed when trying to load the base font that it uses for all its system stuff, including the error screen. So there was no chance to show an error screen in the first place, leading to that awkward crash message. Currently Dolmexica expects a font at font/f4x6.fnt . Regular mugen and the game you linked have a font at font/f-4x6.fnt, but certain CD filesystems struggle with minuses, so I took out the minus for the Dreamcast support. But now this means game files won't work unless you add that font back in manually. Whoops.
   Workaround: Copying the font/f-4x6.fnt and renaming the copy to font/f4x6.fnt.
   Fix for next release: Dolmexica will also check for font/f-4x6.fnt if it can't find font/f4x6.fnt. If neither can be found, it will use the first font in the system.def as its system font.

2. ArtoriaAlter (and others?) lack displayname parameter
   Dolmexica expected characters to have a displayname parameter in their main .def file. ArtoriaAlter apparently did not have that and that made it crash.
   Workaround: Adding the displayname parameter for characters that do not have it in their .def file.
   Fix for next release: Dolmexica will use the name parameter as a displayname fallback if there is no displayname parameter.

3. Ryougi_Shiki palette paths are broken
   They are the wrong relative paths. Dolmexica could not cope and crashed when trying to load one of the palettes.
   Workaround: Fix the palette paths in the main character.def E.g. "Pal1 = Palette/01.act" -> "Pal1 = Ryougi_Shiki/Palette/01.act"
   Fix for next release: Dolmexica will ignore palette files it cannot find.

4. Stage paths in select.def had backslashes instead of forward slashes
   This caused the sprite file search relative to the stage definition file to break for them.
   Workaround: Turn backward slashes \ to forward slashes / in the select.def.
   Fix for next release: Backward slashes in stages will be parsed and treated as forward slashes.

5. Sprites of characters were solid black
   This was about Mugen 1.1 files with PNG files in them. Problem was that the PNG was a paletted PNG, which Dolmexica technically supports, but there was a caveat. When reading paletted PNGs, Dolmexica does not read its raw 8-bit palette data, but instead tries to apply the palette stored inside the PNG. This was not what the characters here expected, they wanted the raw indices read from the PNG and the SFF palettes applied to those. So with that, the characters show up properly. Still have to test that with a couple other characters though, want to make sure this didn't break any other sff files.
   Workaround: Re-save the sprite .sff file in the Mugen Beta format instead of 1.1 to make them work (palettes work there). You could do this with Fighter Factory 3 for example.
   Fix for next release: The fix mentioned above, reading the raw indices from paletted PNGs with bit depth 8.

6. hires parameter in stages means something different in Dolmexica
   Stages in the Melty mod have hires parameters to mean a 1280x720 coordinate system, might be a Mugen 1.0+ thing, I thought that in the original Winmugen, hires = 1 meant 640x480, so I'd like to keep it that way.
   Workaround: Setting localcoord=1280,720 directly instead of hires = 1 in the stage .def file should fix this.
   Fix for next release: I'd like to keep hires to mean 480p, so this will stay the same and I'll have to chalk it up to Mugen version differences unfortunately. The workaround should work though.

7. Fight motifs (lifebars) are completely broken, due to being in a too high resolution.
   I explained it in the Dolmexica bug thread recently, but due to how the system works right now, Dolmexica only supports lifebars in 240p by default, or in 480p if it is saved under data/480p. The lifebar included in the game seems to be too large, and for now would have to be exchanged.
   Workaround: No good workaround unfortunately. For now I'd ask to use 480p life bars in data/480p or 240p life bars in the regular data folder or other subfolders.
   Fix: This is so fundamentally broken and as far as I know, there is no good way to distinguish between life bar coordinate systems. I'll have to think of something. For now I can't promise a fix any time soon unfortunately.

8. Crash in Fate Stay Night.def stage
   This was due to how Dolmexica handles duplicate mugen script groups, it adds a number to duplicates to distinguish them, but this crashed here, because [Name 1] was declared before three [Name] groups, leading to the third one to become [Name 1] and crashing.
   Workaround: Rename [BG POLVO 3] and [BG POLVO 2] to [BG POLVO] respectively inside the .def file.
   Fix for next release: I'll switch up the group name renaming a bit to make these collisions even less likely (although I think this was pretty rare to begin with).

I think that was everything I found. Some more minor issues (graphics drawn at the wrong part of the screen stuff like that), probably due to errors in the way Dolmexica handles controllers and triggers, but I'd fix those as I go. I think smaller errors like those are going to be around unfortunately, but I hope it gets closer to real Mugen over time.

Thanks a lot again for taking the time to share the crash and the files with me! Hope I can get the fixes out soon and if all else fails that the workarounds can help out!