Maxwell Render

Maxwell for Cinema 4D
Version 2.6.11 Release Notes

Changes

• Cinema Luminance Brightness is now used for MXI Emitter Intensity.
• Added support for the (R13) Cinema Camera's "Focus Object" link.
• Maxwell Fire exports are now performed using display LOD (in R12+).
• If no default mxm is found during export, one is written automatically.
• Optimized export of instances, when object motion blur is not enabled.
• Re-wote Render Region, to circumvent Cinema viewport z-clipping issues.

Fixes

• Emitter power was being read and written incorrectly.
• Auto-translated emitter power was written incorrectly.
• Cinema Luminance was ignored unless another channel was enabled .
• Hair UVs were exported reversed (length UVs for root, and vice versa).
• The wrong UVW tag could be used in some circumstances.

Download (please do not share these links)

(version superseded)

_________________
Next Limit Team

Animated Emitters woohooo, big thanks, x (now we can make TV screens etc. just put an avi into the luminance slot of a C4D material, and use it directly, it will autoconvert) Intensity is controlled using luminance brightness and multiply mode for the texture channel. (well thats whats working here)

You may want to increase the sampling size for conversion, its in the cinema tab of the maxwell scene object, and also turn on interpolation.


You can even animate the intensity of a hdr-still, for twinkling lights, or flickering neon without using multilight, or faking an explosion via hdr-bloom. etc.. etc...

Can I make a request here; C4D can use HDR image sequences for animated skies etc. but currently the plug does not pick this up, screenshot attached;

[img=http://s16.postimage.org/6x2jcw7lx/hdr_animation.png]

_________________
Materials, Arch-viz, C4D Dynamics

Hi JD

thanks for the new plugin and the lumiinance support.

in this new version I still find some issue regarding units. The z-buffer in the Scene object is set up in meters (not cinema units whatever they may be). But in the maxwell camera tag the z-clip planes seem to follow the units of the document.

See example scene:
http://www.william-associates.com/tmp/o ... issues.c4d

Cheers
Rogurt

_________________
Win7 64bit SP1; Dual Xeon E5520; 18GB Ram; NVidia GTX 560Ti
Maxwell 2.6; C4D R13 Studio; Maxwell Plugin 2.6

That is correct: while Z-Clip is figured relative to the camera (as it should be, since a camera may be rendered from any number of Scene Objects, each using different Export Units), Z-Buffer is specified absolutely, as it is elsewhere in Maxwell. Are you requesting that it be made to work differently (Z-Buffer being made to work in terms of Scene Object Export Units, I would assume)?

Eric: can you send me a simple example of a scene set up for this? The plugin is just asking the Cinema shader to render its HDR to disk for Maxwell at each frame, so it should work the same as it does for any other animated shader. I can animate a shader to use different HDRs in different frames here, anyway, so I must be doing it differently than you are.

_________________
Next Limit Team

It does not have to be that way. But if different units are used within the plugin there has to be some big hint within the plug in manual. I had a hard time figuring what´s wrong with my scene...

_________________
Win7 64bit SP1; Dual Xeon E5520; 18GB Ram; NVidia GTX 560Ti
Maxwell 2.6; C4D R13 Studio; Maxwell Plugin 2.6

Ah, I see -- I thought I had labeled this directly in the Z-Buffer UI (like in Maxwell & Studio), but that's not the case. It will be in the next build.

_________________
Next Limit Team

courteous as always

_________________
Win7 64bit SP1; Dual Xeon E5520; 18GB Ram; NVidia GTX 560Ti
Maxwell 2.6; C4D R13 Studio; Maxwell Plugin 2.6

I could send you a scene, but i cant include a gig's worth of animated hdr sky. My test was really basic, only using the luminance channel in a c4d material. I loaded the first hdr into the slot and specified a range in the animation tab, thats all. I tried every combo of options in the animation tab, in c4d you get an animation but in maxwell just the first frame.

How do you achieve it? I'm using R12

_________________
Materials, Arch-viz, C4D Dynamics

Okay, I see what you mean (I had literally keyframed a different hdr path in the shader, which works fine), now -- I'll see what I can do.

_________________
Next Limit Team

I'm getting a 100% reliable crash on launch with 2.6.11 C4D R13 plugin & Mac64 C4D Studio R13(.058). After review multiple crashreport dumps, the crash reliably occurs at the same address & exception:

SIGSEGV @ Maxwell for Cinema 4D.dylib:CbaseExtension::internalCreation() + 4).

