OctaneRender™ Standalone v1.0 RC 1 [obsolete]

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Post Reply
User avatar
smicha
Licensed Customer
Posts: 3151
Joined: Wed Sep 21, 2011 4:13 pm
Location: Warsaw, Poland

abstrax wrote:
Elvissuperstar007 wrote:https://vimeo.com/52170540

I can not move the ball
You were running out of graphics memory:
out_of_memory.png
No. It's not about memory. Your GPU failed - look at the red font. I had this problem with my GTX 580 at standard voltage. I also had this problem 2 times so far with GTX 680. The only and best solution to avoid failure is to increase voltage (eg. in MSI Afterburner) by eg. 0.05V or more or lower down you clock a little. Right now I set voltage to max in afterburner and overclocked (watercooled) and never fails.
3090, Titan, Quadro, Xeon Scalable Supermicro, 768GB RAM; Sketchup Pro, Classical Architecture.
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
User avatar
abstrax
OctaneRender Team
Posts: 5508
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

smicha wrote: No. It's not about memory. Your GPU failed - look at the red font. I had this problem with my GTX 580 at standard voltage. I also had this problem 2 times so far with GTX 680. The only and best solution to avoid failure is to increase voltage (eg. in MSI Afterburner) by eg. 0.05V or more or lower down you clock a little. Right now I set voltage to max in afterburner and overclocked (watercooled) and never fails.
Sorry, I have to disagree. If you look at the "memory fill indicator" you can see a grey bar from the left and a red bar from the right. The grey bar shows the memory used by the Octane instance that you are looking at. The red bar shows memory that is "missing" from the available memory, i.e. unaccounted graphics memory. In the video you can see that the red bar is filling almost completely the indicator, i.e. almost all of the available graphics memory is used up by something Octane doesn't know.

There is two possible explanations for the memory usage: Either Octane is leaking GPU memory or some other application uses it. It could be another 3D application, the browser or even the operating systems. Many applications use the GPU for "graphics stuff" these days and eat into your GPU memory budget.

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
smicha
Licensed Customer
Posts: 3151
Joined: Wed Sep 21, 2011 4:13 pm
Location: Warsaw, Poland

Marcus,

If this is the case I truly apologize for messy information. I just wanted to say that in case of GPU failure I increase voltage to gain stability. And I think if gpu fails one need to restart octane or even boot system because - what happened to me - gpu goes into lower voltage state and never comes back to its nominal value, like 1.1V. So if you see "gpu failed" I doubt that objects in preview window will be active.

Kind regards,

Sebastian
3090, Titan, Quadro, Xeon Scalable Supermicro, 768GB RAM; Sketchup Pro, Classical Architecture.
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
User avatar
abstrax
OctaneRender Team
Posts: 5508
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

smicha wrote:Marcus,

If this is the case I truly apologize for messy information. I just wanted to say that in case of GPU failure I increase voltage to gain stability. And I think if gpu fails one need to restart octane or even boot system because - what happened to me - gpu goes into lower voltage state and never comes back to its nominal value, like 1.1V. So if you see "gpu failed" I doubt that objects in preview window will be active.

Kind regards,

Sebastian
Hey, no need to apologize and yes you are right, that unstable power supplies can spoil the fun with Octane a lot. And yes, if a GPU fails it will not become active again until you deactivate it and activate it again in the preferences. We are looking into automating this, but it's not trivial since after some GPU failures the GPU should stay off.

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
bepeg4d
Octane Guru
Posts: 10352
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy
Contact:

i've got a similar issue, the gpu failed and the ram bar full up with a red color ( it's impossible now not recognised a gpu failure, thanks). with big surprise, in the preferences there was a red allert about obsoleted nvidia drivers.
the strange thing is that before the failure of one gpu, the bar displayed 4 gpu correctly and i have made a lot of tests without any issues. :roll:
anyway i have updated the nvidia drivers from 285 to 301.42 and now all works smoothly ;)
ciao beppe
ashurao
Licensed Customer
Posts: 46
Joined: Mon Mar 07, 2011 11:06 pm

Hello,
Firstly, I am very happy to see this new version. Octane is near the end of the beta test. :D

I have the same problem that some users with textures.
I hope that my file can help you.

https://dl.dropbox.com/u/1082636/Test_octane.zip

Ashurao
Attachments
with v1.025 beta  2.58e
with v1.025 beta 2.58e
with v1.0 RC1
with v1.0 RC1
Mac Pro 2010 6 cores 3,33 - Mac OS 10.11.6 - 16Go - GTX 780 3Go and GT 640 4Go - Archicad 19 - Cinema 4D R17 Visualise - Octane Render V3
Zay
Licensed Customer
Posts: 1123
Joined: Sun Jan 17, 2010 2:53 am

Something wrong with the calculation from the .MTL file. Ns 1 = 1.0 roughness, then a really big jump, Ns 2 = 0.5 roughness. Couldn't this be made a more linear calculation like in the previous Octane versions?
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
User avatar
smicha
Licensed Customer
Posts: 3151
Joined: Wed Sep 21, 2011 4:13 pm
Location: Warsaw, Poland

ashurao wrote: I have the same problem that some users with textures.

I confirm. I have the same issue. As I remember well such "circles" occur when scaling is incorrect. But scaling of my objects is fine. My solution for now is by increasing rayepsilon value.
3090, Titan, Quadro, Xeon Scalable Supermicro, 768GB RAM; Sketchup Pro, Classical Architecture.
Custom alloy powder coated laser cut cases, Autodesk metal-sheet 3D modelling.
build-log http://render.otoy.com/forum/viewtopic.php?f=9&t=42540
ashurao
Licensed Customer
Posts: 46
Joined: Mon Mar 07, 2011 11:06 pm

smicha wrote:
ashurao wrote: I have the same problem that some users with textures.

I confirm. I have the same issue. As I remember well such "circles" occur when scaling is incorrect. But scaling of my objects is fine. My solution for now is by increasing rayepsilon value.
I tried this solution, but it did not change anything for me.
Mac Pro 2010 6 cores 3,33 - Mac OS 10.11.6 - 16Go - GTX 780 3Go and GT 640 4Go - Archicad 19 - Cinema 4D R17 Visualise - Octane Render V3
User avatar
Elvissuperstar007
Licensed Customer
Posts: 2506
Joined: Thu May 20, 2010 8:20 am
Location: Ukraine/Russia
Contact:

rendering speed will return the same?

58e - RC1
win 7 /64x C2Quad 6600 2.4/ Nvidia 9800 GX2 1gb 512 bit + Asus 480 GTX/ DDR2 8Gb / NVIDIA 460 GTX 2GB/2x NVIDIA 580 GTX 3GB
Page octane render " В Контакте " http://vkontakte.ru/club17913093
Post Reply

Return to “Development Build Releases”