Okay, I’m not normally one for rants (ed. yeah right) but watching Thursday Night Football lead in and the Verizon commercial comes on.
Unlimited: adjective ˌənˈlimidəd/
1: lacking any controls : unrestricted <unlimited access>
2: boundless, infinite <unlimited possibilities>
3: not bounded by exceptions : undefined <the unlimited and unconditional surrender of the enemy — Sir Winston Churchill>
Verizon’s definition of unlimited: Apparently somewhere between 2GB and ~24GB.
When you add a system to RocketLauncher you have to choose the default emulator – but what if RocketLauncher doesn’t list the emulator you want to use? Note: this is not how to add a new emulator/system if the emulator was not previously added. That has been covered on the RocketLauncher page here.
As you can see above, my System names (left column) don’t all correspond with “traditional” RocketLauncher names. In this case it’s because they were imported from LaunchBox. You can see that rather than being called “MAME”, the name (circled in green to the right) is “Arcade”. While that is because it was imported from LaunchBox, it’s a more descriptive name for the non-initiated. Not that someone would be messing with RocketLauncher if they didn’t know what MAME was, but anyway.
The middle green circled area shows that I’ve chosen MAME as the default emulator. Initially, however, when pressed the magnifying glass icon on the right of the Default Emulator box, the choices that I was presented for Arcade’s default emulator were…nothing. That’s because the program file (.ahk file) that RocketLauncher uses to choose which systems MAME can run did not include “Arcade” in the list.
So how to fix? Relatively easy, actually, although you’ll have to accept that RL* will inform you that you’e changed their precious file. Normally that’s a good thing, … Continue reading
There is no excerpt because this is a protected post.
Using a zipped/compressed ROM in emulator through LaunchBox.
Allows you to save hard drive space, but does take a little longer to launch each game (about 20 seconds per 500MB depending on CPU and hard drive speed.)
You must have the setting checked to “Extract ROM archives before running” in the emulator setting inside Launchbox.
Example: Tools, Manage emulators, Demul (or whichever emulator) then Edit. Bottom right corner is a checkbox for “Extract ROM archives before running”. In this image it is NOT checked, but you’ll need to check it and click the OK button for it to work.
The audio is a little choppy in the game start…this is due to the slower laptop I was editing on and not indicative of the game play.
There is no excerpt because this is a protected post.
Bills at Ravens prediction: Buffalo Bills 28 – Baltimore Ravens 25
Sunday, September 11, 1:00 PM M&T Bank Stadium, Baltimore, Maryland
Qtr 1 Qtr 2 Qtr 3 Qtr 4 OT Final Buffalo Bills 0 12 3 10 3 28 Baltimore Ravens 3 7 0 15 0 25
SCORING SUMMARY 1st Quarter BAL 2:46 FG Justin Tucker 44 yds. 0-3 2nd Quarter BUF 14:16 TD LeSean McCoy 16 yd. run (Carpenter missed extra point) 6-3 BAL 9:02 TD Steve Smith Sr. 13 yd. pass from Flacco (Tucker kick) 6-10 BUF 0:00 TD Sammy Watkins 47 yd. pass from Taylor (Carpenter missed extra point) 12-10 3rd Quarter BUF 4:25 FG Dan Carpenter 29 yds. 15-10 4th Quarter BUF 7:26 TD Sammy Watkins 7 yd. pass from Taylor (Carpenter kick) 22-10 BAL 5:19 TD Breshad Perriman 67 yd. pass from Flacco (Tucker kick) 22-17 BAL 0:49 TD Javorius Allen 11 yd. run (Forsett 2-PT conversion) 22-25 BUF 0:00 FG Dan Carpenter 44 yds. 25-25 OT 1 BUF 9:50 FG Dan Carpenter 29 yds. 28-25 PLAYER OF THE GAME Sammy Watkins (137 yards/2 TDs receiving) TEAM STATISTICS Buffalo Bills Baltimore Ravens First Downs 23 16 – Rushing 7 4 – Passing 14 12 – Penalty 2 0 3rd Down Eff 4/11 9/17 4th Down Eff 0/0 2/2 Rushes-Yards 44-161 34-75 Avg Rush 3.7 2.2 Comp-Att-Int 16-21-0 16-24-0 … Continue reading
Tips and tricks:
1. When RetroArch is launched by RocketLauncher, it still will use per-core settings if you have it enabled in RetroArch. However, rather then naming the config file after the core, you have to name it after the gaming platform. The easiest way to make it work is to make a copy of the per-core config from RetroArch in the same directory/folder, but rename it to the name of the system used by RocketLauncher. Example:
If you are using the Nestopia core and per-core settings in RetroArch, the config file is called nestopia_libretro.cfg.
Make a copy of it in the same folder and rename it Nintendo Entertainment System.cfg
Now when you load RetroArch and play an NES game, that config will load. You can even press F1 and see that config is loaded, and save changes directly to it (i.e. change to shader, controller, etc.)
2. In RetroArch the default exit key is the Esc button. You can set it to use one – or two simultaneous – controller button(s) in the Input Hotkey Binds. See video below:
If you’ve been using RocketLauncher with another front end (i.e. HyperSpin or the like) I recommend you look at Simply Austin’s video tutorial on integrating your already created RocketLauncher profiles: Exiting games when using RocketLauncher as “go-between” using controller.
Works with BigBox version of LaunchBox as front-end. Does not seem to work when using the default LaunchBox desktop mode. Pressing “Esc” key still works from either. Update: It does work from LaunchBox.
In LaunchBox, make sure you have the “use controller automation to control Windows outside of Launchbox” enabled. Then when you press down on the “Hold this button” selected button, and press the “Close the active window” button it will exit the emulator and RocketLauncher and return to BigBox.
Using buttons 10 as initiation button and 9 as the action (close) button on my Xbox360/Xbone controllers means when I depress the left stick, hold it down, and while holding it down depress the right stick it will exit the emulator returning me to BigBox. Per-game/Per-core settings when using RocketLauncher and RetroArch.
See the RetroArch post. Bottom line: RocketLauncher does use per-core and/or per-game settings natively, but you have to name the config file (XXX.cfg) to the … Continue reading
I’m a big fan of emulation on the PC of old(er) games; arcade, home systems, even older computer games.
This will be organized by topic concerning some of the larger groups that either allow you to play the games (i.e. the hardware emulator) or allow you to play them more easily (i.e. front ends or collections).
Generally speaking, you use a hardware emulator to run the game software for a specific system. If you only want to emulate arcade video games, you could use the hardware emulation built into MAME to run the software for each video game. If you want to run games on the Wii or GameCube you could use the Dolphin hardware emulator.
The hardware emulator is like having the actual console or arcade inner workings on your computer. You still need the actual game to play ON the hardware emulator – a ROM for an arcade game, or one of the CDs/DVDs/cartridges from the home systems. Just like you plug in a cartridge into a Supre Nintendo (SNES), you load the game software into the SNES hardware emulator.
If you want to emulate multiple hardware devices, it is convenient to have a front end. You choose the game you want to play, and it loads the correct hardware emulator and loads the software of the game into that hardware emulator.
Finally, in between the hardware emulator and the front end there are some systems – I call them launchers – that add to the experience either … Continue reading