Hyperspin running in foreground and Mame running in background

[jasonpacorbett]

Hey guys,

 

I searched everywhere and I can't find anyone with this problem. Basically I have several systems on my Hyperspin setup but its only when I select Mame that Hyperspin continues to run in the foreground while Mame runs in the background. If I click on the Mame screen it then comes to the foreground and Hyperspin goes away as normal.

 

Every time I esc Mame and start a new game it does this all over again. Any ideas would be greatly appreciated.

[whynotpizza]

Did you find the answer here? I am also struggling here

[bigmike20vt]

Hi

 

I was about to post a similiar issue but as it seems related will put here.

 

My arcade was set up quite well, with snes (snes9x), MD (fusion) and mame

 

however i wanted to set up some scanlines and as i kept getting bezxels coming up in my snes games, i was advised to try disabling them and turning on the scanlines in snes9x itself... so i disabled the bezel, turned on scanline (and unfortunately fiddled elsewhere) and then on launching any snes game, it sounds like the emulator fires up in the background, but hyperspin just sits there on the foreground.

 

i can still move up and down, and exit but that is about all i can do.  I tried to put the settings back to before i started messing, however i am stuffed if i can get it working again.

 

mame and megadrive still work fine, its just snes.. oh and when i try to bring the emulator to the front using alt tab it does not work.  The emulator works fine outside of hyperspin.

 

Thanks in advance for any thoughts

[Broadoak84]

Has anyone found an answer to this question? With my setup, Hyperspin fires up fine and then RL launches MAME when I select a game. Problem is MAME sits behind the Hyperspin window so I have to alt tab into it! I'm also using JOYTOKEY in both Hyperspin and MAME, which is working fine. Is there a setting in any of the applications or .ini files that forces MAME to the front??

[Guest]

Has anyone found an answer to this question? With my setup, Hyperspin fires up fine and then RL launches MAME when I select a game. Problem is MAME sits behind the Hyperspin window so I have to alt tab into it! I'm also using JOYTOKEY in both Hyperspin and MAME, which is working fine. Is there a setting in any of the applications or .ini files that forces MAME to the front??

Which version of MAME are you using?? Also, post on the RL forums with a troubleshooting log.


Sent from my iPhone using Tapatalk

[Broadoak84]

I've set this up in the last 2 weeks using the latest software available:

• Mame64 - I've tried .180 and .181 and a recompiled .180 nonag
• hyperspin 133 with 1.4.16 upgrade applied
• Rocket launcher 1.2.0.1 with updates applied.
• Joytokey 5.8.2

OS is Windows 10 on a dell xps laptop. Everything else running like a dream with just this one issue outstanding. 

[baddeolv]

I've set this up in the last 2 weeks using the latest software available:

• Mame64 - I've tried .180 and .181 and a recompiled .180 nonag
• hyperspin 133 with 1.4.16 upgrade applied
• Rocket launcher 1.2.0.1 with updates applied.
• Joytokey 5.8.2

OS is Windows 10 on a dell xps laptop. Everything else running like a dream with just this one issue outstanding. 

This usually happens when the emulator screen res doesn't match the frontend's and/or the pc's

[Broadoak84]

Thank you for your help - nearly there! I set the resolution in HyperHQ to 1024x768 and ticked the 'full screen' box. That fixed it whilst only using my laptop (no joystick). Feeling very pleased with life, I plugged in the joystick and found that it doesn't work again! Unplug the joystick and it works. I've tried 2 completely different joysticks (a pad and fight stick) but I get the same problem. 

One other thing is that the game might actually be minimised to an icon in the windows bar rather than running behind the other window - difficult to tell. 

[Broadoak84]

I seem to have found the answer! MAME comes in before JoytoKey fires and so when Joytokey finally starts it causes MAME to minimise. The answer is to add a fade setting, which  delays things just long enough so that MAME is the last thing to open and therefore stays maximised. I also had to set HyperHQ screen setting to be maximised as this doesn't work if it runs in a window like 1024x768. Not sure if what I've done is a bodge as I reckon there's an underlying problem like a setting in Joytokey, but hey it's working for now.