NOTE: Because of message length limit, I needed to edit crashreport, full one is available if needed but given nature of the crash and reliability of it occurring at that same point each time, I'm guessing what I've provided ought to be enough.

== BEGIN Crash ==

Process: CINEMA 4D [21632]
Path: /Applications/MAXON/*/CINEMA 4D.app/Contents/MacOS/CINEMA 4D
Identifier: net.maxon.cinema4d
Version: 13.0 (13.0)
Code Type: X86-64 (Native)
Parent Process: launchd [201]

Date/Time: 2012-05-15 04:39:00.022 -0700
OS Version: Mac OS X 10.7.3 (11D50b)
Report Version: 9

Interval Since Last Report: 504589 sec
Per-App Interval Since Last Report: -10 sec
Anonymous UUID: 6AB59031-B93D-4A6C-BF8B-0B662929ED1E

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000

VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000101162000 [ 17.4M] r-x/rwx SM=COW /Applications/MAXON/*/CINEMA 4D.app/Contents/MacOS/CINEMA 4D

Application Specific Information:
objc[21632]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 Maxwell for Cinema 4D.dylib 0x000000011251d394 CbaseExtension::internalCreation() + 4
1 Maxwell for Cinema 4D.dylib 0x000000011251dff0 CextensionManager::InitializeAllExtensions() + 192
2 Maxwell for Cinema 4D.dylib 0x000000011236154b InitializeExtensionManager() + 351
3 Maxwell for Cinema 4D.dylib 0x00000001123524ca PluginStart() + 782
4 net.maxon.cinema4d 0x0000000100a8ce5c catch_exception_raise + 5196300
5 net.maxon.cinema4d 0x0000000100a92099 catch_exception_raise + 5217353
6 net.maxon.cinema4d 0x00000001001c228f 0x100000000 + 1843855
7 net.maxon.cinema4d 0x0000000100d8316a catch_exception_raise + 8301850
8 net.maxon.cinema4d 0x0000000100d86c0c catch_exception_raise + 8316860
9 com.apple.Foundation 0x00007fff8e9f7d32 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 47
10 com.apple.CoreFoundation 0x00007fff8dd30aaa _CFXNotificationPost + 2634
11 com.apple.Foundation 0x00007fff8e9e3fe7 -[NSNotificationCenter postNotificationName:object:userInfo:] + 65
12 com.apple.AppKit 0x00007fff9428060f -[NSApplication _postDidFinishNotification] + 212
13 com.apple.AppKit 0x00007fff94280375 -[NSApplication _sendFinishLaunchingNotification] + 78
14 com.apple.AppKit 0x00007fff9427f03c -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 242
15 com.apple.AppKit 0x00007fff9427ed9d -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 330
16 com.apple.CoreFoundation 0x00007fff8dd7a591 -[NSObject performSelector:withObject:withObject:] + 65
17 com.apple.Foundation 0x00007fff8ea1a7eb __-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_1 + 101
18 com.apple.Foundation 0x00007fff8ea19772 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 283
19 com.apple.Foundation 0x00007fff8ea19600 _NSAppleEventManagerGenericHandler + 105
20 com.apple.AE 0x00007fff96507c25 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 200
21 com.apple.AE 0x00007fff96507b03 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 38
22 com.apple.AE 0x00007fff965079f7 aeProcessAppleEvent + 250
23 com.apple.HIToolbox 0x00007fff97cdeaf9 AEProcessAppleEvent + 102
24 com.apple.AppKit 0x00007fff9427c1a9 _DPSNextEvent + 1247
25 com.apple.AppKit 0x00007fff9427b861 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
26 com.apple.AppKit 0x00007fff9427819d -[NSApplication run] + 470
27 net.maxon.cinema4d 0x0000000100d8683a catch_exception_raise + 8315882
28 net.maxon.cinema4d 0x0000000100019538 0x100000000 + 103736

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff96af07e6 kevent + 10
1 libdispatch.dylib 0x00007fff8f6cf5be _dispatch_mgr_invoke + 923
2 libdispatch.dylib 0x00007fff8f6ce14e _dispatch_mgr_thread + 54

