Command Line Parameters
Compatibility Matrix
Example Usage
--bios
| Compatibility | |
|---|---|
| All | ✅ |
Path to a specific PS1 BIOS file to load.
--bios="bios/SCPH5501.BIN"
--bios-hide-sce-osd
| Compatibility | |
|---|---|
| Syphon Filter V1.00+ | ✅ |
Hides the PS1 start up logos.
--bios-hide-sce-osd=1
--image
| Compatibility | |
|---|---|
| All | ✅ |
Path to a specific PS1 disc image to load.
--image="data/MediEvil(EUS).bin"
--image%d
| Compatibility | |
|---|---|
| Syphon Filter V1.00+ | ✅ |
Sets the path to a specific PS1 disc image with disc id %d.
Supports 0 to 7 (ie. 8 discs)
--image0="ResidentEvil2_SLUS00748_SCEA_EN.bin"
--image1="ResidentEvil2_SLUS00756_SCEA_EN.bin"
--imageName%d
| Compatibility | |
|---|---|
| Syphon Filter V1.01+ | ✅ |
Sets a name to be displayed on the Change Disc menu for disc id %d.
Supports 0 to 7 (ie. 8 discs)
Should be used in conjunction with --image%d.
--image0="ResidentEvil2_SLUS00748_SCEA_EN.bin"
--imageName0="Resident Evil 2 Leon"
--image1="ResidentEvil2_SLUS00756_SCEA_EN.bin"
--imageName1="Resident Evil 2 Claire"
--mtap-to-host-pad
| Compatibility | |
|---|---|
| Rally Cross V1.00+ | ✅ |
Allows you to define how the host (PS4) controllers are assigned to the PS1 multitap slots.
A value -1 would seem to imply the controller slot is not connected.
A value of 0 (Player 1) through 3 (Player 4) can be assigned (presumably up to 7 could be assigned, but the PS4 only connects 4 controllers).
The value for the command appears to assign the controller slots in the following comma seperated order:
| 1A | 2A | 1B | 1C | 1D | 2B | 2C | 2D |
|---|
# Multitap connected to port 1 (1A), 1B, 1C, 1D
# Nothing connected to port 2
# PORTS MULTI 1 MULTI 2
# 1 2 1B 1C 1D 2B 2C 2D
# PS4 Player 1 - 2 3 4 - - -
--mtap-to-host-pad=0,-1, 1,2,3, -1,-1,-1
Rally Cross includes configuration which connects player 1 to port 1, and the multitap (players 2 to 4) on port 2:
# Player 1 connected to port 1
# Multitap connected to port 2 (2A), 2B, 2C, 2D
# Enable 4 player multitap. Rally Cross wants the multitap mapped to Port #2
# PORTS MULTI 1 MULTI 2
# 1 2 1B 1C 1D 2B 2C 2D
# PS4 Player 1 2 - - - 3 4
--mtap-to-host-pad=0,1, -1,-1,-1, 2,3,4
--region
| Compatibility | |
|---|---|
| All | ✅ |
--region="SCEA"
--pad-analog-button
| Compatibility | |
|---|---|
| Rally Cross V1.00+ | ✅ |
Sets the state of the analog button for all controllers.
--pad-analog-button=1
When set to 0 the emulator outputs:
(JoyPort 0) Analog button status changed by app to '0'
(JoyPort 1) Analog button status changed by app to '0'
(JoyPort 2) Analog button status changed by app to '0'
(JoyPort 3) Analog button status changed by app to '0'
(JoyPort 4) Analog button status changed by app to '0'
(JoyPort 5) Analog button status changed by app to '0'
(JoyPort 6) Analog button status changed by app to '0'
(JoyPort 7) Analog button status changed by app to '0'
--pad%d-plug-state
| Compatibility | |
|---|---|
| Rally Cross V1.00+ | ✅ |
No examples from official releases
Sets the state of a specific PS1 controller to always be seen as connected.
The PS1 supported 8 controllers (with 2 multitaps) and each pad number seems to correspond to a fixed controller slot:
| PS1 Controller Slot | Pad Number |
|---|---|
| 1 (1A) | 0 |
| 2 (1B) | 1 |
| 1B | 2 |
| 1C | 3 |
| 1D | 4 |
| 2B | 5 |
| 2C | 6 |
| 2D | 7 |
# Force controllers in ports 1 and 2 to always be connected
--pad0-plug-state=1
--pad1-plug-state=1
This can be useful for testing multitap configurations when you only have access to a limited number of actual controllers.
For example when you have a multitap connected to port 1 with 4 controllers connected to it, you could configure controllers 2 to 4 to always be connected. You can then swap users in the PS4 to test different player slots.
# Force controllers in ports 1B, 1C, 1D to always be connected
--pad2-plug-state=1 # Player 2
--pad3-plug-state=1 # Player 3
--pad4-plug-state=1 # Player 4
# You can of course also make the controller in 1A always connected too:
--pad0-plug-state=1 # Player 1
--pace-gpu-dma
| Compatibility | |
|---|---|
| Syphon Filter V1.00+ | ✅ |
--pace-gpu-dma=true
--scale
| Compatibility | |
|---|---|
| All | ✅ |
Configures the uprendering scale. When used on a version of the emulator that loads Visual Preset configuration from JSON files (ie. files with /app0/global/presets) then this option will supersede any uprendering configuration from those presets.
From Syphon Filter V1.00 the emulator supported up a 6x scale, at some point since then this has been extended to 9x scale.
The Default visual preset uses a 4x scale.
Console Output from v1.9 (Tekken 3 V1.01)
| Upscale Factor | Frame Buffer | Console Output |
|---|---|---|
| No Scale (1) | 1024 x 512 | (GPU) resetScale(1, AAMode::NoAA): framebuffer=1024,512 |
| 2 | 2048 x 1024 | (GPU) resetScale(2, AAMode::NoAA): framebuffer=2048,1024 |
| 3 | 3072 x 1536 | (GPU) resetScale(3, AAMode::NoAA): framebuffer=3072,1536 |
| 4 | 4096 x 2048 | (GPU) resetScale(4, AAMode::NoAA): framebuffer=4096,2048 |
| 5 | 5120 x 2560 | (GPU) resetScale(5, AAMode::NoAA): framebuffer=5120,2560 |
| 6 | 6144 x 3072 | (GPU) resetScale(6, AAMode::NoAA): framebuffer=6144,3072 |
| 7 | 7168 x 3584 | (GPU) resetScale(7, AAMode::NoAA): framebuffer=7168,3584 |
| 8 | 8192 x 4096 | (GPU) resetScale(8, AAMode::NoAA): framebuffer=8192,4096 |
| 9 | 9216 x 4608 | (GPU) resetScale(9, AAMode::NoAA): framebuffer=9216,4608 |
# x1=1280x720, x2=1920x1080, x4=3840x2160
--scale=1
--scale=6
--texrecent
| Compatibility | |
|---|---|
| MediEvil | ✅ |
| Syphon Filter V1.00+ | ❌ |
--texrecent=true
--uprender-scale
| Compatibility | |
|---|---|
| Phantom Menance V1.00+ | ✅ |
No examples from official releases
Configures the uprendering scale. Seems to have the same functionality as existing parameter --scale.
# Set uprendering to 6x
--uprender-scale=6
--userui-remap-%s-pad%d
| Compatibility | |
|---|---|
| Rally Cross V1.00+ | ✅ |
No examples from official releases
Allows remapping of controller buttons.
This parameter does not seem to work in newer versions of the emulator such as Tekken 3 V1.01.
If you want to programmatically configure controls on such versions, consider using the LUA function EM_SetRemapBinding. Control remaps configured via that are also reflected in the user facing Customise Button Assignments menu option.
The syntax appears to be:
--userui-remap-ps1-pad[0-3]=host_button:ps1_button, host_button:ps1_button
The pad values (0 to 3), seem to map to the PS4 player number rather than the PS1 pad numbers.
| Host Buttons (DS4) | PS1 Buttons |
|---|---|
| cross | cross |
| circle | circle |
| triangle | triangle |
| square | square |
| l1 | l1 |
| r1 | r1 |
| l2 | l2 |
| r2 | r2 |
| l3 | l3 |
| r3 | r3 |
| left | left |
| right | right |
| up | up |
| down | down |
| lstick.left | lstick.left |
| lstick.right | lstick.right |
| lstick.up | lstick.up |
| lstick.down | lstick.down |
| rstick.left | rstick.left |
| rstick.right | rstick.right |
| rstick.up | rstick.up |
| rstick.down | rstick.down |
| tpad_left | |
| tpad_right | |
| start |
# Remap Player 1 and Player 2
# Cross button to Triangle
# Triangle button to Cross
# Remap Player 1 DS4 PS1 DS4 PS1
--userui-remap-ps1-pad0=cross:triangle, triangle:cross
# Remap Player 2 DS4 PS1 DS4 PS1
--userui-remap-ps1-pad1=cross:triangle, triangle:cross
# Remap Player 1 and Player 2
# Quake 2 "Both Sticks" control scheme has strafe and turn on the wrong
# analog sticks, relative to a modern control scheme.
# This swaps the x-axis between analog sticks so move and strafe are on the left stick
# and turn and look up/down are on the right.
# Remap Player 1 DS4 PS1 DS4 PS1 DS4 PS1 DS4 PS1
--userui-remap-ps1-pad0=lstick.left:rstick.left, lstick.right:rstick.right, rstick.left:lstick.left, rstick.right:lstick.right
# Remap Player 2 DS4 PS1 DS4 PS1 DS4 PS1 DS4 PS1
--userui-remap-ps1-pad1=lstick.left:rstick.left, lstick.right:rstick.right, rstick.left:lstick.left, rstick.right:lstick.right
If you supply bad configuration, the emulator will output a message like:
ReportError --userui-ps1-remap-pad has an unknown PS1 button name=
--userui-reset-options
| Compatibility | |
|---|---|
| Syphon Filter V1.04+ | ✅ |
No examples from official releases
Resets the user configurable options within the emulators menus (ie. the settings saved within imgui_emu_option.json).
While the settings are immediately reset when the emulator is started with this command, the changes are only persisted if the user then does something that triggers a save of imgui_emu_option.json (such as changing a setting, or loading a save state). Otherwise the users original settings will be loaded again the next time the emulator is started without this parameter.
--userui-reset-options=1
--userui-settings-graphics
| Compatibility | |
|---|---|
| Syphon Filter 2 V1.00+ | ✅ |
No examples from official releases
Enables access to the Graphics emulator menu, which includes options:
Newer versions of the emulator have added support for additional uprendering scale factors (up to 9x scale), but this menu remains hardcoded to only display up to 6x.
- Uprendering scale factor (No upscale -> 6x scale)
- Filter (None Bicubic, Lanczos, Cubic)
- Anti-Aliasing (None, FXAA, CMAA)
# Enable emulator Graphics menu
--userui-settings-graphics=1