This is how I currently have the TXI information (when it exists)
I can certainly have it save the file as well.
I'd been ignoring most of the UX design while getting the functionality built in but before I release it I plan to do a few design passes over it.
Hello!
Thanks for checking into this, Alvar007.
Unless I am mistaken, nobody before you ever attempted to add animations to NPCs so kudos to you. As DarthParametric pointed out, the human TALK_FORCEFUL animation could be a good inspiration for what kind of animation you could create for the Selkath.
Probably something very similar would work perfectly fine in their case as well.
Cheers!
Wow, these are definitely worthy of an animation! I will give it a go this week. Do you want it to be a variant of a normal talking animation or an emotion one like sad, angry, etc?
No worries, I also tag TSL with the thread actually, so I think it's still somewhat relevant.
I was also having that thought as I read your post, though as pointed out by DP and JC -
and an overwhelming fact that occurs on my attempt -
I had decided to live with it.
If it's the same issue as ebmar posted when sabers are are not properly occluding other objects then that's just an inherent render order issue the engine has that affects both games. Likely a deliberate move on Bioware's part, as JC pointed out.
Okay, here it goes.
There are more than I even thought. I also encountered one instance of TALK_HORROR, several TAUNT (but I believe it was a series of mistakes) and one TALK_PLEADING for Selkath. But those are rare enough to not bother creating new animations for, I believe.
manm26aa:
man26_pcexile.dlg
Entry 17
Entry 20
Entry 125
Entry 126
Entry 213
Entry 214 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 0
Entry 4 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 210
Entry 183 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 190
Entry 195
Entry 139
Entry 141
Entry 143
Entry 172
Entry 175
Entry 153
Entry 155
Entry 157
Entry 158
Entry 72 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 146
Entry 145
Entry 189
Entry 22
Entry 23
Entry 123
Entry 124 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 120
Entry 34
Entry 105
Entry 106
Entry 62
Entry 66
Entry 67
Entry 80 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 83
Entry 87
Entry 78 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 70 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
Entry 55
Entry 57
Entry 60
Entry 37
Entry 43
Entry 42
Entry 39
Entry 40
Entry 99 (there is probably a typo here because I am sure the developers meant to be TALK_FORCEFUL rather than TAUNT)
man26_selarb.dlg
Entry 138
Entry 146
Entry 144
Entry 145
Entry 133
Entry 78
Entry 134
Entry 135
Entry 130
Entry 126
Entry 105
Entry 110
Entry 111
Entry 112
Entry 109
Entry 102
Entry 104
Entry 100
Entry 89
Entry 76
Entry 59
Entry 55
Entry 45
Entry 30
Entry 24
Entry 22
man26_trial.dlg
Entry 246
Entry 88
Entry 26
Entry 136
Entry 242
Entry 272
Entry 260
Entry 262
man26_shaelas.dlg
Entry 60
Entry 52
Entry 53
manm26ab:
man26_selarrest.dlg
Entry 1
Entry 2