Author Topic: AnimationFreezing/skippng and/or StateFreezing - Makes entirely no sense  (Read 442 times)

Here is my scenario:
I have two identical cs files for two swords that I'm making; the cs files are identical in every way except for the fact that one has "TraditionalELGImage" and the other is "TraditionalELSImage". I also have two models for each cs file, which are also identical; save the fact that each has a different hand color.
In this case, "TraditionalELG" is the 'working' cs file; in-game, it has no issues and all of the animations play perfectly. "TraditionalELS" however, is the 'broken' cs file; one of the attacks causes the animation to play out of order, followed by freezing it and locking up the weapon.

I have tried copying over the script from the 'working' cs file, over the 'broken' cs file; then changing the names, to no avail. I've taken other methods, such as using the model from the 'working' cs, and putting it to load into the 'broken' cs; it locks up the animations again, though the reverse (putting the 'broken' cs' model into the 'working' cs file) works just fine. Another solution I figured would work would be to re-export the 'broken' model, though the same results were still found.
Lastly, I had tried deleting the 'broken' cs file entirely and copying/renaming the working one with an entirely different name (used TraditionalELSK instead); still broken.


I really don't know what to do, it makes no sense at all. Removing the "ELS" model and cs isn't an option, because other weapon.cs files within the pack that I'm making use the same hand color as the working one, but are also broken. If someone has a solution, please answer.

EDIT: I still don't know why it wouldn't work; still need an answer. I have made a change to the 'server.cs' file, changing the order in which the weapons in my pack are called; this change has fixed the weapons and they work now.
« Last Edit: January 23, 2014, 12:13:24 PM by Deadzone »

Have you tried changing the broken one to use the model of the working one? That'd help you determine where the problem is.