-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Another World (The Company) freezes #842
Comments
Second issue solved (why does the demo continue when entering the debugger in RetroShell?). Here is the thing: I've entered the debugger by pressing Shift+Return. When RetroShell is open, all key events are intercepted and routed into the shell rather than the emulator. However, the interception check was missing for flag-changing keys such as Shift. As a result, pressing Shift+Return in RetroShell routed the Shift key into the Amiga (in addition to the shell). Pressing a key brings the CPU and Agnus a bit out of sync which lets the BTST instruction recognize VERTB and the demo continues. I bet something similar will happen on the real machine. Pressing a key is likely to continue the demo... |
Here's my attempt at a testcase: It uses this sequence before the btst loop to check various cycle "alignments" (d0)
With the vblank handler active the "stop" instruction should retire at the same point during the frame regardless of what happened before. The output is the number of times the VERT bit was observed outside the interrupt. You may find that vAmiga already matches for this test in which case it's just a subtle timing difference in the time it takes to reach the loop start (probably not worth trying to track down as you can see being even a single CCK off matters). |
This is a follow up from issue vAmigaWeb/vAmigaWeb#254 opened in the vAmigaWeb repo.
The demo TheCompany_AnotherWorld.hdf.zip freezes after a couple of seconds.
Regarding the first issue (why does the demo freeze), the following should be done first:
The second issue has to be tackled separately.
The text was updated successfully, but these errors were encountered: