The standard asset FPS Controller is jumping on it’s own. As soon as I enter the “Play” mode and move either the mouse or keyboard, the Y position axis jumps to 0.98 by itself (from 0.0), and will not come down. As soon as I stop the play mode, it jumps back to 0.0. Is it possible the FPS Controller is corrupt? It doesn’t seem to stick to the terrain. Any help would be appreciated, thanks!
To be perfectly honest, you probably shouldn’t be using the standard asset FPS Controller. There are many much easier ways of creating a First Person Controller. The easiest being to stick the camera inside the character’s head. The FPS Controller is most likely not entirely suited to your needs, or you are using it incorrectly, but I do know that Unity did not intend for you to use that actual class in your program. It was more intended for derivation or being a base class for something else. I suggest you have a look at this: https://www.youtube.com/playlist?list=PL3eZfsRk6nF00HSZZJKgZ-HOoz3CJYXJu.
Thanks, I’ll sure look those videos over. It’s frustrating because I’ve had it working in the past now it’s no longer co-operating, lol. Oh well, learning as I go.
Ok, been working with this all morning and here’s where I’m at. No disrespect intended. I’m still using the FPS Controller from the Unity Standard asset package. My terrain, my model (a house), and FPS Controller are all set at the same y co-ordinates. As soon as I “Play” and begin any movement, the y co-ordinate jumps to .98. I’m removing the original camera as well. Seems that Unity designed the FPS Controller to work as a standard asset so I’m not sure how I can be using it wrong. I’ve used this the same in the past and it’s worked just fine. I did uninstall Unity 5 and reloaded from a fresh install thinking that was an issue but not. I’ll try your "sticking the camera in the characters head trick, but right now there is no character, just FPS Controller camera.
Ok, one question. Look at the Rigidbody component in the character, and open the constraints menu. If freezeRotation X and freezeRotation Z are not checked, check them and test. I know that was a huge problem for me, but try that. It might work.
Hhmmm…
That is an odd issue, for sure.
My thoughts are either 1) there’s something wrong with the script, 2) there’s something wrong with one of you values in the inspector, or 3) you’re getting input from somewhere.
Since you say you did a complete re-install, I’m leaning towards #3.
Do you have a gamepad connected? If so, try disconnecting it.
Ok, figured out the issue. I was using a FPS Controller I simply added to the scene. After zooming in on the controller I realized the bottom of the FPS cylinder was touching just below the terrain level. I scaled the FPS cylinder smaller so it wasn’t touching the ground and it solved everything. Stupid little error on my part. Apologies to Derp Merf who suggested I was using the FPS wrong. Good news is, I learned a ton of other things while searching out the problem. Thanks for the advice guys!
1 Like
Oh, good.
im having a similar issue but when in contact to a walll they shoot up to the top
ill try some things here thx:)
Please don’t necro posts. This post is from 2015.
Thanks.