Jump to content

Error When Opening ROMS


BettyW

Recommended Posts

I have followed the setup guide here https://gameroomsolutions.com/setup-hyperspin-mame-hyperlaunch-full-guide/ exactly as described in the article.

 

I can see the Wheel and the selected systems I click HyperSpin.exe. I have removed the systems that I don't use and ONLY have Nintendo, Super Nintendo, Nintendo 64 and MAME.

 

When I wheel down to Nintendo and open any game it shows the following error. It does the same for Super Nintendo and Nintendo 64.

 

post-100090-0-84315300-1456509853_thumb.jpg

 

If I run the ROM from the RocketLaunchUI.exe I get the following error when running Nintendo ROMS

 

post-100090-0-10164900-1456509581_thumb.jpg

 

I click "OK" and the game opens.
 

When I attempt to launch a Super Nintendo or Nintenod 64 from within RocketLaunchUI and open any game it opens and then immediately closes. I can see a black screen and "Loading" but it quickly flashes closed.

 

I'm running MAME .171b but I've also tried .170 and .166 with the same results.

 

My goal is to have Nintendo, Super Nintendo and Nintendo 64 as the only 3 options on the HyperSpin wheel but use MAME as the emulator.  So far, I haven't had any luck.

 

Here's my wheel.

post-100090-0-02399400-1456509971_thumb.jpg

Link to comment
Share on other sites

 

attachicon.gifini.JPG

 

 

 

Your Hyperspin settings ini is not configured,  Hyperspin is not finding Rocketlauncher and is defaulting to using Hyperlaunch 2.

You will need to use a more up to date tutorial; their are other paths you need to add to RL.

 

 

 

 

 

attachicon.gifVideo.JPG

 

this has nothing to do with Rocketlauncher,  Hyperlaunch,  or Hyperpsin.   

 

Not all roms  are emulated at a 100%  accuracy,    this is a disclaimer telling you that their is something wrong with how the game plays in the emulator.

Link to comment
Share on other sites

Within RocketLauncher it indicates MAME .166 ahk file. Do I need to stick with MAME .166 or can I use the updated version.

 

Watching Simple Austin regarding setting up MAME with HyperSpin he states that MAME is version dependent. https://youtu.be/P30C0KI-neM?t=529 (this is almost 1 year old so I'm sure how viable the content is). 

 

Can I put the MAME Emulator folder on the root of the drive or does it need to be installed under C:\HypserSpin\Emulators?

Link to comment
Share on other sites

At some point Austin should show you how to update all your modules in the Rocketlauncher folder.

 

 

 

the emulator has been updated but the launch and exit procedures have not changed

thier has been no need to update the module this is why

the Module may indicate it is for version 166 but it still works with the latest version of MAME

Link to comment
Share on other sites

Everything is setup as the video (except I have it on C: and not external E:). Now from within HyperSpin MAME and NES fames don't give me that ini issues.

 

post-100090-0-52664800-1456519546_thumb.jpg

 

NES and MAME games work but I'm still having issues with SNES and N64. They won't even launch from RLUI.

 

I have attached the troubleshooting log in an effort that someone can tell me what I've done wrong.

Troublshooting.txt

Link to comment
Share on other sites

Further troubleshooting determined that I'm not able to run the ROM even with just running it from MAME (.171 - 64 bit).

 

Looks like I'm missing some files.

post-100090-0-76333600-1456523188_thumb.jpg

 

I'm going to try the 32 bit version and see if that helps.

 

I'm running Windows 7 Ult - 64 Bit.

Link to comment
Share on other sites

Thank you.

 

This is my first rodeo when it comes to MAME, RL and HyperSpin.

 

I'm modifying a Cocktail PacMan table to play Nintendo, Super Nintendo and N64 games. I was told that MAME is the way to go, but I'm finding it troublesome to say the least.

 

Perhaps I should try retroarch since Simple Austin has a walk through. 

Link to comment
Share on other sites

MAME = Multiple Arcade Machine Emulator

 

as the name says MAME only emulates (coin) arcade games.

 

their is an emulator called MESS, that emulates multiple home systems.

 

at some point the two emulators where merged into one,  MAME is the way to go for Arcade systems but its very troublesome to configure the MAME version with the home consoles.

Link to comment
Share on other sites

I have MAME running consoles in my setup and I'm pretty sure the only thing I had to do was set the bios path in the module settings.

Can it run NES, Snes, Super Gameboy and Wonderswan? And can it do it with the same shaders I can run in MAMEUIFX?

I need to setup 2 SNES games, 1 NES game, 1 Super Gameboy game (if it will play a BW game in color) and 1 Wonderswan game to finish my Ghosts'n Ghouls'n Goblins'n Gargoyles wheel.

