OTOY Forums

Yep that sounds right. 2020 is still an experimental build (alpha/beta), so things can change. These changes are in the octane core (see the standalone thread) so the plugins have to follow.

funk wrote:Yep that sounds right. 2020 is still an experimental build (alpha/beta), so things can change. These changes are in the octane core (see the standalone thread) so the plugins have to follow.

I know and it makes sense to make it compatible with 2019. Not blaming anyone else than myself for the extra work.

I did not see any note about this in the XB3 standalone thread though. A search for Radius Maps only takes me to my own post.

Obizzz wrote:

funk wrote:Yep that sounds right. 2020 is still an experimental build (alpha/beta), so things can change. These changes are in the octane core (see the standalone thread) so the plugins have to follow.

I know and it makes sense to make it compatible with 2019. Not blaming anyone else than myself for the extra work.

I did not see any note about this in the XB3 standalone thread though. A search for Radius Maps only takes me to my own post.

Yeah its not specifically mentioned in their release notes, but you can see the change if you run standalone. In standalone, they are automatically converting previous scenes on load, but thats not possible with the modo plugin.

Thanks. I have these scenes saved as standalone scenes as well so I'll open them in XB3 to verify the values.

Paul: Might be worth adding to the 157 release notes that the instruction for build 156 no longer applies and the user needs to change it back if the scene was saved in XB1.

I have updated the installers at the top of this thread with:

2020.1.0.159
- Compiled with Octane 2020.1 RC2
- Fixed issue where saving the Modo scene file would sometimes restart the render
- Revised the render status window to only show relevant information, and also provide details for when render region is on
- Added support for U & V Tile Offset for image maps during on-the-fly material conversions and with Octane Overrides. As Modo and Octane apply UV rotations, translations and scaling in different orders, applying a rotation, scale and translation to a Modo Texture Locator will not render correctly in Octane. I have submitted a feature request to Octane to help resolve this.
- Added texture locator support for UV options on light textures
- Added Object Motion Blur support for Mesh Instances. When the Mesh "Object Motion Blur on Instances" channel is enabled, the visibility of the mesh and instances CANNOT be animated, and the visibility state will be taken from frame 0 and apply throughout the animation. if "Object Motion Blur on Instances" is not enabled, the visibility of the mesh and instances is determined at the CURRENT FRAME being rendered (as happens currently).
- Fixed bug where Animation Samples Per Frame values other than 1 were not working correctly if object motion blur was enabled for that replicator
- Added UI Hints to the Octane material node Dispersion pins
- Improved the rendering statistics window so that it now shows the Info passes being rendered after the beauty pass (useful on complex, slow rendering scenes)
- Fixed issue where Octane Proxies could not be edited or saved if they were an instance source mesh

Thanks

Paul

Hello, I have a simple scene with a vdb item attached to a volume item, and while rendering the animation I get the error "Duplicate material Volume:Volume in AppendMaterialNode" at each frame: the error message stops the renderi every time it popups. Is there a way to get rid of this message?
Octaner for modo 2020.1.0.159

Thanks.

G

GOTHACOM wrote:Hello, I have a simple scene with a vdb item attached to a volume item, and while rendering the animation I get the error "Duplicate material Volume:Volume in AppendMaterialNode" at each frame: the error message stops the renderi every time it popups. Is there a way to get rid of this message?
Octaner for modo 2020.1.0.159

Thanks.

G

Hi - can you send me the scene please?

Paul

face_off wrote:

GOTHACOM wrote:Hello, I have a simple scene with a vdb item attached to a volume item, and while rendering the animation I get the error "Duplicate material Volume:Volume in AppendMaterialNode" at each frame: the error message stops the renderi every time it popups. Is there a way to get rid of this message?
Octaner for modo 2020.1.0.159

Thanks.

G

Hi - can you send me the scene please?

Paul

PM sent.

Substance plugin compatibility looks to be broken with 2020, example below. It seems to be working fine if I manually import and assign all the maps.

Modo 14, Substance 2.7.3 and octane 2020 rc2.

paberu wrote:Substance plugin compatibility looks to be broken with 2020, example below. It seems to be working fine if I manually import and assign all the maps.

Modo 14, Substance 2.7.3 and octane 2020 rc2.

This is a problem with recent versions of Substance. It was reported to the Substance devs about a year ago, but I am not aware of any resolution yet. May I suggest you report the problem on the Substance forums.

Thanks

Paul