JoeViking245

For Start Trek Ultimate, what I just did (literally JUST did as I haven't played FP in quite a while)... Downloaded ST Ultimate and placed the ftp and xml files in the "Tables" folder [D:\Pinball\Future Pinball\Tables\...] Downloaded the latest FP [from their site] and installed it over my existing copy. v1.9.1.20101231 Downloaded the most recent version of BAM and installed on top of my existing install. (It asks for the "Future Pinball" folder during install.) version: v.1.5-322 Downloaded DOFLinx V7.24. I DID NOT install it. (my setup ain't that special. lol) Extracted "DOFLinx.vbs" from the .zip file and placed into D:\Pinball\Future Pinball\Script\ folder. I use a compiled AutoHotkey script to open/run my tables, but I don't remember what's in it. @Headrush69 can hopefully remind me. I think it run BAM's "FPLoader.exe" and puts in some command lines as well. Maybe something like /play /exit /open I had problems opening the table until I put the vbs file in as noted in step #4. After that, it ran perfect.

That last video's not even 'loading' the tables to launch.

Have your C# program start BigBox after it's done parsing/updating the xml.

No. There are no command line options available. This is a stretch, I only tested it only once, you won't be able to save any [subsequent] changes to BigBox (theme, view, button assignments...) but.... it appeared to work. ...after adjusting any applicable settings you need, being in the Platform you want to start in and exiting BigBox..... Go to your ../LaunchBox/Data/ folder and set "BigBoxSettings.xml" to Read Only. There shouldn't be any ill side affects, but I have been wrong before. But I usually do pretty good.

