Hello there! I am making an FPS, and I have deleted way too many good projects of mine due to this problem; I am sick of it and I want it solved. My other question about it got closed because it was unclear, so I'll make this as clear as possible.


I have a simple scene with a plane. The plane is default, with no edits to it, not even a texture. It has only been scaled, that's all. After that, above the ground a bit, is my character. The collision bounds (rectangle) is basically just a collision bound to a model (character) that is set to "no collision" and is not an actor. The character has nothing to do with this. It does not affect anything. The only important part is the head. The head is part of the character and has Mouse (Movement) > Python. The Python is just the mouselook script. The head is the parent of the camera and just has ml.inherit along with some cap options (in the logic editor). There is also some basic lighting.


Every time I look upwards with my mouse (moving my mouse forwards), just 1 degree above where the head normally faces, the whole scene just gets "ruined." However, this does not happen when I look down. What happens when I look up is that it seems that the lighting, first of all, is quickly, every millisecond, "flipped" where the ambient is more brown instead of blueish yellow. At the same time, the head keeps on flashing (going between visible and invisible). I think the head flashes once per second, but I'm not sure. How do I stop the "twitching" from happening? Here is my .blend, thank you!

  • $\begingroup$ Make sure to remember that the collision bounds are also the parent of the character! $\endgroup$ – blackhole Jun 11 '14 at 23:38
  • 2
    $\begingroup$ can you share a blend file? $\endgroup$ – Mike Pan Jun 12 '14 at 8:33
  • $\begingroup$ pasteall.org/blend/29768 - .blend: just look upward and see. $\endgroup$ – blackhole Jun 12 '14 at 18:03

As of 2.72, there is a new mouse actuator which you can use to rotate objects based on mouse movement.

enter image description here

By using this actuator instead of the python script, it seems to work fine:

enter image description here

  • $\begingroup$ I already figured the error in 2.70 but thanks, also, why is 2.72 marked as 2.72b? When is 2.72 coming out officialy, is a and b beta? im confused $\endgroup$ – blackhole Oct 31 '14 at 23:48
  • $\begingroup$ @BlenderDev See blender.stackexchange.com/q/3030/599 $\endgroup$ – gandalf3 Oct 31 '14 at 23:49
  • $\begingroup$ Oh so nothing is wrong with 2.72b, the next one will come along in a long time right? $\endgroup$ – blackhole Oct 31 '14 at 23:51
  • $\begingroup$ @BlenderDev Yes. Well, in a couple months or so. Then next one will be 2.73. $\endgroup$ – gandalf3 Nov 1 '14 at 0:17
  • $\begingroup$ Just 1 more thing, in my Blender folder, since I downloaded 2.72b, is it fine if I delete the 2.7 files? Sorry for all the questions, your just a good source :) $\endgroup$ – blackhole Nov 1 '14 at 2:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.