Which speed do you get with 3.01?funk wrote:Im finding this release almost 2x slower than 2.58 on my setup
PT
3.03 = 0.29 Ms/sec
2.58e = 0.56 Ms/Sec
OctaneRender™ Standalone v1.0 beta3.03 [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.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- indexofrefraction
- Posts: 178
- Joined: Wed Jul 25, 2012 9:53 am
installed 3.03 + cuda driver 4.2.10 --> didnt work
cuda toolkit 4.2.9 --> didnt work
octane says :
cuda driver version 0.00, "cuda driver must be at least of version 4.2... cuda init failed. ... "
this is mac os x 10.7.5

cuda toolkit 4.2.9 --> didnt work
octane says :
cuda driver version 0.00, "cuda driver must be at least of version 4.2... cuda init failed. ... "
this is mac os x 10.7.5

Mac Pro (2012) 2x6 Core | 24GB | 1 x Geforce GTX580/3GB
hi,
i have got the same problem
with os x 10.7.5 you must install cuda drivers version 5.0.24 or 5.0.36.
cuda 4.2.10 works on 10.7.4 only and you need nvidia drivers 270.0 also
ciao beppe
i have got the same problem
with os x 10.7.5 you must install cuda drivers version 5.0.24 or 5.0.36.
cuda 4.2.10 works on 10.7.4 only and you need nvidia drivers 270.0 also

ciao beppe
- indexofrefraction
- Posts: 178
- Joined: Wed Jul 25, 2012 9:53 am
hey thanks that helped 
still no reload mesh function in 3.03?
i thought i read smth like that in one of the beta release notes

still no reload mesh function in 3.03?
i thought i read smth like that in one of the beta release notes
Mac Pro (2012) 2x6 Core | 24GB | 1 x Geforce GTX580/3GB
PTabstrax wrote:Which speed do you get with 3.01?funk wrote:Im finding this release almost 2x slower than 2.58 on my setup
PT
3.03 = 0.29 Ms/sec
2.58e = 0.56 Ms/Sec
2.57 = 0.71 Ms/Sec
2.58e = 0.56 Ms/Sec
2.59 = 0.43 Ms/Sec
3.01 = 0.31 Ms/sec
3.03 = 0.29 Ms/sec
It seems since the 3.x release it's about 2x slower on my gtx 285
UPDATE: I added more versions. It seems since 2.57, speeds have been dropping
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Ok, thanks for the feedback. What's happening here is, that in 2.58 and 2.59 we did some optimizations for Fermi/Kepler, which unfortunately reduced speed on old Tesla GPUs (compute model 1.x). And with beta 3.x we introduced instancing which also doesn't run too well on old Tesla GPUs. Since most of our customers are using Fermi/Kepler (which are many times faster than Tesla GPUs), we are not considering Tesla GPUs anymore when we add new features or work on performance.funk wrote:PTabstrax wrote:Which speed do you get with 3.01?funk wrote:Im finding this release almost 2x slower than 2.58 on my setup
PT
3.03 = 0.29 Ms/sec
2.58e = 0.56 Ms/Sec
2.57 = 0.71 Ms/Sec
2.58e = 0.56 Ms/Sec
2.59 = 0.43 Ms/Sec
3.01 = 0.31 Ms/sec
3.03 = 0.29 Ms/sec
It seems since the 3.x release it's about 2x slower on my gtx 285
UPDATE: I added more versions. It seems since 2.57, speeds have been dropping
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
There has been a reload button on the mesh node for ages? Or what exactly do you mean?indexofrefraction wrote:hey thanks that helped
still no reload mesh function in 3.03?
i thought i read smth like that in one of the beta release notes
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Yeah I understandabstrax wrote:
Ok, thanks for the feedback. What's happening here is, that in 2.58 and 2.59 we did some optimizations for Fermi/Kepler, which unfortunately reduced speed on old Tesla GPUs (compute model 1.x). And with beta 3.x we introduced instancing which also doesn't run too well on old Tesla GPUs. Since most of our customers are using Fermi/Kepler (which are many times faster than Tesla GPUs), we are not considering Tesla GPUs anymore when we add new features or work on performance.
Cheers,
Marcus

Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Hi Marcus ! Have you seen my little bug report in a post above (page2) ? About node input not working with two links in output ?
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
I found similar bug with nodes connections.ROUBAL wrote:In fact, the problem occurs each time there is more than one link connected in output of the obj node.
How to reproduce it:
- Open sample scene from tutorial "23 - Instancing Placement" (http://www.youtube.com/watch?v=5PsGuKA3dZY). Direct link is http://uploading.com/files/get/2b98ma6b/Tutorial.rar.
- After load, disconnect link from topmost "Placement" node output to some of "Placement" nodes input ("Geometry" pin), placed below, in first row of five nodes.
- Then try to restore this link...it can not be done.
AMD R7-2700/64Gb/RTX2080Ti 11Gb + RTX2080 8Gb/Win10 Pro x64/nV driver 451.67/Poser10, DS4.12, Blender2.79, Octane 4.05 Standalone
> Using RAM Disk with Octane <
> Using RAM Disk with Octane <