Community
Arnold for Houdini Forum
Rendering with Arnold in Houdini and Solaris using the HtoA plug-in.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Restart Render bug(s) ?

10 REPLIES 10
SOLVED
Reply
Message 1 of 11
cedric_nivoliez
296 Views, 10 Replies

Restart Render bug(s) ?

Hi,

 

I have an issue with arnold and/or solaris when I restart a render.

 

 

This issue appears when I want to visualize the Pref AOV, when I work with multiple uv sets (when I restart, Arnold maps all my image on the first/default uv set), etc.. I guess the same problem can be found somewhere else.

 

In my Houdini Console I have this kind of warnings

msedge_AlRzoPrQCY.png

cedric_nivoliez_0-1696353278970.png

 

I don't have any problems when rendering with kick, only inside Solaris.

 

Is this a known issue ?

 

 

I'm using Houdini 19.5.682 with HtoA 6.2.3.1 (Arnold 7.2.3.1)

 

Thanks

10 REPLIES 10
Message 2 of 11

Any insight on this ?

 

I'm the only one to have this problem ?

 

To the Autodesk support team, the set-up is super simple, it should be easy to reproduce, test it and give me a feedback (even a small one)...

Message 3 of 11

Works fine for me with the latest HtoA.
Of course, your super-simple setup could be different than mine, since there's always different ways to do things in Houdini. But I've got a Pref attribute and two UV sets.

PS This is a peer-to-peer forum, not an official support forum. 



// Stephen Blair
// Arnold Renderer Support
Message 4 of 11

Thanks for the reply Stephen !

 

I'll try to update our arnold version and see how it goes.

Message 5 of 11

Or post your test scene and I'll try it here...



// Stephen Blair
// Arnold Renderer Support
Message 6 of 11

There it is.

 

So, when I start rendering and watch my Pref AOV I see the result as expected but when I restart the render the AOV goes black. If I enable the rendergeometrysettings1 and restart the render I see the Pref again, until I re-restart the render.

The solution I found is to had a render geometry settings and switch ON/OFF everytime I need to restart the render.

 

Yeah... this is weird !

 

 

Houdini FX Version 19.5.682

HtoA 6.2.3.1

Arnold 7.2.3.1

 

Thanks again

Message 7 of 11
peterDTE7K
in reply to: Stephen.Blair

Solaris viewport is quite troubling:

1. I also often have this bug that render is just black in solaris.

2. Also sometimes the resolution is suddenly lower than it should be - render settings set to 1920x1920 but it renders in 655x655.

3. In the latest htoa in the Arnold "Image viewport" the render region tool is now fixed to render resolution aspect ratio, so if you have 1200x1200 render the render region tool is fixed to 1:1 square. Normal render region tool works, this only applies to the one in the Image viewport.

4. The viewport is still often crashing with error "SymInitialize returned error: 87" which has been already reported by quite a few people https://forums.autodesk.com/t5/arnold-for-houdini-forum/arnold-keeps-crashing-with-error-message-quo... and https://forums.autodesk.com/t5/arnold-for-houdini-forum/houdini-19-5-493-wih-htoa-6-1-4-2-syminitial... 

Message 8 of 11


@cedric_nivoliez wrote:

There it is.

 

So, when I start rendering and watch my Pref AOV I see the result as expected but when I restart the render the AOV goes black. If I enable the rendergeometrysettings1 and restart the render I see the Pref again, until I re-restart the render.

The solution I found is to had a render geometry settings and switch ON/OFF everytime I need to restart the render.

 

Yeah... this is weird !

 

 

Houdini FX Version 19.5.682

HtoA 6.2.3.1

Arnold 7.2.3.1

 

Thanks again


Sorry, I did not repro (reproduce the problem).

I restarted the render 10 times and it worked every time

 

Houdini 19.5.752

HtoA 6.2.4

Windows

Arnold 7.2.3.2 did have this fix, which kinda sounds relevant to your problem:

  • usd#1625 - Fix issue where user-defined primvars were reset


// Stephen Blair
// Arnold Renderer Support
Message 9 of 11
Stephen.Blair
in reply to: peterDTE7K


@peterDTE7K wrote:

Solaris viewport is quite troubling:

1. I also often have this bug that render is just black in solaris.

2. Also sometimes the resolution is suddenly lower than it should be - render settings set to 1920x1920 but it renders in 655x655.

3. In the latest htoa in the Arnold "Image viewport" the render region tool is now fixed to render resolution aspect ratio, so if you have 1200x1200 render the render region tool is fixed to 1:1 square. Normal render region tool works, this only applies to the one in the Image viewport.

4. The viewport is still often crashing with error "SymInitialize returned error: 87" which has been already reported by quite a few people https://forums.autodesk.com/t5/arnold-for-houdini-forum/arnold-keeps-crashing-with-error-message-quo... and https://forums.autodesk.com/t5/arnold-for-houdini-forum/houdini-19-5-493-wih-htoa-6-1-4-2-syminitial... 


"SymInitialize returned error: 87" itself just means it crashed. I don't think there's any special meaning to the message itself, the crashes are all too different. The two linked reports may not even be in Solaris.

So what is important is what causes the crash...and if you have scene that reproduces the crash and that you can share. Or specific repro steps...



// Stephen Blair
// Arnold Renderer Support
Message 10 of 11
peterDTE7K
in reply to: Stephen.Blair

On latest htoa version I also could not reproduce Cedric's error.

 

SymInitialize error is kind of random and happens less often with this htoa version. The black screen error affects the view #5 Image viewport which is the most useful view for rendering. I use 2 viewports like in other DCCs - one to control the scene another one with Arnold for preview. I am attaching video which will reproduce the error but this black screen will happen also in other scenarios. Maybe it might be related to error which appears on 00:18.

 

Also in the video the Perspective viewport outputs correct 1920x1080 resolution but when I switch it to Image viewport it switches to 960x540 at 00:17

Message 11 of 11

Updating Arnold to the last version (6.2.4) solved our problem.

 

Thanks again !

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums