Jump to content

Search the Community

Showing results for tags 'updater'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. There's some sort of problem with the TDM updater whereby it won't create a proper 2.07 installation. Being on a slow Internet connection, my TDM installation/update procedure has always involved downloading just the latest update zip file (currently, 'tdm_update_2.06_to_2.07.zip') from the ModDB site and making that available to the updater locally, to avoid unreliable, slow downloads during the actual update. I followed the same procedure that I've always (successfully) done in the past: extract the huge, 2.3-GB 'THEDARKMODVersion2.0-StandaloneRelease.zip' file (downloaded once from ModDB and re-used many times over the years) change the permissions on all the PK4 files to be write-able (so that the updater can alter the content within, as needed) delete the existing, obsolete (2013-era), read-only 'tdm_update.log' file (which shouldn't be in the zip file to begin with) put a copy of all the 'tdm_update_2.0{x}_to_2.0{x+1}.zip' files amassed to date into that extracted directory download the latest version of the TDM updater app (from the TDM website) run the updater, with the options '--keep-update-packages --noselfupdate' On the 1st run, it proceeds in what appears to be normal fashion. There's no obvious indication that anything has gone amok. However, if you run the game, it comes up with the main menu showing "TDM 2.06", not the expected "TDM 2.07". Here's the TDM updater log file for this 1st run: tdm_update--run-1.log.txt Some analysis of the directory content and the updater's log file seems to indicate that the installation only made it to 2.06! As for the 'tdm_update_2.06_to_2.07.zip' file, I've verified the integrity ('zip -T'). I've also verified the filesize and checksum against the updater-downloaded 'tdm_version_info.txt' file: [UpdatePackage from 2.06 to 2.07] crc = 159677cb filesize = 427644498 package = tdm_update_2.06_to_2.07.zipSo I don't think there's anything wrong with that particular file. If I compare what the updater created as a "2.07" installation with an old, virgin 2.06 installation of mine, the only files that are different are ones that you'd expect to be: 'crc_info.txt', 'tdm_mirrors.txt', 'tdm_update.log', and 'tdm_version_info.txt'. If I run the updater a 2nd time (and all subsequent times) with the same options, it essentially does this: Applying differential update package... [=========================] 100.0% Adding: ExtLibs.dll [=========================] 100.0% Adding: ExtLibsx64.dll [=========================] 100.0% Adding: TheDarkModx64.exe [=========================] 100.0% Adding: thedarkmod.x64 [=========================] 100.0% Adding: vcredist_x64.exe [=========================] 100.0% Adding: vcredist_x86.exe [=========================] 100.0% Replacing: AUTHORS.txt [=========================] 100.0% Replacing: TheDarkMod.exe [=========================] 100.0% Replacing: tdm_update.exe [=========================] 100.0% Replacing: tdm_update.linux [=========================] 100.0% Replacing: thedarkmod.x86 [=========================] 100.0% File: Done applying the differential update.Due to website file upload limitations, the TDM updater log file for this 2nd run will be attached to a subsequent post. The updater log files on that 2nd and all subsequent runs are essentially identical, just with different timestamps and potentially use of a different mirror site. That's the repeatable scenario, the "crux of the matter", if you will. FWIW, I also dug more deeply into the problem. What I describe from here on is less thoroughly documented, but I'll mention what I did, in case it helps.... I tried removing all of the update zip files, hoping it would force the updater to update what is effectively a 2.06 installation but via a slow, painful download of that 408-MB 'tdm_update_2.06_to_2.07.zip'. But instead, it inexplicably wanted to download the 235-MB 'tdm_update_2.05_to_2.06.zip' file, so I aborted the update. Taking a different tack, I dug into the updater source code a bit and noticed this curious-looking snippet in '.../tdm_update/libtdm_update/Updater/UpdateController.cpp': //#4529 stgatilov: Since differential update does not uncompress unchanged OGG/ROQ files, //The hashes of pk4 files are now different from the ones on the server. //That's why we exit right away to avoid redoing the same differential update and redownloading the unchanged data. if (info.fromVersion == "2.05" && info.toVersion == "2.06") { TryToProceedTo(PostUpdateCleanup); break; }I played around with various changes to that code (both bumping the 2 version numbers and outright disabling the whole block), but to no avail. Although I'm running Linux (64-bit Slackware 14.2), I don't immediately see any reason why this would be OS-specific. This issue sounds different from the problem grayman had (running Windows), but I did get an "infinite updater loop" scenario when I hacked that code mentioned above, so maybe there's some correlation. I also noticed during some debugging that the installation I had was not being correctly recognized by the updater app as a valid 2.06 installation. When I looked into the updater's console output and log file, it seemed that every file about which the installer reported "SIZE MISMATCH" was one of the PK4 files that had embedded OGG files, although I did not check every case. I'm simply not able to figure out what's going on here, despite much effort, so I have to "punt" before my head explodes. Any input on this matter would be very much appreciated!
  2. The ELF executable provided from the main download page is 32-bit. It doesn't run on 64-bit systems without adding support for ELF32. Since 64 bit support is now available in 2.06, this needs updating. While the documentation on the download page is accurate in removing the instructions for adding 32 bit architecture support, which should now be unnecessary, the binary download needs updating too. I get the error: "no such file or directory" on Debian Stretch GNU/Linux, on a bash shell. This is perhaps because it requires loading some dynamically linked 32 bit libraries unavailable on my system, or perhaps even the 32bit loader itself is missing. Here is the list of shared libraries it needs to load acquired from 'ldd' application. linux-gate.so.1 (0xf777a000) librt.so.1 => /lib32/librt.so.1 (0xf774e000) libstdc++.so.6 => /usr/lib32/libstdc++.so.6 (0xf765c000) libm.so.6 => /lib32/libm.so.6 (0xf7616000) libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf75f9000) libpthread.so.0 => /lib32/libpthread.so.0 (0xf75dd000) libc.so.6 => /lib32/libc.so.6 (0xf742f000) /lib/ld-linux.so.2 (0xf777b000) Here is a dump from the binary header using readelf application. ELF Header: Magic: 7f 45 4c 46 01 01 01 03 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - GNU ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x804f519 Start of program headers: 52 (bytes into file) Start of section headers: 1690508 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 9 Size of section headers: 40 (bytes) Number of section headers: 33 Section header string table index: 30 The class is ELF32 & Machine 80386. One solution is to provide a separate 64 bit updater, or to statically link the libraries (Which would allow only one executable for both architectures). Is there a 64 bit version of the installer?
  3. Well I just discovered this mod after being a Thief fan since day one. and I am really excited over what the game promises. But I have one problem. I have been trying to download the game now for 3 days. The Updater (v0.66) starts up fine connects and starts to download and it will get just so far and then hang up. I usually let it sit for 5 min or so and then I'll cancel the download. about 1 times in 10 it will close properly otherwise I have to force it closed (not responding) then I restart. at this point I still have 932 MB (9 files) remaining as I type this the loader is stuck on "tdm_textures_stone_brick01.pk4" at 57.5 MB successfully downloaded 6.94% of that 932. I have tried turning off the advanced options but they haven't had any appreciable effect, here are the last few lines of the log Step thread started: 10 Picking mirror waffles.za.net Picking mirror darkmod-alt.taaaki.za.net Picking mirror darkmod-alt02.taaaki.za.net Picking mirror waffles.za.net Picking mirror fidcal.com Picking mirror waffles.za.net Picking mirror waffles.za.net Picking mirror darkmod.taaaki.za.net Picking mirror waffles.za.net Downloading to temporary file I:\tdm_update_win\__tdm_shared_stuff.zip Initiating Download from http://waffles.za.net/tdm/darkmodredist/tdm_shared_stuff.zip Download successful: http://waffles.za.net/tdm/darkmodredist/tdm_shared_stuff.zip Checking filesize of downloaded file, expecting 7558444 Checking download for 'is-a-zipfile'. Checking CRC of downloaded file, expecting 959701f CRC calculated for zip file I:\tdm_update_win\__tdm_shared_stuff.zip = 959701f Downloaded file passed the integrity checks. Removed file I:\tdm_update_win\tdm_shared_stuff.zip Moved I:\tdm_update_win\__tdm_shared_stuff.zip to I:\tdm_update_win\tdm_shared_stuff.zip Downloading to temporary file I:\tdm_update_win\__tdm_textures_stone_brick01.pk4 Removed file I:\tdm_update_win\__tdm_textures_stone_brick01.pk4 Initiating Download from http://darkmod-alt.taaaki.za.net/release/tdm_textures_stone_brick01.pk4 any help would be appreciated. thanks
  4. Since the TDM updater was downloading so slowly, I copied the URL it was accessing and grabbed the file with a download manager (which was an order of magnitude faster, BTW). What can I do with this file? I've tried unzipping it to the TDM folder, but if the updater is to be believed that's not enough. I've also tried copying the file to the temporary path that the updater downloads to, but it just throws the data away and starts downloading it again. I've also tried dragging the file onto the updater executable, but that doesn't seem to achieve anything either. I really hope I don't have to wait for the updater to very slowly download this file for itself!
  • Create New...