Changing script value in animation is bugged

[Kurt-Dekker]

Reaching for Euler angles is almost always not the way to go. Here’s why:

Your best bet is to have local-only float variables to represent traverse and elevation, then change and clamp those floats, and finally drive .localRotation of the parts on their correct Transform axis.

Notes on clamping rotations and NOT using .eulerAngles because of gimbal lock:

Implement a limit in Camera Movement

Generally never read / write to / from eulerAngles. The reason is gimbal lock. Instead track your own float variable that is the heading, adjust and clamp that variable, then “drive” the camera’s rotation each frame.

Implement a limit in Camera Movement

declare a variable float heading; adjust it when conditions warrant: if (conditionToTurn) { heading += AdjustmentWhateverYouWant; } clamp it heading = Mathf.Clamp( heading, minimum, maximum); drive the rotation to the camera transform: cameraTransform.localRotation = Quaterion.Euler( 0, heading, 0);

How to instantly see gimbal lock for yourself:

Confusing bug

Pretty sure this is gimbal lock. To see what I mean: put a cube in a blank scene using the inspector, independently rotate it a little bit around x, y, z - works as expected now set x rotation to 90 try rotate around y and z - note that z works identically to y rotation! You can no longer rotate z! In the context of your game, I’m not sure what the best solution would be, but there’s a few possibilities. Check out some youtube tutorials on changing gravity controllers…

All about Euler angles and rotations, by StarManta:

Euler Angles · UnityTipsRedux

Since you mention animation issues, keep this in mind too:

Anything with Animations / Animators / Mechanim:

Only consider the code AFTER you have done this critical step:

Always start with the Animator state machine and prove it works in isolation, no code at all.

Here’s more reading:

Press keyboard key to play animation using different animations per assigned key

With animation always start with the animator / animation setup itself. You can clear the scene, pull in the animated object, then while the game is running, use the Animator window to wiggle all the properties to make sure it does what you want when you set it. If you can’t get it to work by hand-setting the properties, nothing you do in code will matter, obviously. Usually for one-shot things like a dance you use .SetTrigger, not .SetBool… then mark the dance animation to cleanly exit on it…

Also, code like this is NOT your friend:

@BasicDeveloper_100

rotationWithoutOffset = Quaternion.RotateTowards(
        rotationWithoutOffset,
        Quaternion.LookRotation(targetFlat - currentFlat),
        speed * 40 * Time.deltaTime
        );

If you have more than one or two dots (.) in a single statement, you’re just being mean to yourself.

Putting lots of code on one line DOES NOT make it any faster. That’s not how compiled code works.

The longer your lines of code are, the harder they will be for you to understand them.

How to break down hairy lines of code:

How to break down “hairy code” that has an error. – PLBM Games

Break it up, practice social distancing in your code, one thing per line please.

“Programming is hard enough without making it harder for ourselves.” - angrypenguin on Unity3D forums

“Combining a bunch of stuff into one line always feels satisfying, but it’s always a PITA to debug.” - StarManta on the Unity3D forums