starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-28 01:06:02 +03:00

[GH-ISSUE #1499] Feature request: skip GUI when launching game directly #506

New issue

Closed

opened 2026-02-27 21:06:38 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 21:06:38 +03:00

Owner

Originally created by @fpiesche on GitHub (Nov 7, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1499

It'd be useful if the main Qt GUI executable didn't bother trying to read the entire game directory when it's launched directly into a game (by calling shadps4 path/to/eboot.bin). Some emulators just do this transparently, others (eg. RPCS3) have a command line flag to disable running the main GUI (in RPCS3's case, --no-gui).

This will make the emulator useful for configuring via the GUI when running it directly with no parameters, while also allowing the same executable to launch into a game directly without having to wait for the game list to build on startup first. This is a common use case with game launchers such as Steam's game mode or things like Launchbox and Playnite.

Ideally this should also launch in fullscreen mode, though doing this could also be handled by a separate command line parameter (that is, just running shadps4 eboot.bin will run the game in windowed mode, while running shadps4 --fullscreen eboot.bin will launch it in fullscreen).

Originally created by @fpiesche on GitHub (Nov 7, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1499 It'd be useful if the main Qt GUI executable didn't bother trying to read the entire game directory when it's launched directly into a game (by calling `shadps4 path/to/eboot.bin`). Some emulators just do this transparently, others (eg. RPCS3) have a command line flag to disable running the main GUI (in RPCS3's case, `--no-gui`). This will make the emulator useful for configuring via the GUI when running it directly with no parameters, while also allowing the same executable to launch into a game directly without having to wait for the game list to build on startup first. This is a common use case with game launchers such as Steam's game mode or things like Launchbox and Playnite. Ideally this should also launch in fullscreen mode, though doing this could also be handled by a separate command line parameter (that is, just running `shadps4 eboot.bin` will run the game in windowed mode, while running `shadps4 --fullscreen eboot.bin` will launch it in fullscreen).

kerem

2026-02-27 21:06:38 +03:00

closed this issue
added the
contributor wanted

enhancement
labels

kerem commented

2026-02-27 21:06:38 +03:00

Author

Owner

@DanielSvoboda commented on GitHub (Nov 7, 2024):

There is the SDL version, which is different from the QT version which has an interface

@DanielSvoboda commented on GitHub (Nov 7, 2024): There is the SDL version, which is different from the QT version which has an interface

kerem commented

2026-02-27 21:06:38 +03:00

Author

Owner

@fpiesche commented on GitHub (Nov 7, 2024):

Yeah - thus in the current setup, a user would need both the SDL and the Qt version installed to be able to direct-launch games without waiting for the game list to populate first, but also have the GUI available for configuration. Making the Qt version skip the GUI, or at least the game list read, when launching an executable directly, would improve QOL for users of the Qt version.

I'll admit I haven't actually used the SDL version; does it meaningfully differ from the Qt version once it gets to actually running a game, e.g. in terms of Wayland support etc?

@fpiesche commented on GitHub (Nov 7, 2024): Yeah - thus in the current setup, a user would need both the SDL and the Qt version installed to be able to direct-launch games without waiting for the game list to populate first, but also have the GUI available for configuration. Making the Qt version skip the GUI, or at least the game list read, when launching an executable directly, would improve QOL for users of the Qt version. I'll admit I haven't actually used the SDL version; does it meaningfully differ from the Qt version once it gets to actually running a game, e.g. in terms of Wayland support etc?

kerem commented

2026-02-27 21:06:38 +03:00

Author

Owner

@DanielSvoboda commented on GitHub (Nov 8, 2024):

The QT version didn't even have a command, I remember that I was the one who added the ability to run the game through the command line in the QT version, just like in SDL, I did this just to be able to create game shortcuts correctly. It's a good idea to have a command to run QT headless, similar to SDL.

@DanielSvoboda commented on GitHub (Nov 8, 2024): The QT version didn't even have a command, I remember that I was the one who added the ability to run the game through the command line in the QT version, just like in SDL, I did this just to be able to create [game shortcuts](https://github.com/shadps4-emu/shadPS4/pull/246) correctly. It's a good idea to have a command to run QT headless, similar to SDL.

kerem commented

2026-02-27 21:06:38 +03:00

Author

Owner

@Hermiten commented on GitHub (Nov 22, 2024):

Can you try the last main version ?:)

@Hermiten commented on GitHub (Nov 22, 2024): Can you try the last main version ?:)

kerem commented

2026-02-27 21:06:38 +03:00

Author

Owner

@DanielSvoboda commented on GitHub (Nov 22, 2024):

Can you try the last main version ?:)

It looks like the shortcut is broken...
then I do more tests

@DanielSvoboda commented on GitHub (Nov 22, 2024): > Can you try the last main version ?:) It looks like the shortcut is broken... then I do more tests

kerem commented

2026-02-27 21:06:38 +03:00

Author

Owner

@Hermiten commented on GitHub (Dec 7, 2024):

Fixed

@Hermiten commented on GitHub (Dec 7, 2024): Fixed

kerem referenced this issue

2026-02-27 21:13:15 +03:00

[PR #506] [MERGED] Untranslocate app bundle path if needed on macOS. #1602