Page 1 of 1

Mesh UV projection problem

Posted: Thu Jun 27, 2024 8:37 am
by HHbomb
Hi,

I have a material with a texture with a projection "Mesh UV projection" set to 3.
Each time I open my scene, the projection isn't applied. I need to change the value in the node ( 3 to 2 then 2 to 3 ) then the projection is applied. :evil:

note : UVW MAP modifier applied to the objects is instanced.
pbuv.JPG
Thanks !

Re: Mesh UV projection problem

Posted: Mon Jul 08, 2024 10:10 pm
by neonZorglub
HHbomb wrote:Hi,

I have a material with a texture with a projection "Mesh UV projection" set to 3.
Each time I open my scene, the projection isn't applied. I need to change the value in the node ( 3 to 2 then 2 to 3 ) then the projection is applied. :evil:

note : UVW MAP modifier applied to the objects is instanced.
The attachment pbuv.JPG is no longer available
Thanks !
Hi HHbomb,

I couldn't reproduce the issue.
It seems to work fine..
Here is a sample scene with the uv set to 1,2,3 and mixed on several boxes..
UVSet123_sample.zip
(1.18 MiB) Downloaded 70 times
You may have other settings that prevent the correct initialization at load time ..?
Could you post a sample scene ?
Thanks

Re: Mesh UV projection problem

Posted: Tue Jul 09, 2024 11:21 am
by HHbomb
Hi,
It seems that it is a problem with normal maps.
PBNM1.zip
(342.3 KiB) Downloaded 71 times
when I open the scene, I have the left render, it I change the value of the Map#399 ( from 3 to 2 then 2 to 3 ) I get the render of the right.

Hope the max file can help. :-)

Re: Mesh UV projection problem

Posted: Thu Aug 01, 2024 8:57 am
by HHbomb
bump

Re: Mesh UV projection problem

Posted: Tue Aug 06, 2024 5:24 am
by neonZorglub
HHbomb wrote:Hi,
It seems that it is a problem with normal maps.
PBNM1.zip
when I open the scene, I have the left render, it I change the value of the Map#399 ( from 3 to 2 then 2 to 3 ) I get the render of the right.

Hope the max file can help. :-)
Hi HHbomb,
Sorry for the delay.
Thanks a lot for the scene. I could see the problem.
The issue will be fixed in the next release.
Thanks