Skip to content

TDUMT PatchEditor Patching Game

Jerome Canler edited this page Jun 14, 2018 · 1 revision

Patch Editor’s quick tour:

For now, have a look at: http://syfworld.free.fr/tdu/files/Guide-1.11/patchEditor.html

Patching FAQ!

About the physics for the auto installer, how can I use settings I made from TDUPE?

Dredgy and I have made a bridge between our tools. When exported with TDUPE, use Import instruction feature in TDUMT Patch Editor (Edit > Import instruction(s)) and choose xml file. A new updateDatabase instruction will be added to the list.

What are spaces between values in database instructions?

Those are TAB characters, so I recommend you to insert them:

  • either by using an advanced text editor (I’m working with pspad), allowing to put special characters such as TABs;
  • either by putting your value line in MS EXCEL cells (1 value per cell) then copy-pasting whole line into a text editor;
  • or by using Insert tab link in Instruction Value box (Patch Editor).

How to install vehicle mod over another slot?

If you need to adapt physics to a different slot, there's no automatized processing yet. You should manually modify the physics line using the TDU decrypter and your notepad. Then copy-paste modified line into patch editor instruction details. Knowledge of TDU database is more than required, then;

How can I replace new colors what I've made with TDUMT Vehicle Manager with patching?

You'll have to set new colors in Vehicle Manager, get database lines in decrypted files then paste them in a new updateDatabase instruction.

How can I add/set new names for a vehicle slot?

-Brands subject will be covered later as it does not work the same way-

  • If you use 1.68b patch, some brands and names are included in it already;
  • If not and for other names you have to create them with the updateResource instruction in Patch Editor:
  • resourceFileName : CarPhysicsData
  • resourceValues : 15654545|Model1||1566554|Model2 etc...

, where numbers can be chosen freely, but must not exist already to prevent conflicts. Check in DB Resource editor to know.

Then run this short patch and check if those names are now available in Vehicle Manager => Datasheet. If so, assign those new names to your car, save changes, and see if it works in game.

So now the only way is to go on using TDUPE and its export feature for the slot you’ve just modified. It will generate an .xml file to be put onto your desktop (for example). Refer to TDUPE help for additional information. Then, back to TDUMT and Patch Editor, choose Edit > Import instruction(s) feature and select that .xml file. It will add an updateDatabase instruction to the list. As a result, the patch will override vehicle physics and names. So it’s important to export-import again, each time you’ve changed some physics for that vehicle slot. See instruction reference below about updateResource and updateDatabase for details.

How to export parameters from a modified rim (e.g modified size) ?

Let’s start with the data of the rim you’ve extracted from game files (manually or via Dredgy’s TDUUT): 1243811857;57465512;61976512;5487562;225;35;19;285;35;19;2000;6;57465512;550758512;550758512;0;

Then, you should add an updateDatabase instruction with following parameters:

  • resourceFileName : Rims
  • resourceValues : (the first number in your values above)|(your values above)

that’s to say: 1243811857|1243811857[TAB]57465512[TAB]61976512[TAB]5487562[TAB]225[TAB]35[TAB]19[TAB]285<[TAB]35[TAB]19[TAB]2000[TAB]6[TAB]57465512[TAB]550758512[TAB]550758512[TAB]0

, where [TAB] stands for tabulation character.

See instruction reference about updateDatabase for details: https://github.com/djey47/tdu-cp/wiki/TDUMT-Patch-Instructions-Reference.

Putting install instructions into groups.

First, follow edwin’s tutorial link: http://forum.tdu-central.com/showpost.php?p=357890&postcount=336 While that, you can always download some mods from 2CVSUPERGT or TDUZoqqer and load install.pch file into Database Editor. Then just have a look at it, there are plenty of things to learn :-)