Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(+1)

Another thought occurred to me about the "look at cursor" values. As I am working on a fairly small pixel art character the values are very very small. To the point that in order to have more fine control over exactly what values I was getting I was having to manually resize the honk window itself to get the slider to give me different values. This is one of the problems that would be solved with manual value entry as suggested in my previous post, but perhaps it could be solved by making the sliders change in relation to the largest component on the canvas?

Otherwise maybe the nature of the slider variable could be changed. I'm unsure exactly what the variable is supposed to be at the moment, but perhaps it could be changed that the value represents the maximum number of pixels moved at the extremes of the motion. This would bee a very intuitive way to represent the value and would make it very easy for people to "draft" the motion of certain elements inside the apps they use to draw their assets. The variable being representative of pixels would mean that people could take values directly from their drawing apps and copy them across into honk.

Finally, in regards to the oval settings, it would be nice to have a unified oval option that lets you input 2 different values for x and y, giving some freedom for characters with different eye shapes among other things, a similar equivalent for box tracking too maybe? Rectangle? And to put the cherry on top of that, an even more robust solution would be for both of those options to have 4 values, one for each of the 4 directions  +x -x +y -y, this would give way to emulating a more "spherical" rotation, allowing both more extreme rotations as well as the ability to rig characters with plenty f tracking motion at extreme angles. Imagine (albeit this is a bit of a comical hypothetical) a character drawn facing directly to one side and being able to rig their iris to still roughly emulate where the eye would be facing while taking into account the perspective from the curvature of the eye.

Once again I've had alot to say but it's just my nature to never give suggestions that I cant think of potential solutions myself. I understand your vision for the app is probably a touch more simplistic than what I would like to get out of it and that's totally fine, I tried to give suggestions that could still be achieved in simple/intuitive ways. Once again this app is incredible and the 3.0 update has come with a bunch of wonderful features, you have done a very good job.