I moved this discussion to a separated thread, to not mix it with other old cases.
Checking our archives, i only found two cases which would be related with the slowness issue:
a) When Forest intializes, it scans the texture paths (defined at Customize->Configure Project Paths->External Files), searching for all 'maps' folders.
For some customers, which use multiple texture paths located in network folders, this process may take a long time.
This was solved in recent Forest versions, skipping network paths in the scanning process.
This may be configured at Library Browser->Preferences->Options (see attached image), although this option ('Exclude Network Paths') is enabled by default.
In case you use an older Forest version, the scanning process can be disabled at forestpack.ini (stored at C:\Users\<user name>\AppData\Local\Autodesk\3dsmax\<max version>\ENU\en-US\plugcfg), changing these two variables:
checkTexturePaths=0
collectTexturePaths=0
b) A couple of customers, reported a similar issue when loading presets from the Library. It was caused by an issue with the 'Scene Converter' tool.
By default this tool is opened automatically when Max detects a missing DLL. But if the tool was disabled in their configuration, it would cause a long Max freeze (several minutes), when loading the assets.
We cannot reproduce it, and i'm not sure what Max versions would be affected.
I suggest you take a look to it, and be sure the Converter tool is enabled at Rendering->Scene Converter (see image).
If none of the above works, we'll need more information from you to find the cause.
As said in previous posts, if we cannot reproduce that problem here, there is no way we can identify or fix it.
Regarding the 'Silentum' tool, this script doesn't disable the units warning message. It just detects when the dialog is shown, and simulate a 'click' in the 'Ok' dialog button (sending a notification to Windows) to close it.
This is basically is hack, and would cause undesired side effects. This is not something we want to add in our plugins.
As said before, this warning dialog is part of the Max behaviour, and we cannot change it.
We only may ask to Autodesk some option to disable it (although i guess we already requested it some time ago). But even if such option is added, it would be available only in future 3DS Max versions.
And please, let's calm this discussion.
I will be happy to help you with the tecnical issues, but i'm not discuss about our business model, or compare iToo Software with other companies or products.