OctaneRender for Modo (Windows) 1.52 [STABLE]

[funk]

Small issue with config file prevents the plugin from loading in 701 sp4

You have:

Code: Select all

<configuration kit="OctaneRender" version="1.33.0.48" and="ver]66614">

This states the modo version must be GREATER than 66614, therefore 66614 doesnt load it.


It should be

Code: Select all

<configuration kit="OctaneRender" version="1.33.0.48" and="ver]66613">

[face_off]

1. If I animate octane aperture and focal depth, it only works if I reload the viewport after changing frames.

2. If I use modo focus and modo fstop (the 2 new features you added), animating the modo values doesnt work after changing frames and reloading. It always uses the values at frame 0.

I will look into these.

If I close a scene while the viewport is open I'm getting an error

Steps:
1. Start a new scene (ctrl+n)
2. Open octanerender viewport
3. click back in the modo window to gain focus
4. close scene (ctrl+w)

Error: The scene being rendered in the viewport has been closed by modo. Scene updates will not be sent to the vieport and material and focus picking are disabled until you refresh the scene.

I can just hide future messages but thought I'd mention it

The popup is intended. Perhaps it should be changed to a warning rather than an error. And because the scene has been closed, you cannot really refresh it! I'll change the wording.

Standalone will not load the ORBX (pops up "error during loading"). I assume there is a mismatch due to you using the 1.33 API and it will sort itself out once you use 1.5. The OCS is works fine.

Yes - this will all be OK once the plugin is available for 1.5.

NOTE 2: If you do an export, it seems you need to close the viewport and reopen it for the next one, otherwise, no geometry folder gets saved. I discovered this because I exported, then manually deleted the exported files and tried a second export. Not really a big deal though

Interesting - there is probably some caching mechanism in the Octane API causing this.

This states the modo version must be GREATER than 66614, therefore 66614 doesnt load it.

Fixed in the next version. TY.

Paul

[funk]

I downloaded the updated livedb zip and also tried to update from inside modo with "octane.command downloadLiveDb".
A dialog box came up "Success: Livedb download complete. Pls restart Modo for this to take effect".
Once I OKed it I got another "Error: An octane error occurred. Check the octane log for details". Once I OKed it, there was a progress bar stuck at 75.4% "downloading Livedb Materials", so I clicked abort.

Heres the log:

Code: Select all

Started logging on 25.03.14 18:27:28

OctaneRender version 1.33 (1330000)

graph doesn't have a valid material/texture node
graph doesn't have a valid material/texture node
graph doesn't have a valid material/texture node

I tried this twice, same result

Checking the asset timestamps I see 2 textures were added and 1 LXP "Assets\Octane LiveDb\Materials\Organic\Stone\tiles lappato 60x60cm 3x3 748.lxp"

This was in the modo event log (from later retries):

Code: Select all

octaneRenderFor Tue Mar 25 18:40:51 2014  Info    Authenticating Octane: Complete
octaneRenderFor Tue Mar 25 18:41:22 2014  Info    Error downloading material Material Macro
octaneRenderFor Tue Mar 25 18:41:24 2014  Info    Error downloading material Blued steel test
octaneRenderFor Tue Mar 25 18:41:24 2014  Info    Error downloading material Material Macro
Command Results Tue Mar 25 18:41:33 2014  OK      octane.command downloadLiveDb

UPDATE: I also noticed our presets have different names to the livedb in octane (they have numbers appended to the names)
eg: "materials\organic\skin\white leather" is called "white leather 260" in modo

UPDATE 2: The livedb zip file is missing 2 root categories "textures" and "emissions"

[face_off]

Once I OKed it, there was a progress bar stuck at 75.4% "downloading Livedb Materials", so I clicked abort.

Fixed in the next release.

Checking the asset timestamps I see 2 textures were added and 1 LXP "Assets\Octane LiveDb\Materials\Organic\Stone\tiles lappato 60x60cm 3x3 748.lxp"

Tiles lappato 60x60 seems to be a corrupt LiveDb material. There are a handful of these in the LiveDb which will not load via the Octane API.

UPDATE: I also noticed our presets have different names to the livedb in octane (they have numbers appended to the names)
eg: "materials\organic\skin\white leather" is called "white leather 260" in modo

The numbers are added to differential between materials which have the same name. The number is the LiveDb material id.

UPDATE 2: The livedb zip file is missing 2 root categories "textures" and "emissions"

Only materials are supported at this stage. From memory there are only a handful of "textures" and even less "emissions".

Paul

[face_off]

I have updated the installer at the top of this thread with:

