Djey

It start to looks pretty good now ;) Still lots of work but the basics are here !

Found out a way how to get the cameras.bin file working
 
[ATTACH]22440[/ATTACH]
 
You just have to change the address to match the folder where its actually located on your computer.
 
Here's some things I found out while messing with it:
 
-It only changes the Cockpit_Front camera
-Going below/above some value numbers will make the camera behave like a motorcycle one
-Going below/above will set it to target/source RHD on TDUMT, it seems to be related.
-It doesn't affect/activate idle camera slots like DB7 AR1 or Cobalt SS

So should I guess that handling Cameras.bin file is a feature we need even quicker than stated before ? :D
 
When properly handled, TDUF will generate a JSON file to be easily edited with any application / text editor / or utility web site.
 
Of course, a modified JSON file can be converted to original file format back ;)
 
Here is what the new FileTool thread will deal about.

So should I guess that handling Cameras.bin file is a feature we need even quicker than stated before ? :D
 
When properly handled, TDUF will generate a JSON file to be easily edited with any application / text editor / or utility web site.
 
Of course, a modified JSON file can be converted to original file format back ;)
 
Here is what the new FileTool thread will deal about.

It doesn't really talk to me all this stuff but I'm sure it's gonna be beneficial for many modders :) It's great to see you developing all this Djey. Can't believe TDUMT was released I think in 2009 and 6 years later you're still doing tools for TDU. Thank you so much for still improving the game today ;)

Closed thread: you'll find updated documentation within TDUCP project:
 
https://github.com/djey47/tdu-cp/wiki/TDUF-Reverse-Engineering-Files
 


[TDUF] Understand TDU files with FileTool

Hello,
this thread will explain how to use a TDUF feature, that is FileTool.
Also, it's a place where people may collaborate, to help with understanding of TDU Files.
 
PRE-REQUISITES
 

Installed TDUF Toolset (0.2.1+): http://forum.turboduck.net/threads/32570-TDUF-Djey-Tools-and-Discussion-about-new-modding-possibilities
Web browser (easy!)
Hex Editor software your are comfortable with (optional, but recommended)
Sense of logic (a little)
Free time (a bunch)
Fierceness!
That's all for now :)

 
TUTORIALS
If you'd need to remember only one thing: you don't have to know the complete structure of a file to begin playing with it. Favor baby steps ;)
 
1. OPENING EXISTING FILE
 
 
2. EDITING EXISTING FILE
 
 
3. SAVING EXISTING FILE
 
 
4. ADVANCED: ADD SUPPORT FOR NEW FILE
TODO
 
FILE STRUCTURE UPDATE
Here are all latest known file structures to play with. Feel free to test, modify, understand and enhance them ;)

DOWNLOAD


 
REFERENCE
FileTool instructions

applyjson : writes a json back to TDU file.
decrypt : make XTEA encrypted TDU file readable again.
encrypt : transform file contents with XTEA algorithm - used by some (db, btrq, playersave...).
jsonify : converts a supported TDU file to JSON file, allowing it to be edited.

 
File Structure reference
Example:
First level information reference:

name : to identify file you want to decode
littleEndian : true/false, indicates byte order - most of TDU files are little endian
cryptoMode : in case of encrypted file, indicates the encryption mode used - 0=Savegames, 1=Others (db, btrq...)
fields : list of fields contained in this TDU file (see Field reference below)

Note that cryptoMode set to 0 or 1 will make file to be automatically encrypted/decrypted by FileTool, so you won't have to.
 
Field/Subfield reference:

name : give clearest meaning as possible - must be unique !
type: one of predefined values indicating data kind (see Field types below)
signed: (from version 0.6.0) true if value should be signed, false otherwise. When absent, value is considered as unsigned.
size: number of bytes used by this field (see Size tricks below)
subFields: used when field type is a REPEATER, list of repeated fields

Field types:

TEXT: clear text data
INTEGER: an integer, numeric value (e.g.: 53)
FPOINT: a floating-point, numeric value (e.g : 235,6547)
GAP: an area filled with 0's
UNKNOWN: to be discovered still
REPEATER: embeds a list of complex values (with their own layout)

