Open Hortophyll opened 1 week ago
I believe this would be best as a pgtools
function. If you didn't know pgtools
is a CLI tool designed for mod developers that will have a bunch of useful function related to parallaxgen. I believe this function could fit there. pgtools is slated to be available sometime in the 0.6 release cycle, so sometime soon.
Wow nice! A big thank you :)
Do you think there is a problem in the following case: diffuse: example_d.dds or example_diff.dds
My normal map: example_d_n.dds or example_diff_n.dds
And similarly strange names of diffuse textures?
There are certain suffixes parallaxgen will remove when matching. _d
is one of them, but _diff
isn't. Generally I only include the suffixes that are supposed to be used. So example
diffuse would match with example_d
normal which would not match. Though I guess I could have it try to remove suffixes until there isn't anything to remove, then example
and example
match, but that doesn't solve the issue with _diff
being nonstandard. I can just add _diff
to the list of possible suffixes, it's not a big deal
Ok, so if I understand this correctly, I have the new problem that in the end my normal maps no longer match the diffuse ones if they are named as in my examples. Am I right?
Or, I go through the textures and look at all the suffixes, make a list and give it to you to see what else you could add? Then all suffixes would be removed and it would fit together?
Yeah, though now I'm second guessing how I implemented this so maybe I can figure out a better solution that doesn't break in these cases
I wish I could contribute more :/
But then let's do it this way, you tell me when I should do what exactly and then I do it :D
In the current 0.6 build of parallaxgen, you have to use standard suffixes only. So _d or _n (but not _d_n or _diff etc.).
I will try to figure out a better way to do this for a future version but I don't have guidance on that yet because I'm not sure what it will look like
Yes, that's exactly why I meant, I don't have any stress myself because I still have to tweak textures. Whatever the solution would be then, that's how I'll do it :)
I also sent you a small donation, generally as a thank you for your programme and for wanting to help me. That is not a matter of course :)
@Hortophyll thank you, I appreciate it! I will keep you updated
As discussed, here is the request regarding my problem with the normal maps in enderal.
enderal uses its own meshes with its own diffuse textures, but many of them have normal maps from skyrim in use.
this leads to the problem for my complex parallax mod, which is currently in progress, that with such meshes not my texture is patched, but that of a skyrim mod.
as can be seen in the following example
the solution would be to either manually adjust all normal maps and make the meshes available. or ideally i can use your tool for this. i specify the path to the directory of my textures and your tool matches the diffuse textures with the normal maps and patches all affected meshes. my normal maps always have an _n.dds at the end.
i could then make these meshes available and users of enderal could then use your program as normal to patch the remaining meshes as they wish
if you need more information, please contact me, discord is also fine
thank you