Skip to content
View in the app

A better way to browse. Learn more.

ResHax

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Help us keep the site running.

Error unpacking Starlink Battle For Atlas SDFDATA/SDFTOC

Featured Replies

  • Author
  • Localization

Nooga, posted Sun Sep 26, 2021 3:54 am (66654)


Hi there. I'm trying to use the Ubisoft_SDF script from aluigi.org/bms/ubisoft_sdf.bms to unpack the archives of Starlink: Battle for Atlas' PC version, but get an error as detailed below. Oddly, this doesn't happen when using the script on the Switch version's files. Unfortunately that version has lower quality assets and compressed/swizzled lower res textures and thus doesn't suit my needs. I also tried using the Snowdrop script from the quickbms website, but it just hangs and does nothing, maybe spitting an error about "can't read 4 bytes from offset" if I'm lucky.

Any help is greatly appreciated, thanks for your time :)

Code:
  offset   filesize   filename
--------------------------------------
Info:  algorithm   249
       offset      00001eb3
       input size  0x0064609f 6578335
       output size 0x00ce1dc8 13508040
       result      0xfffffff5 -11

Error: uncompressed data (-11) bigger than allocated buffer (13508040)
       It usually means that data is not compressed or uses another algorithm

Last script line before the error or that produced the error:
  31  clog MEMORY_FILE OFFSET INFO_ZSIZE INFO_SIZE

- OFFSET       0x00001eb3
- ZSIZE        0x0064609f
- SIZE         0x00ce1dc8
  coverage file 0    99%   6578355    6586242    . offset 00647f52

Press ENTER or close the window to quit
  • Author
  • Localization

aluigi, posted Sun Sep 26, 2021 8:27 pm (66677)


If we are lucky it may just be a different compression algorithm.
If you open the archive with a hex editor, what data do you see at that offset 0x1eb3?
Alternatively you can just upload and link here the file created by this script:
Code:
log "dump.dat" 0x00001eb3 0x0064609f
Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.