[GH-ISSUE #3723] [Feature Request]: Updating repository information in connection with future changes in the emulator's operation #1106

Closed
opened 2026-02-27 21:09:57 +03:00 by kerem · 10 comments
Owner

Originally created by @GHU7924 on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3723

Checklist

  • I have searched for a similar issue in this repository and did not find one.

Description

The emulator will soon be split into two parts: the code and the graphical interface. A separate QtLauncher repository has already been created, so we should update the templates with new options that will redirect users to the new repository if their issue is related to a problem or improvement of the graphical interface.

We also need to update the Wiki because a lot of the information will be outdated and some of the new features are missing.

Reason

To be honest, it's become less convenient to keep track of updates due to the separation of repositories, but on the other hand, this may be the right decision because sdl and qt can differ greatly. I think users will be willing to accept this, but the repository should then contain up-to-date information so that users have fewer questions and you are not distracted by trivial matters.

Examples

There are clearly missing new templates or a link to the QtLauncher repository; perhaps the description should be corrected somewhere.

Image
Originally created by @GHU7924 on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3723 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. ### Description The emulator will soon be split into two parts: the code and the graphical interface. A separate QtLauncher repository has already been created, so we should update the templates with new options that will redirect users to the new repository if their issue is related to a problem or improvement of the graphical interface. We also need to update the Wiki because a lot of the information will be outdated and some of the new features are missing. ### Reason To be honest, it's become less convenient to keep track of updates due to the separation of repositories, but on the other hand, this may be the right decision because sdl and qt can differ greatly. I think users will be willing to accept this, but the repository should then contain up-to-date information so that users have fewer questions and you are not distracted by trivial matters. ### Examples There are clearly missing new templates or a link to the QtLauncher repository; perhaps the description should be corrected somewhere. <img width="1603" height="734" alt="Image" src="https://github.com/user-attachments/assets/13aa07d5-e1b9-4b63-a8d3-fbed123b7164" />
kerem closed this issue 2026-02-27 21:09:57 +03:00
Author
Owner

@georgemoralis commented on GitHub (Oct 9, 2025):

Still there isn't an ETA about when qtlauncher will be release to replace the qt interface of the emulator. When it is ready to go , sure we have to adjust things here and there. If you have any suggestion feel free to open a pr ;)

<!-- gh-comment-id:3384219703 --> @georgemoralis commented on GitHub (Oct 9, 2025): Still there isn't an ETA about when qtlauncher will be release to replace the qt interface of the emulator. When it is ready to go , sure we have to adjust things here and there. If you have any suggestion feel free to open a pr ;)
Author
Owner

@GHU7924 commented on GitHub (Oct 9, 2025):

Still there isn't an ETA about when qtlauncher will be release to replace the qt interface of the emulator. When it is ready to go , sure we have to adjust things here and there. If you have any suggestion feel free to open a pr ;)

Regarding the release

The question here is how you plan to release v0.12.0. Will it contain Qt (which is no longer updated, which in theory makes the release more stable in terms of the graphical interface) or the release will contain only sdl versions and information that starting with this release, all future releases will not contain the Qt interface. Most likely, updates will have to be disabled for Qt versions of the emulator (if they are released) to avoid conflicts.

Next, if the user needs a graphical interface for the emulator in the future, they should go to the QtLauncher repository and download QtLauncher (particularly if using the Nightly update channel). They should uninstall the existing emulator version, replacing it with the QtLauncher version, and also delete the shadPS4 folder to avoid settings conflicts. It's also worth mentioning that the user doesn't need to download shadPS4 separately, as they can easily download the desired emulator version from QtLauncher if they use the version with a graphical interface (I hope that by the time of release PR Version Manager will be merged).

Regarding Wiki

As for the Wiki, I think it can already be updated, since QtLauncher already exists (even if in beta mode). It's just worth adding a suggestion (possibly temporarily) that the Wiki is current for emulator v0.11.1 (v0.12.1) and QtLauncher v0.11.1. (v0.12.1), for example. I don't think the Wiki should be divided into new and old, because the emulator is evolving and shouldn't be slowed down by outdated data.

P.S. I would be happy to open a PR, but I'm an ordinary user who doesn't understand much about this and is far from it, so I would entrust this to someone who has at least already participated in writing the Wiki, for example.

<!-- gh-comment-id:3385834381 --> @GHU7924 commented on GitHub (Oct 9, 2025): > Still there isn't an ETA about when qtlauncher will be release to replace the qt interface of the emulator. When it is ready to go , sure we have to adjust things here and there. If you have any suggestion feel free to open a pr ;) Regarding the release The question here is how you plan to release v0.12.0. Will it contain Qt (which is no longer updated, which in theory makes the release more stable in terms of the graphical interface) or the release will contain only sdl versions and information that starting with this release, all future releases will not contain the Qt interface. Most likely, updates will have to be disabled for Qt versions of the emulator (if they are released) to avoid conflicts. Next, if the user needs a graphical interface for the emulator in the future, they should go to the QtLauncher repository and download QtLauncher (particularly if using the Nightly update channel). They should uninstall the existing emulator version, replacing it with the QtLauncher version, and also delete the shadPS4 folder to avoid settings conflicts. It's also worth mentioning that the user doesn't need to download shadPS4 separately, as they can easily download the desired emulator version from QtLauncher if they use the version with a graphical interface (I hope that by the time of release PR Version Manager will be merged). Regarding Wiki As for the Wiki, I think it can already be updated, since QtLauncher already exists (even if in beta mode). It's just worth adding a suggestion (possibly temporarily) that the Wiki is current for emulator v0.11.1 (v0.12.1) and QtLauncher v0.11.1. (v0.12.1), for example. I don't think the Wiki should be divided into new and old, because the emulator is evolving and shouldn't be slowed down by outdated data. P.S. I would be happy to open a PR, but I'm an ordinary user who doesn't understand much about this and is far from it, so I would entrust this to someone who has at least already participated in writing the Wiki, for example.
Author
Owner

@georgemoralis commented on GitHub (Oct 9, 2025):

0.12.0 will be sdl only

For the others questions i will read them and answer later ;)

