binbow

@thacanine: Hmm. I have no idea for now. :sorry:

File "db_data.cpr" must be located in the folder \euro\Bnk\database\. Look for the folder unpacked tdu2 files located.

Do you have file "dbdata.cpr" in the right place?

I might've left a stupid bug. :sorry: After replacing the file "TDU2vPE_ini.xml" with the modified version, please try again. Or, first, remove the value of WorkFolder and ImportExportFolder of file "TDU2vPE_ini.xml" and then try again.

I made a video to introduce . Just for your information.:happyroll:

I made a list of additional or changed files in UP0.4. Just for your reference. :happyroll:

Done. Thank you for waiting.

I made the Vehicle-ID table of UP0.4 and AP1.71. Just for your reference. :happyroll:

You can check and change file name in the "miscellaneous-Sensitive data-Filename definition" on tdu2vpe. With respect to the camera position, find the value to be set by using, for example, camhack, and you need to edit the camerasingame.xmb yourself.

In many cases, the files for unreleased car are not complete. Therefore, you must provide the missing file on your own.

TDU2VPE will be able to change the price of the vehicle. If in the following manner, you can get a lot of money. - After inexpensively setting the price of a particular vehicle, buy the vehicle at the dealer. - Then, change the price of the vehicle you have purchased a high price. And - Sell off that vehicle in the used car shop. Now, you are now unscrupulous merchant. :D --- edit --- Another easy way: You can increase the amount of money to get in FRIM by rewrite the frpoints.cpr in the Euro\Bnk\scenarics. For example, it is possible to obtain a 10-fold prize in each level by changing as follows. It easily earns money if traveling in the neighborhood. <PA_TARGET2 lvl0="0" lvl1="2000" lvl2="3500" lvl3="6000" lvl4="9500" lvl5="15000" lvl6="22000" lvl7="35000" lvl8="50000" lvl9="75000" lvl10="100000" />

Ver3.3.0.5 released. Changes - ver3.3.0.5 Fixed: The bug by which a vehicle name and data are overwritten without intending. When you work such as the following, there was a bug in which the vehicle name and the data is overwritten. Load data "Audi TTRS Roadstar" - Change vehicle list to "Audi S3" - Click the "Apply" button --- Then S3 is overwritten by TTRS. Download link :http://www.mediafire.com/download/q56k74toe69nje5/TDU2vPE_ver3.3.0.5.zip Release for new version with the built-in color setting feature, is likely to take a little more time.

Fixed: incorrect 911GT3 rim. http://www.mediafire.com/download/3hgowc6ou33nbhq/ap1.7_fix_db_data.zip After extract zip file, just over write (replace) "db_data.cpr".

I have released ver3.3.0.4. Changes - ver3.3.0.4 Fixed: Access violation error had occurred in a particular vehicle. - If not find assigned rim, VPE will look for the unused Car-ID, and register the rim set to the database automatically. Download link: HALT I am very sorry. If you load the new vehicle data of the same brand while editing a car, there may be a bug in which the vehicle name in the editing would change. Please wait for a while till bug fixed version release.

I have gotten the information from Mitkop before. But I can not explain it well here since it is so complex. :sorry: Maybe,,I will implement the color setting feature in the near future to TDU2VPE. However, you will not be able to set your own new color. You will only be able to select one of the combination from color combinations that currently TDU2 have.

About an access violation error in a particular vehicle Access violation error in a particular vehicle, it was found that VPE is due to a bug that is not able to view the data correctly. There is no problem if you work to be assigned a new code according to the error workaround that was introduced a while ago. However, to edit the data of their vehicle, please wait until the bug fix version is released. --- Post Updated --- Server response is slow, but the file is normal. Please try again, later.

I have replaced the file in the correct files of ver3303. Please download from here: http://www.mediafire.com/download/d8hloctkkhvs3t4/TDU2vPE_ver3.3.0.3.zip Thank you so much for the bug! information.

Ops! Seems I made something wrong. Please wait a while.:sorry:

You can change the status in Miscellaneous - All items. Or use Autopack verx.x.

TDU2VPE ver3.3.0.3 released. Cahnges - ver3.3.0.3 Fixed: Access violation error had occurred in a particular vehicle. - If not find assigned rim, it was to display a warning to the viewer window. Download Link: http://www.mediafire.com/download/d8hloctkkhvs3t4/TDU2vPE_ver3.3.0.3.zip

Yes I knew it. I'll try to imprement some countermeasures in the next release.

Sorry for the trouble. Is there any error message? Could you please show me your detailed situation? I want to reflect on the next version. Ver3.2.6.2 : http://www.mediafire.com/download/bpaow54z3b0cmx3/TDU2vPE_ver3.2.6.2.zip Ver3.2.6.3 : http://www.mediafire.com/download/39nd965b992tl9i/TDU2vPE_ver3.2.6.3.zip I would recommend Ver3.2.6.3. Here is the latest. This is the version remove the code to compress the execution module that would be used in later ver3.3.0.0. Please try to use it if you can. Ver3.3.0.2 : Halt, ver3.3.0.3 will be release soon.

You should find them by yourself with trial and error. First, finding a max-rpm is I think that it is easy. And, once the new knowledge is obtained, please let us know as well. :happyroll:

The following is an example of using impreza_wrx_sti_2007_high.bnk. R8_V10 also has the same structure. It is in the process of being analyzed yet. I hope this is something helpfull. This tool is useful, I think. http://forum.turboduck.net/threads/34297-hdconv-hex-decimal-mutual-conversion-tool

Cause of the error was found. Rim code in use described in the vehicle data were not correspond with the description of the RIM tables available on the vehicle. Is this a bug originally had been left in the database, or intentionally whether such value has been set? I do not know for now. Anyway, you can correct the data in the following procedure. 0. Load "Lambo Countach 5000QV" data. 1. On the tab page "Tire/Rims", click rim code in "Tire-Rim combination code list". Row in the list will be selected. 2. Click "Rimove" button. After that, 3. Click "Add" button. "TireDBViewer" will be opened. On TireDBViewer, 4. Click "code" column hedder. Cell will be sorted by code. 5. Find code "158", and click it to select the code. 6. Click "Add this combination" button. Code 158 will be registerd in db_data as Rim in use. You can close "TireDBViewer" now. 7. Please remenber to click "APPLY" button at the last.