Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Can't figure out closemul automation steps syntax  (Read 5831 times)

0 Members and 1 Guest are viewing this topic.

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Can't figure out closemul automation steps syntax
« on: July 28, 2008, 04:59:21 pm »
Does anyone know of a closemul guide or sample ini file?
I'm having trouble getting the automation steps to work.
Or if anyone uses it and would be so kind to post their ini file showing the automation steps, that would be appreciated.

Thanks.
"The Manuel"

gonzo90017

  • Trade Count: (+5)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1034
  • Last login:June 23, 2019, 02:41:07 pm
  • I'm a llama!
Re: Can't figure out closemul automation steps syntax
« Reply #1 on: July 28, 2008, 05:20:30 pm »
I think the read me is pretty self explanatory.
Code: [Select]
- Keyboard Automation (Automatically load games for emulators that don't support command line)

  For the automation to be active you must use the auto= parameter to set the "Window Title" of your Program.

  You can define a list of keyboard commands to be executed right after the Program is launched, in the .ini or by using
  autosteps="command1,command2" (autosteps="ALT+F, O, FILE, ENTER, F2")

  You can optionally set a time to wait between commands with autodelay= (defaults to 50 milliseconds).

  The list must be comma separated, with or without spaces.
  You can use Special Commands, Prefixes+Keywords, Keywords, or plain text.

  Prefixes: SHIFT+ CTRL+ ALT+ WIN+ (e.g. ALT+F, ALT+TAB, SHIFT+TAB... WIN+ usually requires a lower case letter: WIN+e)

  Keywords:
  F1-F12, ENTER, NUMPADENTER, SPACE, LEFT, UP, DOWN, RIGHT, ESCAPE/ESC, DELETE/DEL, SLEEP, HOME, END, INSERT/INS,
  PGUP, PGDOWN, TAB, PRINTSCREEN, LSHIFT, RSHIFT, LCTRL, RCTRL, LALT, RALT, LWIN, RWIN.

  Special Commands:
  WAIT xx (in milliseconds, wait 1000 will pause for 1 second),
  FILE (will be replaced by the File you specify using the file= parameter),
  FILE2 (will be replaced by the second file found in the archive if you use the unzip/unrar option),
  AFTERFILE (will be replaced by the Param After File parameter),
  ASCII xxxx (you can also use unicode),


  You can also use pre defined automation for some emulators, using keywords in place of the Window Title.

  Project Tempest v0.95: Add "tempest" to your command line.
  (instead of: auto="Project Tempest" autosteps="ALT+F, O, FILE, ENTER, F2")
 
  Caprice32 v3.6.1: Add "caprice" to your command line.
  (instead of: auto=Caprice32 autosteps="˛, F6, FILE, ENTER, F2, AFTERFILE, ENTER")
  If you want to start with a joystick menu instead of having to type cat, run" on the keyboard, get utility.dsk from
  http://cpc.trak.dk/troels.htm#discexec, load it into Caprice in drive B (F7), type "|b", "run"disc", then press Enter.
  Take a .sna memory snapshot (F4) right after pressing left on the joystick and save it in your Caprice directory.
  Put the name of this .sna file at the end of your command line.
  You will then boot into a joystick controlled menu on the CPC every time you load a game from your frontend.
 
  WinUAE  v1.2.0: Add "winuae" and "config=(yourconfig.uae)" at the end of your command line.
  (auto="WinUAE Properties" autosteps="SHIFT+TAB, SHIFT+TAB, SHIFT+TAB, SHIFT+TAB, F, SPACE, FILE, TAB, ENTER"

  Set all your options, check "Show GUI on Startup" and save your config in the WinUAE "configurations" folder.
  If you use the unzip option and the "winuae" keyword, Closemul will load in drive DF1 any second file present in the archive.

massive88

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 938
  • Last login:February 26, 2024, 02:21:01 pm
Re: Can't figure out closemul automation steps syntax
« Reply #2 on: July 28, 2008, 05:29:31 pm »
I dont have access to mine now, but the readme was pretty helpful if I remember right.  I had it automate playing Ultra64 which was a lot of steps.

Ill see if I can find an ini when I get home, if you cant get it to work at all its probably something very simple that is wrong.

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #3 on: July 28, 2008, 09:03:17 pm »
It is quite explanatory indeed.  I gave the reame a quick glance last night.  I guess I must have been too tired to notice.
I'll give it a shot.
massive88: if you do get to it, I will still find you ini very useful.  It's always easier seeing an example.

Thanks.
"The Manuel"

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #4 on: July 28, 2008, 10:38:25 pm »
I kept trying to no avail.
I don't know what's wrong.  :banghead:
"The Manuel"

gonzo90017

  • Trade Count: (+5)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1034
  • Last login:June 23, 2019, 02:41:07 pm
  • I'm a llama!
Re: Can't figure out closemul automation steps syntax
« Reply #5 on: July 28, 2008, 10:41:20 pm »
What is it you're trying to do?

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #6 on: July 29, 2008, 07:52:17 am »
I'm trying to launch Gambatte (a Gameboy emulator), and automate the sequence:
Ctrl+F, Esc
This will switch mode to fullscreen and hide the menu bar.
I can handle closing the program using MaLa'a hotkeys.
"The Manuel"

massive88

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 938
  • Last login:February 26, 2024, 02:21:01 pm
Re: Can't figure out closemul automation steps syntax
« Reply #7 on: July 29, 2008, 09:34:26 am »
What is it doing?  Part of it?  Nothing?  Have you tried putting in a delay at the start to ensure the program loads first?

Sorry I got tied up last night and didnt even get to set foot in front of my arcade box.

Is Esc closing the emulator?  By default Closemul will make esc an exit hook.

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #8 on: July 29, 2008, 12:39:52 pm »
Well the Esc works so closemul is loading and present but the automation dteps don't work.
I've been using a three second delay to give it time to load.
Part of the problem might be that gambatte's sceen title includes the name of the ROM zip file being loaded.
I have tried with a particular ROM and using the name of the title screen including that ROM's name.  I've tried just the gambatte part of the title.  I've tried with and without quotes, etc.
I'm stomped.  This is why I was Interested to see an ini file that works.
I'll post my ini file when I get home tonight.
"The Manuel"

gonzo90017

  • Trade Count: (+5)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1034
  • Last login:June 23, 2019, 02:41:07 pm
  • I'm a llama!
Re: Can't figure out closemul automation steps syntax
« Reply #9 on: July 29, 2008, 02:40:25 pm »
I couldn't get it to work either.  ???
What frontend are you using? I just wrote a script to launch it full screen.
With Mamewah you can load programs before launching the emulator using:
Code: [Select]
pre_emulator_app_commandlines Which you would need to do in order for it to work properly.

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #10 on: July 29, 2008, 04:45:05 pm »
I'm using MaLa.
However, I have been working from the command line so far to make sure it works before incorporating into the front-end.

Would you care to share your script if it isn't Mamewah specific?
"The Manuel"

massive88

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 938
  • Last login:February 26, 2024, 02:21:01 pm
Re: Can't figure out closemul automation steps syntax
« Reply #11 on: July 29, 2008, 05:33:49 pm »
I downloaded the files at work to see if I could get it working for yas.

This seemed to work fine for me on a clean copy.  I ran closemul and end up with gambatte fullscreen with no menu.

Code: [Select]
[Parameters]
Exit Key 1=
Exit Key 2=
Extract=
Extracted Ext 1=
Extracted Ext 2=
Pre Command=
Post Command=
Mount Program=
Mount Device=
Mount Parameters=
Registry File=
Automation=Gambatte
Automation Steps=wait 5000,CTRL+f,ESC
Automation Delay=
Program=gambatte_qt.exe
Program 2=
Param Before File=
Param After File=
File=
Snap 1 Search=
Snap 2 Search=
Snap Extension=
Snap Source Folder=
Snap 1 Dest Folder=
Snap 2 Dest Folder=
Quit Management=
Quit TimeOut=
Disable Quotes=

I suspect you left out the Automation=gambatte line, which caused me trouble in the past.  I beleive that is telling it which window to send the automation commands to.  I just started with a delay of 5 seconds and it worked, your mileage may vary.

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #12 on: July 29, 2008, 06:04:42 pm »
I just got home.
I'll walk downstairs and try it out.
I have been using the automation=gambatte parameter, though.
Maybe the extra two seconds will do the trick.
Thanks for doing this even grmo work  ;D
"The Manuel"

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #13 on: July 29, 2008, 06:39:48 pm »
Well, that worked.
You don't really need to specify the Program=gambatte_qt.exe parameter for what I'm trying to do.
My problem was that the "F" in CTRL+F needed to be lower case.
I hate it when programs are this finicky but can't look gift horse in teh mouth.

Now I'm faced with the problem I mentioned earlier.  The above works as long as I'm not loading a ROM with the program which is the intent of the whole thing.  If I load it with a ROM, the title of the screen takes the form of the name of the zip file where the ROM was loaded from, a space, a hyphence, another space and then "Gambatte":
Metroid II - Return of Samus (JU) [!].zip - Gambatte
I can't figure out how to address the Window title name generically from the ini file so that it works with any ROM.  :banghead:

While we are on the subject, do one of you know how I can assign the "Tab" key as a hot key in MaLa? 
Every time I try it, the cursor shifts to the next field in the dialog box.  This is normal Windows behavior but it does not let me assign the Tab key.  I can't find where in the MaLa .ini file these assignments are stored.  I posted this question in the MaLa forum but the post is slowly drifting down with no recent responses.

Thanks.
"The Manuel"

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #14 on: July 29, 2008, 10:03:49 pm »
I forgot to mention.
You don't really need any wait time before the commands with Gambatte.
It pops right up in full screen mode and hidden menu bar with minimal Windows screen in between.

Now, if I can only get it to work with ROMs...
"The Manuel"

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #15 on: July 29, 2008, 10:13:38 pm »
I thought of something.
I can feed closemul the name of the zip file as an argument to the auto parameter.
It does not need to be on the ini file.
I'll try it and report back.
"The Manuel"

gonzo90017

  • Trade Count: (+5)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1034
  • Last login:June 23, 2019, 02:41:07 pm
  • I'm a llama!
Re: Can't figure out closemul automation steps syntax
« Reply #16 on: July 30, 2008, 01:16:36 am »
I've attached the script. But like I said it has to be launched before the rom is loaded.
Mamewah and AtomicFE allow you to launch programs before the emulator is loaded. Closemul has
something similiar but I couldn't get it to work.

massive88

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 938
  • Last login:February 26, 2024, 02:21:01 pm
Re: Can't figure out closemul automation steps syntax
« Reply #17 on: July 30, 2008, 09:18:52 am »
By this point I would have given up and gone to a more FE friendly emulator.  Gambatte is just gameboy right?

Have you seen if Mess, kiGB or VBA would suit your needs?

I can speak for KiGB but VBA and Mess are easy to setup and run.

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Can't figure out closemul automation steps syntax
« Reply #18 on: July 30, 2008, 11:36:55 am »
Guys:
My last attempt worked.  I was persistent.
Like I mentioned earlier, all you need in the ini file is:
Automation=Gambatte
Automation Steps=CTRL+f,ESC

On the MaLa OtherEmu configuration window, just feed the name of the rom with the zip extension to closemul.
I'm not at home right now but it should look something like this:
closemul gambatte_qt.exe %path%\%rom%.%ext  auto=%rom%.%ext%
Don't use any wait time to minimize the interruptions.

I wanted to stick with Gambatte because of its accuracy.  It is supposedly better than even VBA for Gameboy (not GBA) games.

Thanks a lot for all your feedback.

"The Manuel"

johnyil

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 1
  • Last login:August 16, 2017, 11:42:39 pm
  • I want to build my own arcade controls!
Re: Can't figure out closemul automation steps syntax
« Reply #19 on: August 16, 2017, 11:40:52 pm »
 ____________________THANKS______________________

 ____________________GRACIAS_____________________

Gracias amigos no sabes todo el tiempo que estuve buscando una solución a este tema.
amigos no duden mas esta es la solución no busquen mas.

les hablo de la solución para que el closemul haga correr el emulador que necesiten en pantalla completa.
casi me vuelvo loco intentando de todo pero ya entendí perfectamente como funciona.

SALUDOS DESDE COLOMBIA

I downloaded the files at work to see if I could get it working for yas.

This seemed to work fine for me on a clean copy.  I ran closemul and end up with gambatte fullscreen with no menu.

Code: [Select]
[Parameters]
Exit Key 1=
Exit Key 2=
Extract=
Extracted Ext 1=
Extracted Ext 2=
Pre Command=
Post Command=
Mount Program=
Mount Device=
Mount Parameters=
Registry File=
Automation=Gambatte
Automation Steps=wait 5000,CTRL+f,ESC
Automation Delay=
Program=gambatte_qt.exe
Program 2=
Param Before File=
Param After File=
File=
Snap 1 Search=
Snap 2 Search=
Snap Extension=
Snap Source Folder=
Snap 1 Dest Folder=
Snap 2 Dest Folder=
Quit Management=
Quit TimeOut=
Disable Quotes=

I suspect you left out the Automation=gambatte line, which caused me trouble in the past.  I beleive that is telling it which window to send the automation commands to.  I just started with a delay of 5 seconds and it worked, your mileage may vary.