Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit) (+1)

Hello! We've just pushed a new update which addresses the bug regarding eyebrows. We also adjusted how the app behave when files are closed. Now when you use the close button on the main window, the app will try to close all currently open files and then shut itself down. But when you use the close button on the tab, closing all files will make the app return to start screen.

We've just tested installing the app on 2 different Windows systems, and found that all of them are working properly through itch.io, so we might need to collect more information before we're able to fix the other bug that you've reported.

As always, thank you for your support and feedback!

Your efficiency is impressive, thank you!

Feel free to ask for any information you need.

If it's not a problem to you, it'll be very helpful to know more regarding this problem:

  • Are you installing through itch.io and running from the itch.io app?
  • Is there any clues onscreen when the app failed to launch?
  • Do you solve this problem by manually downloading via ZIP file through itch.io website, or by other means?

Thank you very much!

  • I'm doing it all via the itch.io app.
  • The fact is, nothing happens while launching Mannequin through the itch.io app. The launching  button displays "En cours d'éxécution" (I'm running it in French, so I don't know what's shown in English) then turns back to"Lancer" ("launch") after a few seconds, while not a single window will open. Lauching via the itch.io app perfectly works with other programs though, I'm only having this bug on Mannequin.
  • Downloading and updating Mannequin on itch.io perfectly works, I don't need to do it manually.

If nobody else is having this bug, don't feel obligated to help me. It really doesn't bother me, I just wanted to report it.

Thank you for your hard work!

(+1)

Thanks for the info! We'll keep in mind that this bug exists and try to test it in other systems whenever there's a chance. Hopefully we'll find the root cause soon!