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
This error comes up when there are a lot of files involved. There are no missing files reported and I attempt to create a zip to get rid of the unused files, but it fails. I always take the map with all its files away to another folder in my desktop to create the res files so resguy does not involve the entire svencoop folder. So far it always worked.
ERROR:
Duplicate filename on disk:
sound\lastunic\ambience\appel.wav
sound\lastunic\ambience\appel.wav
Cleaning up... Done
Archive creation failed! Try a different option.
There are obviously no duplicates.
The text was updated successfully, but these errors were encountered:
Bumping this for important info. Just found out a fix for it, which also showed me what was wrong. This happens whenever a file reference inside the .bsp entity list differs in lowercase or uppercase from the actual file path. The fix is rename the file again, or ripent the .bsp to rename the reference accordingly.
Example:
Inside the .ent file of a .bsp you have "sound\lastunic\ambience\Appel.wav"
Outside of it, in the actual folder with the files you have "appel.wav"
The wrong part is that resguy prints the thing always in lowercase so you can't know the difference, you have to look for it ;)
This error comes up when there are a lot of files involved. There are no missing files reported and I attempt to create a zip to get rid of the unused files, but it fails. I always take the map with all its files away to another folder in my desktop to create the res files so resguy does not involve the entire svencoop folder. So far it always worked.
ERROR:
Duplicate filename on disk:
sound\lastunic\ambience\appel.wav
sound\lastunic\ambience\appel.wav
Cleaning up... Done
Archive creation failed! Try a different option.
There are obviously no duplicates.
The text was updated successfully, but these errors were encountered: