You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I drag-and-drop a DDS texture onto PCD2DDS, it correctly sets the hex at offset 10 to the last two characters of the file name. However, if I run PCD2DDS using a batch script:
for %%i in (*.dds) do PCD2DDS.exe %%i
This offset instead uses the first two characters of the file name, resulting in a hash mis-match error when repacking into a .drm file. However the DRM files still run fine in the game, at least with TRA PC which I'm testing on.
Example: I take a file called "40_36.dds" and drop it on PCD2DDS. When I view the resulting PCD file's hex code, offset 10 is correctly written as "36". However, if I take the same "40_36.dds" file and convert it using the batch file instead, the resulting PCD file's hex at offset 10 is instead written as "40".
It's a minor error in an otherwise superb toolset, but I thought it'd let you know anyway. Thank you so much for creating the cdcEngineTools!
The text was updated successfully, but these errors were encountered:
When I drag-and-drop a DDS texture onto PCD2DDS, it correctly sets the hex at offset 10 to the last two characters of the file name. However, if I run PCD2DDS using a batch script:
for %%i in (*.dds) do PCD2DDS.exe %%i
This offset instead uses the first two characters of the file name, resulting in a hash mis-match error when repacking into a .drm file. However the DRM files still run fine in the game, at least with TRA PC which I'm testing on.
Example: I take a file called "40_36.dds" and drop it on PCD2DDS. When I view the resulting PCD file's hex code, offset 10 is correctly written as "36". However, if I take the same "40_36.dds" file and convert it using the batch file instead, the resulting PCD file's hex at offset 10 is instead written as "40".
It's a minor error in an otherwise superb toolset, but I thought it'd let you know anyway. Thank you so much for creating the cdcEngineTools!
The text was updated successfully, but these errors were encountered: