OctaneRender 3 for Modo [OBSOLETE]

[face_off]

Hi Paul I'm also getting a ton of crashes, almost everytime I change 'render camera' and refresh octane. Would it be possible to have a peek at my scene and see if you can find the issue?

Dino - that scene is not crashing for me. Is it possible you are running out of VRAM - do you have OutOfCore Textures enabled? Can you post your System->Preferences->Octane panel settings pls?

Have you considered upgrading to the latest Modo version?

Paul

[MrFurious]

Thanks Paul.

I had considered upgrading to Modo 10.2, but after having a good look there wasn't much there for an ArchViz guy so I decided to skip this version. Will Modo Version 10.2 offer any more stability with the Octane plugin? I have to assume so since you mentioned it.

Vram looks good to me, plenty of overhead here:

Not using out of core tex:

Here are my prefs settings:

Oh, I almost forgot to mention, I'm trying the latest test release due to the latest stable release being not-so-stable. So far, far fewer crashes, but on the occasion it does crash, it totally crashes and does not show the standard Modo crash reporter dialog.. it just closes and sends me back to the desktop.

You mentioned you weren't able to reproduce the crash. I have to mention it does not always crash, and it's intermittent.. but I can replicate the issue just that sometimes it takes longer than other times.

Try this: fire up the octane render window, then change the render camera and while the octane render is still going, refresh the octane window. go back and forth between cameras a few times and it should crash.

Cheers,
Dino.

[face_off]

Dino - have you tried the latest pre-release 3.06 test build I posted latest week? You are on x.x.x.115, and that pre-release is x.x.x.117 - so 2 version newer, which contains some bug fixes (nothing as drastic as fixing a crash, but you never know....).

I am also missing the textures and a Lightwave file with that sample scene, so that may be the difference between what we are seeing.

Paul

[face_off]

Following is a pre-release (Modo901/10 Windows) of the next version of the plugin. It contains some big changes - so posting this new release for feedback. This release should be stable, although Octane 3.06 may change a little before becoming final.

3.6.2.117 PRE-RELEASE
- Compiled with Octane 3.06 TEST 3 (includes Adaptive Sampling, new Bokeh pins, new Pano Camera DOF pins, new Add/Subtract/Comparison/Triplanar texture nodes, and Normal and Displacement mapping enhancements, new Triplanar projection node)
- Resolved issue with some non-Mesh item geometry meshes loading twice
- Modo Render Region channel modifiers are now evaluated when setting the Octane render region
- The following Imager defaults have changed to better match Modo - Response now defaults to Linear, Gamma now defaults to 2.2 and Vignetting now defaults to 0
- VERY IMPORTANT: The plugin will now correctly convert the Modo scene and image ocio colorspace settings to the Octane Image Gamma values. This means if you have saved scenes with the 8 and 16 bit colorspace at a setting other than Linear (as per the manual), then Image gamma values will change when you render with this release of the plugin. At this stage sRGB, sRGBf, rec709, gamma2.2 are converted to a 2.2 gamma, gamma1.8 is converted to a 1.8 gamma and everything else remains linear/no correction (1.0 gamma). The Octane Environment IBL does NOT take into account the Modo ocio settings.
- Changed the default values for the Camera settings Use Modo Film Offset, Use Modo Clipping Distance, Use Modo Focus Distance and Use Modo F-Stop for Aperture to ON
- The default Environment is now the Texture Environment, rather than Daylight Environment, and Use Modo Environment Power and Rotation properties are now defaulted to ON
- Fixed issue where the octane.saveAnimation command was not exporting animated Environment channels
- Modo Area Lights when do NOT have a mesh item (ie. Octane emitter) attached to them will now convert to an Octane emitter automatically. The emitter geometry will automatically be created, and the Octane material will be created from the Modo area light material. You can still use the Create Octane Emitter function to override this default behavior
- Revamped the proxy system so animations inside ABC nodes in an OCS/ORBX will render correctly.

LINK REMOVED - New test release available below.

Paul

[MrFurious]

Ok.... I re-installed the latest stable release again (3.5.0.115.901), launched up Modo 901 with a clean config file- all back to default. Fire up the octane preview window....

boom, crash. Seems to happen every time.

Here's the updated scene file: http://www.mediafire.com/file/jlskju35s ... test_2.zip

Cheers,
Dino.



Intel i7 Single CPU System
32GB Ram
Windows 7 64bit
Modo version: 901 Service Pack 3 108604
Octane for Modo version: 3.5.0.115.901
GFX Card: 3x Geforce GTX980ti
Nvidia Driver version: 378.78-desktop-win8-win7-64bit-international-whql

[MrFurious]

Bugger it.. switched to 3.6.2.117 PRE-RELEASE and so far much more stable than the latest final release.

I was just apprehensive switching to a pre-release mid way through a job.. but so far so good.

Cheers,
Dino.

[MildMustard]

I think my heart just skipped a beat.. Thanks for making Area Lights work like this now!! This speeds up my workflow already. Really awesome
Will you be adding these changes over to Photometric and Point?

[lightboy]

Hi Paul
I get this error every time I do view port navigation with octane when it asks me to "transfer the octane camera position to the modo camera?" and I say yes
It's been happening for a few versions now and I keep forgetting to mention it.

camera error.JPG (14.62 KiB) Viewed 4214 times

[Greggers]

Im looking forward to this test release for OS X paul. when will it be gracing us

[rrbarb]

Thanks Paul - keep those Keys coming in octane.saveAnimation.

./rrb