I’ve added some checks and dialogs for read and write where applicable. I also noticed a potential issue related to the path of the model. I’ll push an update in the next few days. I’m also in the middle of adding context menus to the scene explorer to add lights and such, so I’ll have to finish that first.
It does also take 2 days for intellij to validate it, so I’ll try to be quick.
I’ve pushed v1.0.2 to intellij. You should recieve an automatic update once it has been validated. I’m confident it should fix your issue, @Mr_Marbles .
I’ve tracked it down. I noticed you had the SDK open and tried to open the boat model from the test-data sub-module, and in doing the same I am able to reproduce the error.
I’ve found the problem. I registered src\main\resources with the assetManager whenever a project opened, but in some projects this directory doesn’t exist (such as the engine), so when the assetManager iterated over the locators it would stumble upon that directory in the list and found that it doesn’t exist (is not a directory). In addition .canRead() would also return false (because it doesn’t even exist) and would trigger the permission error.
This problem has been solved so far as I can tell. I’ve opened .j3o and .j3m files from all manner of setups and haven’t encountered the issue again.
Since it takes so long for intellij to validate the plugin I’m going to add a few more things to the scene explorer before I push an update: