• Due to the dramatic number of changes to the game in 2.2, the old Bug Reports subforum has been archived and we are starting with a clean slate.

    If you feel you have found a problem with the game, please create a new thread with a summary of the bug as the thread name. Try to include as much information as you can in the initial post, including a description of what the expected behavior is and ways to reproduce the bug (if possible). Do not hesitate to upload any screenshots, logs, or WAD files that may aid in identifying and solving the issue. You do not need to enable DEVMODE for any screenshots you take; important information such as location, info, map name, and map number is automatically stored inside every screenshot.

    Please make one thread for each bug you find. Grouping multiple bugs together in a single thread makes it much harder for us to track what bugs have been fixed. To that end, any thread that does group unrelated bugs together will immediately be marked "Invalid" and locked.

    A member of our crack development team will come around and see what they can do about your reported issue. Additionally, if you have any useful information to add to a bug report thread (even if you aren't the original poster), you are welcome to post in the thread to add your input.

    A quick definition of each resolution:

    (none)
    The bug has yet to be confirmed by a member of the development team.

    Confirmed
    The bug has verified to exist in the game, but nobody is currently working on fixing it at the moment.

    Assigned
    The bug has verified to exist in the game, and a developer is currently fixing it (or planning to fix it shortly). Smaller bugs that take a short amount of time to fix may skip this step.

    Fixed
    The bug has been fixed for the next version of SRB2. These threads will always be locked afterwards.

    Invalid
    The submitted report is not valid. Reasons for this include reports of intentional behavior, or reports that have been confirmed to not occur in the original game. These threads may be locked at a developer's discretion.

    Duplicate
    This bug has already been reported. These threads will always be locked with a link to the original bug report given.

    Isolated Case
    The development team has not been able to reproduce the bug. These threads will remain open so that others may provide additional information or clarification.

    Won't Fix
    The bug will not be fixed. This typically means that the bug is too trivial to worry about or has been decided to be kept as an intentional feature. These threads may be locked at a developer's discretion.


    Thanks for helping improve SRB2!

    Note, bug reports for SRB2Kart should be submitted to their bug reports thread: https://mb.srb2.org/showthread.php?t=43795

Confirmed "Run Retry" doesn't work on gamepads

In Record Attack and NiGHTS Mode, the "Pause / Run Retry" control switches functions from quick-pausing the game to restarting the attempt if you hold it for a bit.

However, when bound to a gamepad instead of a keyboard key, pressing "Pause / Run Retry" on the gamepad results in the game showing "Hold to retry..." for a little bit, but that notification goes away shortly thereafter, regardless of whether you hold the control or let go of it, and you don't get to start over in any case.

It's still possible to start over while using a gamepad by opening the pause menu and selecting "Retry" from there. I don't know if this issue also occurs with mouse buttons, but keyboard keys can retry as intended.


Environment: SRB2 v2.2.0 (32-bit), on a 64-bit Windows 10, using an X-Input controller.
 

fickleheart

ms reflec beat stan
This doesn't work with mouse buttons either, and while I haven't looked to make sure, it feels like the retry mechanic relies on keyboard auto-repeat to get its effect.
 
This doesn't work with mouse buttons either, and while I haven't looked to make sure, it feels like the retry mechanic relies on keyboard auto-repeat to get its effect.
That seems to maybe be the case, yes; If I bind "Pause / Run Retry" to the W key on my keyboard, and hold W for a bit, it retries. If I press and hold W, then also press and let go of D (which isn't even bound to anything in-game), which would stop the W key being auto-repeated by Windows, it doesn't retry.


(Semi-related to this bug report, the game also seems to have hardcoded support for retrying by holding the Pause key on the keyboard (also requiring other keys to not be pressed in the meantime), too, though this has its own issues; It doesn't do a fade to white first (it just instantly gets fully white and then fades back to normal, whereas a bound W would do a short fade to white and then back), and unlike keys that are bound to the "Pause / Run Retry" control, it doesn't show the "Hold to retry..." text when pressed. The hardcoded pause key also sometimes fades to black and then shows the act's title card, rather than just a short white fade, though I don't know if this is exclusive to the hardcoded pause key.)
 

Who is viewing this thread (Total: 1, Members: 0, Guests: 1)

Top