OctaneRender 3 for ArchiCAD [OBSOLETE]

[ArchPrime]

Hi Paul,

it's pretty easy to do, you really just need to add the placement node the first one, then 'save as' and then just reload the next mesh you want to 'convert' and 'save as' again. Let me know if you're struggling and I'll come and show you how to do it. You're really better off in the orbx format anyway as you can then have more control over the materials and the geometry smoothing etc.

Cheers, Dan.

Thanks Dan - process does seem simple enough, but even so would be arduous if converting the entire Treefrog library to orbx for example. Something as repetitive as this seems a sitter for some sort of batch file automation script...

[face_off]

Yes, some sort of batch converter would be super useful - most people have hundreds of Objs, and it would be painful to manually set up each one as an orbx

Anyone who is proficient with LUA Octane scripting would be able to do this reasonably easily. I suggest putting the request in the LUA forum here - you may get someone willing to do it.

If so, is there a clever way that these changes can be stored locally and just to the project file

The only way to do this would be to move the proxy host. If you edit the ORBX proxy Placement node, then that change is in the ORBX, not the ArchiCAD scene.

Paul

[ArchPrime]

Is there a way to have the octane plugin, whenever a change is being made on the fly to an proxied orbx via the 'edit' button, save a local copy of that orbx into the project directory and relink proxy to that version, and so leave the original orbx alone?

[face_off]

Is there a way to have the octane plugin, whenever a change is being made on the fly to an proxied orbx via the 'edit' button, save a local copy of that orbx into the project directory and relink proxy to that version, and so leave the original orbx alone?

That could be done, but you would end up with many versions of a proxy ORBX - one for each change.

Paul

[ArchPrime]

Is there a way to have the octane plugin, whenever a change is being made on the fly to an proxied orbx via the 'edit' button, save a local copy of that orbx into the project directory and relink proxy to that version, and so leave the original orbx alone?

That could be done, but you would end up with many versions of a proxy ORBX - one for each change.

Paul

What about setting a 'this is a local copy' flag the first time it is edited from a given project and a copy saved to a directory other than the original directory, such that subsequent times it is edited, it knows to save over that first copy (or even prompts user to confirm save location)

[face_off]

What about setting a 'this is a local copy' flag the first time it is edited

I'm not sure where would this flag be stored? There is also the consideration that when people want to move scenes between PC's, they need to copy all the assets too - so if the plugin is creating it's own assets, the user would not be aware of them.

Paul

[ArchPrime]

What about setting a 'this is a local copy' flag the first time it is edited

I'm not sure where would this flag be stored? There is also the consideration that when people want to move scenes between PC's, they need to copy all the assets too - so if the plugin is creating it's own assets, the user would not be aware of them.

Paul

Could it be stored as metadata associated with the edited and resaved orbx file, which gets saved by default in project assets directory and relinked to there along, with all the other assets like textures etc that can be saved - anyone moving the project would just copy the while project directory, and so links would be preserved?

[face_off]

Could it be stored as metadata associated with the edited and resaved orbx file, which gets saved by default in project assets directory and relinked to there along, with all the other assets like textures etc that can be saved - anyone moving the project would just copy the while project directory, and so links would be preserved?

I think it would be far easier for you to simply have a master copy and then copy it in Explorer and then link the copy.

Paul

[face_off]

I have updated the TEST installers at the top of this thread with:

3.7.0.76
- Compiled with Octane 3.07 TEST 6
- Fixed issue where Specular materials could not be imported from the LocalDb

Paul

[ArchPrime]

Could it be stored as metadata associated with the edited and resaved orbx file, which gets saved by default in project assets directory and relinked to there along, with all the other assets like textures etc that can be saved - anyone moving the project would just copy the while project directory, and so links would be preserved?

I think it would be far easier for you to simply have a master copy and then copy it in Explorer and then link the copy.

Paul

I guess, but that would interrupt the user in the throes of editing, and feel like a workaround?