[Archive] [RELEASE] WoTLK New Combat Animations
[Archive] [RELEASE] WoTLK New Combat Animations
Original source
I've successfully merged 9/10 of them (Paladin spells have strange structure for one of dbc files, cant remember which one. Or am I dumb?). Using mydbceditor and some noob-coding (they use the same new ids, so I wrote a script to increment all new ids in dbc files for each file and sync these new ids in the related tables). The problem is that some patches have some trash lines in dbc files. Especially in SpellVisualEffectName. What trash? (at least what I've found) some pala spells have enormous sizes which causing lags and drops FPS down to 2 when pala uses them. I'm sure, it's not all.
You can find it. Try casting all pala seals using warrior spell patch. Others have bugs too.
Edited June 4, 2020 by Yuritsuki
rektbyfaith
06-04-2020, 05:12 AM #21Archived author: Yuritsuki • Posted: 2020-06-04T05:12:02+00:00
Original source
I've successfully merged 9/10 of them (Paladin spells have strange structure for one of dbc files, cant remember which one. Or am I dumb?). Using mydbceditor and some noob-coding (they use the same new ids, so I wrote a script to increment all new ids in dbc files for each file and sync these new ids in the related tables). The problem is that some patches have some trash lines in dbc files. Especially in SpellVisualEffectName. What trash? (at least what I've found) some pala spells have enormous sizes which causing lags and drops FPS down to 2 when pala uses them. I'm sure, it's not all.
You can find it. Try casting all pala seals using warrior spell patch. Others have bugs too.
Edited June 4, 2020 by Yuritsuki
Original source
What do I mean by the same IDs? Every new spell effect is going after the last wotlk ID. For example, if one of dbc ends with 15000. The new effect will start from 15001. And every patch this author made starts from 15001. So it's not just about merging new lines. You should use different IDs for every table in every patch and then do the same to the other dbcs. And THEN you should fix relations (when one table uses value from another): if other table use 15001 and your current visual patch starts from 15020, you should find the relation in related tables and change it to 15020.
This is why I hate patches that use dbc. There is no migration/partial editing functional. I'd rather override m2s and then fix the problems with 3D and hex-editing. And it will be fully compatible with every possible mod.
Edited June 4, 2020 by Yuritsuki
rektbyfaith
06-04-2020, 05:38 AM #22Archived author: Yuritsuki • Posted: 2020-06-04T05:38:05+00:00
Original source
What do I mean by the same IDs? Every new spell effect is going after the last wotlk ID. For example, if one of dbc ends with 15000. The new effect will start from 15001. And every patch this author made starts from 15001. So it's not just about merging new lines. You should use different IDs for every table in every patch and then do the same to the other dbcs. And THEN you should fix relations (when one table uses value from another): if other table use 15001 and your current visual patch starts from 15020, you should find the relation in related tables and change it to 15020.
This is why I hate patches that use dbc. There is no migration/partial editing functional. I'd rather override m2s and then fix the problems with 3D and hex-editing. And it will be fully compatible with every possible mod.
Edited June 4, 2020 by Yuritsuki
Original source
Uh.. And I also remember that there is a conflict with shaman and mage. They have at least one idenically named .blp but different image. But it's the smallest problem.
rektbyfaith
06-04-2020, 07:04 AM #23Archived author: Yuritsuki • Posted: 2020-06-04T07:04:52+00:00
Original source
Uh.. And I also remember that there is a conflict with shaman and mage. They have at least one idenically named .blp but different image. But it's the smallest problem.
Original source
Quote: 41 minutes ago, Yuritsuki said:Any chance you'll upload your merged patch of this at some point? *puppy eyes*
Uh.. And I also remember that there is a conflict with shaman and mage. They have at least one idenically named .blp but different image. But it's the smallest problem.
rektbyfaith
06-04-2020, 07:46 AM #24Archived author: sh1tdev • Posted: 2020-06-04T07:46:23+00:00
Original source
Quote: 41 minutes ago, Yuritsuki said:Any chance you'll upload your merged patch of this at some point? *puppy eyes*
Uh.. And I also remember that there is a conflict with shaman and mage. They have at least one idenically named .blp but different image. But it's the smallest problem.
Original source
Quote: 21 minutes ago, sh1tdev said:If there is someone who can help me to find which lines are these trash lines that destroy other spells, I will. I need someone who had already worked with Spell[anything].dbc. Can't just upload right now. Unfortunately, I'm playing on russian client too. And my dbcs right now include some of my and other dudes unfinished works. But it's not a problem to do it again and with english dbcs (I have english client).
Any chance you'll upload your merged patch of this at some point? *puppy eyes*
Edited June 4, 2020 by Yuritsuki
rektbyfaith
06-04-2020, 08:06 AM #25Archived author: Yuritsuki • Posted: 2020-06-04T08:06:24+00:00
Original source
Quote: 21 minutes ago, sh1tdev said:If there is someone who can help me to find which lines are these trash lines that destroy other spells, I will. I need someone who had already worked with Spell[anything].dbc. Can't just upload right now. Unfortunately, I'm playing on russian client too. And my dbcs right now include some of my and other dudes unfinished works. But it's not a problem to do it again and with english dbcs (I have english client).
Any chance you'll upload your merged patch of this at some point? *puppy eyes*
Edited June 4, 2020 by Yuritsuki
1 Guest(s)
1 Guest(s)