Will the 3DS max plugin demo work with the standalone 2.0 demo? I'd like to test it but I don't want to mess up my existing 1.5 max plugin. I suspect speeds would be the same regardless if it's the standalone or plugin version so I'm not sure if its even worth to test.
Why v2.0 so slow ?
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Please post only in English in this subforum. For alternate language discussion please go here http://render.otoy.com/forum/viewforum.php?f=18
Yes all of them were running. You can see in the lower right corner of the display port
. I agree it seems like too much of a decrease. I haven't tested any other projects yet but I will because that's a pretty significant issue IMO.
Will the 3DS max plugin demo work with the standalone 2.0 demo? I'd like to test it but I don't want to mess up my existing 1.5 max plugin. I suspect speeds would be the same regardless if it's the standalone or plugin version so I'm not sure if its even worth to test.
Will the 3DS max plugin demo work with the standalone 2.0 demo? I'd like to test it but I don't want to mess up my existing 1.5 max plugin. I suspect speeds would be the same regardless if it's the standalone or plugin version so I'm not sure if its even worth to test.
900D | 4770k | ASUS Maximus VI Extreme | 2x RTX 2080 Ti's | 32GB RAM | AX1200i | Win 7 64bit | Autodesk Inventor | 3DS Max | Blender | Mudbox | Alias
Please make sure that SLI is disabled. And could you send us the scene? Thank you very much in advance.haknslash wrote:Yea I'm seeing huge differences in speed from 1.5 to 2.0 (demo). I was going to upgrade because of all the nice features but if it's going to impact my render times then I think I'm just going to hold out for a while to seee how 2.0 improves for speed. Kinda bummed TBH
Octane Render 1.50 (standalone)
336.43 Ms/sec @ 8 seconds (0:24 seconds est. time to reach convergence of 16,000 s/px)
...
Octane Render 2.00 (demo)
51.10 Ms/sec @ 10 seconds (3:09 est. time to reach convergence of 16,000 s/px)
...
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
mjk wrote:Dear Octane Dev-Team,
I am utterly indignant!
When I bought Octane..... yadda yadda, ranty bollocks

( PC ) i7 5960x octal 4.5ghz / 64GB / 2x Titan X 12GB / 1x 780 6GB - ( Laptop ) i7 4790k 4ghz / 32GB / 980M 8GB - Octane CD4 2.x / C4DR16.x / win 8.x
I just realized, that in the demo version the "use priority" option (see File -> Preferences... -> CUDA Devices) is enabled by default and according to your screenshots the render priority in your scene seems to be set to "low", which would explain at least some of the slow down.haknslash wrote:Yea I'm seeing huge differences in speed from 1.5 to 2.0 (demo). I was going to upgrade because of all the nice features but if it's going to impact my render times then I think I'm just going to hold out for a while to seee how 2.0 improves for speed. Kinda bummed TBH
Octane Render 1.50 (standalone)
336.43 Ms/sec @ 8 seconds (0:24 seconds est. time to reach convergence of 16,000 s/px)
...
Octane Render 2.00 (demo)
51.10 Ms/sec @ 10 seconds (3:09 est. time to reach convergence of 16,000 s/px)
...
Could you set the "use priority" option and render priority to the same settings as in your 1.5 version and try again?
Sorry, that I didn't think of it earlier...
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Yes, when I tried 2.0 with the demo and unchecked "priority" I got the same ms in benchmark as with1.16!
I can't imagine the demo is faster than standalone
I can't imagine the demo is faster than standalone
Octane 2022.1.1 nv535.98
x201t - gtx580 - egpu ec
Dell G5 - 16GB - dgpu GTX1060 - TB3 egpu @ 1060 / RTX 4090
Octane Render experiments - ♩ ♪ ♫ ♬
x201t - gtx580 - egpu ec
Dell G5 - 16GB - dgpu GTX1060 - TB3 egpu @ 1060 / RTX 4090
Octane Render experiments - ♩ ♪ ♫ ♬
- RealityFox

- Posts: 273
- Joined: Sat May 05, 2012 1:43 pm
I'm slightly disappointed in this, hopefully this speed decrease becomes less and less as future updates happen. However the features are a great asset. Hopefully particle/volumetric rendering will be in 3.0. And hopefully without the speed losses 
I have checked and it is at the defaul use priority setting. I'm not sure why it shows otherwise but the setting hasn't been changed and everything is "out of the box default". I am almost positive use priority is selected on 1.50 but I will double check when I'm back in the office. SLI has always been disabled unless 2.0 upon launching is changing my Nvidia Control settings somehow and then reverting when I launch 1.50 (I don't think this is happening). I can send you the file Monday next week for testing. Thanks for looking into it.abstrax wrote:I just realized, that in the demo version the "use priority" option (see File -> Preferences... -> CUDA Devices) is enabled by default and according to your screenshots the render priority in your scene seems to be set to "low", which would explain at least some of the slow down.haknslash wrote:Yea I'm seeing huge differences in speed from 1.5 to 2.0 (demo). I was going to upgrade because of all the nice features but if it's going to impact my render times then I think I'm just going to hold out for a while to seee how 2.0 improves for speed. Kinda bummed TBH
Octane Render 1.50 (standalone)
336.43 Ms/sec @ 8 seconds (0:24 seconds est. time to reach convergence of 16,000 s/px)
...
Octane Render 2.00 (demo)
51.10 Ms/sec @ 10 seconds (3:09 est. time to reach convergence of 16,000 s/px)
...
Could you set the "use priority" option and render priority to the same settings as in your 1.5 version and try again?
Sorry, that I didn't think of it earlier...
900D | 4770k | ASUS Maximus VI Extreme | 2x RTX 2080 Ti's | 32GB RAM | AX1200i | Win 7 64bit | Autodesk Inventor | 3DS Max | Blender | Mudbox | Alias
The demo version doesn't load or save preferences, so your 1.5 prefs are ignored. It's default is: All GPUs use priority and the default render priority is "low". Earlier today I uploaded a new demo build, where the default render priority is "high". Let me know how that goes.haknslash wrote:I have checked and it is at the defaul use priority setting. I'm not sure why it shows otherwise but the setting hasn't been changed and everything is "out of the box default". SLI has always been disabled unless 2.0 upon launching is changing my Nvidia Control settings somehow and then reverting when I launch 1.50 (I don't think this is happening). I can send you the file Monday next week for testing. Thanks for looking into it.
Thanks,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
