OTOY Forums

madssigurd wrote:I can't render at all, i have tried almost everything, both python versions, updating drivers to newest studio drivers, restarting everything that can be restarted, reinstalling octane and houdini. It instantly crashing whenever i try to start a render in the viewport even if it is completely empty... any ideas for a fix?

galleon27 wrote:Can someone please explain to me what is the purpose of this?

Screenshot 2024-08-06 221120.png

What is the point in outputting the image twice? Once in the path set there and once in the path set in the output tab. Enabling and disabling doesn't do anything, it's always outputting twice.

Nimrod7 wrote:Hi,

Can you please clarify what python version is required?
I am getting a crash when trying to render.

Using Houdini 20.5.278 Py3.10 ([windows-x86_64-cl19.37])

Code: Select all

21008: Fatal error: Segmentation fault

Log:

Code: Select all

Traceback from 1352 ThreadId=0x00004fc4
CURRENT THREAD 20420
+0x12054178 [JEDI_SceneGraphView::supportsViewCameras] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libJEDI.dll
+0x12b797be [GUI_DetailLook::updateForRenderInit] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libGUI.dll
+0x12a0c2ce [DM_VPortAgent::setupGeometry] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libDM.dll
+0x12a081cf [DM_VPortAgent::renderViewport] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libDM.dll
+0x129ef6d0 [DM_VPortAgent::doRender] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libDM.dll
+0x129c2342 [DM_Viewport::doRender] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libDM.dll
+0x27ebce61 [UI_Feel::renderMe] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27eb6631 [UI_Feel::doRenderKids] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27eb654b [UI_Feel::doRender] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27ebce61 [UI_Feel::renderMe] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27eb6631 [UI_Feel::doRenderKids] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27eb654b [UI_Feel::doRender] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27fed159 [UI_Viewport::reRender] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27ff3377 [UI_Window::renderChildViews] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27ff00e1 [UI_Window::doRedrawSubclass] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x129b0854 [DM_ViewLayout::doMakeTriple] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libDM.dll
+0x27feff4e [UI_Window::doRedraw] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27f87d75 [UI_Queue::doWindowRedraws] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27f8ab62 [UI_Queue::processNextEvent] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27f87e49 [UI_Queue::drain] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x27f886d8 [UI_Queue::eventLoop] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libUI.dll
+0x1123d9da [AP_Interface::loadWindowGeometry] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libSI.dll
+0x1123e585 [myWinMain] C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\libSI.dll
+0x1400015a2 C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\hindie.exe
+0x140001a32 C:\Program Files\Side Effects Software\Houdini 20.5.278\bin\hindie.exe
+0x7ffaf77c257d [BaseThreadInitThunk] C:\WINDOWS\System32\KERNEL32.DLL
+0x7ffaf92eaf28 [RtlUserThreadStart] C:\WINDOWS\SYSTEM32\ntdll.dll

BK wrote:

galleon27 wrote:Can someone please explain to me what is the purpose of this?

Screenshot 2024-08-06 221120.png

What is the point in outputting the image twice? Once in the path set there and once in the path set in the output tab. Enabling and disabling doesn't do anything, it's always outputting twice.

Hey galleon2,

This feature is a workaround to allow us to render with Octane on its own in a single process quickly.
The $F requirement is for saving images in Houdini when rendering in a single process.
We can use Octane_raster as the Product Type to prevent Houdini from saving frames.

Please note, that when we use Octane_raster to prevent Houdini from saving frames, we still need $F in the file path in the Product name parameter.
The Octane AOVs won't appear in the viewport when using Octane_raster in the Octane node.
For now, we recommend using two Octane nodes to separate for viewport rendering raster and Octane_raster for the final render.

Cheers

connect the USD Render ROP node to the Octane node with Octane_raster to make it clear it is for final output.
Cheers

seriawp wrote:The bug with the cropped camera taken from the SOP has returned again.

galleon27 wrote:Instancing doesn't work now.... Can't you guys do anything right? This is getting really frustrating. And any fix is taking too long. At this rate, Octane Solaris is never gonna be production ready.

200724.png

205278.png

BK wrote:

galleon27 wrote:Can someone please explain to me what is the purpose of this?

Screenshot 2024-08-06 221120.png

What is the point in outputting the image twice? Once in the path set there and once in the path set in the output tab. Enabling and disabling doesn't do anything, it's always outputting twice.

Hey galleon2,

This feature is a workaround to allow us to render with Octane on its own in a single process quickly.
The $F requirement is for saving images in Houdini when rendering in a single process.
We can use Octane_raster as the Product Type to prevent Houdini from saving frames.

Please note, that when we use Octane_raster to prevent Houdini from saving frames, we still need $F in the file path in the Product name parameter.
The Octane AOVs won't appear in the viewport when using Octane_raster in the Octane node.
For now, we recommend using two Octane nodes to separate for viewport rendering raster and Octane_raster for the final render.

Cheers

connect the USD Render ROP node to the Octane node with Octane_raster to make it clear it is for final output.
Cheers

adrianr wrote:

BK wrote:

galleon27 wrote:Can someone please explain to me what is the purpose of this?

Screenshot 2024-08-06 221120.png

What is the point in outputting the image twice? Once in the path set there and once in the path set in the output tab. Enabling and disabling doesn't do anything, it's always outputting twice.

Hey galleon2,

This feature is a workaround to allow us to render with Octane on its own in a single process quickly.
The $F requirement is for saving images in Houdini when rendering in a single process.
We can use Octane_raster as the Product Type to prevent Houdini from saving frames.

Please note, that when we use Octane_raster to prevent Houdini from saving frames, we still need $F in the file path in the Product name parameter.
The Octane AOVs won't appear in the viewport when using Octane_raster in the Octane node.
For now, we recommend using two Octane nodes to separate for viewport rendering raster and Octane_raster for the final render.

Cheers

connect the USD Render ROP node to the Octane node with Octane_raster to make it clear it is for final output.
Cheers

Hey BK, could you explain more why this is neccesary? How is this improving on how it worked before? The Octane lop contains a lot of settings, so I'm always very weary of duplicating things like that to control two of essentially the same thing. Even if you make referenced copies you're still introducing a point of failure to happen right before you need to render - never really a good idea. Is there a solution in the works to not require 2 nodes to work normally?

Hi Adrian,

Thank you .. yes, this is a temporary workaround to allow us to export orbx in Single process. And ability to render output image only via Octane.
It was a workaround offered from SideFX that require $F must be in the file name even if the product type other than raster.
We are working on simplifying the workflow and hope to get it implemented soon!

cheers

I think this is also introducing other strangeness when it comes to rendering ORBXs but I've opened a support ticket about that.