TXD Workshop 3.4 BETA 2

[[enforcA]]

hi there and hi Delfi

 

i have something that might or might not be important but i wanted to let you know, you know that sometimes (or mostly always(?)) the game freezes when you edit a *.txd texture via TXD Workshop 3.4 BETA 2, ok? so i took a look with hex workshop on the edited and unedited *.txd file and there was one thing that was (always(?)) missing, the last lines of the code, i make an example:

 

original unedited Player/sneakerprowht.txd *.txd file:

 

goes from address 0x00000000 to 0x00004800

 

with TXD Workshop 3.4 BETA 2 edited Player/sneakerprowht.txd *.txd file:

 

goes only from address 0x00000000 to 0x000040A8

 

when testing it in-game the game will freeze

 

now i added the last missing lines to the edited *.txd file, tested it in-game and what happened? the game did run just perfect like it should, so i don't know but maybe it helps you with your great TXD Workshop tool

 

please reply on this so that i get feedback if it helped you

 

greetings from germany and sorry that i couldn't describe it better in english

Edited June 18, 2005 by [enforcA]

[Warlord2005]

Nice find there it actualy works

 

Edited June 18, 2005 by Warlord2005

[demonj0e]

hey can anyone point me in direction of the 3.4 beta 2

and do new textures work in game now?

[Warlord2005]

 

Gtatools here u can get it but remember u cant replace every texture cuz its still unstable but it wont take that loong untill next version is out whit the help Delfi got from [enforcA]

[JernejL]

' date='Jun 18 2005, 15:24'] original unedited Player/sneakerprowht.txd *.txd file:

 

goes from address 0x00000000 to 0x00004800

 

with TXD Workshop 3.4 BETA 2 edited Player/sneakerprowht.txd *.txd file:

 

goes only from address 0x00000000 to 0x000040A8

i don't understand, are there missing bytes or size mismatch or something?

 

all saved files parse with steve's rw analyse just nicely

so they shouldn't have any bytes missing..

 

send me the original, edited and fixed version of file and i'll have a look.

 

[[enforcA]]

,Jun 18 2005, 15:24] original unedited Player/sneakerprowht.txd *.txd file:

 

goes from address 0x00000000 to 0x00004800

 

with TXD Workshop 3.4 BETA 2 edited Player/sneakerprowht.txd *.txd file:

 

goes only from address 0x00000000 to 0x000040A8

i don't understand, are there missing bytes or size mismatch or something?

 

all saved files parse with steve's rw analyse just nicely

so they shouldn't have any bytes missing..

 

send me the original, edited and fixed version of file and i'll have a look.

yes, there are missing bytes at the end of the (edited) txd file, it's just empty content that is missing, but in the past it showed that this empty part is important

 

by adding this part to the edited txd file (by using a hex editor) the game won't crush, the textures work perfect, just everything works fine..

 

some textures don't need to get fixed because they don't end with this empty part (for example: ..\models\txd\LOADSCS.txd) but most (or nearly all?) in-game textures do end with this empty part

 

but take a look at this for yourself, like you wanted it:

 

http://www.venylsrecords.com/private/gtasa/pc/txd.zip

 

the *.zip includes the unedited original of the txd, the edited txd and the fixed txd

 

the used *.bmp image (saved with photoshop)

 

and an example that shows that it worked just fine in-game

 

the txd i used as example was denimsgang.txd from player.img

 

..

 

so, i hope this helps you, and thanks for your feedback

[MiLO83]

word it works. copy and paste the 00's at the end of the file.

 

 

- MiLO83

 

Edit : Original file as saved in TXD Workshop didn't work.

Edited June 20, 2005 by MiLO83

[JernejL]

that is vierd, are you sure it is not the img editor's problem that cuts data away? which img editor did you use? it makes little sense that this would break it, maybe the img

editor doesn't correctly allocate padding data and contains garbage, can you edit, save

without fixing, import and then re-export this same txd from the img please?

 

it would clear things up better, i think it is img editor problem.

 

 

[[enforcA]]

 

that is vierd, are you sure it is not the img editor's problem that cuts data away? which img editor did you use? it makes little sense that this would break it, maybe the img

editor doesn't correctly allocate padding data and contains garbage, can you edit, save

without fixing, import and then re-export this same txd from the img please?

 

it would clear things up better, i think it is img editor problem.

ah .. you are right!!

 

i know the problem yet:

 

i tested it with both img editors (img tool and ultimate editor, both newest versions of it)

 

i did exactly what you said

 

here is what happened:

 

(side note: i did not manipulate the edited txd files with hex editor)

 

img tool:

 

- it exported the txd with empty ending (it had the correct size of the empty ending)

- i edited and saved the txd with txd workshop, it saved the txd without empty ending

- i imported it with img tool and exported the txd again, the txd got the needed empty ending (it had the correct size of the empty ending)

 

the img tool worked fine and the file size of the img file didn't change

 

ultimate editor:

 

- it exported the txd with empty ending (it had the correct size of the empty ending)

- i edited and saved the txd with txd workshop, it saved the txd without empty ending

- i imported it with ultimate editor and exported the txd again, the txd got an empty ending but the size of this empty ending was at least doubled (so the empty ending had an incorrect size), also i noticed that the ultimate editor needed much more time to re-export the edited txd

 

the ultimate editor didn't work fine, the file size of the img file increased from edit to edit, that's also the reason why my player.img file has now a size of over 120 mb

 

....

 

so the problem is or might be the ultimate editor, but i have to say something to this case, when i installed it, it asked me 2 times if i want to keep my *.dll file because the dll file that came with ultimate editor was "not newer" than the version i have already of this dll file, so i kept my newer dll file, all together it were 2 dll files that brought up this ("not newer... want to keep?..") message, maybe it has to do with this 2 dlls, i don't know, but i don't want to test it

 

also i am wondering why the img editors add those empty content to the txd file and not the txd editors?!? for me it would make more sense if the txd editors would write this empty end to the edited txd files, because if you extract an original txd file, it also has the empty content at the end

 

greetings from germany, i hope that my description is understandable^^

 

edit:

 

i also tested it in-game with both versions of an edited txd,

 

version 1 = edited txd saved with txd workshop

version 2 = edited txd saved with txd workshop and edited with hex workshop (by adding the empty content at the end of the file)

 

both versions just run perfect with "img tool v2", the img tool seems to have no problems with "if there is the empty content at the end of the txd or not", it just runs fine in-game, so it seems to me that there is no more need for editing the edited txd with the hex editor, if you use the "img tool v2"

 

thank you very much delfi for clearing this up

 

final test results:

 

- problem is caused by the "ultimate editor"

- if you use "img tool v2", you don't have to fix/edit the edited txd with hex workshop, you can, but you don't need to do this, both works with img tool

Edited June 21, 2005 by [enforcA]

[JernejL]

just as i expected, it was suspicious and vierd that adding useless data to the end

of file would make it work because it had made no sense, obviously ultimate editor

has a bug with file internal data alingment, the empty space after end of file comes

from img files where all data is aligned and padded to zeroes to every 2048 bytes.

 

report the bug to gta:UE people, they must fix it.