Log in to your Inkarnate account to give feedback

Bugs

“Base Layer Workflow & Lock Improvements”
FUTURE REQUEST Title: Improved Base/Background Tool Workflow, Accessibility, and Layer Lock Report: I would like to suggest improvements to the base/background tool and layer workflow in Inkarnate. Current issues: • The base/background layer behaves differently from all other layers. • You cannot place assets on it. • You cannot access it throughout the map-making process—it seems you can only access it once, and it’s unclear when that should be. • These limitations make the workflow unintuitive compared to other layers that can be unlocked, edited, and adjusted at any time. Suggested improvements: 1. Allow users to access the base/background layer at any point during map creation. 2. Maintain its purpose as a paint/background layer without allowing asset placement. 3. Open the tool first, so users can set up the background at the optimal point in their workflow. 4. Include a lock icon for the base/background layer, just like other layers. This ensures that once the background is painted, it can be protected from accidental changes and makes the layer visually consistent with other layers. 5. Treat the layer’s behavior similarly to other layers for accessibility and consistency, while keeping its unique background-only purpose. Why it matters: These changes would reduce confusion, improve workflow planning, and make it easier to prepare maps for professional editing. Users would be able to work intuitively while protecting the background from accidental edits. Platform note (optional): Apple/Safari users would particularly benefit from this intuitive workflow, as accessibility and timing issues can otherwise make the process more frustrating.
0
·
Website
Bugs that I found. and descriptions
BUG REPORT Title: Assets placed but invisible + editor freezing after 2.0 update (iMac / Safari) Report: Program Essentially Unusable: Since the 2.0 update, Inkarnate has become almost impossible to use. Assets do not appear when placed, and the program sometimes becomes completely unresponsive. When this happens, I cannot place objects, move around the map, or use any tools. Unlike before the update, when minor slowdowns were manageable, I can no longer work effectively at all. Device and System Information: iMac, macOS 26.3.1 Using Safari browser and logging in with Gmail Safari worked reasonably well before the 2.0 update. It was slightly slower, but the slowdown was minor and did not disrupt my workflow. Performance Issues: The problem occurs consistently, even on small maps with relatively few assets (mostly trees and mountains). Assets that are placed on the map are invisible. However, if I click an asset in the asset list, the program shows that it has been placed and will jump to its location. The asset itself is still not visible on the map. The only way I can tell an asset has been placed is by checking its location in the asset list. The program also sometimes freezes during normal actions. Additional Testing: I tested zooming in and out after placing assets. The assets remain invisible at all zoom levels. The only asset I can see is the one currently attached to my cursor before placing it. Once the asset is placed, it becomes invisible. I also tested placing single assets, spacing them apart, and dragging assets across the map. While dragging, I could see the asset moving through the asset pack interface, but nothing appeared on the map after placement. Map Testing: At first, I thought the issue might be related to a map I created before the update. I deleted that map and created a new one to test, but I now wish I had kept the original because it actually worked better even with minor glitches. This is my first main map project, and I created a few test maps while diagnosing the issue. Internet Connection: My internet connection is stable with full signal bars. Steps to Reproduce the Issue: 1. Open Inkarnate in Safari on my iMac. 2. Load or create a new fantasy map. 3. Place several assets (for example trees or mountains). 4. The assets are placed but do not appear visually on the map. 5. Selecting the asset from the asset list shows its location even though it is invisible. 6. At times during this process the editor becomes unresponsive. Expected Result: Assets should appear immediately when placed and the editor should remain responsive. Actual Result: Assets are placed but remain invisible, and the editor can freeze. Overall Experience: Before the 2.0 update, the program worked fine in Safari with only minor slowdowns. During the short time after the update when the program seemed to work properly, it was still usable aside from minor glitches. Now the program is essentially unusable, which is a major regression from how it worked before. I hope this helps you fix the bugs.
0
·
Website
Load More