binbow

Setting of "Root folder" seems might be incorrect. Root folder must be set the folder that contains the "TestDrive2.exe"

This is my result. :confused: Could you show me the TDU2VPE's version? [ATTACH]23285[/ATTACH]

Which unreleased vehicles used for Murcielago? I also try to replace and want to confirm that problem. Can you check the Id-camera, Id-car and same_IK of the vehicle that was used to order to replace the Murcielago? You can see those IDs value in the "Miscelloneous\Sensitive data" panel. --- Post Updated --- Guys: If you change the folder name of the rim, there seems to be a bug that break the file "dbdata.cpr". :hide: I'm currently investigating the details. Please do not change the folder name of the rim till fix will be provided. The game may not start when the file "dbdata.cpr" is corrupt. When you fell into that situation, please use "Restore" button on the "Settings" page.

After changed the overhang values, did you click to not forget the "Apply" button? I also often the same failure.:bsod: And, what vehicles used in the base of the change? Depending on the vehicle it may not have that changes be reflected.

Guys: Change of rim file name there was a bug that is not reflected in the game. Sorry to trouble you, but please download again who already downloaded. Download link:http://www.mediafire.com/download/awm1dx9ryuju64i/TDU2vPE_ver2.04.zip

I released ver2.0. As for the download link, please refer to the beginning of the thread. You can now edit the file name of the rims. [ATTACH]23235[/ATTACH]

Hmm.. here I can be individually set the "Miami" Mustang and ordinary Mustang of each gear ratio.:confused: I will release new version in a few days. Please wait and try new version, though it's same algorithm. -- update -- It is visible as can be set individually, On the database, I could confirm the value set in each are stored properly. But in the game, it seems actually are using the value of the ordinary Mustang. TDU2vPE is not able to adapt to this kind of trouble . [ATTACH]23202[/ATTACH] -- update 2nd -- I have an additional investigation. The result was "consolation prize!" As follows. The other award vehicle that was acquired and the racing school vehicle, it was all under the same situation. :(

Thank you for the report. No, I had never encountered such trouble. Anyway I will also try to check the problem again. --- update --- I remembered one thing that should be noted. If you delete a dbdata.dec file without the work clicking "Restore", tdu2vpe generate a dbdata.dec from dbdata.cpr under the game folder and use it for edit. So, at that time, if the dbdata.cpr had corruped, it means that its influence will continue. In the next version I will try to improve around this.

Yeah! :thumbsup:

Guys, about ver1.5; Bugs that become unreadable data that have changed the ID seem does not gone completely.. Please use the following methods as workaround for this bug. - Open the TDU2DBCarList.xml in such as Notepad - Find the car of interest - Please match the value that you changed in TDU2vPE each value of cam_id and car_id and id_3rd. [ATTACH]22996[/ATTACH] I will fix this bug in the next release. The next release is expected to be able to change the rim.

The item is only to generate a file name (It rewrite the description of the file name in the database.). So, it is necessary to prepare those files yourself separately.

If it broke the database, you can return to before the change database by using the "RESTORE". All of the changes will disappear. [ATTACH]22981[/ATTACH]

Bug fix was completed. As for the download link, please refer to the thread top post. Version is now 1.5. In this version; Before you change the assignment of the dealer slot, please once exit the tool and do edit work after restart. --- Post Updated --- @ticofa I think "Engine inertia" and "Gearbox inertia" are the related likely. But, only program of TDU2 know how they are used to. So, to tell the true, I am not sure.:rolleyes:

Yes, I hope there is it, if possible. But I do not know exactly how far. Anyway, now the top priority is a bug fix.:headbang2:

I released ver1.5. As for the download link, please refer to the beginning of the thread. ver1.5 can be added vehicle to the free slot of the dealer by the following procedure. ============= Basis of how to add a vehicle to the new slot. =============== [ATTACH]22972[/ATTACH] [ATTACH]22973[/ATTACH]

Yes, as for the ver1.2 wip, I think that there's no problem on the spykers. :rolleyes: And, v34 b16 had not 350z model, i think.:confused: --- Post Updated --- :ty: I will release new version in a few days. Please wait it.

:confused: .. I have no idea. sorry:( Can anyone help? Pleeeeeese!!

I will also check the matters that pointed out by you. And if possible will fix in the next version.:headbang:

Thank you for the information. I will correct them in next version. --- Post Updated --- Db_data that has been applied the patch other than unofficial patch, may not be able to edit normally. Since it may have changed the Cam-id/Car-id/IK-id.

Thank you for the bug report. Let me know what program version are you using ver1.0/1.2wip ? And what game version using? --- Post Updated --- Sorry, no solution for now..:sorry:

Thanks for the bug report. Well.. I'm planning to release ver1.2 (not a WIP) in a few days. Please wait and try it.

Ohhh, that's good.:)

@Abzz Hmm... What game version are you using? TDU2VPE can readout only v34. build16 and with unofficial patch 0.2/0.3/0.4. I have no idea any more.:sorry: I'm planning to release ver1.2 (not a WIP) in a few days. Please wait and try it. --- update --- Please try to set the work folder to the location other than " ..\program files (x86) \ atari \ ...". For example, it is better to create a folder "E:\tdu2vpe" on E drive, and set it to the work folder.

Well,,,, I have come up nothing. :confused: It might resolve if you run as an administrator. Right-click the tdu2vpe.exe's icon, you will see the item "Run as administrator". Just select it. Please try. --- edit --- Has the following things not forgotten？ After fill in all fields, please click the "Save/exit" button at "Setting" tab page.

Thanks. But, there is no the problem in original v34.b16 and with unofficial patch 0.2/0.3/0.4...I think..