Using exporter 4.4.0-beta, the two inspector integrations for the AI-thingy and opening the ts-component are using different project path formats. This way the type cache gets rebuilt two times per custom MonoBehaviour, whenever the inspectors are created/initialized, leading to a very sluggish inspector experience and lots of allocations.
Everything works smooth again after changing InspectorComponentLink.cs:158 to
if (exportInfo) _lastProjectDirectory = exportInfo.GetProjectDirectory();
Hi Krizzl0r,
Thank you for your contribution regarding the issue of the type cache rebuilding. It seems you’ve identified that changing the line in InspectorComponentLink.cs to set _lastProjectDirectory using the method exportInfo.GetProjectDirectory() resolves the performance issues associated with the multiple cache rebuilds.
This change indeed sounds like a solid solution to streamline the inspector experience. By ensuring that all components utilize a consistent project path format, you can avoid the need for the type cache to rebuild unnecessarily.
If you’re looking to implement this change or share it further, you should ensure that other developers are aware of this workaround. Additionally, consider running some tests post-implementation to confirm that performance is enhanced across different setups without introducing new issues.
If you need further assistance with integrating this modification or have additional questions regarding Needle Engine, feel free to ask! You can also check the Needle Engine documentation for more insight on how to effectively manage components and performance optimizations.
Let me know how else I can assist you!
0 replies left - Get a PRO license for more AI replies.
thread_sa5TL2xXovkQcL6O1Z4cO34r
Reply to this message to continue the conversation