| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 03790 | Crash/Freeze | Critical (emulator) | Always | Mar 20, 2010, 20:27 | Jan 12, 2018, 04:20 |
| Tester | NekoEd | View Status | Public | Platform | SDLMAME |
| Assigned To | Kale | Resolution | Fixed | OS | Linux |
| Status [?] | Resolved | Driver | |||
| Version | 0.137 | Fixed in Version | 0.194 | Build | Normal |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 03790: gratia, gratiaa: unhandled priority type f8 | ||||
| Description | When the purple mech says to "follow me" and your character transforms and does so, MAME will exit with the exception "unhandled priority type f8". | ||||
| Steps To Reproduce | Play through the game until you beat the boss that is a large circular thing with a shiny center. Destroy the yellow pylons around it then wait. The background will change to red sky, then MAME will error our shortly thereafter. | ||||
| Additional Information | Savestate attached is right as the "GRATIA" boss is being destroyed. The graphics look bad due to the savestate but it works as intended, just let it go through the score tally then it will error out soon afterwards. | ||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | gratia, gratiaa | ||||
|
Attached Files
|
 gratia.zip (33,872 bytes) Mar 21, 2010, 01:42 | ||||
 No.05897
Tafoid Administrator
Mar 21, 2010, 00:46
|
I ask for an .INP or a save state before the incident, please. |
|---|---|
 No.05901
NekoEd Senior Tester
Mar 21, 2010, 01:44
|
Savestate added. I hope that's all, because I'm really sick of this game now, heh. ;] |
|
No.05902
Tafoid Administrator
Mar 21, 2010, 01:50
|
Confirmed with state provided, albeit minimalist reload of the graphics. |
 No.05904
Haze Senior Tester
Mar 21, 2010, 12:49
|
Interesting.. hopefully it's another test case for m32 priority, although, gratia writes some garbage values during other cutscenes, so it could be useless.... I wish the system made more sense than having to hardcode the modes based on a table. |
 No.09235
haynor666 Tester
Jan 12, 2013, 14:30
|
Might be caused by bad dump ? |
|
No.09236
Haze Senior Tester
Jan 12, 2013, 17:27
edited on: Jan 12, 2013, 17:27
|
it's caused by an unhandled priority case in the video code. not that all the ones we already have are correct. garbage values during blank scenes can happen, you'd never notice on real hw. |
|
No.14643
Osso Moderator
Jan 10, 2018, 10:26
|
Couldn't get it to crash with 0.193. Granted, I used cheat codes to get there. |
 No.14654
Kale Developer
Jan 12, 2018, 04:20
|
It's the ending screen fyi (following are fixed screens): http://mamedev.emulab.it/kale/fast/files/0025_8483438706.png http://mamedev.emulab.it/kale/fast/files/0026_924932467.png |