<!-- gh-comment-id:3385989943 --> @georgemoralis commented on GitHub (Oct 9, 2025): 0.12.0 will be sdl only For the others questions i will read them and answer later ;)
Author
Owner

@Missake212 commented on GitHub (Oct 9, 2025):

0.12.0 will be sdl only

For the others questions i will read them and answer later ;)

So the plan for 0.12.0 and onward is to make people download two different exe instead of shipping them as one if they want a GUI? I really don't understand the reasoning

<!-- gh-comment-id:3385998476 --> @Missake212 commented on GitHub (Oct 9, 2025): > 0.12.0 will be sdl only > > For the others questions i will read them and answer later ;) So the plan for 0.12.0 and onward is to make people download two different exe instead of shipping them as one if they want a GUI? I really don't understand the reasoning
Author
Owner

@StevenMiller123 commented on GitHub (Oct 9, 2025):

I believe the intent is that you download the launcher you want, and that will take care of the emulator setup for you.
Separating the GUI and emulator executable is necessary to work around some of the issues seen in games, so this transition would've needed to happen eventually.

<!-- gh-comment-id:3386012306 --> @StevenMiller123 commented on GitHub (Oct 9, 2025): I believe the intent is that you download the launcher you want, and that will take care of the emulator setup for you. Separating the GUI and emulator executable is necessary to work around some of the issues seen in games, so this transition would've needed to happen eventually.
Author
Owner

@GHU7924 commented on GitHub (Oct 9, 2025):

So the plan for 0.12.0 and onward is to make people download two different exe instead of shipping them as one if they want a GUI? I really don't understand the reasoning

You won't need to download two different executables; you'll just need to download QtLauncher, which will allow you to quickly and easily download the emulator without visiting GitHub. @Missake212, try PR 66 in the QtLauncher repository and you'll see. The main thing is to inform users during the release so that they don’t have any questions.

0.12.0 will be sdl only

In that case, I think the information can safely be updated, at least partially.

  1. Issues -> New issue = New link to the QtLauncher repository for GUI-related issues.
  2. Wiki - II. Setting up shadPS4 [Users] = The information is significantly outdated, and there is no information about new features (Customize Hotkeys, Game-Specific Settings).

Information in the "Quick Start" section [Users], on the website, in the release notes, and other materials will be updated immediately before the release.

