I've had a go at making a tutorial series for Multimedia Fusion 2. Hopefully it'll bring some new members to the site.
I've been making tutorials on mapping for the Source engine (ie, Half Life 2, Counter Strike Source, Portal, Team Fortress 2 etc) for a couple of years and have learned a lot about what is needed from a tutorial and what people tend to get stuck on. I'm new to making MMF2 tutorials but this is my first attempt.
I actually found it very hard to make tutorials on this, it's something that everybody uses for a different purpose and to make a tutorial on it is very difficult. I spent a good 12 hours making the second tutorial, I spend hours typing, editing, re-organising and remaking bits until I felt that it worked properly.
Any feedback is welcome, I will be posting more tutorials soon in more specific areas, like different genres. Also, I understand that I don't go into much depth with the coding, I did have more event examples but I'm saving that for my next tutorial, otherwise the long tutorial length could scare people off. The second video shown here is meant to cover all areas quickly, as a sort of reference.
Actually, I don't really know why I posted these videos here. Maybe I'm just attention seeking.
Don't aim for perfection- you'll miss the deadline
'~Tom~ says (16:41):
well why does the custom controls for the keyboard palyer even affect the menu controls at all whats thep oint jsutm ake it so for the keyboard palyer on the menu screens everything is always up down left right enter regardless of the controls they set'
Really good videos, hopefully it does attract more people to pick up the program.
One little thing that irked me was in the first video you didn't explain a few things, such as when you closed the library window and said 'close this window down here we don't need it', it would've been nice to just quickly explain what the window you're telling them to close is and what it does. Also not explaining what the other editor windows were besides frame editor/event editor, at least explaining what they were and why they are not really core components to creating a game might be helpful for people new to the program who are not really sure what everything does and whether they might be missing out on using something that could be potentially helpful for them. Sorry, I know it's a bit nitpicky But great videos, keep making them!
I have to admit, you have a clear and concise voice which is perfect for video tutorials such as these. With a little bit more thoroughness why not contact Clickteam and see if they would put them up at their site? With even more thoroughness I bet you could probably sell these as DVDs
I wouldn't say i'd buy a cd, but definatley contact clickteam. These are nice and easy to follow. Though I wouldn't get your bat sweeper post mortems. Maybe I just don't like british humor that much, but I did enjoy them none the less.
All platforming problems can be mostly solved here:
Thanks, though I don't think that more thoroughness would help people. I don't explain a LOT of things and I've been attacked for this before, but at the end of the day, people just want to start making games and they don't want to learn useless stuff. By useless, I mean they don't need it for their first (or second) game and instead of teaching them more about the game maker, it's actually just confusing them and replacing more useful stuff that could be taught instead.
Don't aim for perfection- you'll miss the deadline
'~Tom~ says (16:41):
well why does the custom controls for the keyboard palyer even affect the menu controls at all whats thep oint jsutm ake it so for the keyboard palyer on the menu screens everything is always up down left right enter regardless of the controls they set'
Originally Posted by 3kliksphilip Thanks, though I don't think that more thoroughness would help people. I don't explain a LOT of things and I've been attacked for this before, but at the end of the day, people just want to start making games and they don't want to learn useless stuff. By useless, I mean they don't need it for their first (or second) game and instead of teaching them more about the game maker, it's actually just confusing them and replacing more useful stuff that could be taught instead.
I agree with this. At least, in the scope of this community. I'm sure many people would disagree and say that you shouldn't be teaching quick and dirty methods at first just to get some results, but most people would (hopefully) learn more advanced methods as they make more games.