• Custom scripting possibilites
• MAOF integration
• MASS integration
• Other enhancements

Check it out at http://code.google.com/p/ma-sh/: either by downloading the AIR file or getting the source code via SVN!

Level Master 2000: screenshot0001

Today I prepared the initial launch of Level Master 2000 at google code: http://code.google.com/p/levelmaster2000/. There are still a lot of features missing, as the project page states:

August 24th, 2010. Commited as is. Consider this more a preview/announcement rather than a real release. A major restructuring will occur within the next months, but anyway – here it is!

Nevertheless, it’s a good feeling finally having it on air and getting some feedback!

1. Clean all targets
2. Regenerate the qMake file via Qt Creator
3. Rebuild the project
4. Install the latest Flashplayer and add the app/AS3/bin directory to Flash Player’s local trusted

That was it! See for yourself:

Level Master 2000: running on OS X

The GUI needs a bit work though (e.g. the “delete entity” button), but all in all I’m really impressed how easy this was.

I’ll post some more detailed info about this trigger class soon (hopefully this week)!

Level Master 2000 Racing Demo

The weeks before, I was mostly busy with writing the introductional / theoretical background chapters of my thesis. Turned out to be more work than expected…

-static-link-runtime-shared-libraries=true

to the additional compiler options. Doing some more in depth research, I discovered that this isn’t neccessary with a newer version of FlashDevelop – and I can confirm: it’s true =)
After the update procedure, everything compiled fine in debug mode. In release mode, it compiled too, but I got a runtime error: “VerifyError: Error #1024: Stack underflow occurred”. Again, investigating this error on the web, I stumbled over http://bugs.adobe.com/jira/browse/ASC-2266. The piece of code causing this, looked like so:

conn = new LocalConnection();
conn.client = this;
conn.allowDomain('*');
try {
	conn.connect("_SchemaConnection");
} catch (error:ArgumentError) {
	trace("Can't connect to _SchemaConnection");
}

So as you can see, it’s not the same as in the link above. I started commenting out line by line, and then I discovered, that it was the trace call. Replacing it with a Logger call finally fixed the error:

Logger.print(this, "Can't connect to _SchemaConnection");

I guess we’ll just put that on the unsolved mysteries stack

Dino Run - a very addicting flash game!

I wonder if they use any flash game engine like PushButton Engine or Flixel.