ENG New site

Advanced search

[ New messages · Forum rules · Members ]
  • Page 1 of 1
  • 1
Planetary Exploration
sgtreddDate: Sunday, 05.07.2015, 00:50 | Message # 1
Observer
Group: Newbies
United States
Messages: 3
Status: Offline
Anyone know of a way to explore on planets with the camera locked to the level of the horizon. I would really like to eliminate the tilting that takes place as I rotate through 100 degrees or so. I'm sure there's a setting for it but with so many controls I have not been able to figure it out. Thanks. wacko
 
HarbingerDawnDate: Sunday, 05.07.2015, 02:27 | Message # 2
Cosmic Curator
Group: Administrators
United States
Messages: 8717
Status: Offline
It's not possible. Also, please read the forum rules. A new thread for this question was not necessary.




All forum users, please read this!
My SE mods and addons
Phenom II X6 1090T 3.2 GHz, 16 GB DDR3 RAM, GTX 970 3584 MB VRAM
 
DaltonDate: Monday, 27.07.2015, 03:41 | Message # 3
Observer
Group: Newbies
United States
Messages: 1
Status: Offline
Are you talking about the involuntary camera roll that happens when you're using mouse look? Cause I'm getting that too. It's like I'm pressing Q and E when I'm really not.

Quote HarbingerDawn ()
It's not possible.

This is a bit of a shot in the dark since 1) I don't know anything about the engine, and 2) I'm not even sure if we're talking about the same thing, but I may have a solution to the problem. Again, this is assuming you're talking about the involuntary camera rotation during mouse look.

I think the issue might have to do with floating point error during rotation.

In order to fix that floating point error in my own engine, instead of just doing local rotations on the camera, I did this:

1) Zero out the position vector of your camera's matrix
2) Do the same camera rotations that you normally do, but for your Y-Axis (left and right) rotation, instead of doing a local rotation, do a global one (it'll act exactly like a local rotation because your camera is at the origin).
3) Restore the zero'd out position vector to what it was before you set it to 0;

This should solve the issue, assuming of course that it was caused by floating point error in the first place.


Edited by Dalton - Monday, 27.07.2015, 04:41
 
  • Page 1 of 1
  • 1
Search: