SLADE Discussion - Latest: v3.2.7 (25/Dec/2024)

[Ilya_Efimov]

Hello! I've got a problem when saving a wad/pk3 file with entries having duplicated names. The error says "Error. Multiple entries named ... found in ...". Older SLADE didn't care about this problem. I just decided to update it from older version to the newest one recently and faced this problem for the first time. How am I going to deal with this problem? Am I going to rename/delete each duplicated entry (there are over hundreds of them, pk3 file is not mine)? Or is there an option that makes SLADE not caring about duplicated names? What was the purpose of adding this feature if SLADE has an opportunity to check entries with duplicated names, but it doesn't have an opportunity to rename/delete them all automatically. This is a disservice.

[axredneck]

@Ilya_Efimov, pk3 should not contain files with the same name in the same folder.

[Ilya_Efimov]

@Ilya_Efimov, pk3 should not contain files with the same name in the same folder.

I got it already! As I already said, this problem didn't exist in older versions of SLADE. If there's no solution, using an older version is better then.

[sirjuddington]

Hello! I've got a problem when saving a wad/pk3 file with entries having duplicated names. The error says "Error. Multiple entries named ... found in ...". Older SLADE didn't care about this problem. I just decided to update it from older version to the newest one recently and faced this problem for the first time. How am I going to deal with this problem? Am I going to rename/delete each duplicated entry (there are over hundreds of them, pk3 file is not mine)? Or is there an option that makes SLADE not caring about duplicated names? What was the purpose of adding this feature if SLADE has an opportunity to check entries with duplicated names, but it doesn't have an opportunity to rename/delete them all automatically. This is a disservice.

If you really must have multiple entries with the same name, you can set zip_allow_duplicate_names to 1 either via the console or advanced preferences. I agree there should probably be an option to auto-rename duplicates.

[Ilya_Efimov]

Hello! I've got a problem when saving a wad/pk3 file with entries having duplicated names. The error says "Error. Multiple entries named ... found in ...". Older SLADE didn't care about this problem. I just decided to update it from older version to the newest one recently and faced this problem for the first time. How am I going to deal with this problem? Am I going to rename/delete each duplicated entry (there are over hundreds of them, pk3 file is not mine)? Or is there an option that makes SLADE not caring about duplicated names? What was the purpose of adding this feature if SLADE has an opportunity to check entries with duplicated names, but it doesn't have an opportunity to rename/delete them all automatically. This is a disservice.

If you really must have multiple entries with the same name, you can set zip_allow_duplicate_names to 1 either via the console or advanced preferences. I agree there should probably be an option to auto-rename duplicates.

Thank you very much!
Edit: Unfortunately, it doesn't work.

[Blzut3]

What was the purpose of adding this feature

It was added because zip archives with duplicate entry names have portability issues. At least for ZDoom and it's children, the semantics for loading such a file is to pick one of the duplicates effectively at random as the canonical file. Which one is picked varies by compiler runtime used to make the GZDoom binary. Most often this was noticed by Zandronum users since it would cause mods to break when hosted by a Linux server for example. Given that the engine literally ignores the unused duplicates there's literally no reason for them to exist and they waste space and cause the mod to randomly have issues. Now Slade is able to diagnose this error and "force" it to be corrected. Better late than never.

While it's recommended to do so manually since only a human can really know which one is the correct file, if you don't want to manually resolve the duplicates there's an easy fix. Simply rename the file to .zip and then extract with a zip tool of your choice. Now repack those files you just extracted into a new zip file and rename back to pk3. Your zip tool/operating system will clean up the duplicates at random for you. If the mod breaks after doing this then it was already broken before, it just didn't manifest in your particular setup by chance.

[Ilya_Efimov]

What was the purpose of adding this feature

It was added because zip archives with duplicate entry names have portability issues. At least for ZDoom and it's children, the semantics for loading such a file is to pick one of the duplicates effectively at random as the canonical file. Which one is picked varies by compiler runtime used to make the GZDoom binary. Most often this was noticed by Zandronum users since it would cause mods to break when hosted by a Linux server for example. Given that the engine literally ignores the unused duplicates there's literally no reason for them to exist and they waste space and cause the mod to randomly have issues. Now Slade is able to diagnose this error and "force" it to be corrected. Better late than never.

While it's recommended to do so manually since only a human can really know which one is the correct file, if you don't want to manually resolve the duplicates there's an easy fix. Simply rename the file to .zip and then extract with a zip tool of your choice. Now repack those files you just extracted into a new zip file and rename back to pk3. Your zip tool/operating system will clean up the duplicates at random for you. If the mod breaks after doing this then it was already broken before, it just didn't manifest in your particular setup by chance.

Thank you for the information! Anyway, I guess I'll use one of older versions for this as it doesn't care about entries with duplicated names, because it was a real problem when file wasn't going to be saved after I edited a big amount of data in it. By the way, the newest version has features that older versions don't have and vice-versa.

[bimshwel]

alas the new Slade version 3.2.7 gives me a "procedure entry point" error, "CreateFile2 could not be located in the dynamic link library kernel32.dll" presumably since I am using windows 7, as that seems to be the source of most of my surprise post-update non-starts these days.
https://imgur.com/a/Hm4KD3Z
The previous version 3.2.6 still works, thankfully! I need to finish something before the year ends or I will turn into a pumpkin.

[Gothic]

Between v3.2.6 and v3.2.7, did something change with the way it handles MIDI playback? I'm using Fluidsynth on v3.2.7 (x64) and sometimes when I select another midi while still playing, notes from the previous one are still playing even when I press stop and I have to reset the MIDI player. This problem is not present on v3.2.6.

[Laerrus]

alas the new Slade version 3.2.7 gives me a "procedure entry point" error, "CreateFile2 could not be located in the dynamic link library kernel32.dll" presumably since I am using windows 7, as that seems to be the source of most of my surprise post-update non-starts these days.
https://imgur.com/a/Hm4KD3Z
The previous version 3.2.6 still works, thankfully! I need to finish something before the year ends or I will turn into a pumpkin.

I am getting that problem too. Really want that copy and paste Z info on Things.

[bimshwel]

are you also using an outdated operating system?
any version of slade is better than wintex, fortunately.