|
|
help needed error inside Kineme core 0.4 hello everyone i suddently came up with this error at startup: can you help? 0x90986591: -[QCContext renderPatch:time:arguments:] 0x90986366: -[QCGraphicsContext renderPatch:time:arguments:] 0x9098526b: -[QCOpenGLContext renderPatch:time:arguments:] 0x9098510a: -[QCPatch(Runtime) render:arguments:] 0x0000e3aa 0x90a0c23f: -[QCView render:arguments:] 0x90a0c816: -[QCView _renderGLContext] 0x941ad22c: -[NSView _drawRect:clip:] 0x941abd23: -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 0x941ac0ba: -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 0x941ac0ba: -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 0x941ac0ba: -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] 0x941aa679: -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] 0x941a9fbb: -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] 0x941a6adf: -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] 0x940e74b3: -[NSView displayIfNeeded] 0x940e7061: -[NSWindow displayIfNeeded] 0x941a2c37: -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] 0x941a2690: -[NSWindow orderWindow:relativeTo:] 0x9416a022: -[NSWindow makeKeyAndOrderFront:] 0x0000d881 0x183553b6 0x940eaadd: -[NSDocument showWindows] 0x00003ca0 0x90cc843a: _nsnote_callback 0x91de064a: __CFXNotificationPost 0x91de0923: _CFXNotificationPostNotification 0x90cc5690: -[NSNotificationCenter postNotificationName:object:userInfo:] 0x90cceee8: -[NSNotificationCenter postNotificationName:object:] 0x940dd8ad: -[NSApplication finishLaunching] 0x00003994 0x940dd333: -[NSApplication run] kinemecore 0.4beta here. |
which 0.4? KinemeCore, v20090430 (0.4)? If not, make sure you're using the latest beta, and see if that helps.
If you're on snow leopard, please stop using KinemeCore until a future release is made available that works with SL.
If you're on leopard, please send copies of ~/Library/Preferences/net.kineme.KinemeCore.plist and ~/Library/Preferences/com.apple.QuartzComposer.editor.plist (so we can try to reproduce the bug).
To fix the problem, try deleting the above two plists (please email them to us first, for testing!)
ok yes i am on v20090430
i sent them via email
i attach the problematic patch i guess
the error:
*** -[NSCFString objCType]: unrecognized selector sent to instance 0xa024f9f0
ok as far as i can go here i isolated the error with:
xmlparser to kineme Gl Cube Structure is a No GO!
xmlparser to kineme Gl PoinT Structure is a GO!
the composition in attachment. thanks for your pacience.
the point.xml file:
<?xml version="1.0" encoding='UTF-8'?> <points> <vertex> <X>-0.1</X> <Y>-0.1</Y> <Z>-0.1</Z> </vertex> <vertex> <X>0.25</X> <Y>0.25</Y> <Z>0.25</Z> </vertex> </points>kineme core works in SL. see pics.
also check the pic of the gltools bug im getting. for some reason the screen splash screen gets all messed up and looks like the blend modes of the animation templates are all crazy with black boxes where normally they are not. it seems to be inherently sprites that are not honoring their alpha. i hope this is just my system but have tested with various builds on various systems. ist gltools. i love the gltools so i have been moving it in and out of my graphics folder.
i also got some strange results with gl tools in leopard still no GO!
Kinemecore definitely doesn't work in SL. Some functions work, but it doesn't work. I've used it too, but it's definitely a better idea not to use it right now. Crashes can occur, and other weirdnesses when you trigger various options.
It's a good idea to use Snow stock, and introduce patches one by one, and not just throw the whole wad in. Outside of the realm of Kineme stuff, there have been some pretty darn beta plug-ins released over the course of Leopard that should be viewed...skeptically!
Blend modes will be the main apparent issue many time (only working in replace, and alpha value being thrown off).
Kineme3D and Quartz Crystal will be "A-OK" for most scenarios, as well as many of the other plugs.
actually gl tools works fine with a QB bundle in SL as well as I have not had any issues with core yet, well all my kineme stuff disappeared when i tried to move them from library to home folder if that helps anyone. check out this screen shot i got cl mesh files working in quartz composer 3.
I reckon it's a bad cocktail mix, :-).
Nonetheless, very interesting to see just how well supported to one extent or another the 3rd version of QC is in SL.
I actually meant the previous post in relation to the reported GL Tools bug - already advised of by cwright.
In regards of QB supporting such a bundle, that just means , in my working setup for instance, me porting over from my Leo only machine originated comps and adding the GL Tools plugin as a resource from its currently disabled folder on my SL[Y] machine.
Nice news that works, dust.
In fact although I think it's a bad cocktail mix, it really has borne and indicated to you some interesting results and confirmations for us all.
One could of course, create a partition upon one's SL capable machine , and have the best of both worlds.
im not going to say qc3 works as intended with gl tools in SL. honestly the frame rate i get running qc3 in SL with glTools is so horrible it is not usable within those bounds. im talking something that i would get 30-40 fps only gets 3 in associative reference to glTools on SL, although when dealt within the boundaries of an encapsulated context ie.. a leopard qc buld it works flawlessly with gltools bundled as well as within the contextual reference to a leopard built interface builder application. Meaning that gltools works fine in SL when you run a application built in leopard qc3 but not within qc3 running on SL. so it has to be something inherent to a unknown external component to the framework qc runs in SL.
I only think this because a leopard built application rendered into a qcview will run gltools fine on SL as well as the kineme bundled protocol. I don't know enough of the unofficial stuff and i am just getting into plugin design so the issue may have something to do with the gl context but im just guessing becasue im not sure how QB renders its image. is it contextually gl or is it a view driven render deeper down in the core like qcview ? either way if you try to open a gltools project in IB or QC it will crash but running a application either encapsulated or not it runs fine.
try these examples one of them needs gltools in the patches folder the other doesn't.
It's definitely possible to make your own QC editor app even.. I think there's one on the market, but I forgot what it's called... and I can't find it wading through Google searches off the bat.
QB stuff should be totally cool, because it's working in its own environment... thankfully isolating the apps from a decent amount of issues, if not all. I'm still fascinated with the gains in fps I get in many scenarios with QB. Not having to handle the editor surface is a really good thing, amongst other things that make QB faster than Quartz Composer in many scenarios.
Did anybody have old SL qtz patches on their desktop? It's interesting how one gets the prompt that they are opening up an old version of a qtz that there is a newer version of.
Interesting, the Illusion works AOK, albeit not full screen, but both your archived items, and the QB items I have made available now can be package explored and bundled assets removed.
QB will no doubt update if needs be in that regard.
Don't see the point of making a QB app needing a potentially unavailable resource ever.
Does demonstrate a point about 3rd party patches and plugins and QB at this point in time.
I shall await the necessary updates with all due patience.
I fear for many of the NDA respondents, a certain fatigue might well have begun to sink in and ever captious of what is good, one is inevitably captious of that which is bad , especially faster having had to work un-reportable by 'force of law' as it were, for so long.
Some exceptional work and no doubt, what such respondents are in the main reporting will become evident and also solved in time.