FOSS gamedev and creative worlds

Found a difference between the function get_look_yaw and the output when pressing F5
If I'm not wrong you convert from radians to degrees this way:

This results in values 90° shifted to the debug-output.

So your next attempt will be:

That results often in correct values. But sometimes in negative values, no not just by the 90°. They are really absurd.

Next try:


Aw, c'mon. You really have to do this?

If you add the if statement you can delete the -90.

I think the best way to fix this is to correct the F5 to be the same as player:get_look_yaw(). In this way, potential existing mods will be backward compatible.
EDIT: Of course in radians, but the same 0 axis (I hope it is clear)

I'm having trouble with this function: when I do this:

(p is a player)

local yaw = p:get_look_yaw()*180/math.pi
p:set_look_yaw(yaw*math.pi/180)

it actually shakes the camera around, it's really weird.

(same thing when I modify pitch)

[edit] corrected an illogical variable name

ok, solved the problem:


still 2 things: This code locks the camera and it's buggy, and it's not very logical that get_look_yaw gives the yaw in radians and that set_look_yaw takes it in degrees..

AndrOn wrote:ok, solved the problem:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

(p is a player)

            local yaw = p:get_look_yaw()*180/math.pi           
            p:set_look_yaw(yaw)

still 2 things: This code locks the camera and it's buggy, and it's not very logical that get_look_yaw gives the yaw in radians and that set_look_yaw takes it in degrees..

Huh? set_look_yaw definitely need radians value, example use:

dest_angle = 90
player:set_look_yaw(math.rad(dest_angle))