Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06734 Interface Minor Always Oct 25, 2017, 22:02 Oct 31, 2017, 04:38
Tester Zaghadka View Status Public Platform MAME (Official Binary)
Assigned To Resolution Unable to reproduce OS Windows 10 (64-bit)
Status [?] Closed Driver
Version 0.191 Fixed in Version Build 64-bit
Summary 06734: ROMs return to "available" list when launching a Genesis game with "Hide romless" set to on.
Description When you launch a Genesis game from the "unavailable" tab, all the romless sets return to the "available" list upon return to the UI.
Steps To Reproduce Make sure "hide romless sets" option is on.

Launch MAME. Click on the "Unavailable" tab. Note machines and sets shown.

Double-click on "Genesis (USA, NTSC)" in the "Unavailable" folder, double-click on any software item. Press escape to return to the UI after the cartridge has run.

Upon return to the interface, "Unavailable" is now empty, and "Genesis (USA, NTSC)" can be found in the "Available" folder. I am finding that it deposits the caret at a random folder. I have been returned to "Available," "Working," and "Unavailable."
Additional Information Using Windows 10 Fall Creators, v1709, patch level 16299.19.
Regression Version 0.191
Affected Sets / Systems
Attached Files
? file icon genesis.ini (10,614 bytes) Oct 30, 2017, 13:03 Uploaded by Zaghadka
[Show Content]
There are no relationship linked to this issue.
User avatar
Oct 25, 2017, 22:13
Just tried launching a software set from Atari 2600 (PAL) and Atari 800XL (PAL).

When launching a set from those machines, the machines stay "Unavailable" on return to the GUI.

So far, only launching a Genesis (NTSC) software set repairs the "Unavailable" and "Available" folders.
User avatar
Oct 26, 2017, 00:07
edited on: Oct 26, 2017, 00:07
Do you have Configure Options > Miscellaneous Options > Hide romless machine from available list set to OFF?

If not, please do. It will make make them not 'hide' so they will show up. It is On be default as most people only wanted to see what they had romsets for. All romsets which do not require and unique romset, or are 100% clones of another and have no unique roms are now shown, including the machines you've mentioned. It doesn't check that you have software, it only checks the romsets required to start the emulation.
User avatar
Oct 26, 2017, 17:24
edited on: Oct 26, 2017, 17:28
Okay, and Genesis (USA, NTSC) is a romless set even though it shows up as the parent.

Edited to reflect the movement of all romless to "available" when done launching a Genesis game. Can you confirm this behavior?
User avatar
Oct 29, 2017, 16:55
edited on: Oct 30, 2017, 11:05
I've tried seeing what happens to you happens to me.. it doesn't. When I exit a game run through the UI for Genesis, it brought me back to Unavailable listing - right where I was before I launched the system and chose the softlist item to run.

Can you duplicate this one in a completely clean install environment? I can't discount the fact that a stray setting in an .ini or .cfg file might be interfering with things.
User avatar
Oct 30, 2017, 12:53
Tried a clean install. The behavior doesn't happen with a clean install on my end either.

Clean install was: mame64.exe, a roms folder with "megadriv" in it, the hash directory, the plugins directory, and a "mame64 -cc" generated set of INI files.

I'll have to see what it is about my particular install that causes the behavior. This will probably take a while, but I'll see if I can't pin it down.

Incidentally, on a *very* minor note, Mega Drive (Europe, PAL) is what shows up in the available list when "hide romless" is set to on. This is marked as a clone, however. It might be better to mark that as the parent and Genesis (USA, NTSC) as a clone if that is the behavior going forward. Right now, Genesis (USA, NTSC) shows up as the parent in the UI.
User avatar
Oct 30, 2017, 13:02
edited on: Oct 30, 2017, 13:04
Didn't take long at all to pin it down. It was the genesis.ini file I was using. When I replaced it with a clean file, the problem went away.

I'm posting the ini file to see if it replicates on your end. If it does, I'll look through it setting by setting to see what's causing the problem.

(I should note that I believe this file was probably generated by mameui64 at some point, so it is unlikely anyone else will get to the precise state I'm in with vanilla mame.)
User avatar
Oct 31, 2017, 00:17
So is this still an issue? Or can we close it?
User avatar
Oct 31, 2017, 04:38
Can't repo it here so I'll close it.