AcademySoftwareFoundation / AcademySoftwareFoundation/MaterialX

TextureBaker: No way to create baked documents / images without writing to disk

Open
#1,591 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
2.3k
Forks
451
Avg merge
6d 6h
Merged PRs (30d)
5

Description

## Issue

Currently the texture baker API does not allow access to the resulting baked documents and images in memory.
They must be written to disk and re-read in again which is inconvenient where file access is either inconvenient or
not available.

## Proposal

Allow to not always write to disk and provide accessors to the in-memory images and documents.
Basically this members:
* _bakedImageMap
* _bakedTextureDoc

Contributor guide

Open the contributing guide

Research direction

Start with the TextureBaker API and inspect the existing _bakedImageMap and _bakedTextureDoc members. Trace how baked documents and images are currently written to disk, then define the in-memory access path and optional disk-writing behavior. Done means callers can access the baked results without requiring file access.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.