topic Re: Textures mismatch in 3ds Max Shading, Lighting and Rendering Forum

Textures mismatch

joao_pinto6Y3P7 — Tue, 05 Aug 2025 11:40:08 GMT

What am I doing wrong for the texture displayed in the viewport and in the rendering to be different?

Re: Textures mismatch

MartinBeh — Tue, 05 Aug 2025 12:56:15 GMT

For starters, your rendering has different lighting (global illumination, soft shadows) than your viewport.

Unfortunately your screenshot does not show what viewport mode you are in. Maybe switching the viewport from "Standard" to "Realistic" gives you something a bit closer?

But generally you cannot expect the realtime viewport to be a 1:1 match to an offline raytracing renderer.

Re: Textures mismatch

joao_pinto6Y3P7 — Tue, 05 Aug 2025 13:54:01 GMT

That is not true at all. If I use the Unwrap UVW modifier, I can assign the respective texture to each face and make it visible in the viewport. For some reason, I am not able to do this with the UVW Map modifier. My viewport is set to Standard, but the same thing happens if I increase it to High Quality.

Re: Textures mismatch

MartinBeh — Tue, 05 Aug 2025 14:04:40 GMT

Sorry for misunderstanding this (a little longer description would have helped).

I thought you are referring to the differences in lighting/brightness etc. but now I understand you are referring to different UV/texture layouts.

Re: Textures mismatch

joao_pinto6Y3P7 — Tue, 05 Aug 2025 14:23:20 GMT

Sorry for the poor description. Regarding the texture layout, can you understand what the issue is?

Re: Textures mismatch

MartinBeh — Tue, 05 Aug 2025 14:27:57 GMT

No, sorry. There is still too little information.

Also, I am not a Vray/Corona user, which seems to be what you are using, correct?

But if you upload a .max file, I am sure someone will be able to take a look.

Re: Textures mismatch

Casey_H_ — Tue, 05 Aug 2025 17:20:51 GMT

Off the top of my head, I have noticed sometimes that if I change the file linked to the map in the material by drag and drop, that it won't update in the rendering until I manually "reload" the bitmap, or update the preview. This is especially true when said bitmap is deep within a complex hierarchy of sub-materials. Maybe this is also affected by network paths for texture files, as opposed to local files, not updating immediately in Max due to network issues, but I have not tested this.

As far as I know, the Slate Material Editor is set to NOT automatically update material previews by default, so I always make sure that setting is turned on. This drove me nuts at first. There were several times that I was making adjustments to materials based on test renders and nothing was making a difference... until I realized the preview wasn't changing, which then rendered correctly after updating it. I think auto preview updates should be on by default.

This is just a guess!

@MartinBeh is correct that more info is needed for best analysis.