OTOY Forums

Prob a stupid question, howcome this supports only one gpu?

Witpapier wrote:Prob a stupid question, howcome this supports only one gpu?

What are you referring to please?

Paul

@Witpapier

The new Prime/Free version only supports 1 GPU. You need a subscription now to take advantage of multi GPUs.

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

2020.1.0.50
- Compiled with Octane 2020.1 XB3

Thanks

Paul

Thank you

Hi Paul,

I seem to be having an issue using the Smart Unfold in NGE.

I've set up a Specular Material, added some additional functions.
Then when I use smart unfold, the settings remain consitent but I end up with a different render result. Please see screenshots. Any questions let me know.

I seem to be having an issue using the Smart Unfold in NGE.

Hi. I couldn't reproduce this issue. Are you able to send me a scene with just that material (prior to the smart unfold) on a sphere please?

Paul

face_off wrote:

I seem to be having an issue using the Smart Unfold in NGE.

Hi. I couldn't reproduce this issue. Are you able to send me a scene with just that material (prior to the smart unfold) on a sphere please?

Paul

Hi Paul,

Certainly, please see attached . Thank you.

Hi Paul,

Certainly, please see attached

Thanks for providing the scene. Perhaps you could help here...to me it looks like unfolding a non-material node works OK, however when a material node is unfolded the result is a corrupted material, and the Amber Scene Surface can no longer be selected. I also notice that changing pins on the Mix texture doesn't restart the render, so there has been a break in the link between the Octane node in the NGE and the Octane node in the render engine.

Looking at the code, there is no obvious issue, and I suspect the issues around Smart Unfold have been there since the feature was added. My best guess is that fixing this would be a major undertaking.

I think the best solution is to disable the Smart Unfold option on Octane Material nodes.

Thoughts?

Paul

Hi Paul,

Any progress made to figure out why the wrong position is occurring in Octane Viewport compare to Daz Viewport (viewtopic.php?f=44&t=72407&start=10#p372978) ? I hope the scene file attached in that post helped you to investigate the issue. This really needs to be solved as more and more of my scenes are having this issue. Can it be related to world / local coordinates ?

I found something interesting whenever this issue occurs. Whichever object it affects, If all the XYZ rotate angles are within 0 to 90 or 0 to -90, Daz and Octane Viewport will match. But if XYZ rotation goes beyond 90 / -90, then the Daz Viewport shows the correct pose / position but Octane Viewport does not (matrix calculation issue ?) . But again this is only after the issue has happened. I have may scene files where the angles are beyond plus or minus 90 degree and it is sill okay. So not sure what triggers this issue. But once it occurs, the scene will always load that way. Rebuild scene sometimes fixes it. So not sure what is the difference between initial load and rebuild scene in terms on the placement / orientation logic. I have scene that always result it render failure the moment I rebuild scene so I am not able to use rebuild scene to fix this issue in many of my heavy scenes.

Regards,
Rajib