OTOY Forums

What does „future" mean? More like 3 months or more like 2 years?

I don't know - sorry. You will need to ask OTOY.

Paul

Hi Paul, I still get the error 700 memeory on octane render each time something is change into the modo scene and the rendering is active. is this just me. my hardware broken or other users talked about this too.

It's not a problem anyone else is having. Do you have a different card that you can try rendering with?

Paul

Hi Paul
I'm having the same problem as well on some scenes and it is proofing very difficult to track down and I have not found something yet that will give me the error 700 on a consistent basis. The weird thing is if I go back to version 2 of octane I get no error 700 messages or any error's for that matter.
On version 3 I find it's hit and miss but I can't seem to find what starts it and why. I have exported a scene that was giving me problems to standalone and it rendered fine. I have also taken the same scene and sometimes it gives me no error for quite a while ( 15 -20 minutes temps are around 65-68 degrees F on my cards) then if I start moving the camera around all over the place it will still be fine then I might try a material change then move the camera and bang error 700.
As I said I have yet to find something that triggers it that is repeatable so I have not bothered you with it as it's pointless at this point in time until I can get it to happen every time.
I also noticed that other people on the forums are sometimes getting this error to so I don't know if is a plugin error. I'm more inclined to think it's in octane itself.
I'm also of the opinion that it's not a hardware problem because as I said in version 2 I get no errors ever and I find that version 2 also seems to run the cards harder as they get hotter by about 1 - 2 degrees on version 2.
Keith

I'm having the same problem as well on some scenes and it is proofing very difficult to track down and I have not found something yet that will give me the error 700 on a consistent basis. The weird thing is if I go back to version 2 of octane I get no error 700 messages or any error's for that matter.
On version 3 I find it's hit and miss but I can't seem to find what starts it and why. I have exported a scene that was giving me problems to standalone and it rendered fine. I have also taken the same scene and sometimes it gives me no error for quite a while ( 15 -20 minutes temps are around 65-68 degrees F on my cards) then if I start moving the camera around all over the place it will still be fine then I might try a material change then move the camera and bang error 700.
As I said I have yet to find something that triggers it that is repeatable so I have not bothered you with it as it's pointless at this point in time until I can get it to happen every time.
I also noticed that other people on the forums are sometimes getting this error to so I don't know if is a plugin error. I'm more inclined to think it's in octane itself.
I'm also of the opinion that it's not a hardware problem because as I said in version 2 I get no errors ever and I find that version 2 also seems to run the cards harder as they get hotter by about 1 - 2 degrees on version 2.

Keith - if you have a scene which produces this problem, pls send it to me and I will take a look.

Paul

Following is another pre-release (Windows version) of the next version of the plugin.

3.4.3.114
- Compiled with Octane 3.04.3
- Fixed issue where setting the Border Mode with Black Color or Clamp Value was not working after a scene refresh
- octane.SaveAnimation now uses a new Octane API library to export the scene, which should work quicker, and also support strand hair and volumes
- Added Direct Lighting Kernel AO Texture as per Octane 3.04. Drag the property name onto the schematic and attach an RGB Color node to use this
- Added Render Layer Mode combobox to the Render Layer tab as per Octane 3.04
- Added additional Falloff Texture node pins as per Octane 3.04
- Enabling/Disabling render passes now no longer restart the render when viewing the beauty pass
- Resolved issue where vertex motion blur was not working when using the octane.saveAnimation command
- Fixed issue where the User For Tonemap setting was not being set in certain situations

https://render.otoy.com/customerdownloa ... _64bit.exe

Paul

Hi Paul
As soon as I get a scene where the error is more consistent I will send it to you.
Thanks
Keith

lightboy wrote:Hi Paul
As soon as I get a scene where the error is more consistent I will send it to you.
Thanks
Keith

Hi Paul, this is Vlad, for me the problem is caused by the HDRLight Studio 4 plugin image update, I do not know for the lightboy.

Error 700 is not about I said, is about any app that when I open and requiers vram, makes the current octane render get the error 700. I think this is because o new cuda 7.5 or 8 implementation for pascal, that is not supported on the pre-pascal cards. Basically if I open an other app that requests vram, photoshop, substance painter, or if I cahnge the lighing in the hdrlight studio 4, the error 700 for the memory appears, it does not look like is scene dependent.

I think we need a build history for the plug-in because with the last 3-4 plugins I am unproductive, so umproductive that I was thiking to switch back to modo render.

I also think is a problem of how octane/octane plugin is handling textures today, any changes of materials gives me the cuda 700 error

Hi Paul, I have 2 scenes open and I am trying to copy one material from one to the other. I have used the copy material button on the override but it give me an error "Error loading material from clipboard", even if I try paste back into same scene I copied from.

I might be missing a step, what am i doing wrong?

thanks.

Hi Paul, since error 700 for memory is not about pointing fingers, I tested the scenes for one day on the latest version of octane 2 and I got no crash or cuda error.

Cheers,
Vlad

PS: I was worried for my gpus.