No. But where you have a shortcut to BigBox.exe in your startup folder, you could replace that with a shortcut to a batch file. [I'm pretty sure. Not tested.] Something along the lines of start /w "" "D:\LaunchBox\Core\BigBox.exe" C:\Windows\explorer.exe Of course adjusting your LaunchBox drive and location accordingly. This will launch BigBox and then wait until it closes (exits) before running explerer.exe. But you will need to make sure to point to the 'BigBox.exe' located in the ../Core subfolder. Otherwise it'll run exploere.exe without waiting.

I've had this happen when I'm doing miscellaneous testing with plugins and am doing a lot of starting and exiting of LB/BB (exiting only via the respective UI). I presume this has to do with impatient wait-times on my part. I assimilate this to my refrigerator condenser it constantly running. And though I open the fridge door every 3 to 5 minutes to make sure everything's still cold, the motor is still always running. I have never had this happen on my cab nor with an occasional [single] start/exit. So from what I've seen of it, I don't feel it's an issue that needs to be addressed. As [for me] it operates under 'normal conditions', as it should. I do know sometimes it does take a little longer for the LB 'process' to completely clear out from Task Manager as it's cleaning up after itself before vacating. And I'd rather it do that than leave a mess behind. Again, this is just my experience/observations. Your mileage may vary. Taskkill is a Windows command whereas Process, Close is inherent to AutoHotkey. They both act with the same 'brute force'. You could always do a 'Run, taskkill....' from within an AHK script if you wanted. But the end results should have exactly the same outcome.

May could try... for that Platform, do "Tools", "Scan for added roms". Don't search metadata nor import images (will speed it up a little). This 'should' scan that folder your roms are in and add those ones you previously deleted. Now, with the checkbox "Allow deleting ROMs when deleting games" checked (Tools, Options, General), sort the games in that Platform by Date Added. Delete the games that were 'just added'.

Also note that Process, Close is not a very 'nice' way to exit an app. Almost as bad (forceful) as taskkill. Suggest using WinClose, ahk_exe BigBox.exe The others will, well... 'kill' the process. Whereas WinClose is like hitting Alt+F4 which is telling the app "Hey, I need you to close. So save all your data and do what you need to do, then shut down please."

??? That's how I'd start it. Are you saying you have a 'shortcut' (of sorts) in your media center to run the batch file? And by running it that way, it's making the taskbar disappear? If you're running the batch file, BigBox will make the taskbar 'disappear'. I guess I'm not following what you're saying.

timeout 3 taskkill /F /IM "program.exe" /T timeout 2 start /w "" "D:/LaunchBox/Core/BigBox.exe" timeout 2 start "" "D:/program/program.exe"

Oh well heck! lol. Go back to one of our earlier 'attempts' and try start /w "" "D:/LaunchBox/Core/BigBox.exe" That WILL truly wait for BigBox to exit before continuing the batch file. Guaranteed!!

Ya, I kinda tried that too (but with LaunchBox). Potential 'problem' here is "BigBox.exe" spawns "BigBox.exe". Same name. That may muddle things up. Not sure though. Maybe look through your D:\Games\Rovio folder(s) for another Application File that anrgybirds.exe might spawn. See if you can start AB's directly from this 'other file'. I know. I'm kind of reaching here. If you have AutoHotKey, you could run "WindowSpy". Or do like you did with BB and look at Process Explorer when AB is running and see if it's a different executable than angrybirds.exe. Ya, ya. Still reaching.

Sounds like angrybirds.exe is spawning another program that then [actually] runs (is) Angry Birds. So basically angrybirds.exe starts whatever.exe (which will be the actual game) and angrybirds.exe exits. Since "angrybirds.exe" has exited, the batch file continues on, while whatever.exe is still running. If my assumption is correct, you need to find out what 'whatever.exe' is and then account for it somehow. BTW, good find on the "taskkill" command.

Not sure how off hand to close an already opened program, but this should get you going on the rest rem batch file started rem wait 3 seconds timeout 3 rem not sure how to do this, so will comment out for now rem fully Close peggle.exe rem wait 2 seconds timeout 2 rem launch D:Games/Rovio/angrybirds.exe start /w "" "D:Games/Rovio/angrybirds.exe" rem wait till angry birds has exited naturally (as in not in task manager anymore) rem the /w in the previous command line "waits" until that program has exited before continuing rem wait 2 secs timeout 2 rem launch D:/Games/Peggle/Peggle.exe start "" "D:/Games/Peggle/Peggle.exe" Lines beginning with "rem" are 'remarks' (comments).

Glad you got it working! Pretty much all the info (tips, tricks and solutions) are out there. But finding the "correct" key word or phrase to search for can be frustrating. As you've found, a simple change in the lure, bait, line and even pole can make a big difference. As for 'trolling' to a different location, searching in Google will [most] always give you the best results over searching in a specific forum/site. So with the right gear in your tackle box, you too can "fish better than before." I know your son appreciates all your hard work too. "Game on!"

Are either of your 2 programs being ran as admin? Try running the script as admin and see if that changes anything. Tear the script down piece by piece. i.e. To start: Have the script only close Trainer. Open Trainer then run the script. Double check syntax. i.e. my 2nd line didn't show quotes around ahk_exe Trainer.exe. (think I missed that one. Though off hand, not sure if they're actually required or not). Can you show what your script looks like? (btw the 2 picts were helpful). Myself, I cannot help you with anything about RocketLauncher. Not that I won't. It's just that I can't (never used it and have no plans to start. No offense. ) I'm off to bed and will check back in the morning. I expect a full report of your tests and findings. jk Hopefully the admin thing or breaking down the steps will help shed some light.

"I think" this will work. Create a next Text file and then save (or rename) it as an AutoHotkey Script file. i.e. "F:\MyAHKs\GRwTrainer.ahk" Make sure the actual extension is getting changed to "ahk" from "txt"! The contents of the file will be something like this: #SingleInstance Force WinClose, ahk_exe Trainer.exe if WinExist("ahk_exe Ghostrunner-Win64-Shipping.exe") { WinActivate } else { Run, "F:\LaunchBox\Games\PC Games\Ghostrunner\Ghostrunner.exe" } Run, "F:\LaunchBox\Games\PC Games\Ghostrunner\Trainer.exe", , Min Sleep, 10000 Process, WaitClose, Ghostrunner-Win64-Shipping.exe WinClose, ahk_exe Trainer.exe Edit your GhostRunner game and set the Application Path to ThirdParty\AutoHotkey\AutoHotkey.exe ..and the Command Line Parameter to "F:\MyAHKs\GRwTrainer.ahk" With this, your launching the script instead of the game (which in turn will launch the game etc.). What the script does: Force the script to close if it's already running, and 'restart' it. Close "Trainer". (a simple 'catch' that doesn't hurt anything it it wasn't already running) Check if "Ghostrunner-Win64-Shipping.exe" is already running if it is { Bring its window to the top } otherwise { Run GhostRunner } Run Trainer minimized Wait 10 seconds for GR to [I assume this is what it does] spawn "Ghostrunner-Win64-Shipping.exe". It shouldn't take this long to 'spawn', but doesn't matter. He'll be 'playing' for at least 10 seconds anyway. Right? Hang out here until the game is exited. Once the game is no longer running, politely close Trainer. at this point, the script is done and will exit itself. No need to ExitApp. I think I caught from your description that Trainer and GR are independent of each other, in that one doesn't HAVE to be running PRIOR to the other. If that's not the case, this ain't gonna work as expected. If all goes well, you should be good to go. Not tested, but it "looks good on paper".

