2.3 v5 crashes when accessing liveDB matNode

Forums: 2.3 v5 crashes when accessing liveDB matNode
VIP Information, news and announcements regarding new Octane Render commercial products and releases.

2.3 v5 crashes when accessing liveDB matNode

Postby dave62 » Tue Nov 16, 2010 9:59 am

dave62 Tue Nov 16, 2010 9:59 am
hi,

I got some new problems with the 2.3v5:

When drag some mat from the liveDB to the node editor and then make a connect to some mat in my obj-node, octane crashes all the time reproduceable. Even saving the mat locally before connect to obj-node did not solve the prob.
When i drag the material directly onto the scene it works fine without crash!?
But this way i dont know how to edit the mat in the nodeeditor..

edit: i tried it with a another much more simple scene and everything works fine -no crash, so at last it must depend on my mk2 scene.. ??
edit2: NO its not THE mk2 scene: I reimported the scene out of blender into oct, now it works without crashes. The problem must depend on some material editing inside octane i already made... but what exactly..?? Maybe because i already used the mat out of the liveDb database via dragNdrop into the scene but without changing its name.. or something like that...

Anyone any ideas how to solve?

best regards dave
- 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
User avatar
dave62
Licensed Customer
Licensed Customer
 
Posts: 310
Joined: Tue Oct 05, 2010 6:00 pm

Re: 2.3 v5 crashes when accessing liveDB matNode

Postby pamana » Tue Nov 16, 2010 7:30 pm

pamana Tue Nov 16, 2010 7:30 pm
Hi Dave

Are you able to post or pm the MK2 file, and I'll see if its not just your end?

regards
Pamana
Win 7 | Ubuntu | x64 | Quadro FX 5800 | 16 GB
User avatar
pamana
Licensed Customer
Licensed Customer
 
Posts: 25
Joined: Wed Jan 13, 2010 11:48 pm
Location: New Zealand

Re: 2.3 v5 crashes when accessing liveDB matNode

Postby timbarnes » Wed Nov 17, 2010 4:46 am

timbarnes Wed Nov 17, 2010 4:46 am
I see the same behavior. If I drag in a material node and connect it to the current model, Octane crashes. It's possible that it's due to my model being big (almost 1GB) and the update creating a delay, I guess.

If instead, I drag in the material, click on it to see what it looks like, and then while the material ball is visible connect it to my (invisible) model, Octane doesn't seem to crash. When I go back to my model, the new material is visible correctly, on the model.

I'm not sure if this is true for all materials yet: I'll do some experiments when I get some time.

tim
Mac Pro 3,1 / Lion / 14G RAM / ATI HD 2600 / nVidia GTX 470
i5-750 / Windows 7 Pro 64bit / 8G RAM / Quadro FX 580
Revit 2011, SketchUp 8, Rhino
User avatar
timbarnes
Licensed Customer
Licensed Customer
 
Posts: 125
Joined: Thu May 20, 2010 1:56 am
Location: California

Re: 2.3 v5 crashes when accessing liveDB matNode

Postby radiance » Sun Nov 28, 2010 2:36 am

radiance Sun Nov 28, 2010 2:36 am
Can anyone provide a propper testscene and a procedure to replicate the bug ?
I can't seem to here...

Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
User avatar
radiance
 
Posts: 7633
Joined: Wed Oct 21, 2009 2:33 pm

Re: 2.3 v5 crashes when accessing liveDB matNode

Postby msciwiarski » Mon Dec 20, 2010 7:04 pm

msciwiarski Mon Dec 20, 2010 7:04 pm
Hi all,

the same issue here... no matter which object I try to render, just simple object exported from Sketchup... it happens more often when I try to drag the node from the object to the material.

cheers

Michal
Hardware: Core2Quad Q9650, Asus P5Q Deluxe, GeForce GTX580
Software: Windows 7 Ultimate x64, Sketchup 8, Blender 2.56, Octane 2.4
msciwiarski
Licensed Customer
Licensed Customer
 
Posts: 44
Joined: Wed Nov 17, 2010 1:56 pm
Location: Poland

Return to Commercial Product News & Releases (Download here)


Who is online

Users browsing this forum: No registered users and 1 guest

Sat Aug 08, 2020 9:02 pm [ UTC ]