OctaneRender® for ArchiCAD beta - build 1.13a [OBSOLETE]

[face_off]

Artur

I just wanted to let you know the I am rolling out the change to GDL materials which separates them for each instance of the GDL object. Internally, ArchiCAD is treating these materials as the same material, so when I try to split them up, it is causing a lot of synchronization problems between ArchiCAD and the plugin. To be clear, an "internal" GDL material "black" on a car type is considered by ArchiCAD to be the same material as an "internal" GDL material "black" on a wall. So treating them as being different materials is challenging. For the moment, I would like to stabilize the plugin functionality, and when everything has proven to be highly robust for some time, I can look into it again.

A workaround is that you can edit the GDL object and change the material name.

Paul

[face_off]

New version available from the links in the first msg of this thread.

1.13a5
- Fixed crash when changing from "daylight" to "textrue environment"
- Rolled out (ie. removed) the ability to have separate versions of the same GDL material. Now the material "GDL_leaves" is the same material for all objects which use this material (ie. there are not separate instances of the GDL_leaves material anymore).
- Fixed issue where the rendertarget set in the Photorender Settings was not being used for the photorender render

Paul

[face_off]

New version available from the links in the first msg of this thread.

1.13a6
- Fixed issue with Response popup
- Fixed a bug where the previous default rendertarget settings were not being loaded when restarting the plugin

Definitely download this version - for the second item above.

Paul

[BfPuVAK]

Hi Paul,

sorry for my late answering, just too much work at the moment here

Not a bad idea to put the GDL materials back for the moment, it's really a mess with them !

To be clear, an "internal" GDL material "black" on a car type is considered by ArchiCAD to be the same material as an "internal" GDL material "black" on a wall. So treating them as being different materials is challenging.

Well, if you have in mind that "black" is a material from the Archicad-material-list and assigned by a parameter of the GDL-object to a part of it - and the same material is assigned to a wall - so you're not right here, in this case no differentiation is needed. But you need definitely need it when you have some copies of that certain object and each of them has different materials assigned in the parameters of it.
Whatever, just let me know when you return to go about this problem and I will try to help
(recently I ahd that idea: using the object name itself (instead of the ID) could be perhaps a way, too...)

Independant from that I'll mail you two further projects according the material-name-lenght-problem...

Apart from that - 1.13a6 works fine

[edit]
Just wanted to start rendering an animation; at every frame the following error is displayed (and the picture saved as just behind this massage):



Octane itself & Viewport was opened, of course. Archicad render- and animation-settings were also defined properly.
Have tried a bit with different settings, restarted also - no change...

Greetings,
Artur

[face_off]

I have posted a modified version of the plugin to address Artur's issue with material names not matching. The source of this bug appears to be where materials originated from an earlier version of ArchiCAD they had 2 names! This version of the plugin should now correctly match these materials. Because of the substantial nature of the changes required to fix this, I have posted just an ArchiCAD16 version, and given it a new version. If it checks out OK, I'll do an AC14 and 15 version.

OctaneRender for ArchiCAD 16 1.13b beta (32 & 64 bit)

Paul

[BfPuVAK]

Hi Paul,

it works in 99%

Some particular materials still make problems and only shortening the name helps out - but that's not a real problem.
(I mailed you a more bit detailed answer)

Many thanks !
Artur

[face_off]

Just wanted to start rendering an animation; at every frame the following error is displayed (and the picture saved as just behind this massage):

Artur - are you also getting that message with the very latest version?

Paul

[BfPuVAK]

...nope, it works now ! (1.13b beta7)

[edit]
Yes, in one case it worked without problems (600 frames).
Now, another project: it stops suddenly, one time at frame 32, another (after restart) at frame 27...

Thanks,
Artur

[face_off]

Now, another project: it stops suddenly, one time at frame 32, another (after restart) at frame 27...

Hi Artur. A few points on this to help identify the issue:

1) May I suggest monitoring your GPU temperatures - it could be an overheating issue (since it is rendering for a long time). Use TechPowerUp GPU-Z. Also check your VRAM using that tool as the animation progresses.
2) In addition to the above, whilst rendering the animation, check the Window task manager to see if ArchiCAD is using more and more memory during the animation (it shouldn't!)
3) If you have the plugin Setup windows and Viewport are open, and you then run the animation, the ArchiCAD scene will NOT reload each frame - it will instead simply pickup the Octane nodes from the Viewport. So try an animation with the Setup and Viewport windows OPEN, then try it with them both CLOSED. Was there a difference?

Thanks

Paul

[BfPuVAK]

Hi Paul !

1) and 2) are unsuspicious. Temperature max. 64°C, ArchiCad is constantly using 28-30% of RAM. Vram also constantly at 825 MB.

It seems to make no difference how long the render is already running, sometimes the stop is at frame 27, sometimes on 1120.
Using Office or Firefox simultaneously shouldn't make troubles here, sholud it?

3) Up to now I used to render animations with opened plugin. I started just animating with the plugin closed: the point where it stopped yesterday
was passed without problems now...so it looks good at the moment

I'll test it more the next days and report...

Aprart from that;
I generelly need no scene reloading as I use no animated objects within Archicad. Hope it doesn't slow down too much @ big scenes...
With the plugin opened rendering of a complete animation should be faster as ther's no reloading, am I right ?
And the reloading seems not to need as much time as it needs after pressing the reload-button of the plugin...

Thanks & Greetings,
Artur