Page 4 of 16
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 5:05 pm
by aoktar
ron908 wrote:There appears to be a problem when "Render Perfect" is checked on a Sphere object - Octane will just sit there and never start the render. The live viewer works fine though, it's just the actual render that does not start.
it's working for me. any thing else on object?
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 5:57 pm
by ChrisVis
Hi aoktar,
first thank you for the fast development of the C4D plugin! I am really looking forward to use it in my upcoming work! It will speed up my workflow for shure.
But at the moment it doesn`t work for me at all... purchased it yesterday and didn`t get it right yet, I even updated CUDA drivers.
I get the same CUDA error as posted before, when starting C4D (R13, 64bit, Win 7, NVDIA 314.22 driver, C4D plugin 0.3.4)
"OCTANE API ERROR:CUDA device 0: Failed to find a CUDA binary matching compute model 2.0"
I can activate the plugin with my activation data in C4D, but nothing happens nor the rendering starts. Device 0 turns into GTX580, after restarting the plugin in C4D, but nothing happens when checking or unchecking the box and hitting the renderbutton in the plugin. I thought it is a problem of my multi-GPU rig (tried yesterday with every 8 GPUs active), but the problem also is there, when my expansion box is off and only the internal GTX580 is active.
The standalone 1.1 works fine, with one GTX and also with all 8 GPUs active.
I have a german C4D version, but changed to english and tried again with the same results.
So where might be the problem?
Could you send me the 0.3. plugin version or make it downloadable again, so I can check, if this one is working?
Best regard,
ChrisVis
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 8:22 pm
by aoktar
ChrisVis wrote:Hi aoktar,
first thank you for the fast development of the C4D plugin! I am really looking forward to use it in my upcoming work! It will speed up my workflow for shure.
But at the moment it doesn`t work for me at all... purchased it yesterday and didn`t get it right yet, I even updated CUDA drivers.
I get the same CUDA error as posted before, when starting C4D (R13, 64bit, Win 7, NVDIA 314.22 driver, C4D plugin 0.3.4)
"OCTANE API ERROR:CUDA device 0: Failed to find a CUDA binary matching compute model 2.0"
I can activate the plugin with my activation data in C4D, but nothing happens nor the rendering starts. Device 0 turns into GTX580, after restarting the plugin in C4D, but nothing happens when checking or unchecking the box and hitting the renderbutton in the plugin. I thought it is a problem of my multi-GPU rig (tried yesterday with every 8 GPUs active), but the problem also is there, when my expansion box is off and only the internal GTX580 is active.
The standalone 1.1 works fine, with one GTX and also with all 8 GPUs active.
I have a german C4D version, but changed to english and tried again with the same results.
So where might be the problem?
Could you send me the 0.3. plugin version or make it downloadable again, so I can check, if this one is working?
Best regard,
ChrisVis
i have sended, i thinking storage changing causes weird errors
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 9:08 pm
by NVN
Hi aoktar!
my cinema
r13 crased every time if i have only 2 Textures on one Objekt with a polygonselection.
A error comes with "c4dOctane.cdl64"
And!
if i converting my materials, i get no preview.
But when i delete the the "imageTexture" and load the texture manual without "imageTexture" the preview will work.
here is my scene:
http://www.file-upload.net/download-738 ... r.rar.html
i hope u can help me
Greets NICK
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 9:10 pm
by ChrisVis
oaktar, thank you for the old version 0.3. This one actual works! At least with 1 GTX 580... I do more testing now.
I dunno what you mean with the storage changing... I haven`t installed the 0.3 version before... just the 0.3.4.
And yes, I think I started with administration rights the first time... but I am not sure.
Testing now, I will let you know if it works with all 8 GPUS.
Greetings,
ChrisVis
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 9:44 pm
by EricDesign
I find new bug if i export the files .ocs C4D crash every time. thx
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 10:06 pm
by aoktar
EricDesign: we use 1.11 sdk, OCS export is broken in this version. I'll fix asap.
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 10:14 pm
by goumz
Ahmet,
We ran a quick test here at the studio over NET and ran into a texture related problem. As you mentioned the current version doesn't save ImageTexture images to the "tex" file as it should when you save as project. But the bigger problem is over NET Octane will not read the texture files from the "tex" folder, even if we copy all necessary images into that folder. If we render on an individual machine from the same project folder the render is perfect, but the NET client using Octane isn't looking at the "tex" folder for the images.
Does that make sense?
If I add an absolute path to all the image textures using a mapped network path the materials are seen (R:\Projectfolder\tex\test.jpg) but if relative (test.jpg) they are not seen as they should be.
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 10:16 pm
by EricDesign
aoktar wrote:EricDesign: we use 1.11 sdk, OCS export is broken in this version. I'll fix asap.
Thx aoktar.
Re: Beta 0.3.4 released (Actual version)
Posted: Tue Mar 26, 2013 11:27 pm
by RK-art
Hi Aoktar,
first, a big THANK YOU for developing the C4D integrated plugin.
A first run works fine on my 2 x 590 GTX system.
Of coarse, there is still much potential for further improvements, and I will post my suggestions here as anybody else will do, but we have now the power of Octane inside C4D what is a really cool thing.
Thanks.
A first thing I would beg to improve is that it would be usefull that the Octane settings window, tab 'settings', section 'options', would automatically use on the first show-up the C4D-Render-settings as they are set in the C4D dialogue-window and if they change, would also actualize as well.
It is irritating for the workflow that Octane's settings differ from the C4D-render-settings, especially that a 0-100 picture-animation-render is preset when I mostly only want to preview a single shot. So Octanes width/height, From-To and Step-settings should better orientate on the C4D-settings at start-up and any time they are changed.