Animation Error

[Justintime9]

I just added two new animations to my age, and added them to the SDL file as well. the first one is a Rotation animation, and the other is a RotationLocationScale animation. I give it all the right settings, but when I exported, it gave me an error I've never seen before:

Here's my AlcScripts:

Code: Select all

BrownDoor:
    animations:
        - name: DoorOpen
          autostart: 0
          loop: 0
   
BrownDoorBut:
    quickscript:
        stateanimation:
            objectname: BrownDoor
            region: DoorButtonReg
            sdlname: DoorOpen
            avatar:
                animation: DoorOpen
                animtarget: DoorButtonEmpty
            forewards:
                animation: DoorOpen   
            backwards:
                animation: DoorOpen

DayNiteTurn:
    animations:
        - name: TurnNight
          autostart: 0
          loop: 0
   
DayNiteBut:
    quickscript:
        stateanimation:
            objectname: DayNiteTurn
            region: DNRegion
            sdlname: NightTurned
            avatar:
                animation: DoorButtonTouch
                animtarget: DayNightEmpty
            forewards:
                animation: TurnNight
            backwards:
                animation: TurnNight

Here's the SDL file:

Code: Select all

# Remember not to delete the existing versions when creating new SDL versions!
# Doing so could *corrupt* the vault!

STATEDESC Zefora
{
    VERSION 1

    VAR BOOL    WindowOpen[1]    DEFAULT=0
    VAR BOOL    LidOpen[1]    DEFAULT=0
}

STATEDESC Zefora
{
    VERSION 2

    VAR BOOL    WindowOpen[1]    DEFAULT=0
    VAR BOOL    LidOpen[1]    DEFAULT=0
    VAR BOOL    DoorOpen[1]    DEFAULT=0
    VAR BOOL    NightTurned[1]    DEFAULT=0
}


All of the regions and clickable/animated objects are Actors, and have bounds, so I can't see what could be wrong.

[D'Lanor]

Looks like there is something wrong with your IPO curve. AFAIK PyPRP does not support scaling yet.

This has nothing to do with your AlcScript, but it does have an error... there is no avatar animation called DoorOpen in Uru.

[Justintime9]

Hmm, must've missed that xD thx, I'll see if that works

Edit: Hmm, I changed the Avatar animation, and it still doesn't work (same error message)

[D'Lanor]

As expected. I said that had nothing with it.

[Corvus]

Some time ago I had the same error. If I remember right the reason was I changed the name of an object but forgot to do that in the Alcscript as well. You use the words Nite and Night, I guess there could easily happen some confusion.

[Jojon]

I had this.

You have probably got double keys on a frame somewhere. If your IPO curves are not too complex, go through them, dragging each point around a bit, to see whether it shares frame with another -- if so; remove the duplicate.

(tip: You can ctrl-drag in the IPO curve editor too, just like in the views. This will snap to integer (frame_number.00000 on the X axis EDIT: Err, no - it will not "snap", but move whole integer distances, so from 10.2 it will move to 11.2, sorry, forgot :7.


While I'm writing anyway, to whomever might have an answer: What sort of curve interpolation methods do we have in Plasma and pyprp, by the way? It seems no matter what sort of key handles I specify in Blender, the exported animations behave (mostly, but not quite) like every point has Blender's "AUTO" handles, with their overshoot issues, making it hard to do "sharp turns".

[Justintime9]

Hmm, well, one of my animatons did have a duplicate line, but it still gave the same error... I also noticed that for some reason all the animations are linked now. e.g, when I set the endframe for my door to 5, it changes the endpoint to my rotating object to 5 too (even though it's supposed to be 100), so it's either the door animation goes on too long, or the rotating object can't finish the animation. could this be the problem, and how would I fix it?

[Jojon]

Errr, well, with layer animations, all channels share the length of the longest running one, but in this case...? It is possible to use one IPO curve to scale the time of others, but I doubt you've got that...

Either way it may be a good idea to specify loopstart and loopend for your animations, although you shouldn't have to, when the curve has only a single one.

Only thing I can come up with, is that you Press the "N" key, in the IPO curve editor pane, to bring up the "Transform properties" window and check your points again, making sure no two points share a single frame - if rounding is done, "1" and "1.2" may count as the same.