libretro / vice-libretro

Versatile Commodore 8-bit Emulator
GNU General Public License v2.0
40 stars 70 forks source link

Vice PET only autostarts content with model 80XX #359

Closed cucholix closed 3 years ago

cucholix commented 3 years ago

Latest Vice PET core as 6-march 2021 only autostarts content when launched from playlist with 80XX models, other models need you input the command to start the game, it happened to me on Switch, but @sonninnos confirmed it happens on other platform. Worth noting that it doesn’t happen in standalone, not sure when exactly this bug start to happen or if it was always like that.

The 80XX model split the picture like this: D438877F-4663-4D05-9E10-3C8998CFA0C4(Breakout)

So most games are unplayable under 80XX.

By comparison 2031 model for example display the games correctly: 6D36845D-C8DC-404B-8CE6-3D9C61A95F2A

sonninnos commented 3 years ago

Looks like this issue will sort itself with 3.5, since 3.3 standalone actually suffers from it after all.

Replicated by changing the model via the menu and then trying to autostart via the menu. Autostart stops working after the model change reset.

Standalone starts straight up from the saved config, as in no reset required, but this core starts with the defaults, and then resets with the core options configuration. So something is simply not resetting properly.

cucholix commented 3 years ago

Tried with updated core, and the image still appears split with model 80XX

sonninnos commented 3 years ago

That is what model 80XX does.. This didn't fix that, because it can't be fixed. This fixed the non-default models autostarting properly.

cucholix commented 3 years ago

2031 model doesn’t autostart on my end

sonninnos commented 3 years ago

Works fine here on all models, and there is no model 2031.

cucholix commented 3 years ago

Tried with every model available, and only 80XX autostart, but has the split screen issue

sonninnos commented 3 years ago

Log might make things clearer, as usual.

cucholix commented 3 years ago

Was preparing the log for you and it happens now works hah. Maybe it didn't updated properly :)