More often than not, both the Windows 11 (Home) and Web (Chrome stable, latest) versions of Apple2TS (latest revision) "crash" in a specific way during gameplay, using any of the Airheart disk images I've tried (i.e. local copy on HD, or pointed at on Internet Archive), leading me to suspect it's something more fundamental to Apple2TS than anything about the ROM being played.
Steps to reproduce include starting Apple2TS, setting speed to 1MHz, then loading Airheart.woz into S1D1 and playing the game. Within 1 or 2 minutes, gameplay will freeze and a "garbled" static
screen shown (see screenshot linked below). It is still possible to ESC out of full-screen and fiddle with Apple2TS UI controls, however.
No error is thrown, and I'm unfamiliar with debugging in this context, so have no additional details to share, sorry.
(Graphic would not upload despite repeated attempts, so here's the link instead)
Screenshot - https://drive.google.com/file/d/11zp_hVDvTOeWW3fnxK4VWyOk_6Q6L4eb/view?usp=sharing
More often than not, both the Windows 11 (Home) and Web (Chrome stable, latest) versions of Apple2TS (latest revision) "crash" in a specific way during gameplay, using any of the Airheart disk images I've tried (i.e. local copy on HD, or pointed at on Internet Archive), leading me to suspect it's something more fundamental to Apple2TS than anything about the ROM being played.
Steps to reproduce include starting Apple2TS, setting speed to 1MHz, then loading Airheart.woz into S1D1 and playing the game. Within 1 or 2 minutes, gameplay will freeze and a "garbled" static
screen shown (see screenshot linked below). It is still possible to ESC out of full-screen and fiddle with Apple2TS UI controls, however.
No error is thrown, and I'm unfamiliar with debugging in this context, so have no additional details to share, sorry.
(Graphic would not upload despite repeated attempts, so here's the link instead)
Screenshot - https://drive.google.com/file/d/11zp_hVDvTOeWW3fnxK4VWyOk_6Q6L4eb/view?usp=sharing