3: Done

ChartTools does not render in QuartzCrystal

Hey y'all,

ChartTools 1.0 does not produce any rendered movie in QuartzCrystal 2.0.

Solution: install ChartTools 1.1.

iTunes Visualizer

My .qtz file works fine.

So I bought QuartzBuilder 2.0 and exported the project ok.

But when I try to launch the compiled .app i get the following error:

"An unexpected error occurred (error code -10810)"

and my app won't start, grrrrrrrrrrr

I cannot find an explanation of 10810.

Any ideas...?

Crash problem with ArtDmx Receiver

Hi, I am Italian excuse for my English... I have problem with ArtDmx Receiver (ArtNet Sender works correctly). With test file SendReceive.qtz when stop and run again Viewer, Quartz Composer show an error and exit.. In attach the report file. I have try with another Imac but same problem remains. If I don't stop and run the viewer, ArtDmx Receiver receive just one time and then it doesn't refresh the structure. I have regulary purchased the Art-net tools but work just on sender. I use Mac Os X 10.6.4 and the last Quartz Composer. Thanks for your help

Quartz Builder Mouse/Multitouch Events Forwarding/Window Events

In Leopard, I used to do activities like tie mouse outputs to window x/y position, using the Quartz Builder template, and have windows follow the mouse, usually with some smoothing, or something.

I've tried to do this in Snow Leopard, and it just doesn't work. I also tried it with Multitouch, and events still don't forward. Further, I tried hooking up the outputs of mouse/multitouch to a "dud" Billboard, just to make sure they would evaluate. None of this makes it work.

Objects "inside of a qtz" that may be hooked up to mouse also stop tracking when window focus is broken, but I'll file that in a separate report when I'm sure about it (though I'm pretty darn sure). I used to make "floating" apps, or desktop apps that did this. (re:hairball.qtz attachment)

Also, I seem to be having problems with things going Fullscreen. I'm attaching a composition that uses multitouch (which forwards successfully), and SEEMS like it should go fullscreen (nothing fancy with interaction, it's just set on Fullscreen to true).

So, it seems like QuartzBuilder is now limited to opening at a specific width/height, and that if using mouse, the window always has to be in focus to move objects in the qtz. It also seems like all fancy window resize/translate with mouse stuff isn't working.

K3D Loader features - Axis Swap / MTL Loader

This feature would be on the loader, and swap y and z axis.

I've used this loader in Google Sketchup:


... and found the feature to be handy.

In addition, the handling of MTL files with this script is cool. Maybe there could be an Image Structure input on the structure render that is in beta, for loading MTL. Perhaps this could be adapted to work with loading dae texture via this port as well.

Kineme3D crash

In the past i've updated some Kineme-plugins and now the Kineme3D Object Loader doesn't function properly anymore. When i try to connect a .obj of .dae file to the 3D Object Renderer Quartz Composer crashes and generates the following crashreport:

Process: Quartz Composer [2459] Path: /Developer/Applications/Quartz Composer.app/Contents/MacOS/Quartz Composer Identifier: com.apple.QuartzComposer.editor Version: 3.0 (63) Build Info: QuartzComposerEditor-630000~14 Code Type: X86 (Native) Parent Process: launchd [1452]

Interval Since Last Report: 290 sec Crashes Since Last Report: 4 Per-App Interval Since Last Report: 209 sec Per-App Crashes Since Last Report: 4

Date/Time: 2010-08-03 12:01:29.609 +0200 OS Version: Mac OS X 10.5.8 (9L31a) Report Version: 6 Anonymous UUID: 239D11A7-9D24-49AE-8021-77C4568568A9

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000002af3ba50 Crashed Thread: 0

