I'm not sure this will help, but make sure you only list the rom folder in you AM emulator file. Then go to mame.ini in your mame directory and list the CHD folder in there (under "rompath") so Mame is able to run the CHD when AM boots the rom (zip) file.

Thanks for the reply. I tried to add the specific "kinst" chd directory in the mame.ini as you suggested but that didn't change anything.

I did a bit more digging though. It seems that it is reading catver.ini (which contains only the raw rom title and the genre), but it's failing to read the Attract Mode romlist/mame.txt file (which contains the full title, manufacturer, release year and number of players.

The strangest thing is that all of my other roms and chds are displaying perfectly in the favourite folder. This just doesn't make any sense.

For your Mame.cfg, make sure the catver and mame.xml's are listed under "import extras". (i'm assuming you already have an xml generated.) Under "rompath" make sure you list the rompath and not the CHD path. In other words it should only point to the folder holding kinst.zip, kinst2.zip. Only the chd's that do not have a zip that goes along with it should be included here. For example, I have xiistag pointed to because for that particular game, there is no xiistag.zip rom files.

For your Mame.ini (or whatever config file GM uses), make sure you list all the rompaths meaning both the CHD path and rom zip paths. You need to do this because you did not associate it in AM's config file. So if AM boots kinst.zip, then Mame will say the CHD is missing. You put it here so Mame knows to boot it along with the zip.

Whoops sorry about that. I have no idea how I missed that part regarding the favourites. Anyways I tested it out again in favourites and it's still displaying correctly for me. Here's a screen: https://i.imgur.com/FBzYMQy.jpg

Regarding the XML i believe it's for generating the mame.txt, but I could be wrong.

I'm 100% sure the data for displaying the title is inside that mame.txt. But if you a) looked inside the txt file and it looks correct and b) it displays fine in unfiltered, then it surely isn't the mame.txt. But just in case I would delete your mame.txt and since you have the XML now, you can point to it in your cfg, then go to the mame emulator configuration screen and re-generate the romlist.

And if that doesn't work then one must assume the problem is associated to filtering. But I would have no idea how to diagnose that.

If you can boot the game then no need to mess around with it. I was only trying to say don't associate both the zip and chd files in your cfg. Otherwise, when you generate, you will have 2 instances of the same game.