Page 8 of 13
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Fri May 24, 2019 6:19 am
by face_off
An issue I found with the latest V4 build. Changing the cameras White Point does not update in IPR.
edit: same for sky color, sunset color, ground color, stereo left filter and right filter.
This is fixed in the next release.
Keyable camera resolution would be nice too
Can you explain the use of this pls? It is not a trivial change, as things like the render buffer size would need to change each frame during an animation, so if there is another way to achieve what you are trying to do, that would be good.
Paul
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sat May 25, 2019 2:44 am
by face_off
I have updated the WINDOWS version at the top of this thread with:
4.04.0.145
- Fixed error where changing a color property from an item that was not a material (ie. the white balance) was not live updating the Octane viewport
- Fixed "Mesh not present in mesh item map when adding to mesh container" displaying when using the octane.saveAnimation command on a scene with a blank mesh used as an instance source
- Moving the Modo Camera via the OpenGL viewport now live-updates in the Octane Viewport
Thanks
Paul
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sat May 25, 2019 7:06 am
by funk
Thanks for continuing the 4.x updates too Paul
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sun May 26, 2019 8:50 am
by profisatz
v. 4.04.0.145 (and previous)
on
octane.importLocalDB
Values from Index N + K, Index Green N + K, Index Blue N + K
are missing, even if they are made with separate floating value nodes
tested with metallic and universal material
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sun May 26, 2019 11:58 am
by face_off
v. 4.04.0.145 (and previous)
on
octane.importLocalDB
Values from Index N + K, Index Green N + K, Index Blue N + K
are missing, even if they are made with separate floating value nodes
tested with metallic and universal material
Hi. Can you send me an ORBX file from your LocalDb which does this please, and I will take a closer look.
Paul
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Thu May 30, 2019 12:23 am
by face_off
v. 4.04.0.145 (and previous)
on
octane.importLocalDB
Values from Index N + K, Index Green N + K, Index Blue N + K
are missing, even if they are made with separate floating value nodes
tested with metallic and universal material
Thanks for sending through the sample ORBX file. This problem is fixed in the next release of the plugin.
Paul
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sat Jun 08, 2019 7:49 am
by MrFurious
face_off wrote:An issue I found with the latest V4 build. Changing the cameras White Point does not update in IPR.
edit: same for sky color, sunset color, ground color, stereo left filter and right filter.
This is fixed in the next release.
Keyable camera resolution would be nice too
Can you explain the use of this pls? It is not a trivial change, as things like the render buffer size would need to change each frame during an animation, so if there is another way to achieve what you are trying to do, that would be good.
Paul
Thanks Paul, workaround is to duplicate the camera. If this is not so trivial to implement I'd just go with the workaround.
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sat Jun 08, 2019 7:52 am
by MrFurious
Loving the latest v4 build. Having IPR update with the camera is great, reminds me of my lightwave/octane days. Generally IPR seems more responsive even with changes to materials, colours etc. One thing I notice though... if 'enable denoising' is checked in the imager this slows down the fluidity / framerate or IPR refresh. Can this be corrected as I almost always like to have denoising on.
Cheers
Dino.
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sat Jun 08, 2019 7:58 am
by MrFurious
FYI modo shows the installed plugin as 2018 for v4 users with the latest build.
Re: OctaneRender 4 for Modo [TEST and STABLE]
Posted: Sun Jun 09, 2019 11:40 pm
by face_off
FYI modo shows the installed plugin as 2018 for v4 users with the latest build.
Thanks - I will fix this in the next release.
One thing I notice though... if 'enable denoising' is checked in the imager this slows down the fluidity / framerate or IPR refresh. Can this be corrected as I almost always like to have denoising on.
I could not reproduce this. Can you provide a workflow which demonstrates the problem please?
Paul