Size tricks:
- Size attribute is basically the number of bytes used by corresponding field, but with some exceptions:

When UNKNOWN field type, it is not mandatory - if omitted, the field is expected to occupy all remaining bytes in file.
When REPEATER, its meaning is the count of repeated items.
When REPEATER, it's not mandatory either - if omitted, the sub-items are expected to be repeated till the end of the file.

Important: when INTEGER field type, only supported values are 1 or 2 or 4.
When FPOINT field type, 2 or 4 are supported.
 
- Value of this attribute may also be a formula
e.g : size: "=(2+3)*6" will interpret it as 30.
 
- A formula may contain a reference to a previously read field
e.g size: "=5*?fieldName?" will interpret it as 30, as long a field named fieldName has been read before and has a value of 6.
Please note:

Field reference writes itself as field name declared earlier in structure, surrounded by question marks characters (?)
Concerning repeated fields, they get unique name each, following: repeaterFieldName[itemRank].repeatedFieldName
e.g ?itemList[5].speed?, will reference speed field, repeated under itemList field, at rank 6 (as first item is always at rank 0).
Also, it is possible to reference a repeated field with the same rank without giving the full name:
e.g ?speed?, will reference speed field, repeated under the same field as current one and as same rank.

 
CREDITS

2CVSUPERGT &TDUCK community => BIN (cameras) research
mcv100 => BTRQ research
Speeder => PMI/SHK research

Closed thread: you'll find updated documentation within TDUCP project:
 
https://github.com/djey47/tdu-cp/wiki/TDUF-Reverse-Engineering-Files
 


[TDUF] Understand TDU files with FileTool

Hello,
this thread will explain how to use a TDUF feature, that is FileTool.
Also, it's a place where people may collaborate, to help with understanding of TDU Files.
 
PRE-REQUISITES
 

Installed TDUF Toolset (0.2.1+): http://forum.turboduck.net/threads/32570-TDUF-Djey-Tools-and-Discussion-about-new-modding-possibilities
Web browser (easy!)
Hex Editor software your are comfortable with (optional, but recommended)
Sense of logic (a little)
Free time (a bunch)
Fierceness!
That's all for now :)

 
TUTORIALS
If you'd need to remember only one thing: you don't have to know the complete structure of a file to begin playing with it. Favor baby steps ;)
 
1. OPENING EXISTING FILE
 
 
2. EDITING EXISTING FILE
 
 
3. SAVING EXISTING FILE
 
 
4. ADVANCED: ADD SUPPORT FOR NEW FILE
TODO
 
FILE STRUCTURE UPDATE
Here are all latest known file structures to play with. Feel free to test, modify, understand and enhance them ;)

DOWNLOAD


 
REFERENCE
FileTool instructions

applyjson : writes a json back to TDU file.
decrypt : make XTEA encrypted TDU file readable again.
encrypt : transform file contents with XTEA algorithm - used by some (db, btrq, playersave...).
jsonify : converts a supported TDU file to JSON file, allowing it to be edited.

 
File Structure reference
Example:
First level information reference:

name : to identify file you want to decode
littleEndian : true/false, indicates byte order - most of TDU files are little endian
cryptoMode : in case of encrypted file, indicates the encryption mode used - 0=Savegames, 1=Others (db, btrq...)
fields : list of fields contained in this TDU file (see Field reference below)

Note that cryptoMode set to 0 or 1 will make file to be automatically encrypted/decrypted by FileTool, so you won't have to.
 
Field/Subfield reference:

name : give clearest meaning as possible - must be unique !
type: one of predefined values indicating data kind (see Field types below)
signed: (from version 0.6.0) true if value should be signed, false otherwise. When absent, value is considered as unsigned.
size: number of bytes used by this field (see Size tricks below)
subFields: used when field type is a REPEATER, list of repeated fields

Field types:

TEXT: clear text data
INTEGER: an integer, numeric value (e.g.: 53)
FPOINT: a floating-point, numeric value (e.g : 235,6547)
GAP: an area filled with 0's
UNKNOWN: to be discovered still
REPEATER: embeds a list of complex values (with their own layout)

Size tricks:
- Size attribute is basically the number of bytes used by corresponding field, but with some exceptions:

