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.

Djey

V.I.P!
  • Posts

    2,628
  • Joined

  • Last visited

  • Days Won

    88

Everything posted by Djey

  1. No, it doesn't. At the moment, Ultra Community Pack is for people wanting to enjoy all features of patch 1.68b. Either 2.00A will need its own Car Pack onto it (it has been designed to), either it has to be more modular to prevent from installing conflicting changes onto this car pack.
  2. I hope you'll find a solution not involving patching game exe. Project paradise works with DLL injection, that's cleanest way.
  3. Sounds great, but with current knowledge of tdu internals we dont't have hands on this setting. Might be hardcoded in game executable.
  4. Get original 2DB file from a backup (with TDUMT File Browser), then select it, right click Properties. The original texture information is displayed in the table: Dimensions, Mimap count, Format (e.g DXT5-like). You should select same Format (DXT5) when saving DDS back.
  5. Fixed version 1.10.1 available, does not require hot replacing of structure file anymore. Download in OP. ;)
  6. Here we go, so here is an updated cam structure. Same instructions as above to replace original file. There was a 1 byte offset for the wheel settings, as expected. Now fixed, I hope :) --- Edit: removed attachment, Released files now include proper cam structure (1.10.1).
  7. Use check button to seek for potential errors, but don't try fix just yet. I suspect some kind of database corruption. Or can you send me your all your database files ?
  8. Hi, Dds format is the key when you save it from photoshop. It has to be the same as the one from original 2db file. To know texture format, open 2db file with tdumt (2db to dds) and write texture format down. Then use the same setting when saving dds. Finally, when you convert dds to 2db in tdumt back, make sure to provide also original, unmodified 2db file and use keep headers option. That works, that's how I changed menu screen in tducp ;)
  9. Never heard of any project of this kind... World editor from speeder would be a great start, but I can't find the time to work on it... :(
  10. Must be a wrong field assignment to binary file for both wheel settings, then. I'm pretty sure it causes rear view issue as well. I will try to fix structure. Thanks for pointing that out!
  11. Here is updated structure for cameras.bin: all settings now can be entered from -32768 to 32767. Negative values might not have any sense so I will keep only positive ones in the future. To apply update, - close TDUF - rename attached file to BIN-cameras-map.json (remove .txt) - open tduf/tools/lib/tduf-1.10.jar with 7-zip and replace in files/structures directory from archive. It should erase existing file.
  12. At the moment, values can't be lesser than -127 nor larger than 128 in TDUF (read single signed byte). Steering wheel settings might need more values to be entered (2 bytes = [-32768 ... 32767] or [0 ... 65535]) ... guess I'll have to check this.
  13. Could not reproduce issue, though I've changed following settings : - Cam position X - Cam position Y - Cam position Z for the Murcielago roadster cam set. Will continue testing. --- Post Updated --- On your two screens the cameras do not match : is it just an example? - TDUF, camera set 102 (AC Cobra 427), Cockpit view (23) - Cameras.bin editor, camera set 243 (Chrysler FP), Hood (24) Can't test cameras.bin editor as it does not work with TDUCP cameras...
  14. Yep, it supports same settings as Cameras.bin editor, should do the same. Which issue with the cockpit back view exactly?
  15. Announcement : TDUF toolset 1.10.0 now available ! This time major feature is a brand new cameras editor! You will find it in Database Editor (Cameras and IKs tab). Here is short reading about this: TDUF Database Editor Cameras · djey47/tdu-cp Wiki · GitHub As I'm too lazy to post full change log everytime, for the rest please refer to embedded README file in zip archive :D And... have fun!
  16. I would be interested in comparing lifespan of TDU2 servers vs TDU1. TDU1: 2007 to 2012 ? TDU2 : 2011 to 2017. So TDU2's is not so bad after all. Now, unlike TDU1 which has an official announcement before closing servers, will TDU2 end publicly or not? Future of TDU2 only depends of motivation and size of players community. TDU1 did prove eveything is possible to make a game on his feet again. Personally, I'd rather work on TDU2 now as it's clearly richer and prettier than TDU1. But since 2011, noone ever did find a way to undo those hardcoded, crappy physics. There are more chances TDU2 gets a new online life in a couple of years, than being as fun to drive as its elder brother :)
  17. ATI 9800 Pro (desktop) was the oldest ATI GPU which was reported to be used with TDU, if I remember well. A 9600 might be able to start it at least (if it has at least 256Mb vram) Pentium M is not better than C2D at the same frequency, so should be catastrophic, given that this game was a real pain for CPUS (did not use multiple cores well).
  18. Hi, feel free to try, but given your specs (embedded gpu with shared memory), there's not much hope here. I ran TDU it with my first laptop in 2009, 2010, which had a real GPU with dedicated VRAM : - Ati Mobility HD3450, 256 Mb - C2D, 2.0Ghz - RAM 3Gb - HDD 256 Gb barely got 20 to 30 fps à 1024x768, low details. If TDU starts at all, maybe it will run at 800x600 low details. Forget about HD ready res anyway. And TDU2 ... :eek2: Sorry.
  19. We all miss him for sure ;) I'd like to hear news from World Editor as well :p Message in a bottle to @Speeder
  20. Hey, Might be due to database corruption. Download latest TDUF in tools and support section, then follow check and fix tutorial from here: TDUF Database Editor · djey47/tdu-cp Wiki · GitHub Make a database copy before trying to fix yours.
×
×
  • Create New...