OTOY Forums

face_off wrote:I just did a quick test on a blank scene @ 5000x5000 pixels, and it took 8 secs for PNG 8 bit and 16 secs for PNG 16 bit. So sounds like you might be running low on RAM?

Photoshop requires a long time to save this PNGs too. It needs more than 4 minutes to save a frame in PNG from Photoshop.
So, it’s perhaps a problem in OS X and not in Octane or Photoshop.

Photoshop requires a long time to save this PNGs too. It needs more than 4 minutes to save a frame in PNG from Photoshop.
So, it’s perhaps a problem in OS X and not in Octane or Photoshop.

The test results above were on OSX - so the problem seems to be specific to your system. My guess is that it's insufficient memory, meaning excessive disk caching.

Paul

face_off wrote:The test results above were on OSX - so the problem seems to be specific to your system. My guess is that it's insufficient memory, meaning excessive disk caching.

No, even on a fresh restarted Mac with only Photoshop running and a lot of free memory does the save running slow. All other formats like GByte large PSDs are saving very fast. Only this kind of PNG do have this problem.
So this is definitely not a memory problem. This seems to be a bug in Mac OS X.

I this would be a memory issue, then it should run fast with a lot of free memory. But it don’t.

Uhlhorn - with regards to your kernel panics - as smicha says, unfortunately this sounds like a faulty graphics card.

Paul

Uhlhorn - with regards to your kernel panics - as smicha says, unfortunately this sounds like a faulty graphics card.

Then it is faulty since 2013 and only Octane was able to uncover it.

hi Paul,
I have a bug to report.

The command octane.selectCamera formPopover does no open the popover settings. It only does once after the installation, Modo 10.

Cheers,
Vlad

v1adut wrote:hi Paul,
I have a bug to report.

The command octane.selectCamera formPopover does no open the popover settings. It only does once after the installation, Modo 10.

Cheers,
Vlad

I think I found the problem answer. I locked the modo camera, so it can stay in place for the render, and because of this all its parameters locked, including octane render, this is why the popover didn;t appear. is there a work around to have the modo camera locked, and the popover appear. Also, Paul how about instead of pop over, we will get side menus on the property list as modo and vray has implemented.

Hmm … this version is ignoring the GPU active setting. I set the internal GPU to inactive, but the plugin is using it.

Operating System: macOS 10.11.6 (15G1004)
RAM: 32 GB
Internal GPU: NVIDIA GeForce GTX 680MX 2048 MB (iMac 27" late 2012)
eGPU: GeForce GTX 980 Ti (compute model 5.2) (eGPU)
Driver: NVIDIA Web Driver 346.03.15f03
Modo: 902 SP3
Octane plugin: 3.3.3.112.901

I think I found the problem answer. I locked the modo camera, so it can stay in place for the render, and because of this all its parameters locked, including octane render, this is why the popover didn;t appear. is there a work around to have the modo camera locked, and the popover appear.

This looks like a Modo limitation. I have a work-around which will be in the next release. You can also lock just the camera position, which will fix your immediate problem.

Also, Paul how about instead of pop over, we will get side menus on the property list as modo and vray has implemented.

The first release of the plugin had the camera settings in the tab side menus, but all the beta testers wanted it as a separate panel - since there was so much information in there, so that's why the camera info is in a panel - which I think works better than a tab.

Paul

Hmm … this version is ignoring the GPU active setting. I set the internal GPU to inactive, but the plugin is using it.

Operating System: macOS 10.11.6 (15G1004)
RAM: 32 GB
Internal GPU: NVIDIA GeForce GTX 680MX 2048 MB (iMac 27" late 2012)
eGPU: GeForce GTX 980 Ti (compute model 5.2) (eGPU)
Driver: NVIDIA Web Driver 346.03.15f03
Modo: 902 SP3
Octane plugin: 3.3.3.112.901

Did you click the "Apply" button?

Paul