- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
08928 | Crash/Freeze | Critical (emulation) | Always | 30 days ago | 29 days ago |
Tester | Hydreigon | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | Resolution | Open | OS | Windows 10/11 (64-bit) | |
Status [?] | Acknowledged | Driver | |||
Version | 0.270 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 08928: warfa and clones: In a linked operation, if one player challenges another player in singleplayer, the game freezes. | ||||
Description |
Most of networking in War: Final Assault works except attempting to challenge another player in single player to a deathmatch freezes the emulator that was in single player mode. This doesn't happen on hardware. |
||||
Steps To Reproduce |
This requires linking multiple instances of mame (single or multiple computers) with TAP adapters. For a detailed tutorial on how to do so, see here: https://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Board=news&Number=380959 1. Have mame #1 coin up and start a game in single player; wait till mame #1 goes ingame. 2. Have mame #2 coin up; this time, mame #2 will be given an option to either choose co-op or deathmatch. 3. Mame #2 chooses deathmatch 4. Mame #1 freezes; two possible results can happen with mame #2. 5a. Mame #2 immediately drops in deathmatch playing as nothing being able to look around but not move. 5b. Mame #2 freezes for a few seconds then drops in deathmatch with the other "player" not moving. |
||||
Additional Information | It's unlikely the network emulation isn't at fault here with this kind of behavior. Maybe a MIPS core bug? | ||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | warfa and clones | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
1
No.22348
Robbbert Senior Tester
29 days ago
|
Game is listed as fully working. I'm not in a position to verify this problem, so it's been acknowledged. |
---|