Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relative paths to textures? #31

Open
generrosity opened this issue Mar 15, 2023 · 0 comments
Open

Relative paths to textures? #31

generrosity opened this issue Mar 15, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@generrosity
Copy link

generrosity commented Mar 15, 2023

Hi! I see this repo doesn't have a issues template - I hope the below info is ok.

Using: recently downloaded FBX2glTF 0.13.0, and Godot: v4.0.stable.official [92bee43ad]

I recently purchased a Synty bundle thinking that I might be able to 'just drop' assets in Godot. Oh my!

Generally speaking, the Synty folder structure is reasonably fixed with a subfolder of Texture, with individual assets and characters in subfolders (and a demo in its root which tbh is an anomoly and users can shift to subfolder if that is easier);
image

Looking at the demo map fbx with Notepad++ I can see references to;

  • Filename U:/Dropbox/SyntyStudios/PolygonRoyale/_Working/Textures_Unreal/PolygonBattleRoyale_Road_01.png
  • RelativeFilename ....\SyntyStudios\PolygonRoyale_Working\Textures_Unreal\PolygonBattleRoyale_Road_01.png
  • XRefUrl U:/Dropbox/SyntyStudios/PolygonRoyale/_Working/Textures_Unreal/PolygonBattleRoyale_Texture_02_A.png
  • Shininess 4 (if you squint between the double/number/D/etc)

In Godot, this appears to translate to a models with shared textures - awesome! This does make fixing the scene vastly easier.

  • Name: Mat_PolygonBattleRoyale_Road_01 😮
  • surface/material/albedo/texture - empty 😢
  • alpha - I have no idea what to set this to, all the setttings seem weird checking a Quartunius nature tree.
  • Metallic + Roughness - has values? I reset these, and things look cvastly better, and I don't ^think^ I dragged files in the wrong places in all places. 😒
  • ShadowMesh - (part of godot import, never mind)

I imagine this project really isn't able to read the encoded details in these files , especially as they change all the time. And I imagine that the intent of the tool is to deal only in the files that are provided rather than to 'look' around and try fix things.

I'm wondering if "Mat_" is a prefix used in fbx2gltf, and to specify a different prefix/suffix instead? "..\Textures{name}.png" or something that be recognized by Godot might MIGHT be a relatively trivial change?

Thanks for the long read - I hope it makes sense!

@fire fire added the bug Something isn't working label May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants