You need Flash 9 to see this awesome Perlin noise particle system!
This is an early iteration of the system but I think it’s at a good point to publish. I just saw Mario Klingerman present at the FITC, and now I have a ton of new ideas to continue exploring and experimenting. If only I had some more free time.
Eventually I plan to release the code, but not until I’ve explored the possibility a little further.
I thought I would present a problem I seem to be having consistently in Flex builder, and see if anyone is searching for like issues.
For some reason, Flex Builder is not handling Bitmap Data with any sort of consistency when it is included as a class in a SWC exported from Flash. In my opinion, using SWCs to import visual content from the Flash IDE, is for the most part a fluid and excellent work flow. However, every once in a while, in seemingly inexplicable fashion, I get internal build errors.
Lately I’ve been using the Tween class included in the flash ActionScript 3.0 for Flash CS3 library, and I noticed some peculiar behavior with respect to the motion of the Tweens. Often, especially when the program was undergoing points of extreme activity, my tweens would not complete their motions. It was perplexing, and my first attempt to fix the bug was to simply to listen for the tween to stop
(tween.addListener(TweenEvent.MOTION_FINISH,
fixPosition)
, and then to force the asset to its intended end point. This worked on a simple application: Selected Works Site, but it completely failed when I tried it on one with heavy processor activity.
So, after trawling the internet in search of others experiencing the same problem, I believe I found the solution in the comments at a blog called Everything Cool. (I aslo found they talked about it on the live docs). Here I’ll explain what the problem is, how to solve it, and at the same time show you how to use the fl.transitions.Tween class in Flash CS3.
**Warning: The following post is about Object Oriented Design, and may be VERY annoying for those who don’t spend a STUPID amount of time in front of the computer reading the driest material ever known to mankind. **
For those into OOD/OOP, please read on… This is my attempt to make lucid some very spiraling concepts. I’m no expert, I’m a budding programmer, so as such I may be able to present these ideas with a new perception. At any rate… getting them down on paper solidifies the methods in my mind. That’s why I’m sparse on code, and big on concept. So if I get anything wrong, feel free to send evocative comments, I love the sweet vigor of a verbal joust.
Note: All OOD jargon has been italicized and colored for no good reason at all.