(10-07-2024, 04:51 PM)josemendez Wrote: I guess you meant re-*imported* Obi 7? If you export your Obi folder to a package, no changes will take place in your project and you will still be using Obi 6.I suspect that the changes in GUIDs were caused by my extensive use of Obi Fluid 6.5 and the numerous script modifications I made. As a result, the associations were lost when reimporting Obi Fluid 7.0. Could you please advise if there is any way to repair the GUIDs of the Obi Fluid 6.5 assets so that the custom package associations are correctly maintained when importing version 7.0?
It’s all explained step by step in the link I shared in my previous post, including small pitfalls and changes in API method signatures, callbacks, etc.
No, why would you? The files that make up Obi are no different than any other files in Unity: if you import a file with the same GUID than a existing one, it will replace the old file. If the file defines a component, the new component will automatically replace the old one in all scenes/prefabs. If you delete existing components from your scenes Unity will lose track of all references and you will need to re-do everything from scratch.
All that is needed is to delete the old /Obi folder, import the new one, and then remove missing references to components that no longer exist. Up to this step, this process is the same you would follow with any other Unity asset. After this, you will need to perform the steps that are specific to Obi: re-generating blueprints, updating any custom scripts that use Obi’s API, etc.
Kind regards,
Thank you and best regards.
