but I found other, more recent posts where people say they’re still having the same problem.
One workaround I found and tested is the following:
This is what a user said:
“I used for another plugin would be to have what ever materials you want/need in a separate project then migrate to the project you actually want to use without plugin. Make sure when you migrate you select migrating the plugin contents in the pop up that confirms which assets to move. For future asset imports you will need to import into the “import” project then migrate only the new files. Then simply renter the name of the master material for the material instance of the newly migrated asset and all the parameters set from the fab plugin will already be there. This is time consuming but should work well if you need to use this right now”
It’s a bit time-consuming, but at least it lets you keep working for now
Others say that disabling the plugin allows them to do packaging
Here are the links to the posts discussing the issue:
