OctaneRender for Carrara 2.16.0064 [Release Candidate]
-
rashadcarter
- Posts: 71
- Joined: Thu Sep 11, 2014 1:16 am
These were changes made to Octane itself. F-Stop was removed because it really didn't offer anything useful. The default Exposure setting was lowered to help avoid burn-outs with exterior renders, again at the level of Octane. Sighman didn't arbitrarily decide to remove and alter these options.
-
rashadcarter
- Posts: 71
- Joined: Thu Sep 11, 2014 1:16 am
Sighman,
There might still be an issue with Surface Replicators visibility. It is only with particular objects that have been duplicated and then replicated that the problem occurs, I will explain. In this case I have a master object of a clutch of flowers on my Master list (Clutch Master). I need more than 100,000 copies to cover the terrain so I need more than 1 Surface Replicator to get the job done. So I have duplicated the clutch of flowers on the Instances list, so now there are two Instances (Clutch1 and Clutch2) which share the same Master (Clutch Master). Each of the clutch instances is assigned to its own dedicated Surface Replicator (SurfRep Clutch1 and SurfRepClutch2), allowing me to have the 200,000 copies I need.
As a general rule I tend to make all of my objects on the Instances List set to invisible once I've placed them into their respective Surface Replicators. The Surface Replicators themselves however, remain visible at all times. The Surface Replicator 3d view setting is set to "none" as well to remove clutter from the wireframe. Bounding Boxes are nice, but I prefer a perfectly clean wireframe. It is important to note that the behaviors I'm describing below are only occurring on Surface Replicators that are flagged as visible combined with referencing geometries that are duplications and not original instances.
During the initial session everything seems fine, all flowers are visible in the final render. But after I save and re-open the scene file I find that the only Surface Replicator that is visible in the render is the first one Clutch 1, so I end up missing half my flowers. Apparently because the replicator for Clutch2 has stopped working. The same flowers that rendered moments ago before the save and re-open do not render now. I have double checked to make certain all of my visibility settings are the same as they had been during the last session before I saved the file, and indeed they are. All surface replicators are still set to visible, yet only the original instance seems to be replicated. It's as if the Surface Replicator system refuses to make copies from the Clutch 2 instance because it was itself a duplication. OR perhaps the Surface Replicator gets confused and doesn't realize that both instances share the same master mesh but are still unique instances?
One temporary remedy and possible clue into the solution is to momentarily re-enable the clutch instance's visibility, as well as to enable the Surface Replicator as a Bounding Boxes, somehow fixes it. Once I do that OR4C generates a new mesh which includes the flowers I was looking for. I can then reset the clutch instance back to being invisible and I can also reset the Surface Replicator drawing to "none" to keep my wireframe clean. It continues to work as expected until I save and close and then re-open again.
This wasn't an issue with the 2.06 version, if that helps any. Thanks Sighman,
Rashad
There might still be an issue with Surface Replicators visibility. It is only with particular objects that have been duplicated and then replicated that the problem occurs, I will explain. In this case I have a master object of a clutch of flowers on my Master list (Clutch Master). I need more than 100,000 copies to cover the terrain so I need more than 1 Surface Replicator to get the job done. So I have duplicated the clutch of flowers on the Instances list, so now there are two Instances (Clutch1 and Clutch2) which share the same Master (Clutch Master). Each of the clutch instances is assigned to its own dedicated Surface Replicator (SurfRep Clutch1 and SurfRepClutch2), allowing me to have the 200,000 copies I need.
As a general rule I tend to make all of my objects on the Instances List set to invisible once I've placed them into their respective Surface Replicators. The Surface Replicators themselves however, remain visible at all times. The Surface Replicator 3d view setting is set to "none" as well to remove clutter from the wireframe. Bounding Boxes are nice, but I prefer a perfectly clean wireframe. It is important to note that the behaviors I'm describing below are only occurring on Surface Replicators that are flagged as visible combined with referencing geometries that are duplications and not original instances.
During the initial session everything seems fine, all flowers are visible in the final render. But after I save and re-open the scene file I find that the only Surface Replicator that is visible in the render is the first one Clutch 1, so I end up missing half my flowers. Apparently because the replicator for Clutch2 has stopped working. The same flowers that rendered moments ago before the save and re-open do not render now. I have double checked to make certain all of my visibility settings are the same as they had been during the last session before I saved the file, and indeed they are. All surface replicators are still set to visible, yet only the original instance seems to be replicated. It's as if the Surface Replicator system refuses to make copies from the Clutch 2 instance because it was itself a duplication. OR perhaps the Surface Replicator gets confused and doesn't realize that both instances share the same master mesh but are still unique instances?
One temporary remedy and possible clue into the solution is to momentarily re-enable the clutch instance's visibility, as well as to enable the Surface Replicator as a Bounding Boxes, somehow fixes it. Once I do that OR4C generates a new mesh which includes the flowers I was looking for. I can then reset the clutch instance back to being invisible and I can also reset the Surface Replicator drawing to "none" to keep my wireframe clean. It continues to work as expected until I save and close and then re-open again.
This wasn't an issue with the 2.06 version, if that helps any. Thanks Sighman,
Rashad
-
rashadcarter
- Posts: 71
- Joined: Thu Sep 11, 2014 1:16 am
Thanks for the update Sighman. I wasn't expecting it so fast, I had already gone back and created new masters for each instance I was using. I will test it on the version previous and see if it works. Again, thanks much.
Two more questions First, I'm wondering of Clay Rendering Mode will be added at some point?
Also I'd like to know if you will be implementing the ability to render certain areas of the image. I know that the Standalone has this, and I think it will be useful for OR4C as well.
Thanks again, Sighman!
Two more questions First, I'm wondering of Clay Rendering Mode will be added at some point?
Also I'd like to know if you will be implementing the ability to render certain areas of the image. I know that the Standalone has this, and I think it will be useful for OR4C as well.
Thanks again, Sighman!
-
rashadcarter
- Posts: 71
- Joined: Thu Sep 11, 2014 1:16 am
Ah, I see that Render Region support is already added. Great, Off to test it out!
Hi Sighman, I hope you are well.
Recently I have noticed that when adjusting things like the exposure and film type settings, it restarts the render. It used to be that you could play with these and the render would just continue and adjust (which is obviously better). Is this something you are aware of and can we have the old system back please?!
Recently I have noticed that when adjusting things like the exposure and film type settings, it restarts the render. It used to be that you could play with these and the render would just continue and adjust (which is obviously better). Is this something you are aware of and can we have the old system back please?!
Not a bug persay, more to do with Windows Smartscreen, but in last two test releases, Windows pops up a screen saying that it did not run the program as it could not be verified, I just click run anyway and it installs fine, could you look into this? not a great concern, just annoying :p
This has been reported before but I cannot reproduce it. Can you send me a scene where this is happening?PhilW wrote:Hi Sighman, I hope you are well.
Recently I have noticed that when adjusting things like the exposure and film type settings, it restarts the render. It used to be that you could play with these and the render would just continue and adjust (which is obviously better). Is this something you are aware of and can we have the old system back please?!
Win8/64, I7-4770K (3.5Ghz) 24GB, GTX-980ti (6GB) / GTX-TITAN (6GB)