Difference between revisions of "Roadmap"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
We are working to get a compiled version of Sirikata made available for 7/22/09 | We are working to get a compiled version of Sirikata made available for 7/22/09 | ||
| − | =Sirikata content tools= | + | ==Sirikata content tools== |
| − | ==version 0.01== | + | ===version 0.01=== |
*Anticipated release date: 7/22/09 | *Anticipated release date: 7/22/09 | ||
| Line 49: | Line 49: | ||
*select a series of objects and have them scatter from a central axis/point (explode effect) | *select a series of objects and have them scatter from a central axis/point (explode effect) | ||
*Cell or Bounding Box of a mesh coordinates and player coordinates sent out to OSC | *Cell or Bounding Box of a mesh coordinates and player coordinates sent out to OSC | ||
| + | |||
| + | ==physics features== | ||
| + | |||
| + | ===collision callbacks=== | ||
| + | [per IRC discussion 7/17/09, dbm, drh] | ||
| + | object names (new property) | ||
| + | object collision mask (used to group collisions) | ||
| + | use SpaceServiceObjectID in ObjectReference.hpp | ||
| + | for now, properties specified in scene.csv -- may change later (as persistence comes online) | ||
| + | keep track of collision pairs | ||
| + | any time the situation changes, send a message | ||
| + | example: "obj1, obj2 start collision" | ||
| + | "obj3, obj4 end collision" | ||
Revision as of 01:09, 18 July 2009
This is very incomplete at current but should give you a sense of ongoing work
We are working to get a compiled version of Sirikata made available for 7/22/09
Sirikata content tools
version 0.01
- Anticipated release date: 7/22/09
General:
save scene- Tested and distributable on Windows
- Produce Screenshots
- Determine which features from our design sketches and ideas are most likely doable for our current deadline
- Rank features weighted by what's easiest and which are most important to needs of the Augmented Museum
Objects:
importdrag/drop on Windowskey/text input on other platformslocal uploadplacement and scaling w mouse- orientation (Dan and Patrick to talk) [dan: this issue is somewhat alleviated by scene.csv, but still needs a tweak]
deletedecent lights in scene.txt
Features for a later deadline
- Undo
- CDN Upload
- Object Placement, Orientation and Scaling
- text tweaking (scene.txt - key to reload scene file)[dbm: all that is left to do is reload scene.csv]
object properties (for now, physics properties: collision, dynamics, hull type)Scene.csv format (Dan Miller)Convert from scene.txt- Add grouping
Lights:
- placement
- direction (kind of like rotation, but it would be much more intuitive to have them 'point' at a 3D location, perhaps using a selected object?
- attributes (directional, specular, ambient?? whatever)
- Light trigger (off/on)
MiTo Specific Object requests:
- Looped animation of translation
- rotating infinitely in a single direction
- rotate 1 direction then return to origin loop repetition infinitely (like a hammer swing)
- Scatter
- select a series of objects and have them scatter from a central axis/point (explode effect)
- Cell or Bounding Box of a mesh coordinates and player coordinates sent out to OSC
physics features
collision callbacks
[per IRC discussion 7/17/09, dbm, drh] object names (new property) object collision mask (used to group collisions) use SpaceServiceObjectID in ObjectReference.hpp for now, properties specified in scene.csv -- may change later (as persistence comes online) keep track of collision pairs any time the situation changes, send a message example: "obj1, obj2 start collision" "obj3, obj4 end collision"