So... lp_location / gv_hours_on_a_clock should always be in the range [0, 1], and multiplying by 2 * pi, changes the range from [0, 1] to be around a circle... unless... The galaxy editor uses degrees instead of radians? idk.
the result is always gv_CLOCK_RADIUS +/- 1 or 2... which is weird, cause.. cos only goes from -1 to 1... so there shouldn't be a 3 int range.
Am I missing something retardedly simple?
Also, if there is a Galaxy constant for Pi, lemme know =D
Cos(lp_location / gv_HOURS_ON_A_CLOCK * 6.28318531)
lp_location ranges from 0 to 11 hours on a clock is 12
I did TriggerDebugOutput(1, IntToText(FixedToInt(lv_x_pos)), true); on the above code, and the output was always 1, meaning the stuff inside cos is 0.
My guess is that lp_location / hours, because they are ints, are getting rounded down.\
I've tried wrapping the two gvs in IntToFixed()'s, and I get some variation... but not to the length I want.
like.. here is the full line..
fixed lv_x_pos = gv_CLOCK_RADIUS * Cos(IntToFixed(lp_location) / IntToFixed(gv_HOURS_ON_A_CLOCK) * 6.28318531);
So... lp_location / gv_hours_on_a_clock should always be in the range [0, 1], and multiplying by 2 * pi, changes the range from [0, 1] to be around a circle... unless... The galaxy editor uses degrees instead of radians? idk.
the result is always gv_CLOCK_RADIUS +/- 1 or 2... which is weird, cause.. cos only goes from -1 to 1... so there shouldn't be a 3 int range.
Am I missing something retardedly simple?
@DerNalia: Go
Confirmed, Galaxy Editor uses Degrees instead of Radians.