OctaneRender™ 3.0 for LightWave™ - Test build 3.06.0.4

[fibernaut]

Hi Juanjo

i have a problem with a 3.02 project after installing the newest test build. This project makes use of the orthographic camera. Now, the scale value seems to have changed in the newest build. My objects are now extremely far away form the camera. Even if i try to lower the value i can't get as close to the object as in 3.02. Is this a bug?
Thanks

[juanjgon]

Hi,

In the thinlens camera there is a new option to set the orthographic scale in meters to match the LW ortho camera, but with this option disabled the old scenes should be rendered like before. Do you have this option enabled?

Thanks,
-Juanjo

[fibernaut]

Hi

no, i don't have this option enabled. I tried, but there was no change. I also added a new thinlens node to make sure it has nothing to do with some kind of value caching, but also no change.

For now i can render the particular image on my second machine but it would be nice if this could be done within the newest build.

[juanjgon]

Weird. Can you send me the .lws scene file?

Thanks,
-Juanjo

[fibernaut]

There you go.

Deleted all unnecessary objects and images.

SceneJuanjo.zip

(9.1 KiB) Downloaded 200 times

[fibernaut]

This is how the object distance rendered before.

[juanjgon]

Hmm ... this is what I get loading and rendering your scene. It seems fine, using this latest plugin build. Don't you get the same rendering using this scene?

Thanks,
-Juanjo

[juanjgon]

One second. You have the camera node disconnected from the render target node, so this is the view from the default camera, that doesn't have the ortho options enabled. What do you get if you connect the camera node?

-Juanjo

[juanjgon]

Ok. Yes, I can reproduce the problem with the ortho camera. It seems to work fine in the 3.04.3.0 build, but it is not the same in the latest build. Investigating ...

-Juanjo

[juanjgon]

I've found the problem. It was a side effect introduced to fix a problem with the .orbx camera export functions. It will be fixed for the next build that I want to release later this week, but if you need this problem fixed now for your project let me know. I can send you a custom build with this issue fixed.

Thanks for reporting it!
-Juanjo