This may be a stupid question, but are you inserting the byte by adding new, or inserting by overwriting an existing byte? Inserting by adding new will throw off any pointers in the file, as there are usually sections that reference specific addresses that will not go to the right place if you shift everything by a byte.Hey guys, I've got a small hex-related problem. I need to create a chassis file that has a flat-shift sequential gearbox rather than the lift and shift that it's currently equipped with. I'm 99% certain that I have the string that I need to change, but the byte to change isn't there. I want to add that byte and I have the ability to insert it, but I don't have the knowledge of how to make the file actually work after inserting a byte, it just crashes the game. Is there anyone that knows how to add a byte to a hex file without crashing the game?
Translation for mitsubishi_lancer_evo_x_fq400.vdfm
By JDougNY
Version 1.0 - Feb. 12, 2016
NOTE: address locations are typical for almost all VDFM files. Use this translation as a
guide to editing VDFM files.
NOTE: The format of some VDFM files vary starting at address 0x0D8 thru 0x0E7, which
is just after the last tyre height entry.
0x018-0x01B = 6C000000 = 108 // (Decimal) Total Byte length of String data Section.
If additional bytes are inserted into the string data section, this register
is incremented accordingly.
ADDRESS Little End. Value Description
------------|-----------|------|----------------
0x0050-0x053 = XX000000 = 0 // (Decimal) Location in string data for Chassis filename (*.CDFBIN)
0x0058-0x05B = XX000000 = 0 // (Decimal) Location in string data for Engine filename (*.EDFBIN)
0x0060-0x063 = 1E000000 = 30 // (Decimal) Location in string data for Gearbox filename (*.GDFBIN)
0x0068-0x06B = 3D000000 = 61 // (Decimal) Location in string data for Suspension filename (*.SDFBIN)
0x0070-0x073 = 55000000 = 85 // (Decimal) Location in string data for Collision filenames (*.XML)
0x0078-0x07B = 55000000 = 85 // (Decimal) Location in string data for Tyre filename (*.HDTBIN)
0x080-0x083 = XX000000 = // ??Not Tested?? - (Decimal) Location in string data for turbo filename (*.TBFBIN)
0x088-0x08B = CBA1453F = 0.772 // (Float) FL Wheel/Tyre lateral offset in Meters
0x08C-0x08F = 54E3A53E = 0.324 // (Float) FL Wheel/Tyre vertical offset in Meters
0x090-0x093 = 9A99A9BF = -1.325 // (Float) FL Wheel/Tyre fore/aft offset in Meters
0x094-0x097 = CBA145BF = -0.772 // (Float) FR Wheel/Tyre lateral offset in Meters
0x098-0x09B = 54E3A53E = 0.324 // (Float) FR Wheel/Tyre vertical offset in Meters
0x09C-0x09F = 9A99A9BF = -1.325 // (Float) FR Wheel/Tyre fore/aft offset in Meters
0x0A0-0x0A3 = CBA1453F = 0.772 // (Float) RL Wheel/Tyre lateral offset in Meters
0x0A4-0x0A7 = 54E3A53E = 0.324 // (Float) RL Wheel/Tyre vertical offset in Meters
0x0A8-0x0AB = 9A99A93F = 1.325 // (Float) RL Wheel/Tyre fore/aft offset in Meters
0x0AC-0x0AF = CBA145BF = -0.772 // (Float) RR Wheel/Tyre lateral offset in Meters
0x0B0-0x0B3 = 54E3A53E = 0.324 // (Float) RR Wheel/Tyre vertical offset in Meters
0x0B4-0x0B7 = 9A99A93F = 1.325 // (Float) RR Wheel/Tyre fore/aft offset in Meters
0x0B8-0x0BB = 23DB793E = 0.244 // (Float) FL Tyre width in Meters
0x0BC-0x0BF = 54E3253F = 0.648 // (Float) FL Tyre height in Meters
0x0C0-0x0C3 = 23DB793E = 0.244 // (Float) FR Tyre width in Meters
0x0C4-0x0C7 = 54E3253F = 0.648 // (Float) FR Tyre height in Meters
0x0C8-0x0CB = 23DB793E = 0.244 // (Float) RL Tyre width in Meters
0x0CC-0x0CF = 54E3253F = 0.648 // (Float) RL Tyre height in Meters
0x0D0-0x0D3 = 23DB793E = 0.244 // (Float) RR Tyre width in Meters
0x0D4-0x0D7 = 54E3253F = 0.648 // (Float) RR Tyre height in Meters
0x0D8-0x0E7 // (All floats) Some VDFM files have data in this section. Use unknown.
0x0E8-0x0EB = XX000000 = // (Decimal) Location in string data for KERS filename (*.BBFBIN)
0x128-0x12B = XX000000 = // (Decimal) Location in string data for DRS filename (Drag_1.UDFBIN)
0x130-0x0133 = 00001144 = 580.0 // (Float) Brake Disc Glow Min
0x134-0x0137 = 00808944 = 1100.0 // (Float) Brake Disc Glow Max
0x138-0x013B = 0000803F = 1.0 // (Float)
0x13C-0x013F = 0000803F = 1.0 // (Float)
If the hex string reads like this in CDFbin...
[28 1D EA 4C 3D]
Then change to read
[20 1D EA 4C 3D]
Then insert the new byte after the hex string
You need to increment 3 registers at the top of the file, when adding new bytes to the file..
[0x08-0x0B], [0x14-0x17], and [0x24-0x27]
Those registers are decimal and entered in Little Endian.
For instance, let's say you added one byte to the file and register [0x08-0x0B]=CB 10 00 00
New value would be CC 10 00 00
Road cars are not used in Career mode. I don't play the career mode, but I don't see an option for Road cars. Perhaps it's something you edited to make the car appear in Career mode?JDougNY,
I have a quick question for you about Nissan GTR by gvse.
In The Career Mode I can't tweak the car setup - it's not allowing me to change the default settings.
Would you know why?
You would need to contact the person and ask for the tire textures used in that pic.I do not know how to install these tires, if anyone can help me it would be nice thank you
to view the Audi R8 LMS mod 2015 does not bring even the original variants, I modified a few:
Michelin tires 2015 for GT3 with one two logos
Pirelli tires GT3
llatas continrntal 2015 imsa used rolex
logo in the cabin "banner" for Blancpain and audi logo 2016
last yellow headlights and amber glass.