Aller au contenu

Photo

Romantic Animations Suite/Intimate Animations Suite + CEP 2.6


  • Veuillez vous connecter pour répondre
8 réponses à ce sujet

#1
Zeke

Zeke
  • Members
  • 46 messages

Has someone combined them successfully?

 

Community Expansion Pack (CEP) is an awesome resource pack and now I'm trying to add some hot stuff in my module and I'm trying to integrate it with  http://neverwinterva...nimations-suite

 

Has someone already done this? If no, can anyone spare some tips for making a HAK that is compatible with CEP? Thanks!



#2
Tarot Redhand

Tarot Redhand
  • Members
  • 2 670 messages

Very silly question but... Have you checked that those animations haven't already been added to the current version of the CEP?

 

TR



#3
Proleric

Proleric
  • Members
  • 2 345 messages
They haven't.

I imagine these animations are implemented as new phenotypes. If those phenotypes are not already in use by CEP, add them to phenotypes.2da in your top hak.

If you need to use the custom robes in CEP with these animations, duplicate the robe models for the new phenotypes.

Perhaps someone has done this work already?

#4
Zeke

Zeke
  • Members
  • 46 messages

Are a lot of changes needed to implement them for the default phenotype in CEP?

 

There is "ACAG w/ Intimate Animations" which implements them with ACAG (the hak for A Dance with Rogues) and make them part of the default phenotype.



#5
Proleric

Proleric
  • Members
  • 2 345 messages
Using a text editor, if you know what you're doing, you can replace one set of animations in the default phenotype model with another, as long as you don't mind losing the original animations. For example, if, say, a package uses custom animations 1-10, you'd replace those animations (only), leaving regular stuff like walk and run intact.

However, since changing phenotype is only one line of NWScript, it's arguably much easier to add the new phenotype. Making the new robes can be a batch process if you use Model Renamer.

Since there are only 20 custom animation slots per phenotype, sooner or later you'll need a new one.

#6
Zeke

Zeke
  • Members
  • 46 messages

You're right bit changing phenotype in NWScript lags the game for 1-2 seconds.

 

Except if I use Black Fade... or are there other ways out there?



#7
Proleric

Proleric
  • Members
  • 2 345 messages
I haven't noticed any lag - which phenotype did you try?

Was the model compiled?

#8
Zeke

Zeke
  • Members
  • 46 messages

The game just freezes for a second or two when changing phenotypes.

 

I'm sorry, what do you mean by not compiled?



#9
Proleric

Proleric
  • Members
  • 2 345 messages
That lag shouldn't happen on today's PCs.

Open the .mdl file with a text editor. If it contains legible ASCII code, it isn't compiled.

You can obtain the nwnmdlcomp compiler here.

Compiling a model makes very little difference to performance in most cases, but with very large models it can occasionally prevent lag or toolset crashes. This happens so rarely that I wait until I have a problem before compiling the model. I've found this helps with animation sets, and some high-poly creature models (which might also be due to their animation sets).