name: Bug Report
description: File a Bug report
title: '[BUG] '
labels: bug
#assignees: 'anonymous@temp'
body:
- type: markdown
attributes:
value: |
## Please fill out forms as cleanly as possible.
#### Make sure that you have
* properly edited & filled in the title of this bug report
- type: dropdown
id: version
attributes:
label: Raze version
description: |
What version are you using?
Run `raze --version`
Make sure to update to latest [release](https://github.com/coelckers/Raze/releases) version and test again before continuing.
multiple: false
options:
- 1.1.3
- 1.1.2
- 1.1.1
- 1.1.0
- 1.0.3
- 1.0.2
- 1.0.1
- Git
- Other
validations:
required: true
- type: dropdown
id: OS
attributes:
label: What Operating System are you using?
multiple: false
options:
- Windows 11
- Windows 10
- Windows 8
- Windows 7
- Windows Other
- Mac OS
- Linux x86
- Linux x86_64
- Linux ARM (Raspberry Pi)
- Other
validations:
required: false
- type: input
id: other
attributes:
label: If Other OS, please describe
description: Other details
placeholder: "Windows, Mac OSX version, Debian, Ubuntu, Arch, etc."
validations:
required: false
- type: input
id: hardware
attributes:
label: Relevant hardware info
description: Hardware
placeholder: "CPU, GPU, device brand/model: e.g. Intel, AMD, Nvidia, etc"
validations:
required: false
- type: checkboxes
id: checked
attributes:
label: Have you checked that no other similar issue already exists?
description: Searched issues before creating report?
options:
- label: I have searched and not found similar issues.
required: true
- type: textarea
id: description
attributes:
label: A clear and concise description of what the bug is.
description: Describe what happens, what software were you running? _Include screenshot if possible_
placeholder: "How & When does this occur?"
validations:
required: true
- type: textarea
id: steps
attributes:
label: Steps to reproduce the behaviour.
description: How can we reproduce this?
placeholder: "Explain how to reproduce"
value: |
Explain how to reproduce
1.
2.
3.
validations:
required: false
- type: textarea
id: config_file
attributes:
label: Your configuration
description: |
Share the config file(s) you've been using to run the program. (`dosbox-staging.conf`)
Please avoid pasting the full config, _use attachments or links_
placeholder: "example: texture_renderer = opengl"
render: ini # syntax highlighting
validations:
required: false
- type: textarea
id: log
attributes:
label: Provide a Log
description: Please avoid pasting the full log, _use attachments or links_
placeholder: "Copy & paste error log section or provide link"
validations:
required: false
- type: checkboxes
id: terms
attributes:
label: Code of Conduct & Contributing Guidelines
description: By submitting this issue, you agree to follow our [contributing guidelines](https://docs.github.com/articles/github-community-guidelines) and code of conduct.
options:
- label: Yes, I agree.
required: true
- type: markdown
attributes:
value: |
* Make sure you have properly filled in the title of this bug report
* These files are included so that all interpolated weapon QAVs from 0 - 124 can be easily init/load/precache using the same code the game uses to init/load/precache the original QAVs.
* These QAVs have not been tested or patched for any QAV interpolation issues, so best to not declare them interpolated in case a modder uses them and they're messed up.
* The issue here is that `pPlayer->weaponTimer` reaches 0 before the animation plays out. This is because the QAV timer has its own ticrate independent of the game's timer.
* A workaround like this is still the best approach for now as its not easily possible to remove `weaponTimer` within the game without messing up the trigger system that runs at ticrate.
* Switch from macOS 10.15 to 11, Xcode 12.4 to 12.5
* Switch from Clang 11 to 12
* Remove no longer needed workaround for Clang 6 with GCC 11 deinstallation
