Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits) ( 2)

Currently using v2.0. Some UI issues/requests:

1) some indication which layer each image is on, currently they're just stacked, which is much more helpful than it used to be, but I still have to do some trial and error to arrange the sprites correctly. (also would be nice if there were a few more layers--currently 5 is working fine but the image order may not always play nice)

2) the add image button is named "create layer" -- this is ambiguous, since a layer is a different thing in this program. Should be called "add image" or "add sprite"

3) For the emotes, I have to recreate mouth movements every time I want a different idle mouth. Being able to duplicate a sprite would be helpful.

4) being able to name the emote layers would be nice. I need to make a physical cheat sheet so I can actually remember them while making them.

EDIT 5) I think "emote on/off" indicator is backwards, it says "emote on" when I turn it off on a layer

EDIT 2: 6) Another feature request for a bit of aesthetics: an FPS limiter on the image? It looks like it's doing 60 FPS sometimes and that's great but allowing to adjust down to 24 FPS or 16 FPS MIGHT help it look less inconsistently rapid

( 2)

THANK YOU!

These are great ideas. I hit some really really gnarly big bugs that took a solid week to fix with this release. So getting feedback on smaller things is super useful. This is much appreciated.

On 3). I may be misunderstanding, but there is a duplicate element option. If you click on a layer/element, there is an icon with 2 squares. Press that and it will duplicate it in the exact same place.

As for the framerate, I believe it is currently uncapped. With the exception that I limit the framerate on the eye tracking. Since it was super smooth and weird feeling compared to the framerate of the lipsync (I think I did 24fps). I may not put FPS as an in-app setting. Since I think that's more granular than HONK's mission statement of simplicity, but maybe that could go in a config file for advanced users

Thank you again! I'll jump on all of this ASAP.