I see..well I will have a good look at the threads already opened, sorry for this but as there 2 Octane pre-beta 2.42 one for 3.0 and 3.2 I though to mention...kubo wrote: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.
OctaneRender® pre-Beta 2.42 (win/mac) [OBSOLETE]
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.
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.
Last edited by justix on Thu Jan 27, 2011 6:28 pm, edited 1 time in total.
Win 7 64 | 2 X MSI AERO GtX 1070| Intel I7-6850K| 32 GB DDR4 RAM | Asus X99 II-A
I didn't mean to say you were doing anything wrong by reporting, quite the opposite, I meant that I wasn't sure about the actual explanation out of those two and that if you wanted to verify it it was somewhere written.
Cheers
Cheers
windows 7 x64 | 2xGTX570 (warming up the planet 1ºC at a time) | i7 920 | 12GB
It´s only an number bug in Octane...justix wrote:Hi guys, I'm just back to Octane after a long while and realised that I missed some pre-beta releasesnow 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
face
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
no offence takenkubo wrote:I didn't mean to say you were doing anything wrong by reporting, quite the opposite, I meant that I wasn't sure about the actual explanation out of those two and that if you wanted to verify it it was somewhere written.
Cheers

Win 7 64 | 2 X MSI AERO GtX 1070| Intel I7-6850K| 32 GB DDR4 RAM | Asus X99 II-A
Can anyone of the team give an indication as to when the Linux version of 2.4 will come out? Is it something that will happen in the next few days - weeks - months? I'm only nagging because they has barely been a word about it, and the New Year's competition is almost over. Yes, I have submitted an entry, but want to submit another one which represents too much work to fiddle with in my spare time (open, fiddle, save, close, open some time later - blast! everything is mixed up and some nodes won't connect, fiddle again, repeat, lather, rinse). Now you know why I'm bald.
Cheers.
Cheers.
Ubuntu 11.04, Q6600 2.4GHz 4-core, 4GB RAM, 8800GT & GTX 460 2GB, Blender 2.59, Octane 2.51
That's correct. The next version (pre-beta 2.43) will have it fixed. The problem was the weird way how NVIDIA reports CUDA versions. The number is 3020 and we thought it's meant to be something likeface wrote:It´s only an number bug in Octane...justix wrote:Hi guys, I'm just back to Octane after a long while and realised that I missed some pre-beta releasesnow 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
face
Code: Select all
printf("%.2f", version / 1000.f);
Code: Select all
printf("%d.%d", version / 1000, version % 100);

That's just for the interested reader...

For everyone else who doesn't program: Octane reports versions 3.00 and 3.02. 3.00 means CUDA 3.0 and 3.02 means CUDA 3.2.
And as I said before, it will be fixed with beta 2.43.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Could you please stop ranting? Is that too much to ask for? We said already several times, that we are working on a workaround. Is that so hard to understand? Code doesn't grow on trees or drops from the sky. You have to develop it and test it and that takes time.iljubicic wrote:Fix live account for the last time it is unusable. Try to leave an animation overnight! That's not a way to treat your customers.
Yes, problem is always on your server side!
We finished the changes today and the next release (pre-beta 2.43) will work this way: The authentication distinguishes between connection problems and incorrect credentials. If a connection problem occured, Octane automatically retries after 10 seconds. During those 10 seconds you can always cancel the loop and Octane will close. This loop is repeated until a connection has been established. If the authentication then fails due to incorrect credentials, the OctaneLive account dialog is shown (as before). If they are correct, Octane continues with loading the scene and rendering.
We hope that will solve the animation problems.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Sorry, I can't give you a specific date, but I expect it only to be a matter of days and yes the competition will be extended, due to the lack of a Linux version. I'm sorry about the delay. We are working on it.danilius wrote:Can anyone of the team give an indication as to when the Linux version of 2.4 will come out? Is it something that will happen in the next few days - weeks - months? I'm only nagging because they has barely been a word about it, and the New Year's competition is almost over. Yes, I have submitted an entry, but want to submit another one which represents too much work to fiddle with in my spare time (open, fiddle, save, close, open some time later - blast! everything is mixed up and some nodes won't connect, fiddle again, repeat, lather, rinse). Now you know why I'm bald.
Cheers.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
+abstrax wrote:[...We finished the changes today and the next release (pre-beta 2.43) will work this way: The authentication distinguishes between connection problems and incorrect credentials. If a connection problem occured, Octane automatically retries after 10 seconds. During those 10 seconds you can always cancel the loop and Octane will close. This loop is repeated until a connection has been established. If the authentication then fails due to incorrect credentials, the OctaneLive account dialog is shown (as before). If they are correct, Octane continues with loading the scene and rendering.
We hope that will solve the animation problems.
Cheers,
Marcus
" Sorry, I can't give you a specific date, but I expect it only to be a matter of days and yes the competition will be extended, due to the lack of a Linux version. I'm sorry about the delay. We are working on it."
great news!:))
i am really happy about that annnoucement,thought it would take month..
this sounds like a very promising workaround for the anim!!
also cant wait for linux.. but as long as the competition is extended, -relax take your time to make a clean linux build:)
THX:)
keep up
- Mint 10 64bit nvidia drv 260.19.29/cudatoolkit3.0 intel q6600, 4gbRAM, GTX470 1,2GB
- Mint 10 64bit/ Win7 64bit nvidia drv 260.19.29/cudatoolkit3.2 amd X6, 16gbRAM, 2x GTX580 3GB
->Octane 2.44/ Blender2.5x
- Mint 10 64bit/ Win7 64bit nvidia drv 260.19.29/cudatoolkit3.2 amd X6, 16gbRAM, 2x GTX580 3GB
->Octane 2.44/ Blender2.5x