I have a very large patch, which includes many abstractions and subpatches. All is working correctly, but it takes a long time (~15 seconds) to launch, whether within the Max environment or when built as a standalone (my desired goal). There are a lot of time consuming processes buried within many of the subpatches.
My main patch itself is not large or complicated, but it loads a bpatcher which in turn loads many of the other problematic subpatchers. I've tried scripting the creation of that bpatcher dynamically, and that does work within the Max environment to allow the main patcher window to display instantly, before the 15 second wait begins (so long as I deferlow the scripting messages).
When building that as a standalone though, the standalone doesn't work because the collective does not include all the patches and files necessary - this is expected because those are created dynamically by my top level patch, and there's no way Max would know to include those files in the collective. So I included those files in the application build script, manually adding those files to the collective. That allows the standalone to work again, but now it's super slow upon startup all over again.
Does anyone have a workaround for this dilemma?