• 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:

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

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

    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.

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

    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.

    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

[Android] "Scale Divider" resets on game reboot

Using v2.2.8 of the official Android port, the "Scale Divider" setting ("nativeresdiv" convar, cv_nativeresdiv internal source code name) gets reset to the default value of 3.0 whenever the game is rebooted.

This setting controls the game resolution if "Use Native Resolution" ("nativeres") is enabled and "Automatic Scaling" ("nativeresauto") is disabled.

The convar already has the CV_SAVE convar flag, however the src/screen.c file's SCR_ResetNativeResDivider() function resets it to its default value.

That function is called by SCR_CheckDefaultMode() in the same file, next to the comment "// Reset to default if the native width or height changed", however it also gets called on game bootup regardless of if the resolution changed since last bootup.

Relevant source code area, in which scr_nativewidth and scr_nativeheight would always be non-zero, leading to SCR_ResetNativeResDivider() being called: https://github.com/Jimita/SRB2/blob/android-port-build-v228/src/screen.c#L459-L464

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