Hi folks! To update this thread on bulky Project Saving/Syncing failures that may appear from time to time.
This typically happens to the extended Projects with more than 500+ connected Condition Blocks.
Not sure if the solution I've found was already described on this Forum or in any of the platform Manuals, but just for the Community contribution sake:
There is no need to store all the Condition blocks you've already built once in the same Project if those planned to be used for the future use on new Projects, as that entails that your Project will eventually become more bulky and unexportable.
In case anyone needs to use any of the older Condition blocks or some parts of the previous Projects you've already built, FXDreema actually supports Copy/Paste operations through the OS Default Clipboard BETWEEN THE DIFFERENT PROJECTS
Example: one can store his older Condition Blocks in a single "Archive project", occupying any of the Project tabs: OnInit/OnTick/OnDeinit etc for a later use on a new Project, and copy a certain Condition Blocks from the "Archive project" to any new Project through the clipboard, when required
The only requirement would be the "Archive Project" must remain exportable, to make sure you always keep a local recovery backup copy.
This allows keeping the new Project lightweight, while retaining access to the older Condition blocks through an "Archive Project", thus the building and syncing operations on a new Project will be performed much more efficiently and quickly
Additionally, by organizing a personal FXDreema workflow according to the scheme described above, user can significantly optimize the time spent on EA testing and building operations, as he can always use parts of his previous Projects to start with or enhance on the new Projects WITHOUT REBUILDING THE SAME BLOCKS FROM THE GROUND UP each time
Hope that will help many of the aspiring FXDreema users moving forward CC @l-andorrà