Quote from: Oshyan on August 06, 2018, 06:59:20 PM
File sequences of any kind are not supported by the Gather function at this point. It's something we'll need to add in the future.
I think you're kind of missing the point in this case: The real problem isn't that the file sequence isn't being gathered. The
real problem is that there's no way to tell the gather process to just point the (newly-produced) "gathered scene" to a cited path, rather than have it attempt to gather the single file referenced by that path.
Put another way, it's about telling the gather process
whether to gather or just keep as a path reference. There are many cases where if you've got shared content stored on network shares or such, you might prefer to keep those as "common" path references rather than gathering them (read as: duplicating them) into the package.
That the gather mechanism can't gather file sequences is secondary. Even if it could, the user already has the file sequence on a network share, so wouldn't necessarily
want it to be gathered. It's about allowing the user to decide what gets gathered and what gets referenced on a finer-grain level than just by-scene. Esp. in group work environments, having the ability to gather scenes while retaining shared content references (instead of copying them) is quite useful.
Another case where gathering is often undesirable involves certain types of easily-regenerable cache data: In many cases, it is often more efficient to have the recipient regenerate the cache data on their end, rather than for the sender to package and transport large quantities of cache data. Having the ability to tell the gather mechanism to just reference the path rather than gather the file(s) in such cases can help minimize distribution archive sizes.