Jump to content

Wavemanager camera distance assumptions


CarlZalph
  • Fixed

In components/wavemanager.lua, functions 'getRippleRadius', 'getShimmerRadius', and 'getPerSecMult' all make the assumption that the camera is from 30 to 100 without forcing the values.

If a mod makes the minimum distance a negative number, then the output results in a crash on line 146:

	local m2 = TUNING.WAVE_LANE_SPACING * math.floor(math.random(-col_radius, col_radius)) --math.random(-2, 2)

The crash is from the random interval being from a positive number to a negative one and that's not valid.

 

To fix::

Change the lines from:

local percent = (TheCamera:GetDistance() - 30) / (70)

To:

local percent = (math.clamp(TheCamera:GetDistance(), 30, 100) - 30) / (70)

 

To force said assumptions to always hold true.


Steps to Reproduce
Use a mod to adjust the minimum camera distance to be a negative number, view some waves and lock up with a crash.



User Feedback


A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.

There are no comments to display.



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...