On 18/02/2015 at 16:02, xxxxxxxx wrote:
Sorry about the delayed response, I was busy with other matters lately.
Yes, there's a misunderstanding here, as I find it's a complicated situation:
- I assume you see C4D as a black box when I get broad situational questions that lack example code: "Can you please explain me what exactly happens inside the core ... ?". I figured that meant 'message system', so I searched for code that handles MSG_GETALLASSETS, as that's the closest to code I was supplied. Otherwise, there's no way for me to know where to look across millions of lines of code for 'core' functionality.
- When I report back the inner workings, I assume it shifts your view and may answer the real question you might have. Otherwise, I expect a response with clarifications and questions that reveal the exact issue needing to be solved, and within a reasonable delay to keep up the pace to resolution. Clarification only arguably occurred with your recent response.
- From my direction, it appeared to be the same question as back in November, just asking for more details. Without clear information, it seems I gave answers to the wrong questions. From now on, I'll ask for clarification at the beginning instead of assuming too much.
As for the confusion about duplication: Sorry, I didn't specify clearly what I meant. The code I looked at does not immediately imply any duplication avoidance is attempted, even if I theoretically could have found some. There could be duplication reduction happening either before (by not sending the message down certain paths) or after it was done collecting the assets (I didn't explore that possibility). However, if you still find at least some duplicates, it means there isn't an aggressive attempt at reducing duplication. Plus, to try to figure out all cases of duplication reduction would mean spending an inordinate amount of time analyzing the code, while unlikely to provide you with any useful information.
That leads me to answering your new (or at least clarified) question, why the Team Render duplicates the document: When rendering is launched, all the data is duplicated so that you may continue working on the original data while rendering executes. That Satara states tracking assets on a per document basis seems to do the job makes sense. I actually don't know more specifics about the whole process (ie if any data is left out, etc.).
Please let me know if it works out for you or not, I'm glad to help, even if the process does not always go smoothly.
SDK Support Engineer