- Joined
- Dec 31, 2015
- Messages
- 602
- Thread Author
- #1
It would be nice to know BEFORE turning the camera, what the difference in pitch & yaw would be to the object.
This could stop lots of really silly camera calls, I know a lot of people use Object Visibility, and as a matter of fact sometimes the visibility isn't as high as you would expect it to be thus you end up spam calling to turn to it.
By having this method (Which authors technically could implement themselves however it seems to fit rather nicely into the Camera class) it would stop really miniscule camera changes and wasted calls/threads to turn the camera.
Alternatively getPitch() and getYaw() could have an additional paramater allowed that would return the pitch and yaw the camera is required to turn to for that object, so you can do the analysis of data yourself.
Just a thought that popped in my head while showering.
This could stop lots of really silly camera calls, I know a lot of people use Object Visibility, and as a matter of fact sometimes the visibility isn't as high as you would expect it to be thus you end up spam calling to turn to it.
By having this method (Which authors technically could implement themselves however it seems to fit rather nicely into the Camera class) it would stop really miniscule camera changes and wasted calls/threads to turn the camera.
Alternatively getPitch() and getYaw() could have an additional paramater allowed that would return the pitch and yaw the camera is required to turn to for that object, so you can do the analysis of data yourself.
Just a thought that popped in my head while showering.
