Jump to content
We promise no intrusive ads, Please help keep the community alive
Consider supporting us by disabling your ad blocker / add to whitelist / purchasing VIP.

binbow

Modders
  • Posts

    866
  • Joined

  • Last visited

  • Days Won

    50

Everything posted by binbow

  1. 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:
  2. 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:
  3. 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.
  4. 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.
  5. The location of the dealer may have changed. Look for Italian South @ Oahu or Italian East @ Ibiza, you can find Pagani.
  6. 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]
  7. It is necessary to update to V034 build16. StarGT's post should be of service to you.
  8. Oh, that was good. :thumbsup:
  9. 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.
  10. 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.
  11. 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.
  12. 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 remember to click "APPLY" button at the last.
  13. It is probably some kind of bug that the process remains. If you use TDU2_Offline_Mode.bat or online_mode.bat included in the package, it will solve the problem that the process will remain.
  14. Unfortunately, I can not find a clear cause at the moment. I will continue to investigate and improve as much as possible.
  15. @Devinnspell: Can you replace TDU2vPE_ini.xml with a new file and try over from the initial setting? Sorry to trouble you. There seems to be a bug in the initial setting process. I will fix it in the next release.
  16. What version are you using? There is not such a bug in the latest version,,I think.:confused:
  17. Ooops!! That's a big problem. :D
  18. Hmm..., I have no idea for now. Anyway, I will examine about it. -- edit -- Have you tried ver3.3.0.2 already? If not yet, can you try it?
  19. Let me know more details. Is there any error message when crashing?
  20. The "TDU 2 Root folder" column seems to be wrong. You will need to fill in the folder name where "TestDrive2.exe" is located. And, it is necessary to copy all files to the newly created folder outside of "Program Files" or "Program Files (x86)". BTW, the latest tdu2vpe is Ver3.3.0.5. See the top of this thread.
  21. Can tune-up at tuning shop? ; I'm not sure. There may be vehicle that can not be tuned up at tuning shop. However, tdu2vpe can change many of the characteristics of the vehicle, including the engine performance. It can be expected to obtain equivalent results to that tune-up.
  22. Sorry :confused: Can anyone help? please !!!
  23. TDU2VPE is not helpful for your application. You can also sell any vehicle when in the following manner. At used car dealer; 1. Click vehicle name which you want to sell. then 2. Click "Select". So you should see the selling price of the vehicle is displayed. 3. Now, you can sell it by clicking on the "Sell". [ATTACH]27311[/ATTACH]
  24. You may need to register your controller. Articles Xarlith I think that would be helpful.
×
×
  • Create New...