|
|
grass scene (Composition by dust)
just a simple mesh grass and tree scene, utilizing mesh filters and noise to create animations in an otherwise static scene. I'm getting a solid 60fps with both mesh and wire images combined. you might want to take out the wire images to speed things up or to add etc... mesh files made with maya and attached. |
Beautiful ...
thanks
for me in 10.6 snow,it opens without the mesh files, even if i reload them manually.
Have you ensured that the composition file is in the same folder as the meshes.
If you drill down into the macro patches containing the Mesh Importer patches you'll see they have file paths that are simply for "nameofmesh.dae" - but without the quotes. That means that the file has to be in the same folder as those files and at the same level of the folder.
Thus so, see attached picture.
yes, all in the same folder (grass_scene.zip ) .. but the mesh files are not loading (even if put them manually again into the project).
How very puzzling.
Do the mesh files open in Preview for you?
I can't replicate the problem.
Not even when running the example file in Snow's QC.
Very odd report.
Can't explain it.
In fact it runs faster in Snow's QC running in Lion for me than it does running in Lion's QC.
That's probably down to the sky Macro using a movie file - sky.mov, [on my machine the Movie Importer patch is almost totally broken in Lion] the load time decreases somewhat when I'm using Kineme Video Tools QT Player or Video Player patch.
they don't open in preview , and if open them in cinema4d they are empty // i've downloaded them again, same issue
[on my machine the Movie Importer patch is almost totally broken in Lion]
really ? OMG, hopefully I didn't switch yet .. To me this sounds really bad for an hypothetic QC'future
OT, but how can they break something that just worked... with cwright in the team
exactly the same here .... meshes won't load, even if replaced manually
Ah, yes, the hypothetical QC future question... As far as cwright goes, I think Apple has a history of re-purposing the smart folk they bring within the event horizon of the Mothership. Of course he can't tell us; he could be working on most anything.
My hope is that Mountain Lion will resolve (at least 80%) the increasingly untenable QT situation in the Apple OSX world where Quicktime spans 32bit only deprecated stuff, QTkit minimalist stuff, and a slowly revealed AV Foundation future. Lion, of course, straddles everything. I even think it was cwright who commented a few years ago about what an abomination the Quicktime world was even then. It would not surprise me if the challenge of keeping one foot on either side of this ever-widening crevasse is a cause of instability and breakage. It makes some sense of the clean break Apple insisted on with FCP ten from legacy: frailty in the Movie Importer patch suggests just how hopeless it would have been to upgrade an FCP legacy built completely using the ancient quicktime libraries.
It makes me wonder if QC 5 will have new "clean break" patches: the AV Foundation Asset Importer patch or just convoluted, wrapped, AC/DC, backward-compatible fragile-ware?
I think that the mesh related, openCL, most frameworks in general, etc., probably are not made by the QC Team, and that the QC Team is just using integrating them into patches.
If one of those frameworks breaks function, like the Mesh loading breaking in Lion, with many previously loadable objects not loading correctly, or like OpenCL spec changing or getting "fixed", there isn't a great deal that the QC Team could probably do about it.
That may or may not be bad for the future of QC, but I don't think it speaks directly to the efforts of the QC Team/coders. It seems more like a management thing (total conjecture), with departments having a hard time with communicating and not breaking stuff as OS X continues to get sprawling, and big changes are made without much time or care in assessing the possible negative impacts of those changes. To me, ideas like Lion's file save versioning, sound like something that someone comes up with without considering all of the possible problems that could result, and then some poor coder has to make work as best as they can. I think this is the case with many of the problematic things popping up in OS X and Xcode/Developer Tools.
i'm wondering what graphics card you guys are using. can you normally see mesh's. like in the template window can you see a mesh filter template ?
i exported the mesh as maya fbx/dae file. there where some issues with the material on export. instead of baking down a uv map i decided to just use some found image textures in qc. interesting enough qc recognizes the mesh's coloring if not using an image texture even though preview doesn't.
collada exports are tricky as i can confirm c4d doesn't load the mesh files on my systems but preview and qc will recognize them.
I booted into Snow, tried out the DAE files you included in Preview, they didn't open, so then exported them from FBX and converted them back to DAEs into a discrete folder separate from the grass scene folder.
The files then showed in Preview, but didn't show in the composition Viewer.
I had to substitute another tree file for the maple.dae as that file stubbornly refused to be converted to FBX at all.
All done with the same graphics card that I used when successfully booting into Lion and loading your grass scene.
Next I substituted the Mesh Noise patch you'd placed with the stock Snow Mesh Noise patch, still no joy.
Then I substituted one of my Mesh Noise Redrafts [you may well recall that both I and subsequently gtoledo were quite busy with fixing what shouldn't have been broken in the first instance for Mesh Filters, in my case, both Bend and Noise Mesh Composition Repository items http://kineme.net/forum/Discussion/SnowLeopard/MeshBendMeshNoiseRedrafts] and voila - the composition works.
In point of fact my tree model just doesn't suit the layout of the composition., so instead I downloaded another Maple tree by Ganymede from Google SketchUp Warehouse [http://sketchup.google.com/3dwarehouse/details?mid=2761b3bf5f5e18eae08bcdb812e5e7f3&prevstart=0].
I've attached the remade DAEs, grass and ground, that now load perfectly well along with the slightly revamped composition, as I dispensed with the use of Set Mesh Texture for the maple tree model employed, which model can be downloaded from the link above.
Just drop the models and the composition into place as per the picture shown below, RemadeGrassSceneforSnow.png and your good to go.
[until someone says - it doesn't work for me].
great thanks cybero. i thought it had something to do with the mesh filter or ati cards or something. interesting i remember when the mesh filters broke in snow leopard and when george fixed them. for some reason i thought that bug was fixed many SL updates ago. apparently i was wrong. the inconsistency of open cl rather bugs me. its like we have this wonderful new technology that works some of the time. is it just a waiting game till the tech gets pushed down the pipe line for a few more years until it is stable ? some of my SL apps have stopped working due to open cl which is actually pretty disturbing.
Sl to Lion, you'll probably find you're going to gain success with some by declaring
static constantas__constant. You'll also find that whereas__global constor__global constantworked,constreplaces. Sometimes it's a matter of giving a qualifying address space. Then again, simply ensuring that the kernel name isn't set tomainworks wonders sometimes, as is to be expected, wheremainis a reserved name.As it happens, and no surprise really , the revamped for Snow composition doesn't work at all in Lion.
Neither do my SL Mesh Filter fixes or george's for that matter. Both fall foul of declaring __constants without a qualifying address space. Version, version ...
This OpenCL versioning will settle down, eventually, of that I'm pretty sure.