binbow

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

@mitkop81 Thank you for the information. I would like to do something if I can manage it.

@MikeS121 Thank you for the report. There seems to be a bug in the program regarding vehicle name change and rim folder name change, and it is under investigation. However, due to trouble with my computer system, investigation work is stalled. Please wait a while. Regarding F2012: In F2012, it seems that the reason for setting the address saving name is different from that of other vehicles, which is why the changed name is not saved. I do not know if the patch developers intentionally did so or not.

@Ali: Since this error is an error issued by Windows, I can not immediately investigate the cause (phenomenon can not be reproduced). What kind of work do you get this error? Please tell me such detailed information.

Please see the explanation by tdudec itself. Usage: tdudec.exe <d/e> <input> <output> [type] by default type is set to 0 for decrypting the savegame/playersave files, use 1 as type for decrypting other files (like .btrq, .db and so on)

In that case, I will check the following things. - Is the "Read only" setting in the "Eden Games" folder in the document folder off? - Is there enough space on the HDD?

@Minime891: Thank you for the new HUD. It seems to be easier to read RPM compared to ordinary HUD.

@Minime891 Please make that HUD to me.

I thought that want to change not only the red line, but also the timing at which a crossover point between each component element or a specific noise occurs etc. Hmm...It seems that your view might be the correct answer.

Yes! I need digital read out. I want to know the rpm at which a specific sound ( **_onmid.wav etc..) starts to be heard.

Does anyone know of a method to obtain the correct rotation speed in the TDU 2 vehicle? I'm looking for a mod such as a telemetry system or a digital display tachometer.

The setting of the max rpm etc are grasped a little about a specific vehicle. However, I have not been able to generalize them so that can edit all vehicles. In order to handle these values with the tool, the structure of the data must be generalized. I will continue to analyze and expand this tool.

This is a tool for changing the setting value of the volume such as the engine sound described in "CarVSTConfig.xmb". TDU2SVR ver1.1.0.2 released. Changes - ver1.1.0.2 - Expanded the Engine Load/Unload element number to _7. - Fixed a bug in which elements would be grayed out by repeated file loading. Download link : Install: - Store the file generated after extract zip file in a suitable folder. Usage: - Fill in the file name in the "Target ..." field - When you click the folder shape icon, the file selection dialog is displayed. You can also enter a file name by D & D a file. - Either "CarVSTConfig.xmb" or the sound file "xxx_high.bnk" can be read. Note: Reading the sound file xxx_high.bnk may take some time as compared to reading the xmb file. - After changing the value of the element, click the "Save" button to save the value. - After saving, "yyyymmmdd-HHmmss_file name" file is created as backup. Thank: The information of this post was very helpful. I thank the contributor.

There is a field for entering the file name in "Misc - Sensitive data - File name definition" tab page. Here you can specify the file name of the file to use for sound etc. MichaelB450, Thanks for the quick help. [ATTACH]30926[/ATTACH]