due tonight i have to complete this project, pls help!

[LIGEIIA]

Hi everyone! I’m here cuz I didn’t find anything useful online so you are my last hope! Due today I have to create a mini game, let’s call it that way, where basically I would love to “ragdoll” everything you want. I started by making my menu, my hammer, the hammer script ecc but I have a big problem! I imported some assets from a different project (because I need to) and I just want to apply a rigid body and a collider to everything so, logically, it’s supposed to collide with my hammer in the moment I will smash with it the objects! But I’m facing so many problems, like why is the collider flying away from me? I can’t understand, will post some screens because it’s waaaaay easier to explain to you my problem that way. What I am doing wrong??

rigidbody : use gravity, no kinematic, mass 1

if u have any tips to help me with my proect I will be sooo glad <3 ty in advance and sorry for my bad english hehehe

[DevDunk]

Maybe the hammer and player collide? Put them on seperare layers and ignore collisions between the 2

[LIGEIIA]

nope im sure about it, the hammer and the player aren’t colliding! + my script and everything works, it’s just this scene that is driving me crazy! ty btw

[mgear]

some object seems to be static, is that correct?
also error message in the console about collider.

what collider is moving away?
Try adding script with OnCollisionEnter() or something, and print out what it collides with.

[Kurt-Dekker]

Here is the simplest, fastest way to debug stuff like this (see bolded section):

Time to start debugging! Here is how you can begin your exciting new debugging adventures:

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

Once you understand what the problem is, you may begin to reason about a solution to the problem.

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 names of the GameObjects or Components involved?
• 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.

You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as Debug.Log("Problem!",this);

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.

Visit Google for how to see console output from builds. 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 for iOS: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on Android

If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.

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…

“When in doubt, print it out!™” - Kurt Dekker (and many others)

Note: the print() function is an alias for Debug.Log() provided by the MonoBehaviour class.