OTOY Forums

Posted: **Mon Nov 15, 2021 3:31 pm**

HI, on heavy scenes I can't use lastest versions. I need to revert to RC 1 : Max is very slow with 12.6 and 12.07

Posted: **Tue Nov 16, 2021 2:52 pm**

mbetke wrote:I noticed the opacity of my flame gets killed as soon as I move it behind the large glass (specular material).

flame.jpg

Hi mbetke,
enable the alpha shadow in Kernel panel.
Regards
Paride

Posted: **Wed Nov 17, 2021 7:40 am**

Hi mbetke,
enable the alpha shadow in Kernel panel.
Regards
Paride

It is enabled of course! I'm not talking about shadow. The Opacity is just gone. I can see the white background of the flame. When I move the object a meter, so it is not covered by the glass panel, the flame looks right and has its opacity turned on.

EDIT: Two shots

Posted: **Wed Nov 17, 2021 8:18 am**

mbetke wrote:
Hi mbetke,
enable the alpha shadow in Kernel panel.
Regards
Paride
It is enabled of course! I'm not talking about shadow. The Opacity is just gone. I can see the white background of the flame. When I move the object a meter, so it is not covered by the glass panel, the flame looks right and has its opacity turned on.

EDIT: Two shots

Glass-alpha-1.jpg

Glass-alpha-2.jpg

Hi mbetke,
could you share the flame please.
Regards
Paride

Posted: **Wed Nov 17, 2021 8:27 am**

Here is the link: https://www.dropbox.com/s/6srqb41upgj4d ... e.zip?dl=0

Posted: **Wed Nov 17, 2021 3:51 pm**

Hi mbetke,
I think it depends on some .png issue.
Making a new .png it seems to work fine.
Regards
Paride

Posted: **Thu Nov 18, 2021 8:03 am**

I get these errors randomly on several scenes. It's a scene with 4GB. So not out of memory here. What can cause it? Studio Drivers 472.39.
Max has a white background then and I need to close it.

Code: Select all

Started logging on 18.11.21 07:46:43

OctaneRender Enterprise 2021.1 (11000014)

Can't connect node 'oDiff_07 - Default' (NT_MAT_DIFFUSE, 000001E9D7CE3590) to static pin 'layer' (P_LAYER, type PT_MATERIAL_LAYER) of node 'Universal material' (NT_MAT_UNIVERSAL, 000001E9D7CDC510)
failed to create texture object
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to allocate device array
CUDA_ERROR_ILLEGAL_ADDRESS: an illegal memory access was encountered
denoiserThread1 : Exited with a error. Restart required
CUDA error 700 on device 1: an illegal memory access was encountered
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to destroy CUDA event
  -> failed to destroy CUDA event
CUDA error 700 on device 0: an illegal memory access was encountered
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to destroy CUDA event
  -> failed to destroy CUDA event
CUDA error 700 on device 0: an illegal memory access was encountered
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to destroy CUDA event
  -> failed to destroy CUDA event
CUDA error 700 on device 1: an illegal memory access was encountered
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate pinned memory
  -> failed to deallocate pinned memory

Reapeats for hunderets of lines....


CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
OptiX error for device 1: [ERROR] Failed to destroy launch resources (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error de-initializing device (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
OptiX API error for device 1: CUDA error
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 1: an illegal memory access was encountered
  -> could not get memory info
denoiserThread0 : Initialization failed. Restart required

Posted: **Sat Nov 20, 2021 5:13 pm**

Hi Paride,
I am using ornatrix but when I increase hair count vram usage goes up a lot. I thought hair supposed to be treated as instances? And using instanced strands makes hair disappear altogether.
is there a proper way for hair? Thanks

Posted: **Sun Nov 21, 2021 9:03 pm**

mbetke wrote:I get these errors randomly on several scenes. It's a scene with 4GB. So not out of memory here. What can cause it? Studio Drivers 472.39.
Max has a white background then and I need to close it.
Code: Select all
Started logging on 18.11.21 07:46:43
OctaneRender Enterprise 2021.1 (11000014)
Can't connect node 'oDiff_07 - Default' (NT_MAT_DIFFUSE, 000001E9D7CE3590) to static pin 'layer' (P_LAYER, type PT_MATERIAL_LAYER) of node 'Universal material' (NT_MAT_UNIVERSAL, 000001E9D7CDC510)
failed to create texture object

Hi mbetke,

It could come from a scene saved from some particular versions of max plugin, when the 'Material layer' was introduced.
Could you check and post the version that you see in Tools tab, rollout '1.9 version support' : in 'Current Scene', it should show the 'Octane version'.
I'll try to create a similar scene..
Also, could you try to enable 'Fix invalid material layer group' in Preferences, Material tab ? That could fix the issue..
Thanks

Posted: **Sun Nov 21, 2021 10:09 pm**

coilbook wrote:Hi Paride,
I am using ornatrix but when I increase hair count vram usage goes up a lot. I thought hair supposed to be treated as instances? And using instanced strands makes hair disappear altogether.
is there a proper way for hair? Thanks

Hi coilbook,
-Ornatrix hairs are sent to Octane engine as Octane hairs, so it uses information about each strand.
It's more efficient that creating polygons on the plugin side, but still uses some memory per strand...

-The 'Instanced Strands' options is not supported. (and should be disabled)
I'll investigate if that's something that could work with Octane in the future.

Thanks

OTOY Forums

OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07

Re: OctaneRender® for 3ds max® v2021.1 - 12.07