Updates
Tickets

Have something to say?

Tell us how we could make the product more useful to you.

Layers are bleeding together on export/stamps appear which are not there

Hello, sorry for the lengthy title but I didn’t find a shorter description for this problem. I encountered strange behavior when exporting in 4K and higher resolutions. When I export in 2K, the map is exported correctly (see attachments m1_2k.jpg/webp and m2_2k.jpg/webp). When I select a higher resolution, on some maps the layers seem to bleed into each other or some stamps appear which actually are not there (see attachments m1_4k.jpg/webp and m2_4k.jpg/webp). On the m2_4K maps, I outlined the anomaly with a red rectangle so it easier to see. Here are some details on my working/test environment: OS: Ubuntu 24.04.4 LTS (x86_64; GNOME) and Windows 11 Browser: The m1 images were exported using Opera (V133.0.5932.34), the m2 images with Brave (v1.92.139) Graphics Card: Radeon RX 7700 XT / 7800 XT CPU: AMD Ryzen 9 7900X3D 12-Core Processor

Tremah about 1 hour ago

Bugs

Make All Published Maps Cloneable

The thing that has always made Inkarnate special has been its collaborative foundation. There are plenty of other map making tools that have no sharing function, and can replicate much of what Inkarnate can do. The Explore tab used to be more than a gallery, it was a place where map makers and DMs/GMs could find maps that are close, clone them and modify them to fit their needs - assuming they lacked the skill to create impressive maps in the first place. Inkarnate has shifted away from its foundation, though. As a result, many have returned to the old way of Googling the maps that they need, because it provides a much larger selection and an increased likelihood of finding a fitting map. The problem I am talking about is Patreon. It is completely understandable that people want to monetize their work, but the result is that a large majority of the explore tab is no longer usable, or adaptable. Instead, it has become a place for Patreon promotions. I strongly believe Inkarnate would benefit greatly, and reclaim many of its lost subscribers, if ALL published maps were cloneable. Creators can still freely mark their work and promote their websites, but users could still adjust those maps for their specific needs - which again, is the heart of what made Inkarnate so collaborative and popular in the first place. I am not asking to limit creators; if custom assets are used, those will obviously be lost upon cloning, and sure, a creator can make the entire map a custom asset so that it is effectively not cloneable, but that really comes down to a question of character I suppose. If all maps were cloneable, those of us who have been driven away from Inkarnate (I stay because I too make maps for others) would return because it would once again be the best place for TTRPG maps. Unfortunately, due to the influx of Patreon promotions and non-cloneable (paywalled, effectively) maps, that crown has returned to Google Images.

Mickey Hopson 12 days ago

3

Feature Request

Dashboard shows Marketplace Sellers' own unpublished products

The creator can see their own unpublished products on the Marketplace under the 'New' category and in other listings. Potential bug: The site places unpublished products into a published or visible state for the creator themselves. Because the release date is pending, the system treats them as the newest items—essentially answering 'when was it released?' with 'Now'. It's a minor bug and also an edge case, since only the Creator can see it.

Benjamin Weisz 13 days ago

Bugs

In Progress

Published Assets are Deletable

In the art manager, stamps can still be deleted—either one by one or by selecting multiple at once and right-clicking —> Delete Stamp — even if the product is published. (Additional suggestion: it might be worth testing whether this is only possible for Stamps or if other asset types - Texture, Stroke Asset, Preset Asset - can be deleted this way as well.)

Benjamin Weisz 13 days ago

1

Bugs

Let Shadows Point in a Direction (rotation and stretching)

Why is this important? Creating striking dawn/dusk maps with dramatic shadows currently takes a ton of manual work per stamp. Realistically only "super users" have the patience for it, leaving everyone else with flat, “boring” shadows 😥. I also love using the option for solid (non-blurred) shadows, but often, that just makes things look wrong, like they're floating instead of grounded. Why should you consider it? I think this feels totally doable with some basic transform math + object cloning behind the scenes. I mocked it up by hand for the examples below. It'd let way more users create striking, fast directional lighting without needing pro-level tricks :) What could this look like? Simplest version: a rotate slider + squish/stretch transform sliders added to the shadow options. Lets users align a shadow to an object's base and stretch it toward the light source for that dramatic sunrise/sunset look — without extra work for stamp makers or over complicating the feature. For battlemaps (top-down view) this breaks down for things like trees; aligning + stretching to the base gives the shadow the wrong origin point. Fix: an optional mask, centered on the stamp, positioned opposite the shadow's rotation angle, that hides the part of the shadow that the object itself would be blocking. The mask should probably default to centered on the stamp, but a stretch goal could be letting users nudge its origin point manually. Visual examples:

Moop 13 days ago

2

Feature Request