binbow

@Wass Mateen: In the "TDU 2 ROOT FOLDER" column, it is necessary to set a folder name containing unpacked TDU2 files. In case of you, I think you need to set "C:\users\wasim\desktop\tdu2".

Are the tdu2 game files unpacked properly? Where did you install tdu2vpe? If tdu2vpe is installed under the folder "C: \ Program files .. \", it may not work properly.

Is helpful? In the case of the above link, "Generic car" is a vehicle that AI is driving in the game so normally we can not drive in the game. So it is virtually the same as adding a new vehicle.

You can change the target to replace by using tdu2vpe. For example, when you want to use MOD "Replaces: Spuker Pekin - to - Paris D8", it is also possible to replace unnecessary vehicles, such as taxis, depending on the setting. Is that still insufficient in such a way?

No, you can not add newly. If you really want to add a new vehicle, it seems like you can prepare multiple "db_data.cpr" files that registered different vehicles for each and switch which "db_data.cpr" to use when starting the game. Then you can use 284 * n vehicles. If you are offline exclusively, there seems to be such a way.

@Azzarok : Every vehicle that appears in TDU 2 has its own unique ID number. The file name of the 3D data of the vehicle assigned to each ID is defined in the database. We do not know how to define new ID numbers. What we can do is just "replace" the 3D file of the vehicle assigned to an ID. About english, I also using Google translation, so do not worry.:D

@Azzarok: There seems to be a slight misunderstanding. Load / Apply, Export / Import are the following functions. There are 284 vehicles in TDU 2 in all. The data of those individual vehicles are described in a file called db_data.cpr in the form of a database. When you click "Load" on tdu2vpe, you can read and edit the data of the vehicle selected from the vehicle's data described in db_dataa.cpr in the memory and view it and edit it. Click "Apply" to write the data in memory back to db_data.cpr. Click "Export" to save the data of one loaded vehicle as one file. "Import" is a function to read the exported vehicle data on the memory. "Export" / "Import" is prepared to be useful for making cloned vehicles. Since general vehicles such as buses and taxis are not usually registered at dealerships, if you use those vehicles as bases for replacement with another vehicle, you need to register to the dealer.

We still do not understand the structure of the database adopted by TDU 2. So we do not know how to extend the database. After all, what we can do is to replace the existing vehicle unfortunately (although it may be a traffic car).

Please use TDU2VPE to register additional rim and delete original rim.

How to separate "connected" vehicles sharing the database, to use it separately - experimental. With TDU2VPE; 1. Load original vehicle (ex: load Lotus Evora) 2. Export loaded original vehicle's data 3. Load target vehicle (ex: load Lotus Evora "Solar Crown") 4. Import the data you exported before 5. Click "Apply" to save changes. With the above work, the two vehicles can now be handled as independent vehicles not related to each other. After that, according to usual MOD installation procedure, if necessary change tires or adjust performance and complete. As a result of experiments with a school car and several prize cars, it was confirmed that both can be separated. There may be side effects on other vehicles. Moreover, it is not confirmed the behavior etc online. I would appreciate it if you can report the experiment results.

Ver3.5.1.8 released. Changes - ver3.5.1.8 Fixed: An error that "db_data.dec file is missing" occured. FIxed: Brand name change function was not working properly. Download link : TDU2VPE_ver3.5.1.8.zip

TDU2 CameraViewpointEditor ver1.0.0.0 released. Changes - ver1.0.0.0 New: Two items "Range angle - LR" and "Angle inertia" added. - Changing the values of these items allows you to adjust the degree of shakiness of the line of sight when you turn the car with steering. About adjust the degree of shakiness: - The value of "Angle inertia" was good about 90-100. - It seemed to be good to set the value of "Range angle - LR" to be the same value as in the Hood view. Download link : TDU2CVE_ver1.0.0.0.zip I will be busy with Forza horizon 4, so may be no update except bug countermeasure for a while. :D

Was there no problem when adding another MOD? Have you set a value for Price? It seems to be a problem related to TDU 2 VPE, so it is better to continue to post on tdu2vpe thread. And, if there are any images that can give me a detailed picture of the problem situation, please attach it.

Normally, you do not need to use TDU 2 VPE when installing MOD that replaces an existing vehicle. After installation, you will only use VPE if you want to change the model name etc. There may be something to come up with if you have detailed information on where you installed MOD and about it.

Is the MOD file correctly copied to the appropriate folder?

TDU2 CameraViewpointEditor ver0.9.8.0 released. Changes - ver0.9.8.0 Fixed: There are cases where entries with the same camera - ID and same view code overlap. In such a case, editing will not be reflected correctly. Fixed: In the case of Hood view, the screen is not refreshed even if click "Save" New: Added the item "Steering Wheel Offset" to the cockpit view. ; Minime891; thanks for the information. Download link : TDU2CVE_ver0.9.8.0.zip

Known issue: - There are cases where entries with the same camera - ID and same view - code overlap (see below). In such a case, editing will not be reflected correctly. [ATTACH]31953[/ATTACH] - In the case of Hood view, the screen is not refreshed even if click "Save" I will release these bugfixes soon.

