10-30-2020, 10:59 PM
Note: These guidelines are for PS3 non-game applications (such as YouTube, Netflix, Twitch and so on).
a) Check if there's an existent thread for the Title ID you want to report on
- If yes, you must post in that thread
- If not, create a new thread
b) If you're creating a new thread: for thread title write the name of the game and the Title ID in square brackets, in the following format: "Name of the application [ABCD12345]"
- Do not write the game's name in CAPS LOCK and do not include special symbols (symbols that can't be found on the average keyboard like ™).
c) You must include the RPCS3.log and TTY.log files in your post. On Windows, they can be found in the same folder as the RPCS3 executable. On Linux, on .cache/rpcs3.
- You must add them as an attachment by compressing them into a .7z, .gz, or .rar file.
- Do not copy paste output from the emulator's log window as that's NOT the log file, just a short log.
d) You must add screenshots as attachments
- At least one screenshot for Intro, Loadable and Nothing applications
- At least three screenshots for Playable and Ingame applications
e) Your report must follow the template below
- Hacked or work in progress builds are not allowed. Only post results with the latest official master build.
Template:
- Replace the first four lines (RPCS3, CPU, OS, GPU) by the same ones from your RPCS3.log file.
- Take the following reports as examples: Qello Concerts [NPEB02055], TuneIn Radio [NPEB01831]
a) Check if there's an existent thread for the Title ID you want to report on
- If yes, you must post in that thread
- If not, create a new thread
b) If you're creating a new thread: for thread title write the name of the game and the Title ID in square brackets, in the following format: "Name of the application [ABCD12345]"
- Do not write the game's name in CAPS LOCK and do not include special symbols (symbols that can't be found on the average keyboard like ™).
c) You must include the RPCS3.log and TTY.log files in your post. On Windows, they can be found in the same folder as the RPCS3 executable. On Linux, on .cache/rpcs3.
- You must add them as an attachment by compressing them into a .7z, .gz, or .rar file.
- Do not copy paste output from the emulator's log window as that's NOT the log file, just a short log.
d) You must add screenshots as attachments
- At least one screenshot for Intro, Loadable and Nothing applications
- At least three screenshots for Playable and Ingame applications
e) Your report must follow the template below
- Hacked or work in progress builds are not allowed. Only post results with the latest official master build.
Template:
- Replace the first four lines (RPCS3, CPU, OS, GPU) by the same ones from your RPCS3.log file.
- Take the following reports as examples: Qello Concerts [NPEB02055], TuneIn Radio [NPEB01831]
Code:
[b]RPCS3 v0.0.12-11119-f03d4cf8 Alpha | HEAD | Firmware version: 4.86[/b]
[b]Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz | 8 Threads | 15.52 GiB RAM | TSC: 2.592GHz | AVX+ | FMA3 | TSX-FA[/b]
[b]Operating system: POSIX, Name: Linux, Release: 5.9.1-3-MANJARO, Version: #1 SMP PREEMPT Thu Oct 22 20:38:14 UTC 2020[/b]
[b]RSX: Found vulkan-compatible GPU: 'Intel(R) HD Graphics 530 (SKL GT2)' running on driver 20.2.1[/b]
[b]App Version:[/b]
[b]Status:[/b]
[b]Settings:[/b]
-
[b]What works:[/b]
-
[b]What doesn't work:[/b]
-
[b]Untested:[/b]
-
[b]Notes:[/b] (Optional)