I dread having to waste a bunch of time with multiple emulators, but I also don't want to use RetroArch unless I absolutely have to.

Link to comment
Share on other sites

I know it can run nes, snes, and wonderswan. Never tried running superGB. And yes, it can use shaders from uifx. I'm running the CRT Geom HQ from uifx that Sub and I modified.

Thanks. Sounds like that's the way for me to go then.

Just need to find a Mess tutorial and figure out how to get it sorted.

Link to comment
Share on other sites

MAME/MESS developers don't care whether you can play a game or not. If you can play, they consider it a "nice side effect" in their mission to perfectly emulate gaming hardware, down to the smallest chip or pcb. They will even break an entire system if it gets them closer to emulating that system in the way the original hardware did. I think you should be treated better than that.

 

NES, SNES, and N64 are either listed on the MAME/MESS website as (red) Preliminary aka broken or (yellow) Working but imperfect. It's a crap shoot. Since MAME/MESS is not the "preferred" emulator for any of these systems, if I were you I would choose a different way of running them. Emulators that care more about play-ability. Willing to use a plug-in system or hacks if necessary to overcome differences in hardware that aren't perfect yet.

 

To increase the difficulty of running these games with MAME/MESS, the names of the roms that the emulator expects to find is now hard encoded into the combined MAME/MESS. Phulshof also said there are also issues with specifications for memory addressing for certain systems. That is probably what the error popup in Post# 9 was about. This issue is covered by downloading (or using CLRMAMEPro to convert) "Software List" compliant roms. You can see that these are now listed separately on the PD website. "Software List" Roms for tape/floppy/cartridge based consoles. "Software List" CHDs for disc based consoles. [Plain] Roms and CHDs for arcade systems. Since MAME/MESS is looking for those specifically named roms to be loaded, you will also need "Software List" HyperSpin XMLs and rename artwork, themes, wheels, etc. to match. Avoid all of this. Do not download the "Software List" sets, at least for now.

 

Better to just find a more standard way of running those systems. Forget about the "Software List" stuff on PD. Keep MAME for your arcade systems, of course (split rom set/merged CHDs). Best to match your version of roms with the MAME version.  Also, a "no-nag" version of the emulator may help you avoid the popup in Post# 1 about imperfect emulation.

 

Good luck.

Link to comment
Share on other sites

Well... you just convinced me not to use MESS.

However I also don't want to use RetroArch. So that leaves individual emulators, so now I need to decide if I even want to mess with the pain in the ass of setting up 4 or 5 different emulators for only 1 or 2 games each.

I think I'd just rather not finish the project and delete the wheel at that point.

Link to comment
Share on other sites

I use MESS for almost all older systems. For NES, SNES, Genesis, etc. I've hardly encountered any serious issues; just a few games with hickups. For MSX, C64 etc. you should stick to using software list names though; that's why my WIP MSX set uses MAME naming for everything including art.

Sent from my SM-G920F using Tapatalk

Link to comment
Share on other sites

Can it run NES, Snes, Super Gameboy and Wonderswan? And can it do it with the same shaders I can run in MAMEUIFX?

I need to setup 2 SNES games, 1 NES game, 1 Super Gameboy game (if it will play a BW game in color) and 1 Wonderswan game to finish my Ghosts'n Ghouls'n Goblins'n Gargoyles wheel.

I dread having to waste a bunch of time with multiple emulators, but I also don't want to use RetroArch unless I absolutely have to.

 

Have you looked at mednafen? Doesn't support Super Gameboy, but not a lot of emulators do. Does use shaders.

Link to comment
Share on other sites

Phulshof, since the OP is new to HyperSpin, wouldn't it be better to steer to a more standard method (at least for now)? All that renaming and unofficial XMLs alone. Also, OP appears to have multiple issues to resolve first. May not be easy for the uninitiated.

Link to comment
Share on other sites

Phulshof, since the OP is new to HyperSpin, wouldn't it be better to steer to a more standard method (at least for now)? All that renaming and unofficial XMLs alone. Also, OP appears to have multiple issues to resolve first. May not be easy for the uninitiated.

If he just wants NES, SNES, GB, etc. MAME should work fine with the standard HS roms and naming. It's just for home computers that I'd recommend sticking to the software lists.

Also, MAME should not be used for N64+ unless you have a super fast computer. N64 on MAME is agonisingly slow.

Sent from my SM-G920F using Tapatalk

Link to comment
Share on other sites

Ok, great. And thanks again for all the XML work you stepped in for.

You're welcome. :)

What I'd love to see is complete art sets for the MAME software lists. It would make gathering the art and matching romsets so much easier, and no discussions about which game should or should not be included.

Sent from my SM-G920F using Tapatalk

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...