<!-- gh-comment-id:3386071066 --> @GHU7924 commented on GitHub (Oct 9, 2025): >So the plan for 0.12.0 and onward is to make people download two different exe instead of shipping them as one if they want a GUI? I really don't understand the reasoning You won't need to download two different executables; you'll just need to download QtLauncher, which will allow you to quickly and easily download the emulator without visiting GitHub. @Missake212, try [PR 66](https://github.com/shadps4-emu/shadps4-qtlauncher/pull/66) in the QtLauncher repository and you'll see. The main thing is to inform users during the release so that they don’t have any questions. >0.12.0 will be sdl only In that case, I think the information can safely be updated, at least partially. 1) Issues -> New issue = New link to the QtLauncher repository for GUI-related issues. 2) Wiki - II. Setting up shadPS4 [Users] = The information is significantly outdated, and there is no information about new features (Customize Hotkeys, Game-Specific Settings). Information in the "Quick Start" section [Users], on the website, in the release notes, and other materials will be updated immediately before the release.
Author
Owner

@Francyemu226 commented on GitHub (Oct 10, 2025):

With shadPS4 all the configuration and user folders were in the same "shadPS4" folder while with shadPS4QtLauncher the configuration is under "..\AppData\Roaming\shadPS4" will it be possible to have it under the same folder as it happened in shadPS4, so as to have everything under a single folder ?

So there will also be two updates, one for "shadPS4QtLauncher" and one for "shadPS4"? How will it work ?

<!-- gh-comment-id:3388339781 --> @Francyemu226 commented on GitHub (Oct 10, 2025): With shadPS4 all the configuration and user folders were in the same "shadPS4" folder while with shadPS4QtLauncher the configuration is under "..\AppData\Roaming\shadPS4" will it be possible to have it under the same folder as it happened in shadPS4, so as to have everything under a single folder ? So there will also be two updates, one for "shadPS4QtLauncher" and one for "shadPS4"? How will it work ?
Author
Owner

@georgemoralis commented on GitHub (Oct 10, 2025):

With shadPS4 all the configuration and user folders were in the same "shadPS4" folder while with shadPS4QtLauncher the configuration is under "..\AppData\Roaming\shadPS4" will it be possible to have it under the same folder as it happened in shadPS4, so as to have everything under a single folder ?

So there will also be two updates, one for "shadPS4QtLauncher" and one for "shadPS4"? How will it work ?

yes that folder thing is one of our biggest worries atm . We are discussing to find the most proper solution

<!-- gh-comment-id:3388435015 --> @georgemoralis commented on GitHub (Oct 10, 2025): > With shadPS4 all the configuration and user folders were in the same "shadPS4" folder while with shadPS4QtLauncher the configuration is under "..\AppData\Roaming\shadPS4" will it be possible to have it under the same folder as it happened in shadPS4, so as to have everything under a single folder ? > > So there will also be two updates, one for "shadPS4QtLauncher" and one for "shadPS4"? How will it work ? yes that folder thing is one of our biggest worries atm . We are discussing to find the most proper solution
Author
Owner

@Francyemu226 commented on GitHub (Oct 12, 2025):

Perhaps it would be enough to add the path to the emulator's system files to the "patch" section, so everyone can put them wherever they want, so as not to be restricted by "..\AppData\Roaming\shadPS4" and, above all, move the shadPS4 folder to a desired drive.

Perhaps, as @GHU7924 suggested, an "emu_data" folder and all the necessary files inside it.

<!-- gh-comment-id:3394049613 --> @Francyemu226 commented on GitHub (Oct 12, 2025): Perhaps it would be enough to add the path to the emulator's system files to the "patch" section, so everyone can put them wherever they want, so as not to be restricted by "..\AppData\Roaming\shadPS4" and, above all, move the shadPS4 folder to a desired drive. Perhaps, as @GHU7924 suggested, an "emu_data" folder and all the necessary files inside it.
Author
Owner

@GHU7924 commented on GitHub (Oct 12, 2025):

@georgemoralis I think we can release a beta version of the launcher (to collect errors), and also redirect everyone to a specially created thread (as was done with Bloodborne), so as not to create a bunch of threads about Qtlauncher errors.

shadPS4QtLauncher (beta) (first temporary release), then, based on the first reviews, after a couple of weeks, say, replace it with the first release version.

<!-- gh-comment-id:3394248412 --> @GHU7924 commented on GitHub (Oct 12, 2025): @georgemoralis I think we can release a beta version of the launcher (to collect errors), and also redirect everyone to a specially created thread (as was done with Bloodborne), so as not to create a bunch of threads about Qtlauncher errors. `shadPS4QtLauncher (beta)` (first temporary release), then, based on the first reviews, after a couple of weeks, say, replace it with the first release version.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shadPS4#1106
No description provided.