the texture maps of Gears 5 are broken. generally with the ending .b2tex1, .b2tex0 are converted with TexmorphGears in .dds format appearing completely broken,
the problem only in the normal maps.
Using TexmorphGears_BC7 the dds file cannot be opened.
someone else has this problem, is there a way to solve it?
-----ZOOM----
Like I said the BC7 is only supposed to be used with the b2tex1 files. And yes, it appears that you're problem is caused by the photoshop plug-in since it should be able to open output BC7. For blender, BC7 is not supported directly. You can download the compatible one here: https://download938.mediafire.com/1oguyx5m5gcg/9eb8rk1mqcxe9k1/Plug-ins.rar After installing this plug-in, you should be able to open the BC7 output dds files.
I use the Texmorph Free Tool V1.9 I downloaded it 2 days ago with a link that they sent me by mail.
b2tex2, b2tex0 work correctly using TexmorphGears
The b2tex1 files are converted but appear broken.
I can open all the converted files with TexmorphGears using my phrotoshop plugin, even using them directly with blender. in this way I do not need to use photoshop to use this file, I suppose it would be ruled out that my photoshop complement is causing the problem
converting the same file into TexmorphGears_BC7 I get a dds file that cannot be read by photoshop or blender, whether b2tex2 files or b2tex1 or b2tex0, no file works for me using TexmorphGears_BC7
Hi, first of all, thank you for reporting your problem with using our forum. For your problem; .b2tex0 textures are low-res versions of .b2tex2 textures which we assume you won't need. .b2tex1 textures are normal maps and they're supposed to be converted with the BC7 exe. If you get sizzly results like this with the BC7 exe too, that means your Texmorph version is old. Or if you can't open the resulting BC7 DDS EVEN WITH PHOTOSHOP, that means your photoshop plug-in is old or incompatible. Below, there's the correct output DDS normal map of the texture you're trying to open. If you can't open this file, it means there's a problem with your plug-in like I said and we would be more than happy to help with it if that's the case.
@Arwglacy could you help me with this problem?