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

[face_off]

Sorry, my students tell me all the time!!! The only thing you can need to do its a section and select some "morph" in the section view (not in plan or 3d view in this views it work well)

The issue is fixed in the next version.

Paul

[Garquitectos]

Sorry, my students tell me all the time!!! The only thing you can need to do its a section and select some "morph" in the section view (not in plan or 3d view in this views it work well)

The issue is fixed in the next version.

Paul

You are a monster!!!

[face_off]

One annoying thing i have found is when you copy or alt click an archicad "placer" object it loses the octane proxy information, is there a way to code the proxy file name into an archicad object so that it always refers to that object ie have a specific field in the objects gdl code that you can use to pull thru the proxy file location?, I want to have number of placholder objects already set up with their proxy objects sitting on my template then just alt click and place the desired objects within the scene.

This would be a great enhancement to the plug-in

I have done some research into this. Ideally the proxy obj name, scale and rotation would be stored in the "parameters" of the host ArchiCAD Object instance (then you could freely copy it and the proxy info gets copied too). However a plugin cannot ADD parameters to an instance of an Object that is already in the scene. It can however READ and WRITE to existing parameters. So the plugin cannot add a parameter "Octane Proxy File" to a a chair object instance, which does NOT already have "Octane Proxy File" as a parameter in the library. It can however write to the "Octane Proxy File" parameter in the OCTANE PROXY OBJECT.gsm file you provided.

So options are:

1) Current implementation - where copying the host object does not copy the proxy info.

2) Proxy info is stored in the OCTANE PROXY OBJECT.gsm object instance, and ONLY that object can be used as a geometry proxy host object (ie. no other Object could be used as a geometry proxy host). You could copy the OCTANE PROXY OBJECT.gsm object instance and the proxy info would be copied too.

3) As per the current implementation, however IF the host object has a "Octane Proxy File" parameter (and the scale and rotation parameters), then they will be used to store the proxy info, otherwise the proxy info is stored in the pln file. In the case where the host object had the "Octane Proxy File", the plugin would keep this up to date with the current OBJ filename.

Option 3 is the most complex to implement, AND the most complex for people to understand, but offers the best flexibility. I'm tending to think it is the best option.

Paul

[rappet]

Hi Paul,

1) error
While testing a few problems occurred.
I got an unexpected blue screen (might be my system failure, not plugin)
Plugin freezed up a couple of times and the printscreens shows the latest freeze with "working...". I can change camera though and it starts rendering, but I cannot close vieport, plugin or Archicad.

2) Secondly this post is about the use of csv file.
On the left side you can see the example of what I am trying to achieve in testing scattering using a csv file: one leog copied to the right 4 times and rotate them on the spot.
On the right is my proxy that I am trying to make it like the example, but I did not get it work yet.
The printscreen of the csv used in the standalone show a good result. When using the same csv in the plugin it gives another result?

greetings, Jeroen

UPDATE:
the csv lines I used for testing:
-1,0,0,0,0,1,0,0,0,0,1,0
0,0,1,1,0,1,0,0,1,0,0,0
1,0,0,2,0,1,0,0,0,0,-1,0
0,0,-1,3,0,1,0,0,-1,0,0,0

[face_off]

While testing a few problems occurred.
I got an unexpected blue screen (might be my system failure, not plugin)
Plugin freezed up a couple of times and the printscreens shows the latest freeze with "working...". I can change camera though and it starts rendering, but I cannot close vieport, plugin or Archicad.

During the development of the plugin I have managed to crash ArchiCAD many times, but never had a BSD. Did ArchiCAD save a dump report to C:\Users\[username]\Graphisoft\BugReporting-[version]? It would also be worth checking your Window event log.

The freeze with the "Working..." I haven't seen before either, but the latest version I am running has a couple of bug fixes you don't have yet, so they may fix it.

2) Secondly this post is about the use of csv file.
On the left side you can see the example of what I am trying to achieve in testing scattering using a csv file: one leog copied to the right 4 times and rotate them on the spot.
On the right is my proxy that I am trying to make it like the example, but I did not get it work yet.

If the robot is not at 0, 0, 0 in the ArchiCAD scene, it's offset from 0, 0, 0 will be applied BEFORE the transform matrix (which is what is happening in your scene). There are two solutions to this....1) Place the object at 0, 0, 0 (is it actually possible to specify coordinates in ArchiCAD to do this?), or 2) If there is a transform matrix specified for a geometry proxy, I have the plugin set the position of the object to 0, 0, 0 in the Octane scene prior to applying the transform (ie. instanced objects will repositioned at 0, 0, 0 in the Octane scene)

Let me know how your preference.

