OTOY Forums

Hello, is there any news on support for the gtx 1070/1080 gfx cards?

The Windows installer below includes support for the GTX 1070/1080 cards. I will formalise this release once the OSX build is done.

https://render.otoy.com/customerdownloa ... _Win64.exe

Paul

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

3.3.2.75
- Compiled with Octane 3.03.2

Paul

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

3.3.2.75
- Compiled with Octane 3.03.2

Paul

That's the link for Revit ( OctaneRender_for_Revit_2015_3_3_2_42_Win64.exe )

That's the link for Revit

Fixed - sorry about that.

Paul

Following is a pre-release (Windows only) of the next version of the plugin.

3.3.2.76 (pre-release)
- Added the option to upload the current scene to the Octane Cloud Renderer via the Settings->Upload Frame to Octane Cloud Render menu option.
- Added the option to upload the current animation to the Octane Cloud Renderer via the Animation->Cloud Render button
- Fixed issue where the NodeGraph Edit button would no longer be displayed for NodeGraph materials after refreshing the scene
- Fixed issue where Export Animation and Cloud Render (Animation) were both ignoring the Start Frame and End Frame numbers

https://render.otoy.com/customerdownloa ... _Win64.exe

Paul

Thanks for the update Paul! Editing nodegraph materials works great now.

One other thing I noticed (and I apologize if this is already a known issue) is that when trying to use a Gradient texture, the below error comes up when you try and change the Interpolation value. The scene will still render, so I'm guessing it just uses the default linear interpolation, but it looks like the setting can't be changed.

Note that the Gradient texture does not have this issue when used within a nodegraph material, so there is a workaround.




-Matt

One other thing I noticed (and I apologize if this is already a known issue) is that when trying to use a Gradient texture, the below error comes up when you try and change the Interpolation value. The scene will still render, so I'm guessing it just uses the default linear interpolation, but it looks like the setting can't be changed.

I will fix this. The Gradient node via the Material Tree does not allow for the adding of interpolation points, so it is of limited value, and you would generally want to access this node via the NodeGraph. However the python exception needs to be fixed.

Thanks

Paul

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

3.3.3.76
- Compiled with Octane 3.03.3
- Added the option to upload the current scene to the Octane Cloud Renderer via the Settings->Upload Frame to Octane Cloud Render menu option.
- Added the option to upload the current animation to the Octane Cloud Renderer via the Animation->Cloud Render button
- Fixed issue where the NodeGraph Edit button would no longer be displayed for NodeGraph materials after refreshing the scene
- Fixed issue where Export Animation and Cloud Render (Animation) were both ignoring the Start Frame and End Frame numbers
- Fixed issue where selecting the Gradient->Interpolation pin would raise a python exception

Paul

Hi Paul,
is there some description on how that cloud thingy works and what it does in the first place?