When UNKNOWN field type, it is not mandatory - if omitted, the field is expected to occupy all remaining bytes in file.
When REPEATER, its meaning is the count of repeated items.
When REPEATER, it's not mandatory either - if omitted, the sub-items are expected to be repeated till the end of the file.

Important: when INTEGER field type, only supported values are 1 or 2 or 4.
When FPOINT field type, 2 or 4 are supported.
 
- Value of this attribute may also be a formula
e.g : size: "=(2+3)*6" will interpret it as 30.
 
- A formula may contain a reference to a previously read field
e.g size: "=5*?fieldName?" will interpret it as 30, as long a field named fieldName has been read before and has a value of 6.
Please note:

Field reference writes itself as field name declared earlier in structure, surrounded by question marks characters (?)
Concerning repeated fields, they get unique name each, following: repeaterFieldName[itemRank].repeatedFieldName
e.g ?itemList[5].speed?, will reference speed field, repeated under itemList field, at rank 6 (as first item is always at rank 0).
Also, it is possible to reference a repeated field with the same rank without giving the full name:
e.g ?speed?, will reference speed field, repeated under the same field as current one and as same rank.

 
CREDITS

2CVSUPERGT &TDUCK community => BIN (cameras) research
mcv100 => BTRQ research
Speeder => PMI/SHK research

Closed thread: you'll find updated documentation within TDUCP project:
 
https://github.com/djey47/tdu-cp/wiki/TDUF-Reverse-Engineering-Files
 


[TDUF] Understand TDU files with FileTool

Hello,
this thread will explain how to use a TDUF feature, that is FileTool.
Also, it's a place where people may collaborate, to help with understanding of TDU Files.
 
PRE-REQUISITES
 

Installed TDUF Toolset (0.2.1+): http://forum.turboduck.net/threads/32570-TDUF-Djey-Tools-and-Discussion-about-new-modding-possibilities
Web browser (easy!)
Hex Editor software your are comfortable with (optional, but recommended)
Sense of logic (a little)
Free time (a bunch)
Fierceness!
That's all for now :)

 
TUTORIALS
If you'd need to remember only one thing: you don't have to know the complete structure of a file to begin playing with it. Favor baby steps ;)
 
1. OPENING EXISTING FILE
 
 
2. EDITING EXISTING FILE
 
 
3. SAVING EXISTING FILE
 
 
4. ADVANCED: ADD SUPPORT FOR NEW FILE
TODO
 
FILE STRUCTURE UPDATE
Here are all latest known file structures to play with. Feel free to test, modify, understand and enhance them ;)

DOWNLOAD


 
REFERENCE
FileTool instructions

applyjson : writes a json back to TDU file.
decrypt : make XTEA encrypted TDU file readable again.
encrypt : transform file contents with XTEA algorithm - used by some (db, btrq, playersave...).
jsonify : converts a supported TDU file to JSON file, allowing it to be edited.

 
File Structure reference
Example:
First level information reference:

name : to identify file you want to decode
littleEndian : true/false, indicates byte order - most of TDU files are little endian
cryptoMode : in case of encrypted file, indicates the encryption mode used - 0=Savegames, 1=Others (db, btrq...)
fields : list of fields contained in this TDU file (see Field reference below)

Note that cryptoMode set to 0 or 1 will make file to be automatically encrypted/decrypted by FileTool, so you won't have to.
 
Field/Subfield reference:

name : give clearest meaning as possible - must be unique !
type: one of predefined values indicating data kind (see Field types below)
signed: (from version 0.6.0) true if value should be signed, false otherwise. When absent, value is considered as unsigned.
size: number of bytes used by this field (see Size tricks below)
subFields: used when field type is a REPEATER, list of repeated fields

Field types:

TEXT: clear text data
INTEGER: an integer, numeric value (e.g.: 53)
FPOINT: a floating-point, numeric value (e.g : 235,6547)
GAP: an area filled with 0's
UNKNOWN: to be discovered still
REPEATER: embeds a list of complex values (with their own layout)

Size tricks:
- Size attribute is basically the number of bytes used by corresponding field, but with some exceptions:

