Forums WoW Modding Support Archives WoWModding Support Archives [DiscordArchive] hey guys, when retroporting spell from legion, do I need to get blp files through multi converter?

[DiscordArchive] hey guys, when retroporting spell from legion, do I need to get blp files through multi converter?

[DiscordArchive] hey guys, when retroporting spell from legion, do I need to get blp files through multi converter?

rektbyfaith
Administrator
0
06-28-2023, 01:25 AM
#1
Archived author: learning_mouse • Posted: 2023-06-28T01:25:53.691000+00:00
Original source

hey guys, when retroporting spell from legion, do I need to get blp files through multi converter?
rektbyfaith
06-28-2023, 01:25 AM #1

Archived author: learning_mouse • Posted: 2023-06-28T01:25:53.691000+00:00
Original source

hey guys, when retroporting spell from legion, do I need to get blp files through multi converter?

rektbyfaith
Administrator
0
06-28-2023, 01:26 AM
#2
Archived author: learning_mouse • Posted: 2023-06-28T01:26:36.772000+00:00
Original source

if I just need blp file from specific animation, can I just take blp from legion and place it in my spells folder for wotlk?
rektbyfaith
06-28-2023, 01:26 AM #2

Archived author: learning_mouse • Posted: 2023-06-28T01:26:36.772000+00:00
Original source

if I just need blp file from specific animation, can I just take blp from legion and place it in my spells folder for wotlk?

rektbyfaith
Administrator
0
06-28-2023, 09:28 AM
#3
Archived author: <o> • Posted: 2023-06-28T09:28:09.741000+00:00
Original source

after some searching it turns out this was indeed the case. i haven't fully ruled out a way to detect why it happens, but for my purposes just forcing that fix onto every model seems to have worked well enough and we'll handle regressions manually, so thanks for mentioning it.

In short, the issue is fixed by filling the bone lookup table with 0s for anyone else reading
rektbyfaith
06-28-2023, 09:28 AM #3

Archived author: <o> • Posted: 2023-06-28T09:28:09.741000+00:00
Original source

after some searching it turns out this was indeed the case. i haven't fully ruled out a way to detect why it happens, but for my purposes just forcing that fix onto every model seems to have worked well enough and we'll handle regressions manually, so thanks for mentioning it.

In short, the issue is fixed by filling the bone lookup table with 0s for anyone else reading

Recently Browsing
 1 Guest(s)
Recently Browsing
 1 Guest(s)