Thread 0 Crashed: 0 net.kineme.Kineme3D 0x17a5bc64 0x17a49000 + 76900 1 net.kineme.Kineme3D 0x17a4c6ed 0x17a49000 + 14061 2 com.apple.QuartzComposer 0x95a8cae4 -[QCPatch(Private) _execute:arguments:] + 1231 3 com.apple.QuartzComposer 0x95a8cd73 -[QCPatch(Extensions) executeSubpatches:arguments:] + 312 4 net.kineme.GLTools 0x16d8feb6 -[KinemeGLPolygonModePatch execute:time:arguments:] + 822 5 com.apple.QuartzComposer 0x95a8cae4 -[QCPatch(Private) _execute:arguments:] + 1231 6 com.apple.QuartzComposer 0x95a8cd73 -[QCPatch(Extensions) executeSubpatches:arguments:] + 312 7 com.apple.QuartzComposer 0x95acadf1 -[QCLighting execute:time:arguments:] + 1213 8 com.apple.QuartzComposer 0x95a8cae4 -[QCPatch(Private) _execute:arguments:] + 1231 9 com.apple.QuartzComposer 0x95a8cd73 -[QCPatch(Extensions) executeSubpatches:arguments:] + 312 10 com.apple.QuartzComposer 0x95a8cae4 -[QCPatch(Private) _execute:arguments:] + 1231 11 com.apple.QuartzComposer 0x95a8b158 -[QCContext renderPatch:time:arguments:] + 650 12 com.apple.QuartzComposer 0x95a8aeaa -[QCGraphicsContext renderPatch:time:arguments:] + 91 13 com.apple.QuartzComposer 0x95a89daf -[QCOpenGLContext renderPatch:time:arguments:] + 334 14 com.apple.QuartzComposer 0x95a89c4e -[QCPatch(Runtime) render:arguments:] + 92 15 ...apple.QuartzComposer.editor 0x0000e3aa 0x1000 + 54186 16 com.apple.QuartzComposer 0x95b10d83 -[QCView render:arguments:] + 471 17 com.apple.QuartzComposer 0x95b108bd -[QCView startRendering:] + 716 18 ...apple.QuartzComposer.editor 0x0000da9f 0x1000 + 51871 19 com.apple.QuartzComposer 0x95b105eb -[QCView startRendering] + 42 20 com.apple.Foundation 0x961c942a _nsnote_callback + 106 21 com.apple.CoreFoundation 0x9507f47a __CFXNotificationPost + 362 22 com.apple.CoreFoundation 0x9507f753 _CFXNotificationPostNotification + 179 23 com.apple.Foundation 0x961c6680 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128 24 com.apple.Foundation 0x961cfed8 -[NSNotificationCenter postNotificationName:object:] + 56 25 com.apple.AppKit 0x9480f40a -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 849 26 com.apple.AppKit 0x9480f05c -[NSWindow orderWindow:relativeTo:] + 105 27 com.apple.AppKit 0x947d69ea -[NSWindow makeKeyAndOrderFront:] + 189 28 ...apple.QuartzComposer.editor 0x0000d881 0x1000 + 51329 29 ...ineme.QCEditorAppExtensions 0x16f657b1 0x16f60000 + 22449 30 com.apple.AppKit 0x947574a5 -[NSDocument showWindows] + 117 31 com.apple.AppKit 0x94a3270d -[NSDocumentController openDocumentWithContentsOfURL:display:error:] + 525 32 ...apple.QuartzComposer.editor 0x0001ae85 0x1000 + 106117 33 ...apple.QuartzComposer.editor 0x0001adfc 0x1000 + 105980 34 com.apple.AppKit 0x94a32488 -[NSApplication _doOpenFiles:] + 135 35 com.apple.AppKit 0x94a323e1 -[NSApplication(NSAppleEventHandling) _handleAEOpenDocuments:] + 88 36 com.apple.AppKit 0x947540db -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 297 37 com.apple.Foundation 0x961eea9f -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 655 38 com.apple.Foundation 0x961ee7af _NSAppleEventManagerGenericHandler + 223 39 com.apple.AE 0x96bad648 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 144 40 com.apple.AE 0x96bad57e dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 44 41 com.apple.AE 0x96bad425 aeProcessAppleEvent + 177 42 com.apple.HIToolbox 0x96764981 AEProcessAppleEvent + 38 43 com.apple.AppKit 0x947518e9 _DPSNextEvent + 1189 44 com.apple.AppKit 0x94750f88 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 45 com.apple.AppKit 0x94749f9f -[NSApplication run] + 795 46 ...apple.QuartzComposer.editor 0x000037d2 0x1000 + 10194 47 com.apple.AppKit 0x947171d8 NSApplicationMain + 574 48 ...apple.QuartzComposer.editor 0x00001f1e 0x1000 + 3870

