Replies: 1 comment
|
I agree with this suggestion. Having these values hard-coded in I think the important part is to keep the current behavior as the default, while allowing applications to override the values when needed. One possible approach would be to introduce a typedef struct CameraSettings {
float moveSpeed;
float rotationSpeed;
float panSpeed;
float mouseSensitivity;
float orbitalSpeed;
} CameraSettings;The existing values could remain as the defaults, so existing code would behave exactly as it does today. I would also keep these settings separate from Another advantage is that this could eventually allow users to implement their own camera controllers while still reusing the existing Overall, I think making these parameters configurable would be a useful improvement, especially for games that need different camera speeds or mouse sensitivity depending on the camera mode. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The movement settings for the camera are hard coded, meaning if someone wants different settings, they essentially have to write their own implementation.
rcamera.h, starting line 200:
My suggestion is that these should be made configurable variables (like FOV already is).
All reactions