├── .github └── ISSUE_TEMPLATE │ └── bug_report.yaml └── README.md /.github/ISSUE_TEMPLATE/bug_report.yaml: -------------------------------------------------------------------------------- 1 | name: Game Compatibility 2 | description: Add a new game to the compatibility database 3 | title: "" 4 | labels: ["triage"] 5 | body: 6 | - type: checkboxes 7 | attributes: 8 | label: Is there an existing issue for this? 9 | description: Search to see if an issue already exists for this game 10 | options: 11 | - label: I have searched the existing issues 12 | required: true 13 | - type: input 14 | id: build 15 | attributes: 16 | label: Tested Build 17 | description: Enter the GitHub Releases build number of the build tested (It should be `{Version}` E.g. `1.0.0`) 18 | placeholder: #1337 19 | validations: 20 | required: true 21 | - type: dropdown 22 | id: androidversion 23 | attributes: 24 | label: Android Version 25 | options: 26 | - 16 27 | - 15 28 | - 14 29 | - 13 30 | - 12 31 | - 11 32 | - 10 33 | default: 0 34 | validations: 35 | required: true 36 | - type: dropdown 37 | id: socvendor 38 | attributes: 39 | label: SoC type 40 | options: 41 | - Snapdragon 42 | - Mediatek 43 | - Exynos 44 | - Kirin 45 | - Tegra 46 | - UNISOC 47 | - Other 48 | validations: 49 | required: true 50 | - type: input 51 | id: specs 52 | attributes: 53 | label: "Device GSMArena link" 54 | description: "[GSMArena](https://www.gsmarena.com/)" 55 | placeholder: "https://www.gsmarena.com/" 56 | validations: 57 | required: true 58 | - type: textarea 59 | id: behaviour 60 | attributes: 61 | label: Game Behaviour 62 | description: Screenshots and a descripton of what works and what doesn't 63 | placeholder: | 64 | "- Mario's left eye is missing " 65 | "- Audio is broken" 66 | "Screenshots of game: " 67 | validations: 68 | required: true 69 | - type: checkboxes 70 | attributes: 71 | label: Is Log Level is set to 'Info'? 72 | description: Log Level must be set to `Info` for all attached logs 73 | options: 74 | - label: "Yes" 75 | required: true 76 | - type: textarea 77 | id: log 78 | attributes: 79 | label: Log file 80 | description: Please attach a zipped emulator log file (can be saved with button next to settings) 81 | validations: 82 | required: true 83 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ### [Strato's](https://github.com/strato-emu/strato) Compatibility List 2 | A repository with [**GitHub Issues**](https://github.com/strato-emu/compat-list/issues) of Nintendo Switch titles and their corresponding compatibility status with Strato, reporting regressions and progression in a title's status (`nothing`, `boots`, `ingame` or `playable`) alongside tagging them with metadata for efficient retesting and tracking what the most pertinent issues may be for focusing development efforts. 3 | 4 | #### How do I contribute? 5 | You can start contributing by checking if any title you want to test already has a [**issue**](https://github.com/strato-emu/compat-list/issues) by using the search feature: 6 | * **If you can find one**: You can comment on the existing issue given what you see compatibility differs from the previous report. It is recommend to tag along a Strato log (with log level `Info`) and clearly describe the differences you're seeing with a brief description of your device. 7 | * **If you cannot find an existing report**: You can go ahead and [create an issue](https://github.com/strato-emu/compat-list/issues/new/choose) for it by filling all the details in the form. 8 | 9 | #### Should I include a image/video of Strato? 10 | As a general guideline, media should be included when it is useful to do so and provides information that cannot be conveyed via text, these guidelines serve as a rough idea of why they may be important in certain circumstances and not in others. Additionally, any media captured **must** be a direct screen capture rather than an external recording using another phone or a camera. If it is impossible to do so due to the nature of the bug, this can be ignored but generally it shouldn't be. 11 | * **Crash**: A photo/video is generally useless in the case of a crash as the log *should* contain the crash, it may not in certain cases and we can request them in a further comment and in those cases the guidelines of a **Freeze** can be utilized. 12 | * **Freeze**: A video is generally useful to fully understand what the bug is and in this case it should be included, it is important to have the **Show Performance Statistics** enabled in this case as it helps us determine the exact point of the freeze. 13 | * **Auditory Glitch**: A video is useful when there are random dropouts in audio or if it doesn't sound correct, an exception is when the game is not playing any audio at all in which case there is no need to upload a image/video. 14 | * **Visual Bug/Glitch**: At minimum, a photo is required here when the glitching is persistent. A video is useful if the glitch is very visually diverse or pops in occassionally rather than being persistent. 15 | 16 | #### I can't upload a Strato Log (`.log`) to GitHub? 17 | GitHub only allows uploading files with a subset of extensions, it is recommended to rename the extension to `.txt` or zip the log and then upload it. If the zipped file cannot be uploaded due to being too large as a last resort you can use an external file hoster such as [Google Drive](https://drive.google.com/) or [Mega](https://mega.nz/) (Decryption key **must** be included in the URL). 18 | --------------------------------------------------------------------------------