Page 3 of 5
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Mon Apr 01, 2013 8:55 pm
by face_off
Thanks Tlux
Which version of the plugin are you using? (It's displayed on the Render tab of the plugin).
Paul
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Tue Apr 02, 2013 7:35 am
by rappet
Hi Paul,
Minimalizing OR viewport would be nice in future,
especially for those working on one monitor.
Greetings, Jeroen
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Tue Apr 02, 2013 10:15 am
by face_off
Minimalizing OR viewport would be nice in future,
especially for those working on one monitor
This is in the next version - which should be available in the next 24 hrs.
Paul
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Wed Apr 03, 2013 12:45 pm
by face_off
The next version - which I had planned to post today is done....however, it contains the ability to attach difference rendertargets to each of your Views, and the ArchiCAD API is not allowing the identification of the current view, so unfortunately there is a delay while I try to sort out a work-around.
Paul
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Wed Apr 03, 2013 3:55 pm
by rappet
face_off wrote:The next version - which I had planned to post today is done....however, it contains the ability to attach difference rendertargets to each of your Views, and the ArchiCAD API is not allowing the identification of the current view, so unfortunately there is a delay while I try to sort out a work-around.
Paul
Hi Paul,
Sounds great!
It is worth waiting for.
greetings, Jeroen
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Thu Apr 04, 2013 10:21 am
by face_off
Hi Jeroen
It would be an understatement to say that implementing view-based rendertargets has been quite challenging with ArchiCAD!
A question for you....
If you click a new View in the View Map (which has it's own rendertarget), that view might have a different element filter (so the geometry will be different). So if you are rendering in Octane when you change the view, a) should the Octane geometry be updated to match the new view, or b) the render continue with the new views rendertarget settings but with the old geometry, or c) should the Viewport be closed to force the user to reload the scene into Octane?
Paul
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Thu Apr 04, 2013 3:45 pm
by rappet
face_off wrote:Hi Jeroen
It would be an understatement to say that implementing view-based rendertargets has been quite challenging with ArchiCAD!
A question for you....
If you click a new View in the View Map (which has it's own rendertarget), that view might have a different element filter (so the geometry will be different). So if you are rendering in Octane when you change the view, a) should the Octane geometry be updated to match the new view, or b) the render continue with the new views rendertarget settings but with the old geometry, or c) should the Viewport be closed to force the user to reload the scene into Octane?
Paul
Hi Paul,
I think a) is the better one as standard
i.e. each viewmap has its own layersettings and that is very handy with objects on and off by managing layers,
i.e. for making different scenario's in one file. Standard geometry reload/update will be better for future batch render too
b) as an option to turn on/off the refresh geometry might be welcome too
Not only for future batch render to save time when reloading geometry (it will be unnecessary reloading when there are no differences in the scenes, but only different cameras).
But also ...for large scenes it might be frustrated to have it reloaded when it takes a long time?
But I rather have a) if I have to choose between a) and b) otherwise the batch render will simply not be useful (is my guess)
c) I don't see advantage in this option. Do you have a reason for this option?
greetings, Jeroen
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Thu Apr 04, 2013 9:22 pm
by face_off
Thanks Jeroen.
Even if there is NOT a separate rendertarget for each view (ie. the way it is with 1.11b), changing views does not force a geometry reload - which is not optimal. I think the simplest option is a new toggle button on the Rendering tab called :
"View Refreshing"
help text: "When ON, this causes a scene refresh of the Viewport when you select a new 3D view in the ArchiCAD View Map".
Paul
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Thu Apr 04, 2013 10:51 pm
by rappet
face_off wrote:Thanks Jeroen.
Even if there is NOT a separate rendertarget for each view (ie. the way it is with 1.11b), changing views does not force a geometry reload - which is not optimal. I think the simplest option is a new toggle button on the Rendering tab called :
"View Refreshing"
help text: "When ON, this causes a scene refresh of the Viewport when you select a new 3D view in the ArchiCAD View Map".
Paul
Hi Paul,
Yes, the new toggle button is the optimal choice
Both options are very useful in different situations.
It is getting better and better and better and better... Where does it end
You are doing great stuff

Jeroen
Re: OctaneRender® for ArchiCAD beta - build 1.11b [TEST]
Posted: Fri Apr 05, 2013 5:08 am
by face_off
I tried batch rendering in ArchiCAD (via setting the View "Generate In" to "Photorender Window", and then setting all the views to shortcuts to publishing set - as per
http://www.youtube.com/watch?v=tluXEVPayYI), however when I publish the set, it changes the Photorenderer from "OctaneRender Renderer" back to "Internal Renderer". Is this an ArchiCAD bug?