Batch-Powered Emulation v1.2
my gracious donators,
retroInvader Desktop Icons
This tool configures retroInvader & retroarch.
Drag & drop BIOS files to this icon to install them.
( RAR / 7z / ZIP supported)
This tool launches retroInvader.
Drag & drop a ROM file to this icon.
A selction of multiple ROMs can create a playlist, be appended to the retroInvader history file or assigned per-game configuration files.
The retroHost icon will appear on your desktop after hosting.
To host a ROM, drag & drop it to this icon.
Use the shift and ctrl keys to select multiple items.
You can drag and drop BIOS files onto the RIConfig desktop icon. retroInvader will detect and configure any compatible matches. RAR, zip and 7zip files are supported too. Files are cataloged inside
Creating a singular configruation for a folder of ROMs will use the most current settings for both the core and retroarch.
Using a template (selecting a retroarch configuration you've saved which works optimally) you can easily propagate any setup for a folder of ROMs.You can drag & drop a selection of ROMs to the retroDrop desktop icon and select ''Config'' to assign a template for per-game configurations
Each core wll load a configuraiton file and any ROM which has a .opt override in the core's delta-folder.
Deltas files are saved in a core folder named as "ROM NAME.cfg"
eg: C:\retroarch\snes9x\Stuper Face-Basher 3.cfg
.opt files are core-override configuration files.
Changes made to delta overrides must be explicitly saved from within the UI. Deltas which have been saved exclusively from within the Deltas mode will not be loaded in FULL mode
Each ROM loads a complete retroarch.cfg file which is then saved as a Delta file in the loaded core's folder inside the root of the retroArch directory.
Any changes made to a ROM in FULL mode will be saved as a Delta file.
To maximize performance the default options retroInvader sets for retroArch are designed for a low-spec machine in fullscreen mode. When selecting custom options, presing the enter key will chose the default and most compatible choice.
-RESET- Resets all system-core relationships
To facilitate controlling retroArch and navigate Windows using simple joystick key-combinations, a Joystick mapper (Xpadder and antimicro currently supported) can be used to load a profile before and after running retroArch. Profiles for xinput (eg: 360/XBO) joysticks are included.
antimicro users should start antimicro before retroInvader.
Keyboard mappings are used to control retroArch and navigate Windows
Player1 and Player2 profiles are loaded prior to launching retroArch.
The "Desk" profile is loaded after retroArch exits.
If the ROM is not found in the retroInvader history file, the user is prompted to select it. If the host string contains a url link to a ROM, and it is not found in the retroInvader history, it will be downloaded to the retroArch directory if needed. (ROMs will be appended to the retroInvader history file when retroArch closes )
The hosting feature allows you to host any ROM if the selected core supports netplay. Users must forward a port on their router or connect directly to the internet to host a netplay session . Once the host has selected a ROM (or url link), the host can then paste (ctrl+v) to a chat window for player 2 to copy.
Press the "HOST" button when you are ready for player 2 to connect.
Many users will be using retroArch's GUI to browse their libraries and creating playlists with retroInvader is very convenient
Only files with compatible extensions for the selected core will be added to your playlist, however any ZIP files will be added (for non-disc systems).
Any file added to the retroInvader history file is automatically launched by the associated core. Ony files which are not automatically detected by retroDrop are appended to the history.
Because there are several extensions shared amongst several cores, it may be desireable to quickly assign a group of ROMs to retroInvader's history file.
Only files with compatible extensions for the selected core will be added to your playlist, including .zip files (for cores that can launch them).
You can drag & drop a selection of multiple ROMs onto the retroDrop desktop icon to append to the retroInvader history for any core.
The history file is infinite in size, however be aware that adding thouands of ROMs to it may increase load times on slower disk drives. The history file can be found in
"retroarch installation folder\history.ini".
Several standalone emulators for retroArch's supported systems can be easily downloaded and installed from within retroInvader, however many users will want a single file to install all supported emulators. A 64-bit and 32-bit installer have been compiled for your convenience.
An emulators directory which should contain many folders of emulators can be scanned by retroInvader. Detected emulators will automatically populate your un-assigned system-overrides.
Assigning the default emulator will enable a set of compatible options, however cutom settings can be defined for any emulator, including:
argumentsdeclared after the ROM
optionsdeclared before the ROM
Quotes and paths for ROMs and names
2 configuration files
Each system can be assigned an override emulator with pre-defined or custom settings.
If per-game overrides have been enabld, any configuration files specified from a custom config will be copied from the eg: ../retroInvader\Emulator\SYSTEM_emulator\config.ini to the emulator's root directory upon launch.
To reset the emulator assigned for a sytem, select a system/s and ####RESET####.
Emulator overrides can be set to directly launch ROMs or alternatively be presented in a menu of supported cores & intalled emulators.
This feature will enable override options for any ROM dropped to retroDrop, and any ROM in the retroInvader history..
Per-Game configurations are not supported for emulator-overrides at this time and a per-emulator_system configuration is used until it's fleshed out.
Double clicking on the retroDrop desktop icon can launch retroArch, start the invader utility, search or browse the Internet Archive's retro ROM-libraries.
Most ROM files should be detected, however disc-images as well as several other ROM extensions are shared amongst several systms, so if you decide not to append a folder of ROMs to your history, or simply wish to test an unidentified ROM file, retroInvader provides a simple interface to launch, and ease the appending of individual ROMs to your history.
You can drag & drop a selection of multiple ROMs onto the retroDrop desktop icon to create a playlist, generate pre-game deltas or append to the retroInvader history file for any core.
(A .cue file is automatically generated and launched for disc-images which may need one.)
F.A.Q & ANSWERS
Question: Can I send my ROM to another player with retroInvader?
Answer: Not yet.
Question: RetroInvader was just working. Now it won't start. What happened?
Answer: Exit the joytick mapper (antimicro/xpadder) from the tray menu or end the program in the task-manager and try again.
Question: I'm having a problem with retroArch