How do I make my capsule(with a Rigidbody) float 2feet above the ground. pls send help.
Thank you very much in advance.
I’ve watched this video on it but I’m still stuck.
He basically pasted the code you need. What exactly are you stuck on? What have you tried?
1 Like
What are you stuck on? They give you basically all of the code in the video.
1 Like
Ok so… I wrote the code out in unity and it didn’t work. If someone could just make the floating part as a unity project or do something else I will highly highly appreciate it.
Chamoy
Sounds like you have typos. Go back and fix them. Here’s how to find out what’s going wrong:
You must find a way to get the information you need in order to reason about what the problem is.
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.
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:
https://discussions.unity.com/t/839300/3
Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:
How to do tutorials properly, two (2) simple steps to success:
Tutorials are a GREAT idea. Tutorials should be used this way:
Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That’s how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.
Fortunately this is the easiest part to get right: Be a robot. Don’t make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!
If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.
Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.
Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.
Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there’s an error, you will NEVER be the first guy to find it.
Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!
The purpose of this forum is to assist people who are ready to learn by doing, and who are unafraid to get their hands dirty learning how to code, particularly in the context of Unity3D.
This assumes you have at least written and studied some code and have run into some kind of issue.
If you haven’t even started yet, go check out some Youtube videos for whatever game design you have in mind. There are already many examples of the individual parts and concepts involved, as there is nothing truly new under the sun.
If you just want someone to do it for you, you need go to one of these places:
https://forum.unity.com/forums/commercial-job-offering.49/
https://forum.unity.com/forums/non-commercial-collaboration.17/
1 Like
What did not work? How did you know? What happened instead?
Programming is not always plug and play. In fact, rarely ever. You gotta develop some critical thinking.
I realise you are still pretty new to this, but “i pasted the code and it’s not working” will not get you anywhere. If there is a problem, you must find out what it is. If you are ever stuck, of course the forums are here to help you. But maybe you could even fix it yourself… who knows. First you need to find what is actually the problem. @Kurt-Dekker wrote a helpful reply on that regard. Maybe it’s not running at all. Maybe there is errors. If it’s running, maybe it does not what you think it should. Maybe because you have typos. Maybe because you missed something important.
We really cant know these things. We dont know what you did, and we have no explanation of what’s not working.
While you nicely asked for it, you effectively said “i cant get it to work, you do it for me”, which is not how the forum is supposed to work. I’d be much happier to teach you how to fish than you give you a free meal today 
1 Like
I’m sorry for the inconvenience. I will try to give the floating capsule another try. If it doesn’t work, I’ll use normals instead. The main problem for floating it was that the gravity kept pulling it down. Is there a way to override the physics method?