Page 1 of 1
When will the demo be usable with Cinema 4D?
Posted: Fri Jul 30, 2010 11:36 pm
by keithkml
Hi, I'm using OS X 10.6 and I am really impressed by Octane. However, currently there seems to be no way to use the demo with my 3D program, Cinema 4D 11.5.
OBJ Export: Octane will import this, but without any textures. Yuck!
Riptide: Octane crashes whenever I import stuff I exported from C4d using the Riptide plugin - even when it's just a simple cube (see attachment). Apparently this will be fixed in the next release, whenever that will be, according to
http://www.refractivesoftware.com/forum ... =25&t=1055 (i'm using beta2.2)
C4D Octane Plugin: well apparently this is available to customers, but it really needs to be on the public download page IMO! Other 3d software developers (RealFlow, etc) publish these plugins for their demo users.
So in short, I'd
love to evaluate Octane for my projects, and I'm wondering when this will be possible. Thanks!
Re: When will the demo be usable with Cinema 4D?
Posted: Sat Jul 31, 2010 11:32 am
by radiance
Hi,
You are probably using the wrong export settings in riptide.
Post a screenshot of your export settings so we can see what you used.
The plugins are not available yet to demo users as they are not %100 documented yet.
Radiance
Re: When will the demo be usable with Cinema 4D?
Posted: Sun Aug 01, 2010 1:41 am
by keithkml
Thanks for your prompt response!!
BTW, there are no screenshots on the "OBJ export settings" thread for Riptide - just someone asking for help because they get (presumably) the same crash -
http://www.refractivesoftware.com/forum ... s&start=40
Here are my settings!
Re: When will the demo be usable with Cinema 4D?
Posted: Sun Aug 01, 2010 6:01 pm
by atome451
Hi keithkml,
You should try to export without n-gons. Try to uncheck the "Export Ngons" in the second screenshot.
I'm not totaly sure but i think it's one possible reason of your crash.
Re: When will the demo be usable with Cinema 4D?
Posted: Sun Aug 01, 2010 10:22 pm
by keithkml
Thanks for the tip, but unfortunately it still crashes with N-gons disabled. It even crashes when I disable the "export faces" section completely. In fact, it still crashes when I disable everything in the export tab.
Re: When will the demo be usable with Cinema 4D?
Posted: Sun Aug 01, 2010 10:34 pm
by keithkml
I also just tried converting the line endings from UNIX to Windows, I heard that might have to do with it. And it still crashes!
Re: When will the demo be usable with Cinema 4D?
Posted: Mon Aug 02, 2010 10:17 am
by radiance
Hi,
Do the octane demos work ? Have you tried our demosuite ?
You can download it on our downloads page.
Maybe it's a driver issue.
Radiance
Re: When will the demo be usable with Cinema 4D?
Posted: Mon Aug 02, 2010 2:38 pm
by keithkml
Yes, the demo scenes work great. And the crash isn't in driver code, it appears to be in GUI code:
Code: Select all
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 11
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x922d20fa mach_msg_trap + 10
1 libSystem.B.dylib 0x922d2867 mach_msg + 68
2 com.apple.CoreGraphics 0x982fad17 _CGSCreateWindowInline + 371
3 com.apple.CoreGraphics 0x982fa1c1 CGSNewWindowWithOpaqueShape + 666
4 com.apple.CoreGraphics 0x982f9f1f CGSNewWindow + 106
5 com.apple.AppKit 0x98b5dbce _NXCreateWindow + 221
6 com.apple.AppKit 0x98b5da38 _NSCreateWindow + 59
7 com.apple.AppKit 0x98b5cc5e -[NSWindow _commonAwake] + 1784
8 com.apple.AppKit 0x98b7be89 -[NSWindow _makeKeyRegardlessOfVisibility] + 110
9 com.apple.AppKit 0x98b7bde1 -[NSWindow makeKeyAndOrderFront:] + 39
10 ...activesoftware.octanerender 0x001707fa ProjectManager::~ProjectManager() + 1271930
11 ...activesoftware.octanerender 0x001d4dd8 ProjectManager::~ProjectManager() + 1683032
12 ...activesoftware.octanerender 0x001d5333 ProjectManager::~ProjectManager() + 1684403
13 ...activesoftware.octanerender 0x000f7713 ProjectManager::~ProjectManager() + 776083
14 ...activesoftware.octanerender 0x001d717b ProjectManager::~ProjectManager() + 1692155
15 ...activesoftware.octanerender 0x001bb0c5 ProjectManager::~ProjectManager() + 1577285
16 ...activesoftware.octanerender 0x001bb2c6 ProjectManager::~ProjectManager() + 1577798
17 ...activesoftware.octanerender 0x00241bc3 ProjectManager::~ProjectManager() + 2128963
18 ...activesoftware.octanerender 0x00325def NodePinStyle::~NodePinStyle() + 11935
19 ...activesoftware.octanerender 0x00407ff8 BoolNode::~BoolNode() + 12536
20 ...activesoftware.octanerender 0x00408697 BoolNode::~BoolNode() + 14231
21 ...activesoftware.octanerender 0x0031b2a2 ProjectManager::~ProjectManager() + 1842
22 ...activesoftware.octanerender 0x003738e8 std::vector<SelectionObserver*, std::allocator<SelectionObserver*> >::_M_insert_aux(__gnu_cxx::__normal_iterator<SelectionObserver**, std::vector<SelectionObserver*, std::allocator<SelectionObserver*> > >, SelectionObserver* const&) + 12376
23 ...activesoftware.octanerender 0x001d628c ProjectManager::~ProjectManager() + 1688332
24 ...activesoftware.octanerender 0x001d6a26 ProjectManager::~ProjectManager() + 1690278
25 ...activesoftware.octanerender 0x001d6ce7 ProjectManager::~ProjectManager() + 1690983
26 com.apple.AppKit 0x98c9cf6c -[NSWindow sendEvent:] + 5757
27 com.apple.AppKit 0x98bb5aff -[NSApplication sendEvent:] + 6431
28 com.apple.AppKit 0x98b495bb -[NSApplication run] + 917
29 ...activesoftware.octanerender 0x0024b6ab ProjectManager::~ProjectManager() + 2168619
30 ...activesoftware.octanerender 0x0002e238 std::_Rb_tree<std::string, std::pair<std::string const, int>, std::_Select1st<std::pair<std::string const, int> >, std::less<std::string>, std::allocator<std::pair<std::string const, int> > >::insert_unique(std::_Rb_tree_iterator<std::pair<std::string const, int> >, std::pair<std::string const, int> const&) + 140680
31 ...activesoftware.octanerender 0x0002e196 std::_Rb_tree<std::string, std::pair<std::string const, int>, std::_Select1st<std::pair<std::string const, int> >, std::less<std::string>, std::allocator<std::pair<std::string const, int> > >::insert_unique(std::_Rb_tree_iterator<std::pair<std::string const, int> >, std::pair<std::string const, int> const&) + 140518
Looking at the obj files Riptide produce vs the ones Cinema 4D natively produces, I see a huge difference in the "vt" and "f" lines, which describe the texture vertices and faces:
Cinema 4D:
Code: Select all
vt 0 0 0
vt 1 0 0
vt 0 1 0
vt 1 0 0
vt 0 0 0
vt 1 1 0
vt 0 0 0
vt 1 0 0
vt 0 0 0
vt 1 0 0
vt 0.5 1 0
f 3/9 4/12 2/6 1/3
f 5/13 6/15 4/11 3/8
f 7/18 8/20 6/16 5/14
f 1/2 2/5 8/19 7/17
f 4/10 6/15 8/19 2/4
f 5/13 3/7 1/1 7/17
Riptide:
Code: Select all
vt 0.00000 1.00000
vt 1.00000 1.00000
vt 1.00000 0.00000
vt 0.00000 0.00000
vt 0.50000 1.00000
f 3/4/1 4/140733193388035/4294967297 2/8319381562504249346/1 4294967297/1/140733193388033
f 5/4/2 6/140733193388035/4294967298 4/8319381562504249346/2 4294967299/1/140733193388034
f 7/4/3 8/140733193388035/4294967299 6/8319381562504249346/3 4294967301/1/140733193388035
f 1/4/4 2/140733193388035/4294967300 8/8319381562504249346/4 4294967303/1/140733193388036
f 4/4/5 6/140733193388035/4294967301 8/8319381562504249346/5 4294967298/1/140733193388037
f 5/4/6 3/140733193388035/4294967302 1/8319381562504249346/6 4294967303/1/140733193388038
These are interesting numbers Riptide generates:
4294967297 = 0x100000001
140733193388035 = 0x7fff00000003
In fact it looks like all the numbers are just small #'s with junk in the first 32 bits.
Looks like we've found our problem!
A little note - despite these messed up files, Cinema4D and Riptide both import them correctly. (Though perhaps they shouldn't
For now I'm going to write a python script that fixes up the files before importing into Octane...
Re: When will the demo be usable with Cinema 4D?
Posted: Mon Aug 02, 2010 3:14 pm
by radiance
Why not just get a license and use the c4D plugin we have ?
Radiance