[TEC] Multiple AO-map based camoufleges problem.

[kapuhy]

Seeking advice again - I encountered a weird issue I can't seem to fix.

I'm currently preparing a new pack of ships, one of them being a minesweeper for which I've prepared several variants of camouflage. Camouflages are painted over AO maps named (...)AO01.dds, (...)AO02.dds, (...)AO03.dds..., in similar way it was done for Flower corvette. Roster entries that tell game which variant to use are set exactly like the Flower's, and the material/texture properties in GR2 editor seem to be exactly the same as well.

Except, what does work in case of Flower, doesn't for my new ship.

All is fine if I set AO01.dds as texture:



However, when ship is set to use any other camouflage variant, I get this:



It's not a problem with texture files - if I swap names, texture variant that went crazy when it was named AO02 works fine when it's named AO01, and vice versa. I keep checking everything but so far I wasn't able to track down the cause of this problem.

[U-190]

Originally Posted by kapuhy

Seeking advice again - I encountered a weird issue I can't seem to fix.

I'm currently preparing a new pack of ships, one of them being a minesweeper for which I've prepared several variants of camouflage. Camouflages are painted over AO maps named (...)AO01.dds, (...)AO02.dds, (...)AO03.dds..., in similar way it was done for Flower corvette. Roster entries that tell game which variant to use are set exactly like the Flower's, and the material/texture properties in GR2 editor seem to be exactly the same as well.

Except, what does work in case of Flower, doesn't for my new ship.

All is fine if I set AO01.dds as texture:



However, when ship is set to use any other camouflage variant, I get this:



It's not a problem with texture files - if I swap names, texture variant that went crazy when it was named AO02 works fine when it's named AO01, and vice versa. I keep checking everything but so far I wasn't able to track down the cause of this problem.

It looks like the wrong texture conversion in photoshop.

[kapuhy]

Originally Posted by U-190

It looks like the wrong texture conversion in photoshop.

That was my first thought, so as I wrote above - I swapped file names (AO02.dds to AO01.dds and vice versa). If texture conversion was the problem, I expected that now AO02.dds would work, but no - good texture become garbled like this, and "bad" one displayed correctly when renamed to AO01.

[U-190]

Originally Posted by kapuhy

That was my first thought, so as I wrote above - I swapped file names (AO02.dds to AO01.dds and vice versa). If texture conversion was the problem, I expected that now AO02.dds would work, but no - good texture become garbled like this, and "bad" one displayed correctly when renamed to AO01.

So there is something else. what prevents the correct display of the texture. We need to look for a conflict. Maybe it's another shadow mask.

[Kal_Maximus_U669]

For my part I think that these problems are due to the fact that there is no official driver for the Silent Hunter 4 & 5 series the drivers stop at silent hunter 3 moreover we can see it at the end of the installation the hub which gives the info config is wrong all these problems are linked I am convinced of it the problems of shadows of light passing through ... clipping and I once again do it Ubisoft did not look into it .. and does not care I think