嗜血代码 King 夜魔 夜鬼

尊敬的游客，如果您要查看本帖关注 或 回复可见内容请关注或回复后刷新页面查看！

模型为Toolbag3渲染  模型文件为 OBJ

贴图为 dds 格式  大小为4096x4096

模型有Diffuse  Normal 贴图

带Toolbag3 文件

更多精彩图片 请登录

更多精彩图片 请登录

state stack (ds stack senum>)
The "history" of all state changes. Holds the enum values of each state that has been used since the last time the history was clearec
state_queue (ds queue senum>)
Holds the enum for all states queued up as part of a state queue.
Useful Variables
These variables are provided for you to use, ideally within a state script.
state timer (real.
This variable counts up from O for each step that is spent in the current state. Verv useful for timing thines within al state.
state_new (boolean
This variable is true only for the first step the state is ran, It will also be true the first step after using
truestate reset currenti)
state var (orray <variqusy)
This array can be utilized in a wide variety of ways. Its core purpose is to allow you to keep track of values that wil persist between stens but will only he relevant to the current state and -in some cases- the beginning of the next.
state.
For example, say you have a charge attack that requires the player to hold button down for a set amount of time for different effects. Instead of creating a new "charge hold time" variable, you just use state varf0l, put a comment on it so you know what you are using it for for macro or enum) and then in the next state you can use state varlol fol something else.
It's a bit strange at first, but every time vou go back to your create event to initialize a variable that only one state cares about, ask yourself if you could just use state varll instead.

楼主，你是一个大好人！！

666

楼主，你是一个大好人！！

感谢LZ分享

6666666666