assimp / assimp/assimp-net

Is there a EmbededTexture property from which I can get the texture image reference ?

Open
#50 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
218
Forks
83
PR merge metrics
No merged PRs in 30d

Description

have an issue when I tried to read texture image information using AssimpNet.

The fbx file that I tried to read has 10 embedded textures and has no external textures: texture screenshot

according to the information from assimp, the embedded textures are referenced from materials using strings like "*0", "*1" as the texture paths.

However, among the 12 materials in my fbx file, some them have texture paths like "..\buildings.fbm\6M4P000O.JPG" which corresponds to the image file name

As for the first scenario which has strings like "*0", "*1", I can find corresponding texture by using the number as the reference to Textures, but for the second scenario, I could not find the corresponding file name from Textures because in AssimpNet, the EmbeddedTexture has no such property

But according to assimp, which is the base of assimpnet, from its texture.h file, I found that it has a property called mFilename and from this property we could get the texture's image file name; assimp texture.h

I am wondering if AssimpNet should include filename into EmbededTexture properties so that we could find the correct reference if the filepath contains the filename rather than number.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing AssimpNet's EmbeddedTexture representation with Assimp's texture.h, focusing on the mFilename property and how materials reference Textures. Verify how paths such as "*0" and "..\buildings.fbm\6M4P000O.JPG" are handled, then confirm that the requested filename information is available through the managed API and covered by an appropriate test.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
computer-graphics
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 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.