Does HyperLaunch prevent config saving?

[ccarlesco]

I've been having some really frustrating issues with Hyperlaunch.

I've tried 3 different versions of mame and none of them seem to retain any changes I make to the config settings. If I disable hyperlaunch it saves but for some strange reason I get an input delay on my cabinets joysticks and buttons.

One more issue - When hyperlaunch is used I loose player 2 button 3 for some reason.

Everything works perfect outside of Hyperspin.

Any insight would be greatly appreciated!

[BadBoyBill]

Hyperlaunch makes no changes to any files at all, it doesnt do anything with mame at all but simply launch it.
You most likely dont need hyperlaunch to launch mame for you and can just use the normal launching method. Its made more for pesky emu's and such, mame ist pretty straight forward, unless your trying to define multiple exit keys etc...

What button is player 2 button 3? What letter of the keyboard is it?

[ccarlesco]

Thanks for the info -

The weird thing about not using hyperlaunch is that I get input slowdown - pressing a button or moving the joysticks responds about 2 seconds delayed. I'm using a standard i-pac interface.

I also notice that is see tearing in scrolling games that doesn't occur when I run them through mame32.exe. This occurs in both standard and hyperlaunch.

Player 2 button 3 is mapped as the letter Q

Thanks again!

[EVEGames]

I also notice that is see tearing in scrolling games that doesn't occur when I run them through mame32.exe. This occurs in both standard and hyperlaunch.

ccarlesco,
Which are you running from HyperSpin, mame32 or command-line mame?

[ccarlesco]

Mame32.exe

But I also tried mame.exe command line and I noticed the same issue.

[EVEGames]

If mame32 is showing tearing effects when launched from Hyperspin and not showing the same effects when launched stand-alone, I think you must be passing different command-line arguments somehow. Try enabling the -triplebuffer parameter in mame.ini (or pass it as an argument via HyperLaunch). That should clear up your tearing issue.

[ccarlesco]

That fixes the tearing effect

The slowdown when not using Hyperlaunch seems to stem from the emulator running at 100% cpu usage.

Something about the native launcher seems to peg the cpu no matter what game. It never goes down from 100% either -even if the game is paused.

I've tested this with different mame emulators amd different PCs and they all behave the same way.

I was able to recompile hyperlaunch with a different hotkey for letter q and I can now use player 2 button 3. Maybe q shouldn't be the default key?