vinyvince Posted January 20, 2021 Share Posted January 20, 2021 Hi Im getting nutz.. I built the Hoover Dan, in construction in 1932 Colorado, entirely procedurally in Houdini, All went fine until I started to do test rendering in Redshift with something different than a basic material with no texture. I only use 2 differents materials, no displacement or anything fancy for now, quixel surface, and now Redshift is extremely SLOWWWWW to start showing the first pixel… like 8 time slower, more than 30min to start, or don’t even start sometimes… What could I do ? What could be the issue? Idea? Please help, I have no much hair left ! ________________________________________________________________ Vincent Thomas (VFX and Art since 1998) Senior Env and Lighting artist & Houdini generalist & Creative Concepts http://fr.linkedin.com/in/vincentthomas 2 Quote Link to comment Share on other sites More sharing options...
Atom Posted January 20, 2021 Share Posted January 20, 2021 (edited) One thing you could try is to export all (or most complex) of your geometry as a .rs file, if you have not already. Then Redshift will read the geometry from the disk and not have to request the geometry through the Houdini API, which might be a single threaded process IDK. This API request might be part of the slowdown. Edited January 20, 2021 by Atom Quote Link to comment Share on other sites More sharing options...
vinyvince Posted January 21, 2021 Author Share Posted January 21, 2021 Thanks @Atom for the suggestion. Actualyl the main problem was Redshift could have some problem doing tangent computation for the normal bump. Best is to compute yourself and pass it to Redshift using a polyframe. The difference could be dramatic Found another issue as well with the Lab import FBX which even is marked as hidden, obj remain visible. ________________________________________________________________ Vincent Thomas (VFX and Art since 1998) Senior Env and Lighting artist & Houdini generalist & Creative Concepts http://fr.linkedin.com/in/vincentthomas Quote Link to comment Share on other sites More sharing options...
olivetty Posted April 14, 2021 Share Posted April 14, 2021 On 21/01/2021 at 12:35 PM, vinyvince said: Thanks @Atom for the suggestion. Actualyl the main problem was Redshift could have some problem doing tangent computation for the normal bump. Best is to compute yourself and pass it to Redshift using a polyframe. The difference could be dramatic Found another issue as well with the Lab import FBX which even is marked as hidden, obj remain visible. ________________________________________________________________ Vincent Thomas (VFX and Art since 1998) Senior Env and Lighting artist & Houdini generalist & Creative Concepts http://fr.linkedin.com/in/vincentthomas How did you compute it using the polyframe and then passed it on to RS? I think this would be awesomely useful information as I've encountered this before. Usually when RS slows down hard is because it's going out of core (not enough VRAM left). Quote Link to comment Share on other sites More sharing options...
schwungsau Posted April 14, 2021 Share Posted April 14, 2021 for heavy geo, you better get much moooooore GPU Ram, and even then the first time pixel will be slow (time compile it and move it to GPU mem.). that's why CPU rendering is still a think ;-) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.