Djey

Yeah, HUD and Rims have to be updated in carData.mdb. I only added missing vehicles :) Will try to add them in the coming days. This megapack has all names provided in US language only; for final version all language files should be modified. That means a lot of work.

Although it's hard to be automatized for the moment, I can give you a few steps. Will update TDUF main thread :) --- Edit: head to Q&A (1) for small tutorial on how to add new files : [TDUF] Djey : Tools and Discussion about new modding possibilities | turboduck forum

Hi again, here you are ! Please use with caution ! http://bit.ly/1L1i2bQ (replace carData.mdb file by the one in archive) TDUPE 2.77 is recommended, to switch official names and modded names. http://bit.ly/1AaZmBD :)

Hi fellas, I'm currently updating TDUPE database to unlock all slots and early tests seem to be a success :) ... at least vehicles can be loaded in the app. Did not try to save and run game still. It's for TDUPE 2.77, dunno if that would work with previous version (2.5).

Hi, here is a link for 2.77 version : LINK DOWN and here is a mirror for 2.5 version: LINK DOWN @OP feel free to update post with those ;) --- (beta) Use this car database to be able to modify all vehicle slots : http://bit.ly/1L1i2bQ (beta)

Just use a backup of your database. You have made one before modding, right ? If TDUMT can't open your database even to check for errors, you have to delete your database files because they are corrupted. And you should check your PC for hardware issues, as well.

Hi thanks for you interest in TDUMT :) This car shop originally contains 8 vehicles, but only 5 out of these 8 can be bought. I dunno if it can be changed in database (effect of Bitfield parameter ?) - anyway TDUMT can't and won't ever do that. As soon as one classic vehicle (as DB4) is located in a dealer, all other vehicles are sold like classic ones, so no custom rims or colours are available. As an advice, don't mix modern and classic cars in a same building.

If you need even more precise settings, torque curve (in btrq file) will be adjustable soon. Stay tuned :)

Tutorials 2 & 3 just added :) See updated first post. --- I've updated structure package with PMI and cameras.bin support, as well! Dropbox - TDUF-structures.zip

Thanks for the messages anyhow, I keep my hopes up that one day regular players can enjoy what's now preparing under the hood.

First tutorial just added: opening existing file :D Please let me know if some things need to be precised.

Announcement : TDUF toolset 0.2.1 (hotfix) now available ! * General: provides updated file structures * General: add limited support to PMI files (TDU World Map) * Library/structure: supports FPOINT fields, 16-bit (2 bytes) * Library/structure: supports field sizes read in repeater fields. See first post to download!

No, that's me :) There was a mess in bbcode ! Link now fixed, enjoy!

In fact, the .btrq files have been encrypted by EDEN devs :) You should use tdudec to encrypt/decrypt it (with non-savegame mode I believe) I will add a simple btrq read/write example as tutorial. Also, next TDUF version (0.3.0) will handle encrypted files automatically.

Thanks ! Idea is to use this tool to help with first decoding Cameras.bin file. In a while, we'll have our own 'TDUF way' to modify this file and add contents into it :) ---- Announcement : TDUF toolset 0.2.0 now available ! So, what's new ? * General: provides file structures in the release package, to be used with FileTool * Command Line: requests admin access automatically * DatabaseTool: new limited, check operation, performing integrity check of TDU database (need to be extracted and decrypted with additional tools, first) * FileTool (new!): exports TDU files to/from JSON format when provided a structure file * Library/structure: supports new field type : UNKNOWN (values to be discovered, still) * Library/structure: supports new field type : FPOINT (floating-point, 32 bit) * Library/structure: supports formulas and references in field size attribute * Library/parsing: supports endianness See first post to download!

Both, ideally. I think that's possible. A new cam set can be set much like we can add a vehicle slot in database. Customizing cam values is a bit trickier, I hope camera.bin editor works, to help with finding interesting fields in the file.

okay, I'll stop confusing this thread now :D

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.

Thanks for your feedback and solution. Btw, you should not need to install Magic Map after 1.68b, as 1.68b already patches TDU install with a Magic Map. Indeed, some genuine Cameras.bin may not be the one expected and thus make TDUMT to crash.

Yeah, that's been a while - but I made long breaks as well (and many others in the future, probably). :) I totally understand and assume that these contents are for advanced modders and developpers overall. But since TDUMT toolset lacked of documentation, I don't want TDUF prevents motivated people to have a look at it, as that did ages ago.

-Reserved- File structure description is complete, I think. Feel free to ask if you shall need some things to be clarified! ;)

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

Sorry, I can't really understand what was your issue, and how Commodo AV can be related to it :confused: If TDUPE works, TDUMT should work as well. Important : do not run TDUPE and TDUMT at the same time; please save your changes then close app to run the other tool.

That's why best sound mods are so rare and hard to achieve. The best results will be observed with recordings in mostly 'studio' environments :)

Airports as drag strips, finally :D