-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key Frame Editing in App #51
Comments
Ability to record real-time player actions based on a displacement or a time-based interval is now supported. |
There has been a good deal of progress on the initially opened items, so I'm adding an update post here to track this. Original Items to Implement
|
Currently the height offset is visual only, perhaps we should do this the other way around. Let the player place waypoints at a height offset then change their height in-game to preview? |
I'm currently debating between three options for approaches to implementing editing individual waypoints:
All 3 of the approaches outlined above could be implemented simultaneously, but it would be good to have a priority for what needs to be done first. |
Currently keyboard-based axis aligned manipulation of waypoints is supported. If we'd like to support options (1) or (3) from above let me know. Otherwise I consider this development "complete" for now. |
Since there hasn't been a request for more features I'm closing this for now. |
Based on the work described in Issue #44 we've implemented a simple key frame path creator tool when
playMode=False
instartupConfig.Any
. Currently, the user can move about the map and either:q
key can also be used to quick-drop waypoints at the interval set in the menuIn addition the last waypoint can be removed, or the entire set of waypoints can be cleared. This is an issue to track the remaining implementation work and other suggestions for features.
Additional Items to Implement
This is a starting point for a more elaborate path built-in target path editing system. Additional features to support include:
The text was updated successfully, but these errors were encountered: