Moderator: face_off
I also cannot reproduce this issue.if I change certain imager attributes such as exposure, gamma, highlight comp, vignetting, actually pretty much all the flags in the imager.. the octane render restarts.
Do you have a scene that you can send me which exhibits this issue? Then I can look into if it's a change to the plugin a fault, or Octane.- The long delay in loading the scene to the GPU's is still present.
face_off wrote:I also cannot reproduce this issue.if I change certain imager attributes such as exposure, gamma, highlight comp, vignetting, actually pretty much all the flags in the imager.. the octane render restarts.
Do you have a scene that you can send me which exhibits this issue? Then I can look into if it's a change to the plugin a fault, or Octane.- The long delay in loading the scene to the GPU's is still present.
Paul
Please find my scene at the link below. Meantime I'll try and trouble shoot this on my end.Thanks this worked for me.face_off wrote:I have re-updated the Windows installers at the top of this thread to fix the "ERROR: Detected octane.dll version does not match the plugin version.". Sorry for the error in the original versions.
Paul
I'm sorry - I don't know what this is referring to.Modo 10 with a simple torus and new config. Modo 901 is ok.
I will investigate this.Load times into Octane are still really really slow. In previous versions a few versions back loading into octane was going 5-10x faster.
Yes, you are running out of RAM and Octane is crashing due to this whilst saving the EXR. You will need more RAM, smaller resolution, or fewer passes. You can open the Task Manager and watch your memory to confirm this.Also any reason why Modo crashes from time to time when I save 16bit layered ex's with maybe 3-4 different passes? Upwards of 7000px it gets pretty iffy even if I still have plenty of memory left on the GPU.
That's entirely your call. You need to do the math to work out which is the better option for you. I've had my head in the code, so unsure of the thriftiest option.I want to buy 3.x version of the plugin, I don't have 2.x of it. Shall I wait until v3 will be officially released?
Yes, I confirm Funk's findings Dino. For me the scene loads just as quickly in the latest TEST build 3.0.15.106 as any of the older releases (about 1:25min). Could the absence of any image maps in the version we have be the problem? Or perhaps you hard disk is fired.Here are my load times:
modo 10.1 - octane 2.25.0.106.901 = 1m25s
modo 10.1 - octane 3.0.15.106.901 = 1m37s
So I'm not seeing a huge difference in v3.
I do see the render restarting when I change exposure though.
