art3mis Posted November 19, 2016 Share Posted November 19, 2016 Really perplexed why I can't seem to get my imported bgeo.sc to render. Could it be the way I am applying my Redshift material? Just a simple File SOP importing a single bgeo.sc file for a render test. I think I've applied my Redshift water material correctly but if anyone could have a look it would be greatly appreciated! testRender_redshift.zip Quote Link to comment Share on other sites More sharing options...
Atom Posted November 19, 2016 Share Posted November 19, 2016 Check out my post "When Redshift Renders Nothing" on the Redshift forum. Basically you may have to unpack it and or convert it from a mesh to a mesh. ObjectMerge and File nodes seem to have this problem when rendering with Redshift. Quote Link to comment Share on other sites More sharing options...
art3mis Posted November 19, 2016 Author Share Posted November 19, 2016 Thanks Atom. Have tried both options yet still nada. Unpack gives warning Input has no packed primitives. And tried Convert node with various permutations Most frustrating! When I solve will post my solution. Quote Link to comment Share on other sites More sharing options...
Daryl Dunlap Posted November 19, 2016 Share Posted November 19, 2016 Redshift for Houdini cannot render Polygon Soups (at this time), most likely this is what's causing your issue. When all else fails, use the Convert SOP to convert all to Polygons. Quote Link to comment Share on other sites More sharing options...
art3mis Posted November 19, 2016 Author Share Posted November 19, 2016 (edited) Ok, the issue was I was relying on the refresh button(recycle icon), instead of hitting Render. Seems like a bug to me. Changes in your network it seems aren't updated in the Render view unless you hit 'Render'. As suggested, a Convert node with All types or Polygon Soup to Polygons was needed. Edited November 19, 2016 by art3mis Quote Link to comment Share on other sites More sharing options...
Atom Posted November 19, 2016 Share Posted November 19, 2016 (edited) Yeah, Redshift is plagued with update issues. I experience them daily in the form of "sticky" material nodes and lagging render views. Some of the time you make a change and Redshift still presents you with an old result. I have completely abandoned using the Renderview with Redshift for this reason. It wastes your time, especially when you are learning this new material system. You think, Ok, I changed my texture but I am still seeing the old texture what did I do wrong? Instead I tear off a small property panel for the ROP and issue IPR renders by clicking the Render button every time. You have to close the IPR window each time you change the frame or you end up looking at old stale data too. More often then not, if you think you made the correct change to a parameter and Redshift is not showing your result then you are experiencing the bug. Relying only on the IPR gives you a quick fix. Just close it out and popup a new one. This make material development quite slow even though renders are much faster. Edited November 19, 2016 by Atom Quote Link to comment Share on other sites More sharing options...
art3mis Posted November 26, 2016 Author Share Posted November 26, 2016 Thanks Atom, have you posted this to the Redshift team? I've found them to be extremely responsive. 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.