Release Notes for Octane Render SketchUp Plugin 3.06.1.4
Changes in This Release
* The plugin will not waste time converting geometry and materials when the render window is not open. * The default layout now includes the scene outliner. * The current workspace layout is saved and loaded with the scene (in the SKP file). * A bug in which the node graph editor sometimes lost track of the sandbox and showed the wrong node graph when the window was closed and reopened has been fixed.
About This Release Series
This is a public test release of a major update to the Octane Render Plugin for SketchUp. Please note that this is an early beta release and should be used with care.
The 3.06 release series represents a thorough redesign of the plugin's user interface. The plugin now uses a separate window of its own, similar to the standalone Octane Render application. You can open this window through the Octane button on the SketchUp toolbar, or from SketchUp's Extensions menu.
The Octane plugin window is built from a set of panels similar to the standalone app:
* The Scene Outliner (on the left in the default layout) shows an expandable list of all nodes in the Octane version of the scene. This panel also has tabs giving access to the LiveDB and the local database. This panel is not visible in the default view but can be opened from the Window menu.
* The Render Viewport (top) shows the image rendered by Octane. This was originally a separate window in earlier versions of the plugin.
* The Node Graph Editor (bottom) depicts a "sandbox" that shows only the material nodes (and linker nodes connecting them to the geometry); the rest of the node graph (geometry, rendering options, etc) is hidden. You can manipulate the material nodes in the same way you would in the Octane standalone app.
* The Node Inspector (right) shows the full details of any selected node, and allows them to be edited by hand.
You can learn more about the new user interface from the manuals and tutorial videos for the Octane SketchUp plugin and the Octane Render standalone application:
* There are no longer separate menu options for converting a SketchUp material to an Octane one, or for creating a new Octane material from scratch. These are no longer necessary since the new GUI window provides equivalent functionality. Converting a material from SketchUp to Octane is not a separate operation now; it happens automatically as soon as the material is used.
* All information about Octane materials is now saved with the SketchUp scene in the .SKP file. Unlike earlier versions, all texture graphics are included in this; textures are no longer saved in a separate directory. The saved scene also records any changes you make to the material nodes through the node graph editor. This has two important consequences:
* You can now transfer a scene file to another computer, or send it to another user, without losing the texture information.
* Scene files containing Octane plugin data are necessarily larger (sometimes much larger) than they were as plain SketchUp scenes, since they now contain all of the image files needed to reconstruct the Octane textures.
* The plugin requires SketchUp 2015, 2016, or 2017 for Windows x64 * SketchUp 2017 is recommended * Microsoft Windows 7, 8, 8.1, or 10 for x64 * The plugin is not compatible with any x86 (32-bit) version of SketchUp or Windows
* 64-bit Intel or AMD CPU * One or more recent model Nvidia GPU cards * Nvidia drivers 353.x or later; CUDA 8.0 support is required * The plugin is not compatible with AMD or Intel GPUs
The installer has been completely rewritten. There are now separate installers for the SketchUp 2016 and 2017 versions of the plugin. You can install both versions on the same computer; they are now treated as separate applications. (The 2016 version of the plugin is also compatible with SketchUp 2015, although you will need to manually edit the install location.)
We recommend uninstalling all previous versions of the SketchUp plugin before installing the latest version.
Please note that stable and test releases will not be identified by any special version numbers. Because of potential compatibility issues if different builds of the Octane engine are run on the same system, we believe it is more important to keep plugin version numbers synchronised with the corresponding build of the standalone Octane application and the Octane SDK. If you are having problems, the first thing you should check is that you do not have different versions of other Octane products installed.
If you have a support issue, please provide the following information: - Operating system (e.g. Windows 8.1 x64) - CPU type (e.g. Intel Core i7) - Amount of RAM - Graphics cards - model (e.g. Nvidia GTX 690 with 4GB) - Nvidia driver version (e.g. 365.10) - SketchUp version (e.g. SketchUp Pro 2016 version 16.1.1449 64-bit) - Skatter version (if you have it installed; e.g. Skatter 1.2.0) - OctaneRender for SketchUp version (e.g. 3.06.1.4)
The most important part of resolving a problem is our being able to reproduce the problem, so please provide as much detail as possible!
These changes were made in earlier 3.x releases of the plugin, and are still relevant in the latest release:
* Like the Octane 3 standalone version, the SketchUp plugin uses the new single sign-on system. You still need to have purchased a license for the SketchUp plugin, but it will now be checked automatically when you log in using your Otoy account credentials; you no longer need to keep track of user IDs and passwords for individual licenses. The new authorization management window is a modal dialog where the user can sign out and sign in. It also informs the you under which name you are signed in and if that sign-in was in offline or online mode. When a user signs out, all of your licenses which were activated on this computer will be deactivated. This requires that all these licenses are currently not in use by other Octane processes; if that is not the case the sign out will fail.
* Because most rendered images are now stored in your computer's main RAM instead of your video card's RAM, all Octane 3 applications, including the SketchUp plugin, will frequently use a good deal more memory than their Octane 2 equivalents, especially for high resolution renders. You should keep this in mind when upgrading.
* 3.03+ releases include experimental Pascal GPU support. Please note that we are still working on performance issues there.
* Support has been added for the Skatter plugin's Render Only mode.
We hope to fix these in a coming update.
* Custom resolution in the material preview does not work.
* Material picking is not fully working yet.
* Once a texture has been copied from SketchUp to the Octane version of the scene, any changes made to either version of the material are not reflected in the other version. (This is a simplification applied to ensure the two versions of the material are handled correctly in this version of the plugin; we intend to add automatic transfer of changes from one to the other in future, where the different properties and behaviour of Octane and SketchUp materials allows it.)
* The new GUI currently only supports one view of a scene; SketchUp models with multiple views are not supported yet.
* Importing materials directly from the LiveDB can crash the plugin. Materials can be brought in by copy and paste instead.
* Re-applying the same texture after an undo may fail to work. This is a bug in SketchUp, not related to the Octane plugin.
3.06.1.4 - Fix slow geometry transfer when render window is not open; add scene outliner to default view; save workspace layout with scene file.
3.06.1.2 - Initial public test release with the new user interface.
Last edited by CaptainCrowbar on Sun Jun 18, 2017 11:48 pm, edited 1 time in total.
Thank you guys for your work - we are getting closer and closer
1. When I close Octane plugin it is till rendering in the background - my selected GPUs are still active.
2. When I create any component there is no nodal representative of it until I apply any material onto it. MY HUGE WISH - please give us geometry nodes that would represent SU geometry (groups, components). This would also serve as proxy source when replaced with external obj/ocs.
3. We have to have full functionality of mesh insert items - objs, ocs - instead of proxy in SU we shall be able to link obj/ocs in Octane and replace original geometry from SU. * The Node Graph Editor (bottom left) depicts a "sandbox" that shows only the material nodes (and linker nodes connecting them to the geometry); the rest of the node graph (geometry, rendering options, etc) is hidden. You can manipulate the material nodes in the same way you would in the Octane standalone app. Can we have geometry nodes visible?
4. I still don't see the icons for kernel settings and all other icons to the right.
5. There is no other than "preferences" tab in the file menu - no save as orbx, save as default,... - is this intentional or will be added in next releases?
#1 is critical and #2 (and #3) stops me from using the plugin - we have to have visible geometry nodes (not materials only).
On startup I'm still seeing Octane geo being built meaning large file load times...Also crashes when activating / de-activating Octane plug in the Extensions Manager.
Crashes when making groups - only way to prevent crash is to have plugin open when making them - though on application of a new SU native material - crash...
Crashes also when selecting multiple faces (say, 300 or so, possibly fewer) and changing their material while Octane is not running...100% sure the plugin is the source of crash as doesn't happen when de-activated in Extensions Manager...
So work around for me is wait for crash, re-open SU, deactivate plug, undertake material change on polys, save, turn on plug, let it crash, re-open file and render
So it seems the plugin is still processing certain SUp commands even when not active?
Live DB materials will also not save - no undos...Is this correct?
'Find' dialog not present
Also - no way to 'lock' a view to render out while continuing to work in SUp - 'lock' button and pause do not work...
'Film Settings' remembered on exit, however on re-open these default and are only re-applied by manual entry rendering the exercise pointless
Thanks for the effort again!!
Last edited by -rb- on Thu May 25, 2017 4:45 pm, edited 8 times in total.
@Captain, with the Octane standalone clone approach you got here, what happens when SU's parallel projection camera is active? It was one of my fav features of Fuzzybro's plugin and I used it a lot. Do we still have it?
Next feature I'm working on, hopefully ready very soon, will allow you to set up multiple views in SU with different cameras, and have them automatically converted to separate render targets on the Octane side.