GGMAX Bug - Importer Shows Incorrect _surface filename

[TenebreGaming]

So this has been perplexing me for a while and I finally realized what's going on...

When importing a .FBX, if the texture files are in the same directory, MAX ill use them. In order for this to work, the texture names must be assigned (inside the model file) as (for example) "texture_color.png", "texture_normal.png", and "texture_surface.png". This is how it's supposed to work.

However, the importer fills out the surface field by appending "_surface" to the name of the albedo, so it will be "texture_color_surface.png". The .FPE file, however, is given the correct name of "texture_surface.png".

[MonkeyFrogStudio]

This is not happening on my end ... so far. I import .fbx files almost daily and MAX is using the exact names I am giving all my textures. However, my workflow from Blender to MAX is most likely a bit different than yours. Yet, like you, I have each model in its own folder with it's textures. So, when I import into MAX, MAX is getting the textures from that folder for that model.

[TenebreGaming]

The import happens correctly, as the .FPE gets the correct file names. It's just showing wrong in the importer.

On Tue, Apr 2, 2024 at 6:52 PM MonkeyFrogStudio @.***> wrote:

This is not happening on my end ... so far. I import .fbx files almost daily and MAX is using the exact names I am giving all my textures. However, my workflow from Blender to MAX is most likely a bit different than yours. Yet, like you, I have each model in its own folder with it's textures. So, when I import into MAX, MAX is getting the textures from that folder for that model.

— Reply to this email directly, view it on GitHub https://github.com/TheGameCreators/GameGuruRepo/issues/5422#issuecomment-2033395158, or unsubscribe https://github.com/notifications/unsubscribe-auth/A725E4WJRUH2WNY2A3GYR4TY3NOGNAVCNFSM6AAAAABFUASWROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGM4TKMJVHA . You are receiving this because you authored the thread.Message ID: @.***>

[MonkeyFrogStudio]

Again, not happening on my end. Here's a screen shot of a model being imported in the importer in MAX:

Notice the name ... not '_surface' appended in the importer. It's bringing in the exact name I've given the texture.

[davetgc]

Is anyone else experiencing this?

[TenebreGaming]

@MonkeyFrogStudio If you re-read the original report as I posted it,

However, the importer fills out the surface field by appending "_surface" to the name of the albedo, so it will be "texture_color_surface.png". The .FPE file, however, is given the correct name of "texture_surface.png".

Perhaps I was unclear by saying it appended to the end of the albedo name, but it takes the albedo name, strips off the file extension, then appends "_surface" to it and adds the extention (and puts it in the Surface field.)

Here you can see the Albedo name

And here is the Surface name (which is wrong and will not match what is put in the .FPE)

As can be seen in this image:

I also just noticed that the path is wrong. While Blender did put the original textures in a xxxx.fbm directory, that is not the name of the directory, as the importer expects them to be in the same directory (and Blender did not have anything to do with making the _surface texture). I would expect this directory to match that of the albedo.

[MonkeyFrogStudio]

This is not happening to me in my Surface channel, either. However, I do name my textures so that they already end with _color, _normal, and _surface.

[TenebreGaming]

I also have the textures properly named, but Blender only knows about the _color texture in this particular case.

On Wed, Apr 3, 2024 at 6:33 PM MonkeyFrogStudio @.***> wrote:

This is not happening to me in my Surface channel, either. However, I do name my textures so that they already end with _color, _normal, and _surface.

— Reply to this email directly, view it on GitHub https://github.com/TheGameCreators/GameGuruRepo/issues/5422#issuecomment-2035933081, or unsubscribe https://github.com/notifications/unsubscribe-auth/A725E4XA24IPJ57P7WN5CDTY3SUWHAVCNFSM6AAAAABFUASWROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVHEZTGMBYGE . You are receiving this because you authored the thread.Message ID: @.***>

[3coms]

This is an old bug for me and still happens to me. GGMax EXP here

[Kasseyus]

I’m currently in the process of going through all the outstanding issues. As this ticket is over a month old, I'm just checking to see if you are still having a problem with this, or if the matter has since been resolved, either through an update to the engine, or if the issue was resolved when another, similar issue was fixed.

Please let me know by replying to this issue and I will investigate further.

[3coms]

The issue still happens; if done, I will report it. :)

[3coms]

I'm still getting, as for example: mytable_color mytable_normal mytable_color_surface, rather than mytable_surface.

The code should just take the texture name and add the _surface subfix. then it'll get: mytable_surface.

[Kasseyus]

@LeeBamberTGC Verified.

When the Importer is launched, and a model has the correct textures to be auto-assigned, the CORRECT _surface file is used, however the file path in the importer is INCORRECT.

The keyword _color is inserted in the file path field, i.e, "mytable_color_surface".

This appears to be a cosmetic issue, as the resultant FPE file is CORRECT and the models function as intended.

[3coms]

I agree. You can close it from my end; although no my ticket. :) This is not a huge issue.