Tafoid wrote: ↑Thu Dec 19, 2019 7:20 pmYou have to be able to duplicate it with the same version, with a fresh save state. If that save state was used with another version - even a Git WIP binary build, such fitness isn't guaranteed. That said, I tried a couple tests with blktiger set using -autosave. I tried booting to title, exiting and restarting MAME, entered a credit, exited and restarted again and even credited again, started, played a game and upon game over, I tried exit/restart with -autosave again and I had no issue entering a coin or starting the game.
Can you try in a clean environment to duplicate - using only released binary and see if it repeats?
Tafoid wrote: ↑Fri Dec 20, 2019 11:19 pmWell, it is comforting to know it works with baseline, but I have no idea why or what would cause a Ubuntu built binary release to not function properly. It is entirely possible the save state got corrupted along the way or that you original saved with 0.215 or earlier and enough changed during Dev of 0.216 to muck something up.
I assume you have also tried a fresh install with that in Ubuntu as well with a fresh (no) save state to try to duplicate? I can't help thinking there may be some configuration issue somewhere or (as mentioned earlier) save state corruption.
Users browsing this forum: No registered users and 3 guests