Open topic with navigation
ArchiCAD -> Options -> Add-On Manager. The “OctaneRender for ArchiCAD” and “OctaneRender Renderer” Add-Ons should both be ticked. If they have a red “!” next to them, then they could not be loaded, which is most likely due to not having the latest NVidia Cuda drivers loaded.
In general, due to the nature of the way ArchiCAD constructs the flat surface geometry, the vast majority of material should have “smooth” DISABLED. Only curved surfaces should be “smooth” enabled (like grass, motor vehicles, etc).
Set the Internal Engine material Emission Attenuation to be equal or greater than the “Emission Percent” set in the plugin “Configuration” screen (available from the Settings tab of the plugin).
This is due to using the same card for Octane rendering and for your Windows display adapter. It is highly recommend to have a separate card as your Windows display adapter (your on-board graphics card for example).
If you are using one card, set the Render Priority to Low (see GPU Settings).
For reference, Otoy have recommended registry settings that you should use:
In cases of the Windows Vista/7 “Timeout Detection and Recovery”, settings can be changed using Regedit. The recommended setting for Octane are registry setting HKLMSystemCurrentControlSetControlGraphicsDrivers, TdrLevel = 3, TdrDelay =10 (if these settings are not already there, rightclick the right panel -> New -> DWORD). You will need to reboot after changing these settings.
It is also recommended that you view the ArchiCAD scene using the Internal Renderer whilst rendering large scenes in Octane (right click the Perspective Camera in the Navigator-Project Map->3D Window Settings->Change 3D Engine to Internal Engine.
The ArchiCAD plugin does not have a node graph. Instead it uses a tree structure which enables macro type functions (copy, paste, import, export, etc) which is more efficient and much better matches the ArchiCAD workflow.
You can import an ORBXThe ORBX file format is the best way to transfer scene files from 3D Authoring software programs that use the Octane Plug-in such as Octane for Maya, Octane for Cinema 4D, or OctaneRender Standalone. This format is more efficient than FBX when working with Octane specific data as it provides a flexible, application independent format. ORBX is a container format that includes all animation data, models, textures etc. that is needed to transfer an Octane scene from one application to another. format from the Octane Standalone LocalDb.
There is now no limit.
No, the memory available will be the memory capacity of the smallest card in your system. If you have a 1Gb and a 2Gb card, and need over 1Gb of memory for your scene, turn off the 1Gb card in the Cuda Devices tab of the plugin.
Yes, it was introduced in version 1.16a.
A MacIntosh version is planned.
At this stage texture map scaling is implemented, however Octane does not currently support texture map offsets or rotations, nor disabling of tiling. To use these effects in your renders, manually adjust the texture maps in your image editing program.
This is most likely occurring because the texturemap for the tree is inside an ArchiCAD library archive (icf file). To get around this, extract the archive and use the extract as your library by doing the following:
The above is .pln file specific – so you will need to do the above on a blank document and save as a template if you want it always applied by default.
During the upgrade, your graphics card may have been disabled by Octane. To fix this, go into the Devices page of the plugin and re-tick “Active” for your video card.
If your scene was originally a very large scene, and you deleted all the items in the scene to start from a blank scene, then some/all the deleted items may still be in the pln file, so when the plugin searches through all the scene geometry, it may still search through the deleted items. Saving the scene to a pla file, and then reload that pla should resolve this issue.
Open topic with navigation