State:Closed|TargetRelease:No Target|icon_bug|icon_modo|database:public|Resolution:Duplicate|BugID:297187|
Problem summary
Normal behaviour would be for the import function to copy the data across and then unlock the file again, so that you can move/delete/make changes to the file outside of the program.
Tested against Nuke and Maya, which both unlock the file correctly after importing.
Customer reported version
modo.13.0v1
Customer reported platform
windows10
Steps to reproduce
- Import an OBJ into MODO
- Open your file browser (Windows Explorer or Finder)
- Try and delete the OBJ file from the file browser
- It will say that the file is in use by MODO
- Close the MODO scene (not the application)
- Try again and it will still say it is in use
- Try this in Maya or Nuke and compare results
Expected behaviour
The OBJ file should be deleted.
Actual behaviour
The OBJ file is locked as "in use"
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
13.1v1 - Windows 10
13.0v1 - Windows 10
12.2v2 - Windows 10
12.1v2 - Windows 10
12.0v1 - Windows 10
11.2v3 - Windows 10
11.1v1 - Windows 10
11.0v3 - Windows 10
10.2v4 - Windows 10
Unable to reproduce bug in:
13.1v1 - macOS 10.13 - Centos 7
Earliest version tested
10.2v4 - This issue appears to be in all versions of the product.
We're sorry to hear that
Please tell us why