| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 08387 | Crash/Freeze | Critical (emulation) | Always | Jul 30, 2022, 18:34 | Aug 1, 2022, 18:50 |
| Tester | Hydreigon | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Open | OS | Windows 10/11 (64-bit) | |
| Status [?] | Acknowledged | Driver | |||
| Version | 0.245 | Fixed in Version | Build | 64-bit | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 08387: vaportrx, calspeed, hyprdriv, sfrush, sfrushrk: Game freezes under certain circumstances | ||||
| Description | These games have a moderate chance of freezing when you either enter and exit test mode or go into network test. | ||||
| Steps To Reproduce |
Enter and exit test mode (or alternatively enter network test). May take a few tries until the freeze occurs. The circumstances for freezing may increase if one plays starts/finishes a game and then does the above steps to reproduce. |
||||
| Additional Information |
For calspeed, the 'exit test mode freeze' won't occur if the unit number is set to 'Unassigned' but entering network test still has a chance to freeze. This freeze seems to be network related for the following reasons: - calspeed and vaportrx if exiting test mode would freeze on the message initializing the network. - The freeze never occured in 0.233 and happened when smc91c96 got updated to be used with LANceGS card (this would fix cartfury and hyprdriv not talking to each other at all). I recall it was much worse in 0.234 with freezes and hangs happening more often. |
||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | 0.234 | ||||
| Affected Sets / Systems | vaportrx, calspeed, hyprdriv, sfrush, sfrushrk | ||||
|
Attached Files
|
 vaportrx.png (1,849 bytes) Jul 30, 2022, 18:34 Uploaded by Hydreigon | ||||
| calspeed.png (2,334 bytes) Jul 30, 2022, 18:34 Uploaded by Hydreigon | |||||