Deleted Item 0003
Posted: November 5th, 2013, 4:34 pm*deleted*
Is there any provision for "easing" — smooth acceleration/deceleration along a path?
DKC Atlas Forum
An explorer's discussion forum for Donkey Kong Country
http://www.dkc-atlas.com/forum/
Deleted Item 0003
Page 1 of 1
Posted: November 5th, 2013, 4:34 pmRe: Paths, Events, and Save Variables
Posted: November 5th, 2013, 6:10 pmPath definitions are concise, yet seemingly exhaustive.
Is there any provision for "easing" — smooth acceleration/deceleration along a path?
Is there any provision for "easing" — smooth acceleration/deceleration along a path?
Re: Paths, Events, and Save Variables
Posted: November 5th, 2013, 6:14 pmThat can be done with "Predefined Variable-Speed (VS)" mode.
It's practically impossible to have both fixed path length and variable speed at the same time, though, so you have to pick one or the other.
It's practically impossible to have both fixed path length and variable speed at the same time, though, so you have to pick one or the other.
Re: Paths, Events, and Save Variables
Posted: November 5th, 2013, 6:37 pmUpdated (VS) path mode info to clarify something.
Re: Paths, Events, and Save Variables
Posted: November 6th, 2013, 10:13 amI've updated the specification to remove redundancy and improve its ease of use.
The "Path Events" no longer exist, and there are Object Events instead.
Thanks to Qyzbud's discussion I decided you can pass up to 6 auxiliary variables in an Object Event (passing large amounts of data is expected to be done with memory management and pointer passing etc).
The path Script Triggers have a relaxed definition - they can now raise any event at all, or set any level or game variable.
All events can have names now, as well, but the Object Event names are simply generated by CRC32-ing the name you provided (only done once the first time that such a line of code runs). The other events will use a similar method to obtain the ID numbers automatically (searched/obtained upon first request only) so that users will not have to mess with retrieving them manually in their C++ code.
Hopefully these revisions make things a bit more uniform.
The "Path Events" no longer exist, and there are Object Events instead.
Thanks to Qyzbud's discussion I decided you can pass up to 6 auxiliary variables in an Object Event (passing large amounts of data is expected to be done with memory management and pointer passing etc).
The path Script Triggers have a relaxed definition - they can now raise any event at all, or set any level or game variable.
All events can have names now, as well, but the Object Event names are simply generated by CRC32-ing the name you provided (only done once the first time that such a line of code runs). The other events will use a similar method to obtain the ID numbers automatically (searched/obtained upon first request only) so that users will not have to mess with retrieving them manually in their C++ code.
Hopefully these revisions make things a bit more uniform.