- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09532 | Gameplay | Major | Always | 2 days ago | 1 hour ago |
| Tester | CT92 | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Open | OS | Windows (x64) | |
| Status [?] | Acknowledged | Driver | |||
| Version | 0.288 | Fixed in Version | Build | x64 | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 09532: soulclbrjc and other (ver.c set): Kilik and Mina moveset not correct | ||||
| Description |
In verC versions, of all regions: - SOC11 (JAP) - SOC13 (USA) - SOC14 (KOR) The characters Kilik and Mina have incorrect movesets and entry (only Kilik) with wrong animations, wrong hitboxes, etc. That B or A2 do not have, i attach a video in which I show some of them In the video, a battle is performed using Mina, but the bugged moves are not present |
||||
| Steps To Reproduce |
1. Use official MAME 0.288 with a clean cfg/nvram. 2. Start one of the affected Ver.C sets: - soulclbrjc - soulclbruc - soulclbrac 3. Select Kilik or Mina 4. Perform the same moves shown in the attached Moveset.mp4. 5. Compare the result with SoulCalibur Ver.B/A2, where the same moves do not show the issue. 6. The same type of problem also appears to affect Seong Mi-na in Ver.C, likely because of related/shared move or animation data. Actual result: In Ver.C, Kilik and Seong Mi-na show incorrect moveset behavior, including wrong animations, wrong hitboxes and/or wrong move data. Expected result: The Ver.C sets should not show broken or mismatched moveset behavior if the real PCB/reference behavior is correct. |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | soulclbrjc and other (ver.c set) | ||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
4
|
No.24622
Robbbert Moderator
1 day ago
|
It's acknowledged. Not sure why you changed the version to 0.129 - I've changed it back to 0.288 as your text says that's the version you tested with. |
|---|---|
|
No.24623
CT92 Tester
12 hours ago
|
Thanks for the reply. I tested SoulCalibur on MAME 0.129 to check whether this was a recent regression or an old issue. The result is clear: the bug is already present in MAME 0.129. That means the Kilik / moveset / animation / command problem has been present since at least MAME 0.129. It is not caused by recent MAME changes, and it is not related to any external patching/frontend work. Confirmed: - MAME 0.129: bug present - Current MAME: bug present So this should be treated as a long-standing SoulCalibur VER.C / Namco System 12 emulation or data-mapping bug. Is there any possibility that this issue can be investigated and eventually corrected? |
|
No.24630
Robbbert Moderator
6 hours ago
|
If it was present in 0.129 then it's probably been there since it was added - whenever that was. According to mameinfo.dat, the first one was added in 0.77, with major work and renaming done in 0.142u2. As to getting it fixed, that's entirely up to the devs. No idea if or when one of them might become interested enough. |
|
No.24636
CT92 Tester
1 hour ago
|
Thank you, that is useful context. If the game was first added in 0.77 and the bug is already present in 0.129, then I agree: it may very well have been there from the beginning, or at least from very early in the driver history. I understand that getting it fixed is entirely up to the developers, and I also understand there is no guarantee or timeline. I do not want to put pressure on anyone. If any developer ever becomes interested in investigating this, I would be happy to help with testing. I can test specific MAME versions, including 0.77, 0.129, 0.142u2, and current builds, and provide short video comparisons or any other information that may help narrow the issue down. Also, if there is a proper and acceptable way to do this within the community, I would be willing to financially support or sponsor the investigation and fix. I am not trying to demand anything; I just want to make clear that this bug is important enough to me that I would support the work if someone is willing and able to take it on. Thanks again. |