[DiscordArchive] Another question.. File in wow follow the LittleEndian's memory storage right ?
[DiscordArchive] Another question.. File in wow follow the LittleEndian's memory storage right ?
Original source
Another question.. File in wow follow the LittleEndian's memory storage right ?
rektbyfaith
12-31-2021, 05:50 PM #1Archived author: Intemporel • Posted: 2021-12-31T17:50:07.470000+00:00
Original source
Another question.. File in wow follow the LittleEndian's memory storage right ?
Original source
soldan has done some pretty decent amount of model stuff
rektbyfaith
12-31-2021, 05:57 PM #2Archived author: tester • Posted: 2021-12-31T17:57:14.707000+00:00
Original source
soldan has done some pretty decent amount of model stuff
Original source
remove, maybe not, disable maybe yes
rektbyfaith
12-31-2021, 06:05 PM #3Archived author: Intemporel • Posted: 2021-12-31T18:05:25.556000+00:00
Original source
remove, maybe not, disable maybe yes
Original source
```md
uint nParticleEmitters | Start:128h | Size 4h
```
<@!424550803722862610>
If you set the value to 0 it will disable the particle
rektbyfaith
12-31-2021, 06:07 PM #4Archived author: Intemporel • Posted: 2021-12-31T18:07:37.633000+00:00
Original source
```md
uint nParticleEmitters | Start:128h | Size 4h
```
<@!424550803722862610>
If you set the value to 0 it will disable the particle
Original source
Keep the old value in mind, just in case it's not that
rektbyfaith
12-31-2021, 06:08 PM #5Archived author: Intemporel • Posted: 2021-12-31T18:08:36.612000+00:00
Original source
Keep the old value in mind, just in case it's not that
Original source
What determines order of mpq loading? I have 2 cases, one is a texture replacement that shows up in Noggit but not WoW, and another one that displays in neither. Both are in their correct file locations and they have the highest mpq number.
rektbyfaith
12-31-2021, 06:25 PM #6Archived author: whatwere • Posted: 2021-12-31T18:25:44.238000+00:00
Original source
What determines order of mpq loading? I have 2 cases, one is a texture replacement that shows up in Noggit but not WoW, and another one that displays in neither. Both are in their correct file locations and they have the highest mpq number.
Original source
<@!419265958549520385>
1 -> 9 **and after** A -> Z
rektbyfaith
12-31-2021, 06:47 PM #7Archived author: Intemporel • Posted: 2021-12-31T18:47:29.637000+00:00
Original source
<@!419265958549520385>
1 -> 9 **and after** A -> Z
Original source
The textures I'm replacing are in 4, the replacement in 5, not entirely sure what's going on especially since one replacement shows up in Noggit.
rektbyfaith
12-31-2021, 06:50 PM #8Archived author: whatwere • Posted: 2021-12-31T18:50:43.811000+00:00
Original source
The textures I'm replacing are in 4, the replacement in 5, not entirely sure what's going on especially since one replacement shows up in Noggit.
Original source
try to put in patch-A ?
rektbyfaith
12-31-2021, 06:57 PM #9Archived author: Intemporel • Posted: 2021-12-31T18:57:58.008000+00:00
Original source
try to put in patch-A ?
Original source
https://discord.com/channels/40766404101...8838450247
I found the answer !
it's because after write my value qint32 ( use 0x4 byte ) to adress `193E4` i write an `QString::lenght`, **AND** `myStr.lenght()` return an `qsizetype` and use 0x8 byte to `193E0` lol
rektbyfaith
12-31-2021, 07:02 PM #10Archived author: Intemporel • Posted: 2021-12-31T19:02:56.677000+00:00
Original source
https://discord.com/channels/40766404101...8838450247
I found the answer !
it's because after write my value qint32 ( use 0x4 byte ) to adress `193E4` i write an `QString::lenght`, **AND** `myStr.lenght()` return an `qsizetype` and use 0x8 byte to `193E0` lol
1 Guest(s)
1 Guest(s)