View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004356 | NoesisGUI | Studio | public | 2025-08-25 17:33 | 2025-08-27 14:32 |
| Reporter | dstewart | Assigned To | jsantos | ||
| Priority | normal | Severity | feature | ||
| Status | assigned | Resolution | open | ||
| Product Version | Studio_Beta | ||||
| Target Version | Studio_Beta | ||||
| Summary | 0004356: Method To Support Vectors As Files | ||||
| Description | This ticket comes from recent Client feedback in which it was stated that there was an unmet expectation that Vector artwork files would be able to be treated as equally to Bitmap, Video, Audio, or other asset filetypes. The particular use case for this, was that in many production workflows, when the appearance of an Asset is updated, it is simply exported from the external tool its authored in, and saved over the previous version of the assets. For example, an artist may create a Badge in Photoshop, export it as a PNG, and reference it in-Engine. Then, when the asset requires an update, the artist will make the changes in the Photoshop file, and then directly write over the original PNG, to have the updated asset update in-game without having to touch anything other than the PNG itself. However, for an artist working with vector formats, they are unable to accomplish an equivalent workflow using Adobe Illustrator, and the SVG export format. Instead, to update any Vector asset, they must not only open the editor to make the changes, but then they must also find each instance where the vector artwork is used, delete the previous version of the artwork, and then copy-paste the newest version in its place in all relevant XAML files. The fact that vectors must be manually implemented and updated one-by-one also means they cannot benefit from batching/exporting processes in the same way bitmaps can be. Vectors are currently the only asset type which don't follow the 'File' asset format, resulting in friction in both expectations, as well as requiring exceptional workflows from all other assets if vectors are desired to be used and supported. | ||||
| Platform | Any | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-08-25 17:33 | dstewart | New Issue | |
| 2025-08-25 17:52 | jsantos | Assigned To | => jsantos |
| 2025-08-25 17:52 | jsantos | Status | new => assigned |
| 2025-08-25 17:52 | jsantos | Target Version | => Studio_Beta |
| 2025-08-25 17:52 | jsantos | Relationship added | related to 0002311 |
| 2025-08-25 17:52 | jsantos | Relationship added | related to 0002614 |