You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you start a new emulator session and select Disk/Tape in the settings the emulator crashes.
Also randomly happens when you Load Disks and then click Done and attempt to run a Program or switch to a new program via Done when one was last running.
This happened once when I pressed the on-screen keyboard in portrait, changed to landscape and back to portrait again.
This and the other issues I reported tonight are all low priority, I just thought you should be aware of them.
The text was updated successfully, but these errors were encountered:
This appears to be if you quit the emulator before its done initialising (i.e. before the C64 screen appears). The crash is deep in the bowels of Vice and is caused by an AudioQueue error. No idea why yet though.
I'll look to see if I can workaround this in someway but for the moment, if you wait until the emulator screen appears then this should stop the crash
Okay, that kinda makes sense because it was also doing when I accidntally pressed "Load Disk", and would crash upon my correction.
FYI - As there appears to be no suggestions area, I'll give one here. My biggest suggestion would be to enable two player play. Either using a controller pad or another iOS device as a controller for a joystick port with or without screen sharing and sound. This would take this emulator to the next level big time! Second suggestion is having an alternative on-screen joystick with "left and right" on the left and "up, down and fire" on the right because in some games its hard to jump (using "up") whilst walking.
When you start a new emulator session and select Disk/Tape in the settings the emulator crashes.
Also randomly happens when you Load Disks and then click Done and attempt to run a Program or switch to a new program via Done when one was last running.
This happened once when I pressed the on-screen keyboard in portrait, changed to landscape and back to portrait again.
This and the other issues I reported tonight are all low priority, I just thought you should be aware of them.
The text was updated successfully, but these errors were encountered: