Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Asset Forge

Create your own 3D models and 2D sprites! · By Kenney

2.5.0 - Saving/exporting is broken - MacOS

A topic by MarkOates created 79 days ago Views: 130 Replies: 5
Viewing posts 1 to 6
(1 edit)

Just downloaded 2.5.0 and the native OS save dialogs do not spawn when trying to save. This happens with Save, Save As, Export Sprite, and Export Model (edit, also when trying to open, too).

Things I tried:

  • Restarted computer
  • Updated MacOS to latest version (Sequoia 15.4.1)
  • Started app in command-line (several lines of "memorysetup-*" during startup, no error/warning messages when trying to save)
  • Reinstalled previous 2.4.1 Deluxe - this saves normally as before

I'm on an M1 chip

(I spoke too soon with https://itch.io/t/4831551/new-update-250-wow, sorry for the curse)

I'm currently investigating this issue, sorry for the trouble it has caused. I can't test on Mac anymore because Apple made my iMac obsolete, not enough funds to buy a new device.

(2 edits)

Some good news - We've found a workaround for the time being. The problem seems to only affect Apple Silicon macs (mine being an M1) and appears to be related to a third-party Unity plugin that allows using native dialogs for Windows, Linux, and MacOS.

The workaround is to run the app in "Open using Rosetta" mode. To do this:

  1. Right click the AsssetForge.app package
  2. Click "Get Info"
  3. Click the checkbox "Open using Rosetta". It should be under the "General" tab.
  4. Open the app again

All the native "Saving" and "Open" should now work as expected.

I couldn't find the "Open in Rosetta" checkbox on my Mac. Btw using this on Mac Mini M4.

(1 edit)

> I couldn't find the "Open in Rosetta" checkbox on my Mac. Btw using this on Mac Mini M4.

Oops! I missed a step in the instructions, my bad. When right-clicking the AssetForge.app, you should click "Get Info". The "Open using Rosetta" checkbox is in there. I updated the post.

This has been fixed in the upcoming 2.5.1 update of Asset Forge, thanks for reporting!