OTOY Forums

ricky_otoy wrote:

lavrenovlad wrote:BTW can those crashes and stuff be also related to Windows 10 updates? This year windows updates were terrible, most of them not installing properly and for the first time I experienced BSOD when rendering in IPR (only with octane though). I installed windows updates 2-3 times this year after which I couldn't boot up properly, had to recover and try again, even now I have one security update that just won't install, such bullshit

It is possible, issues with corrupt OS files can also produce BSOD. But I can't be 100% sure... Please also try export the ORBX and have a look at how standalone behaves with the denoiser.

You could try the following for windows to scan the OS file system:

Code: Select all

sfc /scannow

and another for the windows update:

Code: Select all

DISM.exe /Online /Cleanup-image /Restorehealth

**You shouldn't need to, but in case I would just backup important files. This is just more of a disclaimer

Yeah Windows been weird lately. I also get crashes with Karma XPU rendering over-night, tried to do all the cmd commands for repairing system files and so on like almost a week ago and stuff. I can partly tell that something is off with win10, after updates and repairs I made last week my last over-night test render passed and rendered everything fine.

Regarding trying octane standalone, I did, didn't seem to crash, but again I didn't spend there an hour or so how I usually do in Houdini, so can tell that it's not crashing, but who knows.

My whole system is quite a bit more unstable lately as well. Had two blue screens as well. And more memory allocation errors - which I find Houdini generally can have from time to time. But currently it works better, if for example I close Nuke and or Resolve, when working and rendering in Houdini. It's quite annoying. Guess Microsoft tries to mess up Win10, so people switch to 11..

Is the new Output AOV group working? Can't see anything nor there is a setup-guide in the document.

LewisO wrote:Is the new Output AOV group working? Can't see anything nor there is a setup-guide in the document.

The attachment abc.png is no longer available

Hi Lewis, you are missing an Output AOV to plug into the Output AOV Group. For any AOVs you use in the setup, you will still need to first enable them the usual way.

Here is a screenshot of a very basic setup:

ricky_otoy wrote:

LewisO wrote:Is the new Output AOV group working? Can't see anything nor there is a setup-guide in the document.

The attachment abc.png is no longer available

Hi Lewis, you are missing an Output AOV to plug into the Output AOV Group. For any AOVs you use in the setup, you will still need to first enable them the usual way.

Here is a screenshot of a very basic setup:

The attachment Output_AOV.png is no longer available

Hi Ricky thanks for the reply, I *sort of* got it to work, partially. The problem is that the Open Image Denoise does not work, it outputs black result.
Basically, I am trying to figure this out, it would be great to get some sort of info/insights on this specific topic viewtopic.php?f=33&t=83364&p=432682#p432682

Also it seems like the OBJ's "Shadow visibility" is not working when "Packed Geo Instancing" is on, is this a known limitation?

LewisO wrote:

ricky_otoy wrote:

LewisO wrote:Is the new Output AOV group working? Can't see anything nor there is a setup-guide in the document.

abc.png

Hi Lewis, you are missing an Output AOV to plug into the Output AOV Group. For any AOVs you use in the setup, you will still need to first enable them the usual way.

Here is a screenshot of a very basic setup:

Output_AOV.png

Hi Ricky thanks for the reply, I *sort of* got it to work, partially. The problem is that the Open Image Denoise does not work, it outputs black result.
Basically, I am trying to figure this out, it would be great to get some sort of info/insights on this specific topic viewtopic.php?f=33&t=83364&p=432682#p432682

settings.png

Hi there, you should use the "Render AOV" node and choose the appropriate AOV from that instead. The pin output doesn't match the input needed. (Also use a layer)

Sorry thought I posted a screenshot.
Hope it helps!