Thread 2:
0 libsystem_kernel.dylib 0x00007fff96aee67a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96aedd71 mach_msg + 73
2 com.apple.opengl 0x00007fff96ef5371 glcDebugListener + 494
3 libsystem_c.dylib 0x00007fff95c438bf _pthread_start + 335
4 libsystem_c.dylib 0x00007fff95c46b75 thread_start + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff96aee67a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff96aedd71 mach_msg + 73
2 net.maxon.cinema4d 0x0000000100597993 0x100000000 + 5863827
3 libsystem_c.dylib 0x00007fff95c438bf _pthread_start + 335
4 libsystem_c.dylib 0x00007fff95c46b75 thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0301000007feedfa rcx: 0x0000000000000001 rdx: 0x0000000100000001
rdi: 0x0301000007feedfa rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff5fbfce60
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000005441bf8 r11: 0x00000000ffffefff
r12: 0x0000000101f832a0 r13: 0x0000000101f832a0 r14: 0x00007fff5fbfced0 r15: 0x00007fff5fbfcec0
rip: 0x000000011251d394 rfl: 0x0000000000010246 cr2: 0x000000011a066c50
Logical CPU: 0

Binary Images:
0x100000000 - 0x101161ff7 +net.maxon.cinema4d (13.0 - 13.0) <6CF102D0-B593-5D04-A756-00FA80060873> /Applications/MAXON/*/CINEMA 4D.app/Contents/MacOS/CINEMA 4D
0x1122f6000 - 0x11270afe7 +Maxwell for Cinema 4D.dylib (??? - ???) <A4343525-349E-4FB8-66EB-15BAACC8EEA3> /Applications/MAXON/*/Maxwell for Cinema 4D.dylib

== END Crash ==

_________________
John W.
2.7.10 Mac64 on MacPro(12C/24T/10.7.4),32GB,ATI 5770
"Sir, that stolen lemur bit one of your prostitutes right in the face, and she says she can’t go to hospital because she’s quote, ‘tripping balls’."

What this means is that the .mxx files found in your Maxwell /extensions directory are not version 2.6.10. So most likely, you just need to install Maxwell Render 2.6.10.

_________________
Next Limit Team

Thanks, I could have sworn I'd already installed it, but regardless re-installing it did fix the crash.

_________________
John W.
2.7.10 Mac64 on MacPro(12C/24T/10.7.4),32GB,ATI 5770
"Sir, that stolen lemur bit one of your prostitutes right in the face, and she says she can’t go to hospital because she’s quote, ‘tripping balls’."

For what it's worth, I often have trouble with Finder "fixing" file associations and such -- I will trash the Maxwell folder and install a new version, only to have Finder try and open MXS files using the trashed binaries. So, when the plugin queries launch services in order to find Maxwell, it is actually given a path leading to a directory in the trash. Or, when opening an MXS via Finder, it will run Studio.app from the trash, which will crash, because it is unable to find its libs; ostensibly, some files are being redirected, while others are not. I have even, once or twice, found OSX keeping an old image resident in memory, even when the trash has been emptied, and its binary no longer exists on the system. So if there is any question, the only completely foolproof method I know of is to trash the app, empty the trash, reboot, and then install.

_________________
Next Limit Team