Hyperlaunch HQ Module duplicate ID

[mcelveensc]

I did a search on google for this and found an old topic from 2013, but when clicking on it, it just takes me to the main forum :/

Im having trouble accessing MAME from the mainmenu in hyperspin as when i click on it it immediately exits out of hyperspin. It used to work fine until i believe i cleared a few systems from HyperHQ to declutter my setup a bit. I did this today, but I havent tried MAME specifically in a week or so, so im not sure if that was the culprit or not.

My hyperlaunch is setup to direct to the correct rom location and had a green dot, my emulator is also set to the correct directory. The only error i can find is when i go to the module itself, it displays an error indicating that it has duplicate idS and that i have to manually fix this. Unfortunately i dont know how.

Im at work right now so i dont have access to the log, but if its needed to help resolve this, i can post what its saying when i get home. The error the log displays is that it cannot find the roms.

Any help is greatly appreciated and hopefully ive provided enough information to get someone in the ballpark of whats happening.

Thanks!

Smuppy

[mcelveensc]

Okay, so the problem is elsewhere then. I assumed through duplicate module Ids that it was reading a duplicate (possibly with nothing in it) in the same place and assuming that there were no corresponding roms based on the duplicate. Hmm...Im sure this will most likely need a log to troubleshoot then.

 

My next question is how do I turn on or find the detailed log? The only log I see currently gives me very basic information and is located in the main directory.

 

Thanks,

 

Smuppy

[mcelveensc]

Great, Thanks Jeremy. I'll do that when I get home then. Is it an easy setting to find? What tab would I find that under?

[32assassin]

Im having trouble accessing MAME from the mainmenu in hyperspin as when i click on it it immediately exits out of hyperspin. 

 

 

 

you more than likely have some type of game filtering in HyperHQ, and don't have any of the parameters to support your game filtering method.

[mcelveensc]

Okay, so the culprit could potentially be HyperHQ. I'll start there then. I don't remember changing any of those settings, but I may have thinking I would get some sort of improvement.  Would something as simple as changing a setting such as CPU usage High from normal do something like that? I know I changed that setting, and possibly some others that just seemed like computer efficiency oriented options. I'm sure this is where the log will come in handy. I have been trying to run the emulators and hyper programs from a SSD while using the roms on a separate HDD. That may have something to do with it as well. 

[mcelveensc]

Issue resolved! Thanks for the guidance. Turns out that the roms location in hyperHQ was set to ..\ (triggering C:\) where the roms were in D:\

 

What's curious to me is that in the MAME wheel, the execution was radio buttoned selected to hyperlaunch.  When I scroll through the other wheels, all of my other emulators and roms are also radio button selected to hyperlaunch and have the ..\ directory pathway and give me no trouble. MAME is the first item in the main menu on startup, so perhaps that has something to do with it?

 

Anyway, thanks for the support and for helping me get this resolved.

 

Smuppy