When UNKNOWN field type, it is not mandatory - if omitted, the field is expected to occupy all remaining bytes in file.
When REPEATER, its meaning is the count of repeated items.
When REPEATER, it's not mandatory either - if omitted, the sub-items are expected to be repeated till the end of the file.

Important: when INTEGER field type, only supported values are 1 or 2 or 4.
When FPOINT field type, 2 or 4 are supported.
 
- Value of this attribute may also be a formula
e.g : size: "=(2+3)*6" will interpret it as 30.
 
- A formula may contain a reference to a previously read field
e.g size: "=5*?fieldName?" will interpret it as 30, as long a field named fieldName has been read before and has a value of 6.
Please note:

Field reference writes itself as field name declared earlier in structure, surrounded by question marks characters (?)
Concerning repeated fields, they get unique name each, following: repeaterFieldName[itemRank].repeatedFieldName
e.g ?itemList[5].speed?, will reference speed field, repeated under itemList field, at rank 6 (as first item is always at rank 0).
Also, it is possible to reference a repeated field with the same rank without giving the full name:
e.g ?speed?, will reference speed field, repeated under the same field as current one and as same rank.

 
CREDITS

2CVSUPERGT &TDUCK community => BIN (cameras) research
mcv100 => BTRQ research
Speeder => PMI/SHK research

Closed thread: you'll find updated documentation within TDUCP project:
 
https://github.com/djey47/tdu-cp/wiki/TDUF-Reverse-Engineering-Files
 


[TDUF] Understand TDU files with FileTool

Hello,
this thread will explain how to use a TDUF feature, that is FileTool.
Also, it's a place where people may collaborate, to help with understanding of TDU Files.
 
PRE-REQUISITES
 

Installed TDUF Toolset (0.2.1+): http://forum.turboduck.net/threads/32570-TDUF-Djey-Tools-and-Discussion-about-new-modding-possibilities
Web browser (easy!)
Hex Editor software your are comfortable with (optional, but recommended)
Sense of logic (a little)
Free time (a bunch)
Fierceness!
That's all for now :)

 
TUTORIALS
If you'd need to remember only one thing: you don't have to know the complete structure of a file to begin playing with it. Favor baby steps ;)
 
1. OPENING EXISTING FILE
 
 
2. EDITING EXISTING FILE
 
 
3. SAVING EXISTING FILE
 
 
4. ADVANCED: ADD SUPPORT FOR NEW FILE
TODO
 
FILE STRUCTURE UPDATE
Here are all latest known file structures to play with. Feel free to test, modify, understand and enhance them ;)

DOWNLOAD


 
REFERENCE
FileTool instructions

applyjson : writes a json back to TDU file.
decrypt : make XTEA encrypted TDU file readable again.
encrypt : transform file contents with XTEA algorithm - used by some (db, btrq, playersave...).
jsonify : converts a supported TDU file to JSON file, allowing it to be edited.

 
File Structure reference
Example:
First level information reference:

name : to identify file you want to decode
littleEndian : true/false, indicates byte order - most of TDU files are little endian
cryptoMode : in case of encrypted file, indicates the encryption mode used - 0=Savegames, 1=Others (db, btrq...)
fields : list of fields contained in this TDU file (see Field reference below)

Note that cryptoMode set to 0 or 1 will make file to be automatically encrypted/decrypted by FileTool, so you won't have to.
 
Field/Subfield reference:

name : give clearest meaning as possible - must be unique !
type: one of predefined values indicating data kind (see Field types below)
signed: (from version 0.6.0) true if value should be signed, false otherwise. When absent, value is considered as unsigned.
size: number of bytes used by this field (see Size tricks below)
subFields: used when field type is a REPEATER, list of repeated fields

Field types:

TEXT: clear text data
INTEGER: an integer, numeric value (e.g.: 53)
FPOINT: a floating-point, numeric value (e.g : 235,6547)
GAP: an area filled with 0's
UNKNOWN: to be discovered still
REPEATER: embeds a list of complex values (with their own layout)

Size tricks:
- Size attribute is basically the number of bytes used by corresponding field, but with some exceptions:

