OTOY Forums

Rick - did you upgrade your Cuda driver to 6.5?

Paul

did you upgrade your Cuda driver to 6.5

Yes, CUDA and NVIDIA are up to date.

I am moving over to Windows to give this a go.

./rrb

rrbarb wrote:

did you upgrade your Cuda driver to 6.5

Yes, CUDA and NVIDIA are up to date.

I am moving over to Windows to give this a go.

./rrb

What exactly is the problem? The memory is reported incorrectly? Could you please check if the problem exists in the Standalone, too?

You also wrote about locking up. What did you do to make it lock up? Does it happen in Standalone, too?

Thanks,
Marcus

What did you do to make it lock up? Does it happen in Standalone, too?

Oh nothing really, he seems to do it on his own with no help:)

If I click anything, for example, to change the number of samples.

All drivers and such are as required, have been removed, reinstalled.
Cards removed and reseated. Permissions fixed, and all other Mac voodo, and death grips ect. Tried on two machines.

But on either of these machines, I roll back to 2.12, and zippityDooDa it all works.

./ rrb

rrbarb wrote:

What did you do to make it lock up? Does it happen in Standalone, too?

Oh nothing really, he seems to do it on his own with no help:)

If I click anything, for example, to change the number of samples.

All drivers and such are as required, have been removed, reinstalled.
Cards removed and reseated. Permissions fixed, and all other Mac voodo, and death grips ect. Tried on two machines.

But on either of these machines, I roll back to 2.12, and zippityDooDa it all works.

./ rrb

What about the Standalone? Do you have the same problem there?

That is StandAlone, from modo he runs, degraded, but runs and no lockups
./ rrb

rrbarb wrote:That is StandAlone, from modo he runs, degraded, but runs and no lockups
./ rrb

Could you try to switch to the software viewport (see http://render.otoy.com/forum/viewtopic. ... 12#p215712).

Thanks again,
Marcus

Could you try to switch to the software viewport (

Will do, first thing in the morning.
./ rrb

Could you try to switch to the software viewport

Yes, this and: CUDA driver 6.5.33 did the trick. All is well. Both GPU's recognized, VRAM reporting correctly.

All this time I was on CUDA 6.5- however it was 6.5.25. Just yesterday did NVIDIA post 6.5.33

Besides the viewport bug, I think the version of 6.5 was more the issue here.

If Otoy has an inside track to drivers, could you post those up along side the releases that absolutely require that exact .xx version.
Or maybe just post the full driver designation, xx.xx.xx?

As always, Thanks to everyone who makes this product Rock!

./rrb

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

2.16.0.47
- Compiled with Octane 2.16 (see the Octane Standalone 2.16 release notes for details on this release)
- Daylight illumination power has been re-calibrated (pls see Octane Standalone 2.16 release notes for details). You may need to tweak the Daylight power to compensate for this change
- Scene load errors now pop an Octane error (in the Octane Log) rather than a Modo Event Log entry. If this causes too many pop-ups, pls let me know.
- Implemented a number of code changes to prepare for Octane 2.20

2.15.0.46
- Compiled with Octane 2.15
- Added option to import a material from the Octane Standalone LocalDb (use the command "octane.importLocalDb")
- Added support for Modo "Front Projection" mapping. This assumes the Render Camera is the Projection Camera
- Various additions/enhancements to emitters, including addition of "Surface Brightness" and "Cast Illumination" pin. See Octane 2.15 Standalone release notes for details. IMPORTANT: Modo Materials with Luminous Intensities > 0 will convert to an Octane diffuse emitter with Surface Brightness enabled
- Removed ISO and FStop Imager pins. See Octane 2.15 Standalone release notes for details. Scenes saved with plugin versions prior to 2.15.0.37 will NOT have the exposure converted to the new scale, so will need manual adjustment. Your default rendertarget "exposure" setting will need to be adjusted too.
- IMPORTANT: The above change means the default Daylight Power of 1 will be too bright - this will be rectified in the next release
- Added support for Texture Locator U Tile Offset and V Tile Offset for the UV Map projection type
- Added support for the Modo Constant Shader Tree item. The supported Effects are "Diffuse Color", "Diffuse Amount", "Transparency Amount", "Transparency Color", "Luminous Color"
- Added support for the Layer Mask effect. This only works when the Layer Mask is applied to a Image in the Shader Tree, and only works with Constant and Image nodes above the Layer Mask with an effect of Diffuse Color

Paul