[DiscordArchive] I've made some pretty rudimentary texture paints on blizzard adt's and am trying to run `ground_dood
[DiscordArchive] I've made some pretty rudimentary texture paints on blizzard adt's and am trying to run `ground_dood
Original source
I've made some pretty rudimentary texture paints on blizzard adt's and am trying to run `ground_doodads_fixing.exe` to regenerate the ground effects.
It spits out the `_new` files fine and dandy. Bundle them into an MPQ and then in game I get the following:
Does anyone have any ideas?
![[Image: unknown.png?ex=690c7533&is=690b23b3&hm=8...11701f485&]](https://cdn.discordapp.com/attachments/415944535718494208/876771082789601280/unknown.png?ex=690c7533&is=690b23b3&hm=875b0836278b9ffd740fb801dca9fb07ddd1333948d03775f2e5a5911701f485&)
rektbyfaith
08-16-2021, 10:15 AM #1Archived author: Deleted User • Posted: 2021-08-16T10:15:16.235000+00:00
Original source
I've made some pretty rudimentary texture paints on blizzard adt's and am trying to run `ground_doodads_fixing.exe` to regenerate the ground effects.
It spits out the `_new` files fine and dandy. Bundle them into an MPQ and then in game I get the following:
Does anyone have any ideas?
Original source
```This issue is caused by the ADT referencing a detail doodad ID that is not given in the DBC, either by saving incorrectly or not editing the DBC correctly. This can be fixed by adding an entry to GroundEffectTextureRec for all IDs or by removing the id from the ADT.
This is a bug that has happened with certain versions of Noggit which should be fixed these days. The detail here is ADT's MCNK's ReallyLowQualityTextureingMap which references an non-existing layer. This is fixed and broken again in up to date versions of Noggit. Loading and saving an ADT with such intermediate a version will fix the issue automatically. This is a known Noggit issue, sorry.
Basically, each chunk can contain 4 textures (each on a layer), which each can have a specific applied groundeffect ID. The ID is further defined within the .dbc, however, this is not important. The most important thing is simple; Wow tries to visual a groundeffect for a texture that is not existing. On a chunk with 3 layers, but 4 ground effects noted, it is bound to lead to a crash.
A simple fix is easy; simply use the texture painter, apply some texture, set it to some size but the lowest speed and apply it onto the adt, until every chunk has 4 layers. The crashes stop.```
rektbyfaith
08-16-2021, 10:30 AM #2Archived author: A2 • Posted: 2021-08-16T10:30:34.918000+00:00
Original source
```This issue is caused by the ADT referencing a detail doodad ID that is not given in the DBC, either by saving incorrectly or not editing the DBC correctly. This can be fixed by adding an entry to GroundEffectTextureRec for all IDs or by removing the id from the ADT.
This is a bug that has happened with certain versions of Noggit which should be fixed these days. The detail here is ADT's MCNK's ReallyLowQualityTextureingMap which references an non-existing layer. This is fixed and broken again in up to date versions of Noggit. Loading and saving an ADT with such intermediate a version will fix the issue automatically. This is a known Noggit issue, sorry.
Basically, each chunk can contain 4 textures (each on a layer), which each can have a specific applied groundeffect ID. The ID is further defined within the .dbc, however, this is not important. The most important thing is simple; Wow tries to visual a groundeffect for a texture that is not existing. On a chunk with 3 layers, but 4 ground effects noted, it is bound to lead to a crash.
A simple fix is easy; simply use the texture painter, apply some texture, set it to some size but the lowest speed and apply it onto the adt, until every chunk has 4 layers. The crashes stop.```
1 Guest(s)
1 Guest(s)