rpcs3/.github/ISSUE_TEMPLATE/1-regression-report.yml

name: Regression report
description: If something used to work before, but now it doesn't
title: "[Regression] Enter a title here"
labels: []
body:
  - type: markdown
    attributes:
      value: |
        # Summary
        Please do not ask for help or report compatibility regressions here, use [RPCS3 Discord server](https://discord.me/RPCS3) or [forums](https://forums.rpcs3.net/) instead.
  - type: textarea
    id: quick-summary
    attributes:
      label: Quick summary
      description: Please briefly describe what has stopped working correctly.
    validations:
      required: true
  - type: textarea
    id: details
    attributes:
      label: Details
      description: Please describe the regression as accurately as possible. Include screenshots if neccessary.
    validations:
      required: false
  - type: markdown
    attributes:
      value: |
        # Identify the regressed build
        Please provide the _exact_ build (or commit) information that introduced the regression you're reporting.
        * Please see [How to find the build that caused a regression](https://wiki.rpcs3.net/index.php?title=Help:Using_different_versions_of_RPCS3#How_to_find_the_build_that_caused_a_regression.3F) in our wiki.
        * You can find [History of RPCS3 builds](https://rpcs3.net/compatibility?b) here.

        Make sure you're running with settings as close to default as possible
        * **Do NOT enable any emulator game patches when reporting issues**
        * Only change settings that are required for the game to work
  - type: input
    id: regressed-build
    attributes:
      label: Build with regression
      description: Provide _exact_ build (or commit) information that introduced the regression you're reporting.
      placeholder: v0.0.23-13948-31df99f7
    validations:
      required: true
  - type: markdown
    attributes:
      value: |
        # Log files
        Obtaining the log file:
        * Run the game until you find the regression.
        * Completely close RPCS3 and locate the log file.

        RPCS3's Log file will be ```RPCS3.log.gz``` (sometimes shows as RPCS3.log with zip icon) or ```RPCS3.log``` (sometimes shows as RPCS3 wtih notepad icon).
        * On Windows it will be in the RPCS3 directory near the executable
        * On Linux it will be in ```~/.cache/rpcs3/```
        * On MacOS it will be in ```~/Library/Caches/rpcs3```. If you're unable to locate it copy paste the path in Spotlight and hit enter.
  - type: textarea
    id: logs
    attributes:
      label: Attach two log files
      description: |
        Attach one file for the build with regression and another for a build that works.
        Drag & drop the files into this input field, or upload them to another service (f.ex. Dropbox, Mega) and provide a link.
    validations:
      required: true
  - type: markdown
    attributes:
      value: |
        # Other details
        If you describe a graphical regression, please provide an RSX capture and/or a RenderDoc capture that demonstrate it.
        * To create an RSX capture, use _Create_ _RSX_ _Capture_ under _Utilities_.
        * Captures will be stored in RPCS3 folder → captures.
        * To create a RenderDoc capture, please refer to [RenderDoc's documentation](https://renderdoc.org/docs/how/how_capture_frame.html).
  - type: textarea
    id: captures
    attributes:
      label: Attach capture files for visual issues
      description: Compress your capture with 7z, Rar etc. and attach it here, or upload it to the cloud (Dropbox, Mega etc) and add a link to it.
    validations:
      required: false
  - type: textarea
    id: system-info
    attributes:
      label: System configuration
      description: Provide information about your system, such as operating system, CPU and GPU model, GPU driver version and other information that describes your system configuration.
    validations:
      required: false
  - type: textarea
    id: other-details
    attributes:
      label: Other details
      description: Include anything else you deem to be important.
    validations:
      required: false