1.50.0.48
- Compiled against Octane 1.50
- Added Octane Camera option to use the Modo focus distance to set the Octane focus distance, and the Modo Fstop to set the Octane aperture
- Removed non-material LiveDB items from the downloadable LiveDb Presets archive (LiveDbPresets.zip)
- Fixed issue where moving a LivDb Octane Override prior to the workspace having been created was displaying a warning message
- IMPORTANT: Fixed issue where adding an Octane Override for a material in a subgroup of a material group was converting the wrong Modo material tag
- Initiating the plugin no longer flags the current scene as "changed", so if you exit Modo without making other changes, you will no longer be asked if you want to save the scene
- Added "Exporting Octane Scene...Pls Wait" message when exporting to OCS or ORBX
- IMPORTANT: Substantial reworking of the geometry loading system, so a mesh will only be loaded once, and shared between all the replicators and instances which use it. This has resulted in a faster load time, and reduces polygon count, but live updating is not working correctly yet. This has also fixed many issues related to ticking Incl Child Items on replicators. It also means replicators with a Group prototype now work.
- Plugin will now not load into any Modo build prior to Modo701 SP4.
- Changed the world of the warning given when you close the scene that is currently being rendered.
- Updated "About" graphic
- The progress dialog is now closed after you download the LiveDb materials via the plugin
- The shortcut downdrop to select the render camera has moved from the Octane Camera panel to the Octane Kernel panel, since changing the camera in the Camera panel was not updating the camera properties
- Saving default settings for the Kernel and Camera can now be done via a new button on the Kernel and Camera panels. I will implement the loading of these defaults in the next release. Defaults are saved to MyDocuments\Octane Defaults

Next on the list is a few animation improvements, proxy mesh support, loading of defaults and material conversion tweaks.

Thanks for all the feedback people are giving. Everything anyone says goes onto the list and gets looked at (priority given to bugs over enhancements).

Paul

[Dmi3ryd]

Many thanks for update!

[funk]

Thanks for the update Paul.

Small issue: The EXR savers are the wrong way around (this bug is also in the LW plugin so it must be an API bug)
eg. "Save Render > EXR" is saving a clamped EXR (LDR) while "Save Render > EXR Tonemapped" is saving a HDR


For some reason it's now taking longer to load/authenticate for me than earlier in the day. If I select "octanerender viewport" from the menu, I see the "Loading Octane, pls wait" roughly 10 seconds. Standalone is taking a little while to launch too. I thought that it doesnt need to authenticate with every single launch... pretty annoying but I guess there is nothing you can do about it.

[face_off]

Small issue: The EXR savers are the wrong way around (this bug is also in the LW plugin so it must be an API bug)
eg. "Save Render > EXR" is saving a clamped EXR (LDR) while "Save Render > EXR Tonemapped" is saving a HDR

I will report this to the Otoy team.

For some reason it's now taking longer to load/authenticate for me than earlier in the day. If I select "octanerender viewport" from the menu, I see the "Loading Octane, pls wait" roughly 10 seconds. Standalone is taking a little while to launch too. I thought that it doesnt need to authenticate with every single launch... pretty annoying but I guess there is nothing you can do about it.

This seems to vary depending on a number of factors - including the time of day. Right now - yes, I'm getting 10 sec authentications too. Suggest reporting slow authentications to FooZe - since he monitors the web bandwidth.

Paul

[funk]

For some reason it's now taking longer to load/authenticate for me than earlier in the day. If I select "octanerender viewport" from the menu, I see the "Loading Octane, pls wait" roughly 10 seconds. Standalone is taking a little while to launch too. I thought that it doesnt need to authenticate with every single launch... pretty annoying but I guess there is nothing you can do about it.

This seems to vary depending on a number of factors - including the time of day. Right now - yes, I'm getting 10 sec authentications too. Suggest reporting slow authentications to FooZe - since he monitors the web bandwidth.

Paul

I just noticed the standalone says "status: offline" so there are obviously some issues with their servers right now. The plugins dont report the status so you wouldnt know.

I tried running the livedb update in modo and was getting "unable to load category array" in the modo log

[riggles]

For some reason it's now taking longer to load/authenticate for me than earlier in the day. If I select "octanerender viewport" from the menu, I see the "Loading Octane, pls wait" roughly 10 seconds. Standalone is taking a little while to launch too. I thought that it doesnt need to authenticate with every single launch... pretty annoying but I guess there is nothing you can do about it.

As a workaround, if you're going to be closing and reopening MODO with any frequency, turn off your computer's wifi. The preview loads instantly when there's no internet connection.