Forums WoW Modding Support Archives WoWModding Threads [DiscordArchive] I am curious if anyone has a method on how they debug what is causing a model to simply not work or

[DiscordArchive] I am curious if anyone has a method on how they debug what is causing a model to simply not work or

[DiscordArchive] I am curious if anyone has a method on how they debug what is causing a model to simply not work or

rektbyfaith
Administrator
0
11-27-2024, 09:58 PM
#1
Archived author: ohno.hono • Posted: 2024-11-27T21:58:53.379000+00:00
Original source

I am curious if anyone has a method on how they debug what is causing a model to simply not work or causes a crash in the server. I often come across some models from shadowlands and older that retroport just fine with very little work. And then I come across a random creature model or gameobject model that simply does not show up at all and does not show a missing model box or just outright crashes the client when logging in with that m2 in the patch. I know the solution is probably some hex editing to fix the problems but how do you debug what the problem is in the first place? Here is a simple example of a model that crashes my client when loading it.
faeriedragon3.zip
rektbyfaith
11-27-2024, 09:58 PM #1

Archived author: ohno.hono • Posted: 2024-11-27T21:58:53.379000+00:00
Original source

I am curious if anyone has a method on how they debug what is causing a model to simply not work or causes a crash in the server. I often come across some models from shadowlands and older that retroport just fine with very little work. And then I come across a random creature model or gameobject model that simply does not show up at all and does not show a missing model box or just outright crashes the client when logging in with that m2 in the patch. I know the solution is probably some hex editing to fix the problems but how do you debug what the problem is in the first place? Here is a simple example of a model that crashes my client when loading it.
faeriedragon3.zip

rektbyfaith
Administrator
0
11-27-2024, 10:12 PM
#2
Archived author: Titi • Posted: 2024-11-27T22:12:11.738000+00:00
Original source

- try to find if the error code exists in [wowdev](https://wowdev.wiki/Client_Error_Analysis)
- try to import the model in WBS and see if it outputs any error message
[Embed: Client Error Analysis]
https://wowdev.wiki/Client_Error_Analysis
rektbyfaith
11-27-2024, 10:12 PM #2

Archived author: Titi • Posted: 2024-11-27T22:12:11.738000+00:00
Original source

- try to find if the error code exists in [wowdev](https://wowdev.wiki/Client_Error_Analysis)
- try to import the model in WBS and see if it outputs any error message
[Embed: Client Error Analysis]
https://wowdev.wiki/Client_Error_Analysis

rektbyfaith
Administrator
0
11-27-2024, 10:12 PM
#3
Archived author: ohno.hono • Posted: 2024-11-27T22:12:49.661000+00:00
Original source

I will start here thank you for the information
rektbyfaith
11-27-2024, 10:12 PM #3

Archived author: ohno.hono • Posted: 2024-11-27T22:12:49.661000+00:00
Original source

I will start here thank you for the information

rektbyfaith
Administrator
0
11-27-2024, 10:35 PM
#4
Archived author: Xahnder • Posted: 2024-11-27T22:35:33.525000+00:00
Original source

In addition to what Titi mentioned, I find it great to try and load models in WowModelViewer (WMV) (https://wowbay.wordpress.com/2012/01/10/...or-3-3-5a/). It doesn't catch everything, but it's rare that something loads in WMV but won't load in WoW.

One thing to pay attention to is that texture references are relatively resolved in the M2. That means that unless you modify the M2 file after a retroport, you need to ensure it is placed in exactly the same location within your MPQ (first pic).

The model you posted above is working properly in WMV (second pic). If you're having trouble beyond that, it's almost certainly an incorrect value in a DBC.
[Image: image.png?ex=690c79f5&is=690b2875&hm=b6b...5748c20e4&]

[Image: image.png?ex=690c79f5&is=690b2875&hm=274...287d55f21&]
rektbyfaith
11-27-2024, 10:35 PM #4

Archived author: Xahnder • Posted: 2024-11-27T22:35:33.525000+00:00
Original source

In addition to what Titi mentioned, I find it great to try and load models in WowModelViewer (WMV) (https://wowbay.wordpress.com/2012/01/10/...or-3-3-5a/). It doesn't catch everything, but it's rare that something loads in WMV but won't load in WoW.

One thing to pay attention to is that texture references are relatively resolved in the M2. That means that unless you modify the M2 file after a retroport, you need to ensure it is placed in exactly the same location within your MPQ (first pic).

The model you posted above is working properly in WMV (second pic). If you're having trouble beyond that, it's almost certainly an incorrect value in a DBC.
[Image: image.png?ex=690c79f5&is=690b2875&hm=b6b...5748c20e4&]

[Image: image.png?ex=690c79f5&is=690b2875&hm=274...287d55f21&]

rektbyfaith
Administrator
0
11-27-2024, 10:47 PM
#5
Archived author: ohno.hono • Posted: 2024-11-27T22:47:22.295000+00:00
Original source

<@489963862096084994> this is very valuable info thank you. I will make sure to pay attention to this and mess around with my DBC files to see if I incorrectly referenced something along the way.
rektbyfaith
11-27-2024, 10:47 PM #5

Archived author: ohno.hono • Posted: 2024-11-27T22:47:22.295000+00:00
Original source

<@489963862096084994> this is very valuable info thank you. I will make sure to pay attention to this and mess around with my DBC files to see if I incorrectly referenced something along the way.

rektbyfaith
Administrator
0
11-27-2024, 11:50 PM
#6
Archived author: ohno.hono • Posted: 2024-11-27T23:50:40.668000+00:00
Original source

so it seemed to be a skin problem. going into the m2 and changing the nViews to the number of skins and renaming them appropriately seemed to fix the crashing
rektbyfaith
11-27-2024, 11:50 PM #6

Archived author: ohno.hono • Posted: 2024-11-27T23:50:40.668000+00:00
Original source

so it seemed to be a skin problem. going into the m2 and changing the nViews to the number of skins and renaming them appropriately seemed to fix the crashing

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