Thread 1: 0 libSystem.B.dylib 0x9754d46e __semwait_signal + 10 1 libSystem.B.dylib 0x97577dcd pthread_cond_wait$UNIX2003 + 73 2 libGLProgrammability.dylib 0x90199b32 glvmDoWork + 162 3 libSystem.B.dylib 0x97577155 _pthread_start + 321 4 libSystem.B.dylib 0x97577012 thread_start + 34

Thread 2: 0 libSystem.B.dylib 0x975769c6 kevent + 10 1 com.apple.Foundation 0x961c9dfd -[NSThread main] + 45 2 com.apple.Foundation 0x961c99a4 NSThread__main + 308 3 libSystem.B.dylib 0x97577155 _pthread_start + 321 4 libSystem.B.dylib 0x97577012 thread_start + 34

Thread 3: 0 libSystem.B.dylib 0x9754d46e semwait_signal + 10 1 libSystem.B.dylib 0x9754d236 usleep$UNIX2003 + 61 2 com.apple.AppKit 0x947b7bf1 -[NSUIHeartBeat _heartBeatThread:] + 2042 3 com.apple.Foundation 0x961c9dfd -[NSThread main] + 45 4 com.apple.Foundation 0x961c99a4 __NSThread__main + 308 5 libSystem.B.dylib 0x97577155 _pthread_start + 321 6 libSystem.B.dylib 0x97577012 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit): eax: 0x00b1a400 ebx: 0x00b11800 ecx: 0x00000002 edx: 0x2a42a24c edi: 0x00b1e000 esi: 0x42b40000 ebp: 0xbfffe158 esp: 0xbfffe120 ss: 0x0000001f efl: 0x00010a97 eip: 0x17a5bc64 cs: 0x00000017 ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037 cr2: 0x2af3ba50

I've attached the composition and the .dae file i used.

In the past this composition used to work. Should i update or downgrade some plugins in order to get this working again?

grtz, Slof

KnM 3D / render in image flicker

Hi, i'm having problems using KnM3D FBX mesh loader and renderer, when used in a render in image patch. The whole object is flickering, when shadows are enabled.

See the attached example comparing apple's stock teapot and a FBX teapot, exported straight from 3dsmax.

Is it hardware related ? i tested on a Geforce 9600M and a 9400M. Can anyone confirm ?

Thanks in advance.

Is this a Bug? Structure To/From File patches

The .plist file is accurate.

The structure output from Structure From File appears out of order?

Struct Maker data:

Structure From File outputs:

Lighting Bypass

It would be useful to have a macro, much like the GL Shade Model, that allowed an object inside a Lighting Environment to not be affected by the Lighting Environment, assuming that it would yield the kind of performance increases that it does when one typically compares FPS with renderers inside a Lighting patch vs. not in a Lighting patch. It may be useful for it to be combined with the GL Shade Model.

This isn't a priority thing, but something that has occurred to me, as Lighting issues come up regularly in my discussions with people who use QC (surprisingly).

Structure > Outputs Patch

Here's an idea for an addition to a future Structure Tools: A patch that takes a structure as input, and creates an output port for itself of the appropriate type for each item in the structure.