Paul

[Nuge]

I have done some research into this. Ideally the proxy obj name, scale and rotation would be stored in the "parameters" of the host ArchiCAD Object instance (then you could freely copy it and the proxy info gets copied too). However a plugin cannot ADD parameters to an instance of an Object that is already in the scene. It can however READ and WRITE to existing parameters. So the plugin cannot add a parameter "Octane Proxy File" to a a chair object instance, which does NOT already have "Octane Proxy File" as a parameter in the library. It can however write to the "Octane Proxy File" parameter in the OCTANE PROXY OBJECT.gsm file you provided.

So options are:

1) Current implementation - where copying the host object does not copy the proxy info.

2) Proxy info is stored in the OCTANE PROXY OBJECT.gsm object instance, and ONLY that object can be used as a geometry proxy host object (ie. no other Object could be used as a geometry proxy host). You could copy the OCTANE PROXY OBJECT.gsm object instance and the proxy info would be copied too.

3) As per the current implementation, however IF the host object has a "Octane Proxy File" parameter (and the scale and rotation parameters), then they will be used to store the proxy info, otherwise the proxy info is stored in the pln file. In the case where the host object had the "Octane Proxy File", the plugin would keep this up to date with the current OBJ filename.

Option 3 is the most complex to implement, AND the most complex for people to understand, but offers the best flexibility. I'm tending to think it is the best option.

Paul

Paul,

Option 3 would be perfect for me, if you control and publish what parameters we need within our objects (file name rotation etc) the code can be added simply to any existing object.
For example I use a number of 2d plant objects showing on plans, with this i can add in the code and have octane render the required obj file automatically, fantastic!

A simple check box in the plugin "use GSM paramaters" would get the job done and allow total flexability of workflow.

hope this helps, let me know if you need help with and GSM coding

John

[face_off]

Hi John

The current status is.....
- I have created a revised Octane Proxy Object.gsm object, which includes scale and rotation as parameters
- The plugin detects if the current object is the above gsm object, and if it is it uses the gsm object parameters as the master copy of the obj filename and scale/rotation
- If you edit the obj filename/rotation/scale in the plugin, it then saves these back to the above Object.
- If you copy the above object and then paste it - the new object contains the proxy data (which was the aim of all this)

There is one very very big limitation to the third point above....the save can only occur if you are viewing a 2d window. If you are viewing the 3d window when you update the filename/scale/rotation in the plugin window, the API will not let the parameters be updated by the plugin.

So I am re-working how this has been implemented, and moving away from the "parameter" method, and instead going to see if it's possible to use some internal data structures which won't be visible to the user, but achieve a better outcome. Unfortunately it will take another 24hrs to get it out to you.

Paul

[Garquitectos]

Update parameters if painfully in Archicad!!! I made a GDL objet to make complex geometry (like generative components) to updte parameters finally I put a button in the gsm, because sometime it not update parameters well...

Another implemetation can be save "like special objet" an this object has the parameters...
For example:
Save object like "custom object" (another kind of special object like "leaf door", "door"...)

Then insert "proxi" objet and choose the previous "custom object" this "proxi" has all the parameteres that you want...

With my poor English I can't explain better...

Hi John

The current status is.....
- I have created a revised Octane Proxy Object.gsm object, which includes scale and rotation as parameters
- The plugin detects if the current object is the above gsm object, and if it is it uses the gsm object parameters as the master copy of the obj filename and scale/rotation
- If you edit the obj filename/rotation/scale in the plugin, it then saves these back to the above Object.
- If you copy the above object and then paste it - the new object contains the proxy data (which was the aim of all this)

There is one very very big limitation to the third point above....the save can only occur if you are viewing a 2d window. If you are viewing the 3d window when you update the filename/scale/rotation in the plugin window, the API will not let the parameters be updated by the plugin.

So I am re-working how this has been implemented, and moving away from the "parameter" method, and instead going to see if it's possible to use some internal data structures which won't be visible to the user, but achieve a better outcome. Unfortunately it will take another 24hrs to get it out to you.

Paul

[face_off]

Jose - very cleaver - I never thought of that.

I think I have found an even simpler way. I can directly save the proxy info to the Objects (not as parameters, but as raw data). This raw data gets copied when you copy and paste an Object, and gets saved with the pln file. This means any object can be copy and pasted and it's proxy info will get copied. I still have lots of testing to do - but it seems at this stage to work. The only downside is that it save the scatter transform file with the proxy info, but it's probably rare you would copy and paste a scattered proxy.

Paul

[face_off]

New test version posted at http://render.otoy.com/forum/viewtopic.php?f=56&t=33132. This version has been moved to STABLE status.