Tong Le Posted February 7, 2011 Share Posted February 7, 2011 Hi there, I was wondering is there a good way to output parameter info to my render test pic? I am doing my render test and twist a lot of parameter in my shader. Sometimes, i get good results. However, after a long day test make my brain broken and I can't remember all the setting I had for that render. I used to use font sop display certain channel on top of my render. I was talking to my friend this morning and he said if exr can use one channel to export all the settings or shop setting, it will be awesome. Do you guys have any smart solution or tricks for my question? Thanks! Quote Link to comment Share on other sites More sharing options...
LaidlawFX Posted February 7, 2011 Share Posted February 7, 2011 Here is a dumb solution Joyce, since I can't directly answer the question since I don't know that. It would be wicked cool if some one else knows who has done it though... If you take your reference object in hand and you work on each component of that object one by one, and shut everything else off you should be able to fly through it. If you focus on the sizes of the specs, adjust that, the levels of occlusion, the different types of scratches in the paint, etc. it will add up pretty quickly, and then you can know what effects caused what to adjust later. Esp. if you're building the shader yourself, create a network box for the areas you do know what they're doing and build it up from there. It simple help, but it's effective. Alternatives: If your sending a sequence of to the farm, you can make a pre-script that copies you Houdini file to the render directory. unix cp myfile.hip etc. so you can back check. You can pump the parameters into an .exr so it is an image layer, but that data is not very useful to look at, better for "raw data" The best solution would be to write a pre-script with the opscript command and write it to a file, and set render to ip (this is probably what you want with some finessing, ask graham) opscript -r /shop/mantrasurface opscript Quote Link to comment Share on other sites More sharing options...
Tong Le Posted February 8, 2011 Author Share Posted February 8, 2011 Here is a dumb solution Joyce, since I can't directly answer the question since I don't know that. It would be wicked cool if some one else knows who has done it though... If you take your reference object in hand and you work on each component of that object one by one, and shut everything else off you should be able to fly through it. If you focus on the sizes of the specs, adjust that, the levels of occlusion, the different types of scratches in the paint, etc. it will add up pretty quickly, and then you can know what effects caused what to adjust later. Esp. if you're building the shader yourself, create a network box for the areas you do know what they're doing and build it up from there. It simple help, but it's effective. Alternatives: If your sending a sequence of to the farm, you can make a pre-script that copies you Houdini file to the render directory. unix cp myfile.hip etc. so you can back check. You can pump the parameters into an .exr so it is an image layer, but that data is not very useful to look at, better for "raw data" The best solution would be to write a pre-script with the opscript command and write it to a file, and set render to ip (this is probably what you want with some finessing, ask graham) opscript -r /shop/mantrasurface opscript Thanks, Ben! I really wish Houdini can output certain parameter in a layer of exr file. For the render farm, I thought their is an option in Houdini's HQ which automatically copy the hip file to the render directory. I might be wrong cos I didn't really use HQ for any final project render. I am still using a old way which is ssh to different machine for render. Still thanks for the answers and helps. Quote Link to comment Share on other sites More sharing options...
Tong Le Posted February 8, 2011 Author Share Posted February 8, 2011 Here is a dumb solution Joyce, since I can't directly answer the question since I don't know that. It would be wicked cool if some one else knows who has done it though... If you take your reference object in hand and you work on each component of that object one by one, and shut everything else off you should be able to fly through it. If you focus on the sizes of the specs, adjust that, the levels of occlusion, the different types of scratches in the paint, etc. it will add up pretty quickly, and then you can know what effects caused what to adjust later. Esp. if you're building the shader yourself, create a network box for the areas you do know what they're doing and build it up from there. It simple help, but it's effective. Alternatives: If your sending a sequence of to the farm, you can make a pre-script that copies you Houdini file to the render directory. unix cp myfile.hip etc. so you can back check. You can pump the parameters into an .exr so it is an image layer, but that data is not very useful to look at, better for "raw data" The best solution would be to write a pre-script with the opscript command and write it to a file, and set render to ip (this is probably what you want with some finessing, ask graham) opscript -r /shop/mantrasurface opscript Thanks, Ben! I really wish Houdini can output certain parameter in a layer of exr img. For the render farm, I thought their is an option in Houdini's HQ which automatically copy the hip file to the render directory. I might be wrong cos I didn't really use HQ for any final project render. I am still using a old way which is ssh to different machine for render. Still thanks for the answers and helps. Quote Link to comment Share on other sites More sharing options...
Tong Le Posted February 8, 2011 Author Share Posted February 8, 2011 Here is a dumb solution Joyce, since I can't directly answer the question since I don't know that. It would be wicked cool if some one else knows who has done it though... If you take your reference object in hand and you work on each component of that object one by one, and shut everything else off you should be able to fly through it. If you focus on the sizes of the specs, adjust that, the levels of occlusion, the different types of scratches in the paint, etc. it will add up pretty quickly, and then you can know what effects caused what to adjust later. Esp. if you're building the shader yourself, create a network box for the areas you do know what they're doing and build it up from there. It simple help, but it's effective. Alternatives: If your sending a sequence of to the farm, you can make a pre-script that copies you Houdini file to the render directory. unix cp myfile.hip etc. so you can back check. You can pump the parameters into an .exr so it is an image layer, but that data is not very useful to look at, better for "raw data" The best solution would be to write a pre-script with the opscript command and write it to a file, and set render to ip (this is probably what you want with some finessing, ask graham) opscript -r /shop/mantrasurface opscript Thanks, Ben! I really wish Houdini can output certain parameter in a layer of exr img. For the render farm, I thought their is an option in Houdini's HQ which automatically copy the hip file to the render directory. I might be wrong cos I didn't really use HQ for any final project render. I am still using a old way which is ssh to different machine for render. Still thanks for the answers and helps. 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.