Hello. I'm sorry you've had trouble with the tool. It's not common to have problems using the tool. LOD swapping should work on any Render Pipeline and any supported version of Unity. There might be something wrong with your development environment. LOD generation is unpredictable due to its nature of simplification, but it's possible to adjust the parameters to get better results, especially if you didn't get what you expected. However, I noticed you haven't contacted me for support. Unfortunately, I can't help without you first requesting support. You can contact me through my support email "mtassets@windsoft.xyz". I'll be happy to help.

Hello! Thank you for choosing and using ULOD! Your feedback is very welcome, but I would like to explain some of the points you raised. :) The tool does not contain pop-ups, but it does contain warning dialog boxes that appear at "key" moments during the use of the tool, usually to alert you to something important that needs to be highlighted, and things like that. One of these moments is right after importing the tool, which generates a dialog informing you whether the import was successful, etc. This dialog only appears once, during the first import of the tool. I understand that it can be a bit annoying for more experienced Unity users, but for beginners, it can provide guidance on the first steps to follow when using the tool. :) Still on the subject of dialog boxes, another example is when performing a scan, in which the tool warns you not to delete the component that contains the scan information, so that it is possible to undo the scan in the future. This dialog box has an option to dismiss it and never appear again. These are the main times when dialog boxes appear during the use of the tool. In any case, with the next update that I have planned for ULOD, this last dialog box will be extinguished, since the tool will use a different mechanism for persisting scan data. In any case, I understand you well, and the last thing I want is to leave things feeling "spammy" during use, after all, I also use my tools and I always want to offer the best I can for my clients and for myself. However, there are specific situations in which these dialog boxes really are necessary. As for the Assets folder, I really understand you. At the moment ULOD relies on being in a specific place to perform some important operations. Previously, the tool was located in the "Assets/MT Assets" directory, but knowing that the ideal is to have a better organization of the project, I changed the default directory of the tool, and now it is in the "Assets/Plugins/MT Assets" directory. This way, the tool folder will not "break" the visual organization of the folders, inside the "Assets" folder. I really understand this, and a bunch of asset folders inside the "Assets" folder, is not good. As for the files generated by ULOD, ULOD only generates files that are absolutely necessary within your project. It also automatically deletes them when they are no longer needed. An example of this is the "greetings" file that is created with ~0Kb, just as a checker, to ensure that the import dialog does not appear more than once. In the past, I have tried to rely on other mechanisms such as a "PlayerPrefs" equivalent for the Editor, and there were cases where it was sometimes unreliable and generated a spam of the welcome message. So I decided to use a simple file, which solved this problem permanently. Anyway, I agree with all your points, I just wanted to explain each of them as it relates to ULOD. :) Thanks again for the review! Kind regards