In general, due to the nature of the way Revit 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).
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.
For reference, Otoy have recommended registry settings that you should use:
In cases of the Windows Vista/7 “Timeout Detection and Recovery” http://msdn.microsoft.com/en-us/library … 87368.aspx. 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.
The Revit 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 Revit workflow.
Not at this stage, but it is planned.
The GTX 500 series cards have a limit of 64 LDRImage formats that have 8 bits per color channel such as the common image formats JPEG, PNG, GIF among others. (8 bit) RGBA, 32 LDR (8 bit) greyscale, 4 HDR (16 bit) RGBA and 4 HDR (16 bit) greyscale texturemaps. The GTX 600 series cards have a limit of 144 LDR (8 bit) RGBA, 68 LDR (8 bit) greyscale, 10 HDR (16 bit) RGBA and 10 HDR (16 bit) greyscale texturemaps.
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.
Yes.
When a Revit scene is loaded which has Octane materials, the plugin checks to ensure the texturemap files for each Octane RGB Image node actually exist on your hard disk. If they do not, the plugin requests the user select a search path for locating the missing texturemap. If you “Cancel” at this point, searching for missing texturemaps is aborted (and if you open the Viewport, Octane will report an error for the missing texturemap, but the Viewport will still open and the render will still start). However, if you do not Cancel, and instead specify a search path. the plugin will search all folders inside that search path for the missing file(s). If the plugin encounters a folder within the search path for which the users does not have read access to (i.e., the plugin cannot read the files in that folder), the message “You do not have read access to that folder” is displayed. If you get this error, refine the search path so that it is searching a folder which you do have access to.
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.
This might happen if you put the Viewport on a second monitor, then disable that monitor (Revit will “remember” the window position on the second monitor and place the Viewport there out of sight). The easiest solution is to delete your config.xml file (as per the Configuration topic).
This is due to either not having Cuda drivers installed, or by starting Revit NOT via Revit.exe (i.e., you have started Revit by double-clicking an .rvt file). To fix the second situation, edit OctaneRender_for_Revit.addin as per the Configuration topic.
This is due to either not having Nividia video drivers loaded, or not having a sufficiently recent enough version of these drivers. Please see FAQ questions 1 and 2 here for details.