OctaneRender® pre-Beta 2.42 (win/mac) [OBSOLETE]

[radiance]

Abstrax

No, the frame in question was cooking.I am running this new windows X64 version with the latest WHQL Nvidia driver.It was about 15 mins into the cook when it just stopped working.

I then of course thought it was my machine and tried to restart.Of course that is when i discovered that although my internet connection was ok (I'm running 10MB/sec broadband)

Octane would not connect for sometime.Got back onto the message board a little later to discover you had a DDOS attack.

Hey, Octane only requires a connection when you start the engine, if it freezes while rendering it's not due to octane live, most likely a hardware or heat issue.
You can start octane, start rendering, pull your network cable and do whatever you want for as long you want except: restart the engine by changing resolution, use livedb, change your preferences in the prefs panel.

Radiance

[radiance]

quoted: "* We are developing a new secure solution to enable mobile use of OctaneRender® v1.0+, without the requirement of an internet connection."

hope this announcement out of the octane live faq, point five: http://www.refractivesoftware.com/forum ... =24&t=4069 is still vailid??
this announcement changed a lot in my previous decisions about using octane, since there where octane live.

theres is no need for hurry atm but pls dont forget about that promis..

thx and keep on

I had the same feeling, even I wrote an e-mail to the Refractive Software time ago before I bought Octane Render asking for the security method cause I felt it wasn't right to have an internet connection and all the dependency from a thirds persons, and what did change my mind was the same forum thread, but right now you are saying you're not going to change the security system, so I found this to not be fair with your costumers, we are to pirates, we are YOUR costumers and we deserve a friendly software.

We never said we dropped this plan, you probably misunderstood,
On the other hand, i have not had much luck finding the right solution, so it won't be here "tomorrow".

Radiance

[Cronicash]

Love the update, "nice work"

[Faizol]

We never said we dropped this plan, you probably misunderstood,
On the other hand, i have not had much luck finding the right solution, so it won't be here "tomorrow".

Radiance

The users understand that the solution won't be here tomorrow. And as long as the final product won't have a dependency from a third party to operate on the software, then it should be fine. Further investigations on licensing schemes can still be done in the mean time. I wouldn't want Octane to be pirated and in turn jeopardizing Refractive's income that future Octane development after version 1.0 will have to be stopped. Many of the users here would want to see how Octane version 2.0 (and more) will handle subsurface, volumetrics and others. But at the same time, freedom to use the software for the legit users, anywhere and at anytime, is also a very important matter.

I guess it will take some time before a good solution can be found.

[Jaberwocky]

Abstrax

No, the frame in question was cooking.I am running this new windows X64 version with the latest WHQL Nvidia driver.It was about 15 mins into the cook when it just stopped working.

I then of course thought it was my machine and tried to restart.Of course that is when i discovered that although my internet connection was ok (I'm running 10MB/sec broadband)

Octane would not connect for sometime.Got back onto the message board a little later to discover you had a DDOS attack.

Hey, Octane only requires a connection when you start the engine, if it freezes while rendering it's not due to octane live, most likely a hardware or heat issue.
You can start octane, start rendering, pull your network cable and do whatever you want for as long you want except: restart the engine by changing resolution, use livedb, change your preferences in the prefs panel.

Radiance

Yep your right.Just tried it.

That's put my mind at rest for now

Cheers.

[Jaberwocky]

Hello everybody

I used to work on a scene (OBJ.) with version 2.3 V5. The GPU memory read as 638.6/997 MB. If I open the same scene with version 2.42, the GPU memory reads as 743.9/997 MB and I only get a black screen in the render viewport (on my system, any scene over 700 MB either freezes or crashes Octane, or gives me a black screen in render viewport). How can it be explained that the same scene takes more GPU memory with the newer version? I did update to the latest NVidia driver for my FX 3800 card. Thanks

One thing you need to think about is that if you are using windows 7 at say 1920 x 1200 res then this takes up 177MB of Video card memory before you start using Octane.To see for yourself download the latest V2.0 of MSI afterburner and switch on Card monitoring.This info is not reported in Octane which states that it sees 993Mb free on a 1GB card.This may be the reason for your problem.If This version of Octane is indeed using more of the cards memory then it may have taken you over the limit now.Not sure i think we may need a comment from refractive to make sure.

[kubo]

Hello everybody

I used to work on a scene (OBJ.) with version 2.3 V5. The GPU memory read as 638.6/997 MB. If I open the same scene with version 2.42, the GPU memory reads as 743.9/997 MB and I only get a black screen in the render viewport (on my system, any scene over 700 MB either freezes or crashes Octane, or gives me a black screen in render viewport). How can it be explained that the same scene takes more GPU memory with the newer version? I did update to the latest NVidia driver for my FX 3800 card. Thanks

One thing you need to think about is that if you are using windows 7 at say 1920 x 1200 res then this takes up 177MB of Video card memory before you start using Octane.To see for yourself download the latest V2.0 of MSI afterburner and switch on Card monitoring.This info is not reported in Octane which states that it sees 993Mb free on a 1GB card.This may be the reason for your problem.If This version of Octane is indeed using more of the cards memory then it may have taken you over the limit now.Not sure i think we may need a comment from refractive to make sure.

Could it be that in 2.4 you were using alpha background, I'm not sure but that could be eating extra Ram. Also what Jaberwocky said is true, if you are rendering with the display gpu there is some vRAM needed to use as display, also there is some other app that use de vram of your gpu as the latest 3dmax and such. The more you use the lest responsive your sistem would be

[justix]

Hi guys, I'm just back to Octane after a long while and realised that I missed some pre-beta releases now I did download the pre-Beta 2.42 Cuda 3.2 version as suggested for the 4XX series (470) and update the card drivers to 266.58 which shows me that I have a cuda 3.2.1 driver component BUT if I check the Octane cuda device in my preferences it shows only cuda 3.02 ?? any advice?

thanks

[kubo]

justix that's what it should show. I'm not sure if either is the actual nvidia internal number for 3.2 or it's a number buggy of octane but it's been explain in this or in 2.41 thread, check it out.

[superAl]

Hello everybody

I used to work on a scene (OBJ.) with version 2.3 V5. The GPU memory read as 638.6/997 MB. If I open the same scene with version 2.42, the GPU memory reads as 743.9/997 MB and I only get a black screen in the render viewport (on my system, any scene over 700 MB either freezes or crashes Octane, or gives me a black screen in render viewport). How can it be explained that the same scene takes more GPU memory with the newer version? I did update to the latest NVidia driver for my FX 3800 card. Thanks

One thing you need to think about is that if you are using windows 7 at say 1920 x 1200 res then this takes up 177MB of Video card memory before you start using Octane.To see for yourself download the latest V2.0 of MSI afterburner and switch on Card monitoring.This info is not reported in Octane which states that it sees 993Mb free on a 1GB card.This may be the reason for your problem.If This version of Octane is indeed using more of the cards memory then it may have taken you over the limit now.Not sure i think we may need a comment from refractive to make sure.

Could it be that in 2.4 you were using alpha background, I'm not sure but that could be eating extra Ram. Also what Jaberwocky said is true, if you are rendering with the display gpu there is some vRAM needed to use as display, also there is some other app that use de vram of your gpu as the latest 3dmax and such. The more you use the lest responsive your sistem would be

Thanks for your answers. My setup demands a large amount of GPU memory. I have a dual monitor setup, one being a 27-inch monitor at 2560x1280 resolution , the other one a 22-inch monitor at 1980x1080. That surely explains that I only have 700 GB of available GPU memory. What I do find strange in my case is that I open the exact same obj file, and it takes more GPU memory in the latest Octane version compared to the previous one. Could any of you guys try the same thing on your systems ?