binbow

Autopack is one of MOD's aggregates.

Your friend and you should use the same MOD for the same vehicles with the same ID. Or stop using MOD. It can not be modified with parameters that can be changed with VPE.

In the TDU 2 server, all the vehicles are managed by the ID code. That is, if the IDs are the same, they are handled as the same vehicle. "Using vehicle MOD" means replacing the body of another vehicle with the body of an ID. The body is replaced only on the local computer. So, what you experienced is that it happens normally when you use vehicle MOD, I think.

There should be a file called "org_db_data.cpr" in the folder "backup" in the folder where you installed tdu2vpe. Rename it to "db_data.cpr" and copy over it to the game file folder. --- edit --- Using the "RESTORE" button makes it easy to rename and copy as above.

Ohh, that's good:p

See here.

So,,,the file size of db_data.cpr seems to be somewhat different, so I am concerned. I think the file size should be 1192 bytes. For example, if you download Autopack and extract db_data.cpr, you should be able to get the correct file, so please replace it.

The installation folder is OK on the desktop. Is the error message displayed immediately after starting vpe? Or is it displayed when loading something vehicle data? By the way, is the error since ver.3.5.0.5? Was the same situation in the previous version? P.s. Please delete the file called "TDU2vPE_ini.xml" in the installation folder and try the initial setting of tdu2vpe again.

I have not confirmed well what kind of influence it has on online when I change the performance data of the vehicle. It is easy to imagine that if you modify the performance data of a vehicle, the result of online racing can be unfair results. However I do not think that will result in that can not participate in a particular race. I think that you can check immediately if you replace db_data.cpr with the original db_data.cpr to see if the situation you are encountering is due to the result of using tvu2vpe. Pleare try it.

Sorry for the inconvenience. Please give me more detailed information. What version of tdu2vpe do you use? The latest is ver3.5.0.5. If not latest, please try to use the latest version. In which folder is tdu2vpe located?

The following may be misguided, but I think it's worth a try. There should be a file called "DevicePC.cpr" in the folder containing the TDU2 game files. Please try to replace that "DevicePC.cpr" with the original one.

Unfortunately, the gear ratio for the reverse gear data seems not to be found anywhere in db_data.cpr.

There are up to 11th gear ratio data items in db_data.cpr. However, in past experimental results, I think that the data set after 8th value was not reflected in the game. Well,,It may depend on the vehicle to be tested. I will experiment with BMW i8 again. --- edit --- Even in the current version you can set 8th and 9th gear ratio. Please select "Gear_ratio 8" or "Gear_ratio 9" in "All Items" on the "Miscellaneous" page and fill in the value. p.s. Regarding engine type of 2CV; In fact, I can not find any place where the engine type name is described anywhere yet. In vpe, the type name is displayed by checking the value of the item against the in-game display. It is easy to change vpe's display, but that does not make sense, I think.

Ver 3.5.0.5 released. Changes - ver3.5.0.5 Fixed: The phenomenon that the display of model name garbled. Download link: https://www.mediafire.com/?j763eqwqsnncjf1 Notation like "R34 GT - R Nür" has also become possible. :thumbsup:

Such an indication is displayed because an unsupported character code is used in the file of TDU 2. The latest ver 3.5.0.3 released the other day changed handling of character code. Please try it. --- edit feb/27 --- The phenomenon that the character display is broken does not seem to be improved even in ver3.5.0.3. I will continue to make efforts to improve, please wait. :headbang:

Ver 3.5.0.3 released. Changes - ver3.5.0.3 New: Changes related to car body color and indoor color are now available. Fixed: Reexamined the code that may be dependent on the Windows version. Others: "IniLdr.exe" which was included in the old version is no longer needed. Download link: https://www.mediafire.com/?6e5822m3u7keeew How to edit the color: Important points: After adding / modifying colors, please do the process of placing the vehicle newly in the dealer. If the vehicle has already been registered, please delete it once and register again. Special thanks: As for color change, information from mitkop81 has become very helpful.

OK I will implement it in next version. Please wait for a while.;) --- edit --- It might be difficult..:( Each engine type has assigned a code one by one, and we can only select a code from existing them. So, it is difficult to add new engine type, I think. Anyway, I will investigate.

The location of the dealer may have changed. Look for Italian South @ Oahu or Italian East @ Ibiza, you can find Pagani.

Did you download the file using ”TDU2*****utoPack 1.6.torrent" file? You can see the Product version by right-clicking Testdrive2.exe and opening its properties. Product version must be "TDU2 DLC2 v034". If the versions are different, the only way to avoid the error is to somehow obtain a compatible version of the file. If you search, you will find lots of ways, so please check it yourself. [ATTACH]28005[/ATTACH]

It is necessary to update to V034 build16. StarGT's post should be of service to you.

Oh, that was good. :thumbsup:

I tried to solve the bug that export on windows XP caused a "TFilesavedialog requires windows Vista or later" error. Could anyone who is using Windows Xp please check? Please download test version from here. Note: The test version has the item "Color combination" but it does not work yet.

Certainly Aston Martin DBS coupe Carbon Black edition seem to be not listed up. Hmm. . I will investigate. --- edit --- Aston Martin DBS Coupe Carbon Black Edition is listed at the time of Autopack 1.6. In the subsequent Autopack 1.71, it turned out that Carbon Black Edition was replaced by Aston Martin Vanquish. Just for your information.

Oops! As you can see from the error message, VPE uses a special dialog since Vista. I will take some measures in the next release.

It was confirmed that the error occurred. I will fix that error in next release. Please wait.:sorry: --- edit --- It was found to be the same error as in the case of Countach 5000 QV in post #710. The following procedure can solve the error. 1. On the tab page "Tire/Rims", write down the Code number (code = 123) in the Tir-Rim combination list. 2. Click "Add" button. "TireDBViewer" will be opened. On TireDBViewer, 3. Look for the code number (code = 123) that you noted and double click on it. Code 123 will be registered in db_data as rim in use. You can close "TireDBViewer" now. Please remeｍber to click "APPLY" button at the last.