My turrets are driving me nuts [Wrong rotation/Shooting issues]

[Kurt-Dekker]

I actually read the code more and line 69 actually is making a rotation (via Lerp) and then taking the eulerAngles. While we’re at it, make shorter lines.

I honestly don’t even know what to tell you about the above code because it looks like it has waaaaay too many moving parts.

This was my solution to 3D turret aiming/rotating:

Vector Lookat unprecise

I just did this a few weeks ago for a gun turret system in my Jetpack Kurt Space Flight game, which is getting more combat mode targets. This is the aiming portion (it’s a partial class): You should call StartAimer() from Start() You should call UpdateAiming() from Update() using System.Collections; using System.Collections.Generic; using UnityEngine; public partial class TurretBrainAndTargeter { // Feel free to make these public, drag them in using the Editor, // then remember to …

At the end of the day:

• use Atan2() to find the angle in degrees
• use MoveTowards (or Lerp) to smoothly change the angle
• use Quaternion.Euler() to create rotations for the angle

Smoothing movement between any two particular values:

Beginner - need help with SmoothDamp

The problem is the choice of integer values for lanes. They can only either be lane 0, 1 or 2. They can’t be in between round numbers. It needs to be a floating point value so that it can be between lanes. This type of question comes up so universally I have finally just made a sample package to demonstrate the basic concept. Read my first post above and see if you can correlate each part of the code to the steps indicated. Code located here: SmoothMovement.cs · GitHub 6430100–719246–SmoothMo…

You have currentQuantity and desiredQuantity.

• only set desiredQuantity
• the code always moves currentQuantity towards desiredQuantity
• read currentQuantity for the smoothed value

Works for floats, Vectors, Colors, Quaternions, anything continuous or lerp-able.

The code: SmoothMovement.cs · GitHub

For score count-up (like a cash register whizzing lots of numbers upwards), I like this approach:

Create Score increasing effect

I like to have two quantities for this: int actualScore; int displayedScore = -1; When the game logic adds points, it does this: actualScore += 12345; Now over in the display logic you periodically: adjust displayedScore towards actualScore (magic happens here!) output displayedScore Now… onto the magic. Obviously if you count one point (or any constant amount) it is pretty uninteresting… a huge score add might take forever to get together. Keeping it all as integers, here is the …

To figure out what is actually happening in your code above, same rules apply:

What is often happening in these cases is one of the following:

• the code you think is executing is not actually executing at all
• the code is executing far EARLIER or LATER than you think
• the code is executing far LESS OFTEN than you think
• the code is executing far MORE OFTEN than you think
• the code is executing on another GameObject than you think it is
• you’re getting an error or warning and you haven’t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

• is this code even running? which parts are running? how often does it run? what order does it run in?
• what are the values of the variables involved? Are they initialized? Are the values reasonable?
• are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

Coroutine missing hint and error

This is so unnecessary. Use the beauty and power of instantly and immediately putting a Debug.Log() statement into the very start of the coroutine, right at the top. Do this always at the very first sign of trouble or question in your mind. The instant you did this you would see “Oh man, this code is simply not getting run!” And you could LASER-FOCUS 100% your efforts on studying what you expect to run it, eg., the call location, and isolate why it is not running. You would look at literall…

You must find a way to get the information you need in order to reason about what the problem is.