OTOY Forums

Hi richardyarlett,
This problem is fixed in new version 2.23.
I added a new option, (currently disabled by default), in Tools tab of the Render Setup window:
'Enable 3dsMax Viewport UV correction'

To summarize the issue:
When using 'real world scale' in geometry, 3dsMax generate unusual UVs (far from the 0 to 1 range, depending on unit settings, for example 0 to 50)
This would normally display the texture as tiled (eg, 50 times)
To keep the visual appearance correct, the 'real world scale' in the Standard Bitmap settings automatically set a corresponding 'big' scale (eg 50)

In Octane, this 'big' scale is set in the UV transform of the RGB image.
As you can see in the material editor preview, the default result is that only a zoomed portion of the center of the texture is visible. This was also used in the max viewport, witch gives the visible tiling effect..
The new option enables to use the un-zoomed version of the texture for the max viewport..

It might also be needed in other cases, even not using 'real world scale', if UV settings are tweaked somehow..

I hope you'll be able to see your work correctly now !

Thanks for pointing this out, and for your patience.
NeonZorglub

Thanks.

I think long term this HACK needs to be correctly inserted into the main code and stable though. A hack is fine for a while, but lets get it fixed in the core.

Ok ok after a LOT OF RESEARCH and installing and uninstalling every version since 3.02 - 3.17 upwards, I have found the exact version where the VIEWPORT TEXTURE PREVIEW was broken for textures using the "REAL WORLD MAP SIZE" as I use in architectural rendering.

VERSION 3.03.2 - 4.9 it was completely fine. See attached.

VERSION 3.03.2 - 4.10 it was suddenly broken. See attached.

Both of these screenshots have IDENTICAL settings. Nothing changed. The texture map is applied with a 12 x 12 "REAL WORLD MAP SIZE"
There must be something subtle in the code you guys changed that broke the VIEWPORT textures preview system. Please try to dial into this new information. It took hours to figure out exactly when it got broken.

This is totally an issue for me as well. Any update on a fix?

It is SUPPOSED to be fixed in the next version, 4.27, but I have been waiting for ages. I have gone back to 3.03.2-4.9 which is right before they broke it. Works fine.