The hot pixel visibility should work fine to remove the specular hot pixels ... what is your problem with this parameter?
It is true that the render region behavior is a bit complex. The render time is going to be the same, but the region is a lot more clean because all the whole image samples are used to render the selected region, so the region has more samples/pixel than the whole image. I should test this issue again, anybody knows if Standalone shows the same behavior?
About the shadowed areas very dark, you should play with the imager node film response presets and the gamma settings. Or perhaps you could need to add a fill are light to the scene.
-Juanjo
Octane/LW questions and comments
Moderator: juanjgon
Thanks Juanjgon!
1# The hot pixel removal works pretty well but my problem is next : I like to look of the IPR window view, but there is some hot pixels. I connect Imager to put on Hot Pixel Removal but as I do that, also all the other Imager settings (ISO, gamma, etc.) start effecting the view. But I want only the Hot Pixel Remove to work, not all the other settings also...
2# About the render region : Let´s say I have a large scene that takes 5 hours to render. Then I want to change a small chair to another model. I change the chair, set render region to only the small area that covers the chair and render the region around only the chair with F9. I have to wait for another 5 hours for just to render the chair that is about 1/20 of the total render image.
I used Fprime before. When I rendered a 5 hour scene with FPrime and wanted to change only a small piece of the picture, the rendering for that small part took only like couple of minutes...
- Builtdown
1# The hot pixel removal works pretty well but my problem is next : I like to look of the IPR window view, but there is some hot pixels. I connect Imager to put on Hot Pixel Removal but as I do that, also all the other Imager settings (ISO, gamma, etc.) start effecting the view. But I want only the Hot Pixel Remove to work, not all the other settings also...
2# About the render region : Let´s say I have a large scene that takes 5 hours to render. Then I want to change a small chair to another model. I change the chair, set render region to only the small area that covers the chair and render the region around only the chair with F9. I have to wait for another 5 hours for just to render the chair that is about 1/20 of the total render image.
I used Fprime before. When I rendered a 5 hour scene with FPrime and wanted to change only a small piece of the picture, the rendering for that small part took only like couple of minutes...
- Builtdown
But to work in a real production scene you are going to need a full setup of the render target, with all the render target nodes ... without an imager node how do you configure your tone mapper, the exposure, the gamma and so on?
You should begin your projects with a default render target nodes configuration, like the one you get with the feature "default setup" that you can find in the root node tools menu. Without this setup a lot of rendering features are not available, or you can't adjust them.
About the render region, if you are rendering a 1/20 of the total image, you could set 1/20 samples to get the same render quality in your rendered region, so render time is going to be also 1/20. I am not sure now if this an Octane problem also present in the Standalone ... I need to check it.
-Juanjo
You should begin your projects with a default render target nodes configuration, like the one you get with the feature "default setup" that you can find in the root node tools menu. Without this setup a lot of rendering features are not available, or you can't adjust them.
About the render region, if you are rendering a 1/20 of the total image, you could set 1/20 samples to get the same render quality in your rendered region, so render time is going to be also 1/20. I am not sure now if this an Octane problem also present in the Standalone ... I need to check it.
-Juanjo
- Attachments
-
You need to install the last daily build (version 2.6.1):Builtdown wrote:Thanks for the tips, Juanjgon!
How can I get the Default Setup in Render Target (as shown in your previous post)? When I right click on the Render Target Node, the Node Menu is greyed...
http://render.otoy.com/forum/viewtopic.php?f=36&t=40793
-Juanjo
nice nice!UnCommonGrafx wrote:Someone posted this graphic for using the lw camera's dof settings to control the Octane camera's dof.
I have found it indispensable and keeps it lw-ish.
Freddy
Hi,
Next question is about IES-lights :
I have done IES-related illustrations for a client with MAX/Vray. I have got ies-files from the client and they have worked well. Now I would like to test if I can do the same in LW/Octane. So I decided to test it.
I made a scene with a wall and 1 light pointing towards it. I first tested the scene with Octane Sample Scenes IES-file. Works well.
Then I change the ies-file from a client. Nothing.
The ies-file should work because it works perfectly in MAX/Vray. What´s the problem? (I attached the ies-file)
Thanks,
Next question is about IES-lights :
I have done IES-related illustrations for a client with MAX/Vray. I have got ies-files from the client and they have worked well. Now I would like to test if I can do the same in LW/Octane. So I decided to test it.
I made a scene with a wall and 1 light pointing towards it. I first tested the scene with Octane Sample Scenes IES-file. Works well.
Then I change the ies-file from a client. Nothing.
The ies-file should work because it works perfectly in MAX/Vray. What´s the problem? (I attached the ies-file)
Thanks,
You can compress the .ies file in a .zip file to attach it, or send it to me to [email protected]
-Juanjo
-Juanjo