Tools. Options. They do not get deleted when deleting a game. Easy fix though.... Tools. "Clean Up Media..."It'll scan your media (images, videos etc) for ones that are no longer associated with a game in your LaunchBox setup.

The score is definitely nothing to brag about, in fact not even worth mentioning... but there at least one new "high score". With everything lowercase now, exit and restart LaunchBox, Run Time Pilot, Try to beat my Weekly high score (lol. jk), Exit the game, Exit LB and look at the most recent log file. Hopefully it'll change from something like thisTo something like this

Hmm.... based off the debug log, LaunchBox is looking for the game (rom) .hi file using a capital "T", but all the others in the log show lowercase. That's why I was assuming that hi2txt searches are case sensitive since it came back with "ERROR: No XML description found for ROM 'Timeplt'". My next (and probably last) guess is Edit your game in LaunchBox and see if the filename (rom_name) it's pointing to is capitalized.

Any chance you manipulating your timeplt.hi file? Though it found "Timeplt.hi", the hi2txt (I believe) needs to see "timeplt.hi". Try changing the capital "T" to a lower case "t" in your ../Documents/Mame/hi/ folder. I didn't test that particular one, but MAME should be saving the file in all lowercase.

The log file only references Hyper Sports. Nothing in there about Time Pilot.

...and as it turns out I thought wrong. ? So back to editing each game. Unless this [hack] works.!.!.!.!.!..... Create a "crosshair" folder directly under MAME. D:\Emulators\MAME\crosshair\ Place in there a empty "transparent" png image and name it "cross1.png". If you're setup for multiple players, copy it to "cross2.png", "cross3.png".... This at least seemed to make the 'default' crosshair invisible in Big Buck Hunter without going into the tab menu. (just remove ".txt" off the attached file) Not sure if this messes up other things [beyond all games will now have an invisible crosshair]. cross1.png.txt

See here: https://docs.mamedev.org/advanced/multiconfig.html Though it doesn't address the cfg files. So we'll use our noodles to make up some logic. The main purpose of the cfg file under ../ctrlr/ is to tell MAME what "mapdevice" to look for and use. And ya, basic mappings per your liking. So it kinda has to load when MAME loads. [otherwise you (possibly) wouldn't be able to use your controller to maneuver around its' UI] When a game-specific cfg file is created, it copies the default.cfg (and anything we added to that 'read-only' file) and then adds any subsequent game specific config changes you make, to it. So [in my mind] it stands to reason that if a game-specific cfg file exists, MAME has no need to look at the default.cfg. Thus won't. ..which brings us full-circle to

Curiosity got to me, and here's what I found... It is indeed in the cfg file for the game(s). For your cab that you want to have NO crosshairs shown in MAME, edit the "default.cfg", save and set it to read only. <?xml version="1.0"?> <!-- This file is autogenerated; comments and unknown tags will be stripped --> <mameconfig version="10"> <system name="default"> <crosshairs> <crosshair player="0" mode="0" /> </crosshairs> </system> </mameconfig> If by chance your "default.cfg" has other 'stuff' in there, leave that there and just add the 3 "crosshairs" lines right above "</system>" (2nd to last line), leaving the rest of the 'stuff' above that point. If you already have cfg files for each game(s) (which you may or may not), you can either edit each of those [ugh], or simply delete them. Now when you launch a game, MAME will read the default.cfg file (if a game specific one doesn't exist) and the crosshairs will be set to Off. ...I think...