OTOY Forums

The Qt5 IPR is not available yet, although the options to configure or open it are already there. Now when you select the Qt5 IPR, the plugin falls back to the conventional OpenGL IPR.

RTX is not enabled by default yet because there are still some issues with this feature in the core. It will be enabled in the future, but in any case, if you enable it, it should remain enabled.

Thanks,
-Juanjo

juanjgon wrote:The Qt5 IPR is not available yet, although the options to configure or open it are already there. Now when you select the Qt5 IPR, the plugin falls back to the conventional OpenGL IPR.

RTX is not enabled by default yet because there are still some issues with this feature in the core. It will be enabled in the future, but in any case, if you enable it, it should remain enabled.

Thanks,
-Juanjo

Hey Juanjo,
sorry for asking - might be a stupid question.
What is the Qt5 IPR?

Best,
Gregor

Gregor.Zimmermann wrote:
Hey Juanjo,
sorry for asking - might be a stupid question.
What is the Qt5 IPR?

Best,
Gregor

It is a new IPR window based on the same GUI lib used by Houdini (Qt5) that hopefully will replace all the other IPR modes in the future, including new features like docking, full support of all OS including MacOS, etc.

Thanks,
-Juanjo

on 2020.1 this current project renders just fine, not a single issue with complexity or cuda 700.
on 2020.2 it starts to render and fails immediately reporting


*** OCTANE API MSG: -> failed to unload module
*** OCTANE API MSG: OptiX error for device 1: [ERROR] Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
*** OCTANE API MSG: OptiX API error for device 1: CUDA error
*** OCTANE API MSG: OptiX error for device 1: [ERROR] Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
*** OCTANE API MSG: OptiX API error for device 1: CUDA error
*** OCTANE API MSG: OptiX error for device 1: [ERROR] Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
*** OCTANE API MSG: OptiX API error for device 1: CUDA error
*** OCTANE API MSG: OptiX error for device 1: [ERROR] Failed to destroy launch resources (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
*** OCTANE API MSG: OptiX API error for device 1: CUDA error
*** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered

Great to see OCIO integration! Also excited about the new QT IPR. Any estimate on when that feature will be working?

Hey Juanjo,

As usual thanks so much for all your hard work!! Running into an alpha-channel related issue - while enabling alpha channel still works, I'm unable to get pre-multiplied alpha working. Looks like pre-multiplied alpha toggle isn't having any effect at all in this build.

Hello juanjgon
May I write some features and fixes, I would like to see in future updates?
1. Some time i work with small scene scale, and in AO Passes when I decrease less than 0.01, there is no effect. To get the radius I want in the AO pass, I have to enlarge the whole scene. And sometimes it can be very problematic. Please make available values below 0.01
2. It would be very cool to set a distance range for the Zdepth pass. One parameter "Z-depth max" is not enough. Wanna "Z-Dept min" too.

Thanks you

any idea when a demo will be released for this? excited to try out

snakeboxmedia wrote:There seem to be a bug where the Post process, bloom / glare all of it doesn't work. Doesn't matter if denoise is enabled or not, the entire tab just doesn't do anything (I haven't tested in the IPR fix build yet).

This problem comes from a bug affecting all the nodes with pin names including underscores. It will be fixed in the next build.

Thanks,
-Juanjo

mlmcgoogan wrote:Hey Juanjo,

As usual thanks so much for all your hard work!! Running into an alpha-channel related issue - while enabling alpha channel still works, I'm unable to get pre-multiplied alpha working. Looks like pre-multiplied alpha toggle isn't having any effect at all in this build.

This problem also comes from the bug affecting all the nodes with pin names including underscores. It will be fixed in the next build. The same happens with the vertex displacement. All come from the same issue.

Thanks,
-Juanjo