Weekend Code Update

I was a bit dejected after Friday's Flash session. I'm really struggling with following a myriad of online and book tutorials when it comes to piecing them all together into a cohesive whole. It always seems to me that a lot of example scripts only show you a small part of the code and never explain everything fully enough to comprehend where each specific line should be placed (or expect you to know, which as a novice I don't). I spent most of today going through the books again at home and mainly working with axis-based collision detection (p308, Van der Spuy) to little avail.

I decided to have another look on the Internet for some much needed help and inspiration - something a bit more suited to my skill level and tailored to my racing game design needs. Luckily, one of my favourite Flash maestro's Emanuele Feronato (sounds like a Ferrari driver to me - he is Italian after all) has come up with the goods yet again. and provided an excellent, well-commented/explained step-by-step tutorial on how to 'Create a Flash Racing Game - AS3 version'. Part one is available at:

http://www.emanueleferonato.com/2010/06/16/create-a-flash-racing-game-tutorial-as3-version/

I will need to check that I'm allowed to use this, but it should be fine because I don't see how following a better guide can be viewed as a bad thing. At least this way, if I go through it carefully I will be able to grasp the processes at work and take something away from my time, rather than struggling with an array of sources I have little understanding of and just muddling through. I will still need to adapt the code to suit my concept, such as adding front-end UI, a leaderboard, overhead multi-axis scrolling and audio to name but a few features.

We have a Dissertation Flash session first thing Monday morning so I will bring up this possible plan of attack then and see it its given the green light. I know it will still be a major challenge for me but hopefully using this tutorial as a foundation won't cause constant exasperation and pulling of hair. Plus Chris might make it through without offering 24 hour-a day Adobe Tech Support!