Importing an FBX file loses any texture assignments that point to broken texture paths
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- computer-graphics
Research direction
No files, tests, or entry points are named. Locate the FBX importer’s texture-reference handling and inspect how broken paths are discarded. Done means imported materials retain broken texture assignments; optionally, same-named textures from the source folder are selected with a warning.
Written by the indexing model from the issue text.
Description
When importing an FBX file, it is common that some of the texture paths are broken. This is due to the lack of tooling to properly export relative paths for FBX textures.
A typical fallback is to look for the texture in the source directory, the one containing the source FBX file being imported.
In addition, completely discarding textures that are not found makes it impossible to fix the texture paths in a post-processing pass, as it would be usual in an asset ingest pipeline.
Expected Behaviour
Importing an FBX file with broken texture references will result in materials with the broken textures still assigned, so that it is possible to inspect the usd stage and proceed with fixing the paths.
Optional Extension
As a fallback, any textures with the same filename, present in the source folder, will be picked instead, but a warning will be logged so that the user is aware of the tentative fix.
Actual Behaviour
The texture is completely ignored and the material will be missing the texture assignment, making it impossible to reassign the texture at a later stage.
- Dominant language
- C++
- Stars
- 396
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/USD-Fileformat-plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
adobe/USD-Fileformat-plugins#79 · 1 comment ·
-
Use system eigen Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
adobe/USD-Fileformat-plugins#80 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 50/100
All issues in adobe/USD-Fileformat-plugins
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·