Emulators take way too long to start after selecting a game

[kajgies]

Hey,

I already searched a lot but couldn't find a solution so here's my problem:

When I select a game it takes very long for the emulator to start. It can take from 10 seconds up to a few minutes.

When they are started, they run at full speed.

This happens with all my emulators, with or without HyperLaunch.

Outside of HyperSpin they all launch instantly. (also tried launching with the same commandline in the log file)

I've tried moving hyperspin to C:\hyperspin and that makes no difference.

This happens with and without a joystick.

My emulators are in HyperSpin\Emulators\(consolename)\(emuname) and my games are in HyperSpin\Emulators\(consolename\Games.

The HyperSpin intro video starts instantly when I start HyperSpin.

I'm running Windows XP.

I'm running the latest version of HyperSpin.

Any help would be greatly appreciated.

[somail]

Do you have a high level of error logging turned on in Hyperlaunch? try turning it off.

The emulators do matter. If you are trying to start a cd based system then Hyperlaunch needs to unzip the file first (if they are compressed). Should not be a problem on mame or 8/16 bit emulators.

[kajgies]

Thanks for replying.

Mame is the only one not using HyperLaunch but it still takes 10 - 20 seconds to start a game.

Logging level in HyperLaunch was on "error" I turned it to "off" and I disabled some joystick setting but it made no difference.

A GameBoy Color game for example takes about 15 seconds to load while outside of HyperSpin it's almost instantly.

[marxkemp]

Ill make a guess: run as administrator and turn of any av program

[kajgies]

Thanks for your suggestion.

I'm on windows xp as administrator and my av is already turned off.

[marxkemp]

Go to run, type msconfig and uncheck everything on startup?

Or try:

Safe mode? (Dont know if hs would start)

[marxkemp]

Btw check hyperlaunch.log it has timestamps and maybe that will give us a clue where to look..

[kajgies]

I already unchecked everything in startup before.

And I checked task manager and there were only system processes running and a few windows things which don't take any cpu or memory.

It takes about 4.5 seconds for HyperLaunch to start, looking at the logs.

Then HyperLaunch takes about 2 seconds to run the commandline for the emulator.

Then HyperLaunch takes about 5 seconds to start the emulator WinWait, WinWaitActive and waitClose module.

That's a total of over 10 seconds, which I find a bit long, It's better then before but still.

[albert_c]

Silly question but have you sync'ed the latest version of HyperLaunch from Git?

[mickkn]

Do you have any fade delay on? Check HLHQ

Sent from Tapatalk

[kajgies]

I have the latest HyperLaunch from this website and have fade disabled.

I tried copying everything to an external hard drive and played it on a Windows 8 64 bit laptop and I didn't have any problems.

So I think either there are some things I have to set up different for windows XP, or my XP computer just isn't fast enough.

But then when I start the emulators dirrectly in windows, they start instantly, so maybe the problem is with HyperSpin/Launch itself.

Any ideas?

[aliens8us]

I have a similar issue; and I am so glad you brought this topic up. I too have a Windows XP PC. Hyperspin and everything else is on a separate 500gb hard drive. When I choose a game, it takes afew seconds as well and then I get the 'running scripts error, OK to proceed' message and have to hit OK to run it. Then after about 10 seconds, it runs the game. Any suggestions?

[albert_c]

The HyperLaunch download on hyperspin-fe.com is out of date. The most correct method to install HyperLaunch is to follow this tutorial here. Once you have synched your HyperLaunch installation from Git, try to launch your emulators again.

[aliens8us]

The HyperLaunch download on hyperspin-fe.com is out of date. The most correct method to install HyperLaunch is to follow this tutorial here. Once you have synched your HyperLaunch installation from Git, try to launch your emulators again.

Holy crap, that's quite the tutorial (from the link you provided)! Will this actually clear up my issue with the 'script issue' I'm having?

[zargon33]

Curious are the roms stored on an internal or external hard drive? It might be that the drives are powering down when they are idle, and taking some time to access. You can typically change those settings in your power settings in control panel. Even if they are powering down, it shouldn't delay it over 10 seconds I wouldn't think. You could test by trying to open a video or file from the drive that the roms or stored on while the system has been idle a while to see how quickly the video or file launches, just to rule out the possibility of there being an issue with a delay in accessing the file on the drive. I only mention since I had a 4tb external HD that had long delays whenever I would access it. After backing the files up and formatting again, checking power settings etc it turned out my drive had issues and needed to be replaced. Might not be the case for you but couldn't hurt to check.