OTOY Forums

bepeg4d wrote:Hi,
can you share a screenshot of the entire interface?
ciao Beppe

Sorry, very likely my fault. When I use the Substance PBR material from Live DB it works as expected.

bepeg4d wrote:Hi,
can you share a screenshot of the entire interface?
ciao Beppe

I have looked into this some more, and maybe there is an issue with the Universal material.

In case it helps. Here is the interface and the viewport result.

A new scene, with no other changes. It does not seem to matter which texture map I use - this one was a 4k export out of Substance Painter.

I can verify something is up with universal and metallic maps, I set Metalness to 1.0 float and it just ... stopped rendering. It won't start back up, won't restart. The app isn't frozen, I can still adjust the nodes, change settings etc. Even deleting the offending Universal material does nothing. The other tex inputs work fine it seems. I also tried a Noise node, same odd freeze behavior. This is with my Intel Integrated graphics enabled or by itself. Disabling the Intel GPU returns functionality to normal. Universal + Metallic work with just the Radeon VII. I suspect this is why the issue manifests on M1, which is also technically an integrated GPU.

Hardware:
Mac mini 2018 Intel i7-8700B 32GB
Razer Core X eGPU - Radeon VII 16GB
macOS Big Sur 11.1 + Octane X Standalone PR 7

Weezer wrote:I've got problems with the Denoise function in PR7 (see bug report viewtopic.php?f=86&t=76579). Can anyone else with a 2019 Mac Pro replicate these issues? Or is it just me? I'm running dual RX5700XTs.

Getting a similar failure on the denoiser.

Can anyone help me understand what I am doing wrong here? I have not been able to get OctaneRender and now OctaneX to ever get past a "waiting for image" hang on Blender.

I had the same problem on my PC with CUDA, and had been waiting for OctaneX to try it on my MacbookPro.

16" i9 Macbook pro with 5500M and a 5700XT in eGPU.
Image never renders, but the GPU can sit there for hours at 100% utilisation (this is on the default cube scene).

This is all just a clean install and then render.

The Octane Log shows the following;

Code: Select all

Tried to access pin via an invalid ID P_UNKNOWN (0)
Tried to access null node pin
Can't read bool from static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0x10d537de8)
Tried to access pin via an invalid ID P_AI_LIGHT_STRENGTH (385)
Tried to access null node pin
Can't read float from static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0x10d537de8)
Tried to access pin via an invalid ID P_AI_LIGHT_STRENGTH (385)
Tried to access null node pin
Can't write float to static pin 'unknown' (P_UNKNOWN, type PT_UNKNOWN) of node '' (NT_UNKNOWN, 0x10d537de8)

Thanks in advance!

Apparently this is being fixed for the next build. For me, this will be the last major issue. OctaneX has been great so far!

Is it possible we could get a material library that doesn't re-render the materials everytime you open it but caches the renders instead? Also: would it be possible to use a custom shaderball for ORBX previews?

How do I create a post in the plugins C4D section? There isn't a create topic button like on other forums?


Thank you.

susu2k wrote:Is it possible we could get a material library that doesn't re-render the materials everytime you open it but caches the renders instead? Also: would it be possible to use a custom shaderball for ORBX previews?

How do I create a post in the plugins C4D section? There isn't a create topic button like on other forums?


Thank you.

Not clear with first, what you mean with caching material renders? Custom previews are not supported.

Hey there

I'm using C4D R23 (last build) with PR7 and I have this issue:

Code: Select all

Octane X Prime PR7 (Internal Build) (10000302)

Compute error 2097152:116:
compute device 0: Linking 6d197dfc90d19e72 shader failed
device 0: failed to initialize render thread 0x7fa73148a350

LV is black, nothing happens.
My device: iMac Pro 2017 Radeon Pro Vega 64X 16 GB

Thanks for your help!

Weezer wrote:Apparently this is being fixed for the next build. For me, this will be the last major issue. OctaneX has been great so far!

Do you mean the denoiser? This is the only thing not working for me.