GSOC pause

As it happens, I needs to complete some work related to my student status. It’s about my exams. In this regard, in the coming week my time should be given to questions about tropical geometry and information models/processes.

At the end of week, I will continue to work on Director engine.

Director: New week – new challenge

And once again I’m writing about my GSOC progress.

This week:

  • Loading transition info and implementation of some movings (8/52).
  • Imitation 2 track sound system (such as in Director).
  • Rendering trail sprites (it works like background images)
  • Parsing new kind of scripts  – movie scripts.

Director: Initial Lingo, events.

A week went by, engine changes, but slowly. Now is the moment when differences in Director versions are important.

Under the supervision of sev, I started to learn life cycle of the playback/draw system, it’s important because it can tell about when causes local events, such as frameEnter, frameExit, idle. In other words, we want to achieve event order, same as in Director. For me personally, it was hard to figure out what order is correct, sev advised me to check it right in Director. Because our target game is Journeyman Project, I looked in 4.0 version. By writing a simple script, I have found right positions in my code for calling this events.

Director: First official GSOC days

In previous post I promised to implement frame by frame system and deal with transparent objects.

At the beginning, I have written tempo channel handler. And depending on the frame tempo value (FPS/Delay) , it can determine time for next frame. Some examples: