Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

• Forgot your password?
• Apply for membership

1. • CommentAuthorTackleMcClean
   • CommentTimeJun 5th 2009

    
   What are the main advantages/disadvantages of the two renderers?
   
   So for I've only noticed that I cannot add filters to the DisplayObjectRenderer. Is one faster than the other?
2. • CommentAuthorTripleH
   • CommentTimeJun 8th 2009

    
   I don't know about the relative speeds of the two, but I think you have the same problem I had.
   
   I started using a DisplayObjectRenderer to produce streams of particles to represent water flows through pipes. I added a BlurFilter to the particles themselves, and it worked out alright. However, each stream required a Steady counter of 25 particles a second. With 7 emitters, the amount of particles made it run horribly slow on anything other than a high end computer (fortunately my work computer is one of those).
   
   That's when I decided to try the BitmapRenderer. Each emitter is now down to 2-4 particles per second, and adding the BlurFilter to the renderer itself produces the nice motion blur that I was looking for. The hardest part is to make sure you import all the necessary components.
   
   I also found this handy little helper: http://www.visualisations.co.nz/visualise/flint-collide-update/. It allows you to use lines as collision surfaces to bounce particles off ( or have them follow the line if you set the bounce to 0 ). I don't know if you have use for it, but it's cool nonetheless.
   
   Overall, I prefer the BitmapRenderer, but it's really up to what works best for you. If you need help implementing it, just ask and I can post some of my code.