This saturday me and Simon met in order to do some syncronuous hacking on SteamWinter. Actually, we didn't hack much but found a much better way to define levels using the .scene files. More specific the triggering markup was way too complicated to understand and needed a brush over. Further more, we identified some other features/bugs that need fixing before we can actually make the simple level required as a part of a flight2 release. I've already done some of the stuff:
- Make areatrigger into sphere and boxtrigger
- Make 'system' a valid target for a trigger. Used when it is not an actor that is interested in a trigger event
- Revised .scene format
- Show names properly and not a generated name as previously
- Print version number to console upon start (only linux for now)
The are no missing part before we can actually make a simple level, but these are the things that should get implemented as soon as possible to easy the level editing:
- Visualization of trigger areas
- A debug mode flag indicating that all names and triggers should be rendered
- Document the script bindings!
- Build time printed to console on windows
- Click to get world position
- Tutorial of creating a simple scene
After that I'll release flight2.... probably with some flight3 features as well.
This saturday me and Simon met in order to do some syncronuous hacking on SteamWinter. Actually, we didn't hack much but found a much better way to define levels using the .scene files. More specific the triggering markup was way too complicated to understand and needed a brush over. Further more, we identified some other features/bugs that need fixing before we can actually make the simple level required as a part of a flight2 release. I've already done some of the stuff:
No comments:
Post a Comment