When UNKNOWN field type, it is not mandatory - if omitted, the field is expected to occupy all remaining bytes in file.
When REPEATER, its meaning is the count of repeated items.
When REPEATER, it's not mandatory either - if omitted, the sub-items are expected to be repeated till the end of the file.

Important: when INTEGER field type, only supported values are 1 or 2 or 4.
When FPOINT field type, 2 or 4 are supported.
 
- Value of this attribute may also be a formula
e.g : size: "=(2+3)*6" will interpret it as 30.
 
- A formula may contain a reference to a previously read field
e.g size: "=5*?fieldName?" will interpret it as 30, as long a field named fieldName has been read before and has a value of 6.
Please note:

Field reference writes itself as field name declared earlier in structure, surrounded by question marks characters (?)
Concerning repeated fields, they get unique name each, following: repeaterFieldName[itemRank].repeatedFieldName
e.g ?itemList[5].speed?, will reference speed field, repeated under itemList field, at rank 6 (as first item is always at rank 0).
Also, it is possible to reference a repeated field with the same rank without giving the full name:
e.g ?speed?, will reference speed field, repeated under the same field as current one and as same rank.

 
CREDITS

2CVSUPERGT &TDUCK community => BIN (cameras) research
mcv100 => BTRQ research
Speeder => PMI/SHK research

Closed thread: you'll find updated documentation within TDUCP project:
 
https://github.com/djey47/tdu-cp/wiki/TDUF-Reverse-Engineering-Files
 


[TDUF] Understand TDU files with FileTool

Hello,
this thread will explain how to use a TDUF feature, that is FileTool.
Also, it's a place where people may collaborate, to help with understanding of TDU Files.
 
PRE-REQUISITES
 

Installed TDUF Toolset (0.2.1+): http://forum.turboduck.net/threads/32570-TDUF-Djey-Tools-and-Discussion-about-new-modding-possibilities
Web browser (easy!)
Hex Editor software your are comfortable with (optional, but recommended)
Sense of logic (a little)
Free time (a bunch)
Fierceness!
That's all for now :)

 
TUTORIALS
If you'd need to remember only one thing: you don't have to know the complete structure of a file to begin playing with it. Favor baby steps ;)
 
1. OPENING EXISTING FILE
 
 
2. EDITING EXISTING FILE
 
 
3. SAVING EXISTING FILE
 
 
4. ADVANCED: ADD SUPPORT FOR NEW FILE
TODO
 
FILE STRUCTURE UPDATE
Here are all latest known file structures to play with. Feel free to test, modify, understand and enhance them ;)

DOWNLOAD


 
REFERENCE
FileTool instructions

applyjson : writes a json back to TDU file.
decrypt : make XTEA encrypted TDU file readable again.
encrypt : transform file contents with XTEA algorithm - used by some (db, btrq, playersave...).
jsonify : converts a supported TDU file to JSON file, allowing it to be edited.

 
File Structure reference
Example:
First level information reference:

name : to identify file you want to decode
littleEndian : true/false, indicates byte order - most of TDU files are little endian
cryptoMode : in case of encrypted file, indicates the encryption mode used - 0=Savegames, 1=Others (db, btrq...)
fields : list of fields contained in this TDU file (see Field reference below)

Note that cryptoMode set to 0 or 1 will make file to be automatically encrypted/decrypted by FileTool, so you won't have to.
 
Field/Subfield reference:

name : give clearest meaning as possible - must be unique !
type: one of predefined values indicating data kind (see Field types below)
signed: (from version 0.6.0) true if value should be signed, false otherwise. When absent, value is considered as unsigned.
size: number of bytes used by this field (see Size tricks below)
subFields: used when field type is a REPEATER, list of repeated fields

Field types:

TEXT: clear text data
INTEGER: an integer, numeric value (e.g.: 53)
FPOINT: a floating-point, numeric value (e.g : 235,6547)
GAP: an area filled with 0's
UNKNOWN: to be discovered still
REPEATER: embeds a list of complex values (with their own layout)

Size tricks:
- Size attribute is basically the number of bytes used by corresponding field, but with some exceptions:

When UNKNOWN field type, it is not mandatory - if omitted, the field is expected to occupy all remaining bytes in file.
When REPEATER, its meaning is the count of repeated items.
When REPEATER, it's not mandatory either - if omitted, the sub-items are expected to be repeated till the end of the file.

