UV map discrepancy

[Godstrike]

Hi Juanjo,

I have noticed that on Octane for LW version 3.02.2.0 under LW 15.2 that sometimes a UV map is rendered differently depending on whether the map is loaded 'natively' (for the want of a better word), or whether I load the same UV map in the LW material and use UVMAP / Lighwave T colour functionality.

Is this a known issue?

Carlo

[juanjgon]

Can be possible. The LightWave UV map extraction functions can be not exactly the same the Octane functions (for example while managing negative UV values, UV values over 1.0, UV seams or discontinuous maps, etc). Can you post a sample scene or a screen grab about the differences you have found?

Thanks,
-Juanjo

[Godstrike]

Been slammed with work, will find that issue today and send some screenshots.

Another thing that cropped up is the motion blur on a 3 blade propeller.

It's spinning at approx. 3000rpm, and the ends the propeller have green tips.

I would have thought the blur would have been perfectly circular, but it's very asymmetric.

Any ideas?

Thanks,
Carlo

[juanjgon]

You could need increase the objects motion blur steps perhaps to 15 or 20 (or even more). You have this parameter in the render target root node options panel, in the MB tab.

-Juanjo

[Godstrike]

I tried up to 12 with no difference, will bump up further. Thanks.