Ryzom

Report N2 : 28/05/2012

Work completed last week :
- Changing TStrigId to CSheetId for sounds

Work I had to complete but i could not complete :
- Add in the world_editor_classes.xml file the camera animation action that will tell us which animation to play.
- Add in the world_editor_classes.xml file the sound trigger action that will tell us which sound to play and where.

Reason why I couldn't complete this work :
- The completed task took me more time than expected

Work to complete this week :
- Add in the world_editor_classes.xml file the camera animation action that will tell us which animation to play.
- Add in the world_editor_classes.xml file the sound trigger action that will tell us which sound to play and where.

Report N3 : 04/06/2012

Work completed last week:
- Add in the world_editor_classes.xml file the camera animation action that will tell us which animation to play.
- Add in the world_editor_classes.xml file the sound trigger action that will tell us which sound to play and where.
- modification of the mission compiler to compile camera animations and sounds triggers in actions + check that the animation exists
- wiki article on how to create camera animations

Work to complete this week:
- parsing of the new actions in the EGS (camera animations and sound triggers)
- parsing of the camera animation instructions in the EGS
- make csheetid sounds work

Report N4 for camera anumations and sound triggers

Work completed last week:
- make csheetid sounds work
- parsing of camera instructions in the EGS

Work to complete this week:
- parsing of the camera animation modifiers
- parsing of the new actions in the EGD for camera animations and sound triggers

Report N5 : 18/06/2012

Work completed last week:
- parsing of the camera animation modifiers
- parsing of the new actions in the EGS for camera animations and sound triggers

Work to complete this week:
- send camera animatin instructions to the client via impulses
- send sound triggers instructions to the client via impulses

Report N6: 25/06/2012

Work completed last week:
- searched how to use impulses and how to use timers

Reason why I could not complete the scheduled work:
- had to search how to do the work I had to do

Work to complete this week:
- send camera animatin instructions to the client via impulses
- send sound triggers instructions to the client via impulses

Report N7: 03/07/2012

Work completed last week:
- fixed some bugs / improved some parts of the code

Work I had to complete but I could not complete:
- send camera animation instructions to the client via impulses
- send sound triggers instructions to the client via impulses

Reason why I could not complete this work:
- I was in holidays from last Tuesday to last Monday

Work to complete this week:
- send camera animation instructions to the client via impulses
- send sound triggers instructions to the client via impulses

Report N8: 10/07/2012

Work completed last week:
- send camera animation instructions to the client via impulses
- send sound triggers instructions to the client via impulses

Work to complete this week:
- Test the work done on the service
- Start parsing of client-side impulses for camera animations and sound triggers

Report N9: 17/07/2012

Work completed last week:
- Getting information about how to get an entity, about impulses on the client, and about sounds
- Implementing a basic impulse for sounds in the client
- Implementing a class that can contain either an entity or a position (used mainly for camera animations)

Work I had to complete but I could not complete:
- Finish the implementation of the impulses in the client
- Testing the work done in the service

Reason why I could not complete this work:
- I could not launch the game, and I still have no clue on how to solve this problem. So I lost a lot of time trying to make it work and I could not test my work

Work to complete this week:
- Finish implementing impulses on the client
- Test my work

Report N10: 23/07/2012

Work completed last week:
- Researches about the way to get entities from the client
- Tried to test my work

Work I had to finish but I could not complete:
- Finish implementing impulses on the client
- Test my work

Reason why I could not complete this work:
- I had to ask for some help after some unsuccessful researches
- My tests to solve the issue I have with the client (when I want to test my work) were unsuccessful

Work to complete this week:
- Finish implementing impulses on the client
- Test my work

Report N11 - 30/07/2012

Work completed last week:
- solved issue when launching the client
- testing my work
- implemented impulses on the client
- implemented basis of the camera animation player on the client

Work to complete this week:
- Understanding how the camera works
- Implementing a part of the steps and modifiers

N12 - 06/08/2012

Work completed last week:
- Implementing a part of the steps and modifiers (client side)
- Trying to understand how the camera works in the client

Work to complete this week:
- Finish understanding how the camera works
- Implementing more steps and modifiers (client side)

N13 - 13/08/2012

Work completed last week:
- Finish understanding how the camera works
- Implementing more steps and modifiers (client side)

Work to complete this week:
- Test and debug of the work done