Infos and pictures :)
Hey!
Long time since I updated this site. The Particles Kit v2 is ready, although i didn’t have the time to write the full documentation for it yet. I finish the work @ Budapest this week, after that I’ll go to a short vacation to Praha, and then i’ll finish the Kit. It’s a very huge update, and a new thought-process behind it. Until that time, take a look at this gallery, i made these pictures as a birthday present for one of my friends :)
Tags: birthday present, particles kit
Comments (2)
Ross
| #
Yeah. As glitches go, its a bit of a weird one. Can’t off hand esbailtsh weather its C4D in general or just a glitch generated in Simon’s saved out scene file by C4D as a one off on his machine.Could be one or the other or a bit of both. Only real way to prove it is basically do the thing over from scratch, clean. See if ones own machine replicates the same fault without using any of the scene elements in Simons file. It’s a good thing to run into actually. Nothing here is any fault of Simons the TP and Xpresso side of things are faultless. Nobody would ever sensibly assume this kind of result would happen but for whatever reason as far as the scene file as C4D saved it out on Simons machine goes what Cinema’s doing is reading the TP Group links in the Tracers and basically confusing the Tracers themselves with the order in which the actual particle groups are produced and generated.Thus the Tracers are basically acting in accordance with the conditions set in the Xpresso as far as the render engine is concerned. It’s as if C4D is treating them like the particle groups they’re linked to rather than seeing them as simply just the Tracers they’re supposed to be.When Simon originally worked up the scene and rendered it I doubt that version was anywhere near as nicely ordered and layed out as the version distributed for the tutorial if Simons anything like everyone else what he most probably did afterwards was come back to that version of the scene file, re-name things logically and ordered everything out exactly as the final version is. Nice, neat, easy to follow.I don’t know possibly something in the naming convention he chose for the scene objects might have caused it (or, at the very least, allowed it to become possible) like I say, you’d really have to do the thing out clean from scratch to really find out. However, and whatever the case, as far as the distributed scene-file goes taking out the original attract-tracer appears to break the spell. Damn fine tutorial though. Extremely useful, massively informative and very playable with. The completed scene-file’s nothing but a genuine bonus. It’s making one aware of possibly more than originally intended, but that of itself is actually a damnably useful thing to actually know. Would never have occurred to me a problem like this might crop up using tracers applied to TP like this. Being one up on knowing it can happen that can save one a lot of seriously expensive time consumption further down the line at some point. You’d not expect the problem to be what it is unless you’d run into it before. This is one I haven’t, so I’m well pleased.Obviously, if push ever came to shove all one really has to do in a case like this (should the problem persist into render) is just split the render out into two parts one with the bugged tracer disabled up until the point one frame before the whole chain works and then render the rest as a separate pass with the problem tracer active: stick em back together in post.I do love a new thing though . Cheers me up something hellacious.Cheer’s, Mr Chops. All teh best with your stuff.R
Reply
c1p0
| #
I’m not sure where did you want to put this comment :)
Reply