You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Neverputt, sometimes the ball ends up in an inconvenient place where an obstacle prevents you from seeing the ball (and maybe also your target) when you're making your shot. Other times, people have made really large levels and the camera is too close when you're making your shot -- your target is too far away or off camera and you can't even see it, making it very hard to aim. (This could also be useful when trying to make very small, precise shots, allowing you to get closer and see it in finer detail.)
I think both of these cases could be (if not entirely fixed) at least largely mitigated by a fairly simple and intuitive control: Have the mouse's scroll wheel move the 'camera' closer to or farther away from the ball. No change of angles or anything ... just simply adjusting the distance between the camera and the ball.
Within limits, of course. You don't want to make the entire putting course a tiny speck, and you don't want the ball to fill up the entire screen. And it's only needed when the player is actually making the shot -- giving input. It might be fun for this feature to also work when the ball is in motion, but that's not really of any practical benefit and certainly isn't necessary.
I'm not familiar with your code base, but it seems like that would be a fairly easy feature to implement. Somewhere, you've got to have code dictating how far the camera stays from the ball ... then just combine that with a multiplication factor that depends on scroll wheel movement. And it shouldn't bother anyone who doesn't want to use the feature: just continue not using the scroll wheel, and you won't notice any difference.
(Not sure if this might be useful for Neverball also? I don't play it much, but being able to quickly and intuitively change how far/close the camera is to the ball might be beneficial in that game also.)
The text was updated successfully, but these errors were encountered:
Oh man I would love this, it seems like an oversight to not have this. Happens to me quite often; on a few holes it happens every time. (eg. can't see the top of a long hill)
In Neverputt, sometimes the ball ends up in an inconvenient place where an obstacle prevents you from seeing the ball (and maybe also your target) when you're making your shot. Other times, people have made really large levels and the camera is too close when you're making your shot -- your target is too far away or off camera and you can't even see it, making it very hard to aim. (This could also be useful when trying to make very small, precise shots, allowing you to get closer and see it in finer detail.)
I think both of these cases could be (if not entirely fixed) at least largely mitigated by a fairly simple and intuitive control: Have the mouse's scroll wheel move the 'camera' closer to or farther away from the ball. No change of angles or anything ... just simply adjusting the distance between the camera and the ball.
Within limits, of course. You don't want to make the entire putting course a tiny speck, and you don't want the ball to fill up the entire screen. And it's only needed when the player is actually making the shot -- giving input. It might be fun for this feature to also work when the ball is in motion, but that's not really of any practical benefit and certainly isn't necessary.
I'm not familiar with your code base, but it seems like that would be a fairly easy feature to implement. Somewhere, you've got to have code dictating how far the camera stays from the ball ... then just combine that with a multiplication factor that depends on scroll wheel movement. And it shouldn't bother anyone who doesn't want to use the feature: just continue not using the scroll wheel, and you won't notice any difference.
(Not sure if this might be useful for Neverball also? I don't play it much, but being able to quickly and intuitively change how far/close the camera is to the ball might be beneficial in that game also.)
The text was updated successfully, but these errors were encountered: