Bug Report: Camera Bop Ceases To Function When Zoom Level Is Set To 1.25x Or Higher

[Average-FNF-Modder]

Issue Checklist

• I have properly named my issue
• I have checked the Issues/Discussions pages to see if my issue has already been reported

Platform

Newgrounds (Web/HTML5)

Browser

Microsoft Edge

Version

0.5.3

Description (include any images, videos, errors, or crash logs)

      When using the "Zoom Camera" event, if you set the zoom to 1.25x the stage zoom or above, the camera will stop doing it's a regular bopping. There is also a point on the absolute zoom scale where this happens as well, and while I haven't confirmed it I assume it's whenever that value reaches a zoom above 1.25x the stage zoom as well.

      This effect does not seem to be based on any absolute zoom threshold, but rather specifically on a multiplicative threshold based on the stage, as testing it out on different stages showed the same results for zoom multiplier needed to break the camera's bopping.

      This bug is pretty annoying, and definitely hinders how creative you can be with your events. Fix it pls!

Steps to Reproduce

1. Open da game
2. Open chart editor
3. Set your zoom to 1.25x or higher on the relative scale, or to the (what I assume to be) equivalent value on the absolute zoom scale
4. No more bopping :(

[MrMadera]

i think it's because of this!

i'm not sure if this would be considered an issue or if it's intended,,

[cyn0x8]

this limit seems kinda arbitrary... there should be no limit imo

also tangentially related but imo the bop should also be proportional to the current zoom so the bop looks the same at all levels
adding 0.1 to 0.5 zoom looks a lot different than adding 0.1 to 1.5 zoom!

[Average-FNF-Modder]

i think it's because of this!

i'm not sure if this would be considered an issue or if it's intended,,

If it is intended that's a really strange limit that really shouldn't exist lmao.

[MrMadera]

If it is intended that's a really strange limit that really shouldn't exist lmao.

i agree! if they decide to implement it, i think it would be better to handle it proportionally, as @cyn0x8 suggested, or simply remove it altogether