|
|
Particle Rain (Composition by gtoledo3)
This is a simple particle tools scene that makes something that looks like a rain fall. I've used it when wanting a scene to look like there is some rain going on somewhere; it doesn't seem especially taxing on my laptop. Edit: If running with Snow Leopard, QC should be run in 32 bit mode. Do this by finding your Quartz Composer app in the Developer folder, performing a "get info", and checking off 32 bit mode. |
Crashes QC upon opening every time.
Oh, I'm sorry, I think I noted it in the composition, but I should have noted it in the post. When run in Snow Leopard, one should find their version of the QC.app in the Developer folder, "get info" on it, and check "32 bit" mode. Particle Tools (and Vee frameworks that it uses) is not compatible with 64 bit mode in QC Snow Leopard.
I happened to be using Leopard the day I posted this, and didn't think about that.
I found that the neatest solution was to duplicate the QC application, set one to 32 bit as you detailed and then rename that as QC 32 bit, easily distinguishable too with a bit of label colouring.
Result, both can run concurrently, meaning 64 bit only items do not get held up and 32 bit items can be examined and utilised simultaneously.
That's an interesting idea; I've heard others mention it too. Do you get weirdness in which version of QC opens up various files? (I already do sometimes between partitions... SL made comps want to pull open my SL located QC, when I'm in Leopard, and it of course, loads the Leopard framework, even if I already have Leopard QC open sometimes. Big irritation.)
I pretty much always leave QC in 32 bit. Sometimes if I know I'm going to be editing the OpenCL kernel heavy, I change to 64.
I thought you might ask about weirdness - like crossing streams of information, calling upon the same frameworks. I rarely use Leopard , but can echo that open me in SL deal, been there and still got the t-shirt :-).
Using duplicate bit type differentiated QC duplicates in SL has not caused me any significant reportable problems.
In Activity Monitor, both are listed with identical names but unique PIDs and are detected correctly as either 32 bit - no notice in fact - just Intel, or Intel 64-bit.
I do find that the system seems to lean towards one , or the other, as the default opening application, which can cause problems sometimes when trying to keep the 32 bit items for 32 bit QC only. This un requested preferencing can swing either way.
Most 10.6 only items work AOK in either version.