TDU2 CameraViewpointEditor ver1.0.0.0 released. Changes - ver1.0.0.0 New: Two items "Range angle - LR" and "Angle inertia" added. - Changing the values of these items allows you to adjust the degree of shakiness of the line of sight when you turn the car with steering. About adjust the degree of shakiness: - The value of "Angle inertia" was good about 90-100. - It seemed to be good to set the value of "Range angle - LR" to be the same value as in the Hood view. About bumper view: - It seems that bumper view is not defined for most vehicles. For those vehicles, it seems that the default bumper view setting is used, and the setting of bumper view with car-id = 9998 is used. [spoiler=Screen shot] [ATTACH=full]31952[/ATTACH] Download link: TDU2CVE_ver1.0.0.0.zip [spoiler=Histry] Changes - ver0.9.8.0 Fixed: There are cases where entries with the same camera - ID and same view code overlap. In such a case, editing will not be reflected correctly. Fixed: In the case of Hood view, the screen is not refreshed even if click "Save" New: Added the item "Steering Wheel Offset" to the cockpit view. ver0.9.0.0: Initial release Install: - Put "TDU2CVE.exe" a suitable folder after extract the zip. [Note] It is desirable to copy to the newly created folder outside of "Program Files" or "Program Files (x86)". How to use: [Initial startup] - Specify the location of the "cameraasign.xmb" file the first time it starts up. - Fill in the prescribed column on the "settings" tab page and click "Done" button. The set location is saved in "tdu2vce.ini". "tdu2vce.ini" will be created in the folder where TDU2CVE is installed. [Read data on "cameraasign.xmb"] - After starting, select the target camera ID using the list box and click the "Load" button. - The current setting value for each item is displayed under "current" label. - Cockpit view, Hood view, Bumper view are loaded at the same time, you can browse each one by switching tabs. [Change data] - It is need to change for each view. - Open the tab page of the view you want to change and fill in the new value in the edit box below "new" label. - Save data after change - Click "Save" button when the change is completed. Changed items on all view are overwrite to the "cameraasign.xmb" file. - Using stored data of camhack - Save data of camhack.exe can be imported. - Imports must be run on a per view basis. Open the tab of the desired view and click "Import tdu2cam.sav" button and specify the file to load. - After importing, the new corrected value will be put in the edit box under "New" label. [Notes] 1. In the saved data of camhack, the offset amount with respect to the value described in the xmb file is saved for each view. The camera ID is not included in the data. Therefore, If importing inadvertently, the correction value of unintended camera ID will be read. Please execute data saving operation using camhack for each view on the vehicle to be imported in advance. 2. Only saved data of camhack.exe ver1.2 can be imported. Acknowledgments: This tool consulted scripts created by tomsolo.

Hi:) I'm investigating "camerasingame.xmb". I uploaded the data for each camera-id described in the xmb file. For reference, also listed the corresponding vehicle model name in up0.4 for each camera-id. According to the correspondence list, we found that there is a camera-id which is not used in any vehicle. These unused camera-id are likely to be used as an independent camera-id that is not affected by other vehicles when adding a new vehicle. My experimental results showed that id 411 and id 412 can be used without problems. In addition, I'm planning to release editing tools soon.

@Adm-RAL: I examined the file you sent. The number of data items per vehicle should be 214. There are 315 data on your file, it is the cause of the error. If this CSV file is the file right after exporting, db_data.cpr is probably broken. Or, the version of db_data.cpr being used may be different. Can the game start normally and play without problems?

@Adm-RAL: I do not know how to add new car slots yet. Because the structure of the database in TDU 2 is not fully understood yet. Regarding "can not read.." error: Is it occur the error every time? I can not reproduce the error. Can you send to me that csv file?

Ver3.5.1.7 released. Fixed: Bug that minus (-) value can not be entered. Download link: TDU2VPE_ver3.5.1.7.zip Please use a period (.) for the decimal symbol. The comma symbol (,) can not be used as a decimal symbol depending on the specification of the compiler.

Can you tell me the detailed situation so that the reproduction experiment can be done? - Does the problem occur in any vehicle? - Specifically, what item's value is trying to change? The column of the specific item was set not to accept inputs other than numbers, but it may have been wrong. I want to fix it as soon as I know the item. -- edit -- Sorry, as a result of examining source code, it seems there was my mistake. I will release a revised version soon.

@Refusinq: It is necessary to change the saved rim file name to the file name used by the vehicle. I think that you should study the use of [URL='https://forum.turboduck.net/threads/tdu2vpe-release.32907/']tdu2vpe[/URL]. You can reset the file name of the rim to use. As an example of using tdu2vpe, I think that [URL='https://www.youtube.com/watch?v=g6ET9MiAR5c&t=50s']this link[/URL] will be helpful.

Ver3.5.1.6 released. Fixed: Bugs where editing on tire, rim, brand name was not functioning properly. Fixed: Suppressed the potential to rise the error "Another application is using db_data.dec" as much as possible. Other, minor bug modification Download link: TDU2VPE_ver3.5.1.6.zip