@@jiho98 yes, I do but the plotting material is spread out. I’m not sure which video or videos covers those topics, otherwise I’d link you to them

You can use find to get the index of what you want to find and then turn around and use the indexes to get the corresponding values: a = [1 5 7 23 7 8 3 46 23 2 46 7 4 5] locations = find(a==23) values = a(locations)

@@Stefano-v-s5v que es un script de multibox? (I don’t speak Spanish, but I’m using Google translate)

Great question. Off the top of my head, the speed x time right side of the equation probably needs replaced with the horizontal component of projectile motion V0 x time x cos angle. I’m not sure what else. Traveling right now but I’m excited to answer this question when I get back.

@@NealHoltschulte Alright I appreciate your time, thanks in advance!

It was harder than I expected, but I did it! The most up to date code is on github currently. Video here: kzbin.info/www/bejne/fqvKoGiAp5eaf5Y

Start simple and see if the look_at function meets your needs, but if not, I can certainly see this tracking code for the turrets being applicable, depending on what precise behavior you're hoping for.

@@arekkubiak5957 I’ve got a shitty HotDS clone working in Godot! When life gets less busy I’ll make a video and put it out there :)

@@NealHoltschulte Ooo can't wait!

Yeah, sorry about that. I think I put all my turret "heads" on backwards when I first made them and then instead of doing the obvious fix of righting the head, I negated z in the code. Play around with negating or changing the model and you should eventually get it sorted out.

@@NealHoltschulte Sorted - thanks! For others - I negated both instances of global_basis.z, and both the variables final_y and final_x. This alongside reversing the head rotation clamp solved the inverted direction. Great tutorial :)

Big Thanks to both of you, i was wondering about this as well but my solution left the turrets jittering like crazy <3

Glad to hear it!

This is fantastic, thank you!

@@NealHoltschulte My pleasure. Good learning exercise for me, so win win. BTW do you know if symbolic has a semilog/loglog plotting analog?? Haven't found one yet.

@@4tee2 I'm not aware one way or the other.

Thanks!

@@NealHoltschulte You're welcome, my little contribution to the advancement of civilization. Thanks for your videos btw, very nice and helpful and informative.

It's the side length of the spiral-like shape. step_size determines the length of the straight lines in the pattern shown at 0:20.

Short answer, no. I don't know. Things to try: Check if the progress window got moved behind other windows (switch windows with alt-tab). Sometimes that happens for reasons I don't understand. Make sure you've closed out of other programs before starting the install process. Make sure you have enough space on your harddrive for the install. Sorry I can't be of more help.

I have the same issue please let me know if you fix it. Try getting jarfix as well

You're welcome! I hope it's useful to people.

@@NealHoltschulte Well it's for sure useful to me! I'm making a security camera that's got an armature/rig and can track a player. So it's slightly different in that I am working on bones instead of nodes, but other than that, it's pretty much the same. I originally tried to use the "look_at" and "looking_at" functions and just multiplying the axis I don't want to modify by 0 to "lock" axises. Those functions have some very specific requirements around the axis orientations that seem to not work well with bones though (ex: +Z or -Z needs to be forward and there needs to be a fixed well known global pos up axis). In my experience with rigging (which is limited and I might be missing something), your bone axis orientation is dependent on the bone chain, so you can end up in scenarios where +Z and -Z being forward just doesn't work and there isn't a good well known global position up axis, which makes makes those "look_at"/"looking_at" functions very difficult to use and debug issues with. The lower level approach taken by this video, and the easy to read code is exactly what I've been looking for. After this security camera, I plan to try and get this same thing working on a human's head/neck bone chains to try and get some character face tracking too, so yea I think this video helped me a boatload! Thanks again!

@@brennennen1761 I've not worked with bones before, but I'm happy this was helpful. I had a similar frustration with other tutorials telling me what to do, but not why and I was immediately stuck when I tried to do something slightly outside the box, so I wanted to make something that wasn't so rigid once I figured out how the hell to do it.

Yup, they're super useful!

Watched*

Thanks, I'm glad you think so!

If you use a raycast, then you don't need my video because it tells you where the hit occurred. If the characterbody3d pushes the target around, that's likely a masks versus layers issue. You may need to assess whether the bullet needs to know about the target or vice versa, but not both. Good luck!

@@NealHoltschulte I'm not using a Raycast like a hitscan. Rather, a Raycast3D of limited length moves with the projectile and it used to see if the projectile in its forward motion collides with something. And thanks :)

@@OnyxIdol Oh, I understand. Hmm, I thought the character bodies took care to interpolate the positions inbetween the start and end of a frame so that they don't "tunnel" through something they should have hit, (in which case you wouldn't need a limited length raycast carried along with the projectile) but I gotta admit, you've moved into an area that I don't know much about.

That's awesome! Thanks for following along on this journey.