Important: when INTEGER field type, only supported values are 1 or 2 or 4.
When FPOINT field type, 2 or 4 are supported.
 
- Value of this attribute may also be a formula
e.g : size: "=(2+3)*6" will interpret it as 30.
 
- A formula may contain a reference to a previously read field
e.g size: "=5*?fieldName?" will interpret it as 30, as long a field named fieldName has been read before and has a value of 6.
Please note:

Field reference writes itself as field name declared earlier in structure, surrounded by question marks characters (?)
Concerning repeated fields, they get unique name each, following: repeaterFieldName[itemRank].repeatedFieldName
e.g ?itemList[5].speed?, will reference speed field, repeated under itemList field, at rank 6 (as first item is always at rank 0).
Also, it is possible to reference a repeated field with the same rank without giving the full name:
e.g ?speed?, will reference speed field, repeated under the same field as current one and as same rank.

 
CREDITS

2CVSUPERGT &TDUCK community => BIN (cameras) research
mcv100 => BTRQ research
Speeder => PMI/SHK research

If someone has a problem with (unable to load the vehicle requested date):
 
1. Clean install Test Drive Unlimited
 
1a. Install MegaCarPack
 
2. Install the patch 1.67d [found acting versions - Click ;)] - That's not my upload !
 
3.Install the patch 1.68b [without 1.67d did not want to install]
 
4.Magicmaps Click :)
 
5.TDU Modding Tools [1.16.2] Click !;)
 
6.Create new shortcut to TestDriveUnlimited.exe
 
 
 
7.[Paste this file into the folder xml <root of TDU>] Click ;)
 
8.Set path to Root TDU Folder - in TDUMT (File -> Settings -> Main -> TDU Root)
 
9. O.o. Wow! It works. :nuts:

ohh yh that would be so EPIC:drool: :drool: :drool: :drool: :drool: :drool: :drool: :drool:
the whole airport with street mesh and nice Hq textures :O

Yes!! Get rid of that horrible bumpy runway that limits your speed..

Airports as drag strips, finally :D

Airports as drag strips, finally :D

Airports as drag strips, finally :D

Airports as drag strips, finally :D

Airports as drag strips, finally :D

Hi, Tob-Racer !
 
Maybe this document will contain interesting things,
http://bit.ly/qniFQd
 
(be warned that some of contents are obsolete, though ;) )

:clap: Moddingly speaking, 2014 did end well and 2015 is starting even better, way better than expected.
 
TDUF 0.2.0 is in great way to release, it will provide features to reverse engineer game files.
I hope it will be useful to understand those and speed'up the project ;)

:clap: Moddingly speaking, 2014 did end well and 2015 is starting even better, way better than expected.
 
TDUF 0.2.0 is in great way to release, it will provide features to reverse engineer game files.
I hope it will be useful to understand those and speed'up the project ;)

:clap: Moddingly speaking, 2014 did end well and 2015 is starting even better, way better than expected.
 
TDUF 0.2.0 is in great way to release, it will provide features to reverse engineer game files.
I hope it will be useful to understand those and speed'up the project ;)

:clap: Moddingly speaking, 2014 did end well and 2015 is starting even better, way better than expected.
 
TDUF 0.2.0 is in great way to release, it will provide features to reverse engineer game files.
I hope it will be useful to understand those and speed'up the project ;)

:clap: Moddingly speaking, 2014 did end well and 2015 is starting even better, way better than expected.
 
TDUF 0.2.0 is in great way to release, it will provide features to reverse engineer game files.
I hope it will be useful to understand those and speed'up the project ;)

Here is a list of misc. tutorials and info threads, I hope there will be useful.
 
> TDU Mod FAQ (by thunderhawk17382)
> List : .bnk Exterior and Interior - What the File Names Refer To
> Best Cameras and IK's (compliant with TDUMT 1.14 and patch 1.68a) (by Kurgan777)
> How add new name in TDU Modding Tools (by reventon09)
> How add new color to cars with TDUMT (by reventon09)
> Using groups for installer (by edwin)
> Change camera and IK (LHD/RHD) (by DJvitas)