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
I just discovered that DSMS doesn't close file handles properly after loading a map.
I noticed this because I wasn't able to delete a mapbnd from DS3 file until I closed DSMS. The same also happened with a tpfbdt. This is a huge problem for me, because I mainly mod DS3 via a custom program I made that modifies game files for me. So DSMS locking those files completely ruins my workflow...
I'm very certain that this is a resource leak, because the files were still considered in use by the OS even after I unloaded the map in DSMS. I also noticed that which files were considered in use was random. Sometimes it was just a few dozen, sometimes more, and always different files.
I confirmed that this bug is present in versions 1.10 and 1.11.1. Version 1.06 doesn't have the bug.
The text was updated successfully, but these errors were encountered:
I just discovered that DSMS doesn't close file handles properly after loading a map.
I noticed this because I wasn't able to delete a
mapbnd
from DS3 file until I closed DSMS. The same also happened with atpfbdt
. This is a huge problem for me, because I mainly mod DS3 via a custom program I made that modifies game files for me. So DSMS locking those files completely ruins my workflow...I'm very certain that this is a resource leak, because the files were still considered in use by the OS even after I unloaded the map in DSMS. I also noticed that which files were considered in use was random. Sometimes it was just a few dozen, sometimes more, and always different files.
I confirmed that this bug is present in versions 1.10 and 1.11.1. Version 1.06 doesn't have the bug.
The text was updated successfully, but these errors were encountered: