Hi,
could we please get a better naming convention for the 'Export Gathered Project' function? Right now it adds the ' (gathered)' suffix, but using blank spaces and parenthesis seems to be causing difficulties on our Linux based render farm dispatcher.
Then is also the slash incompatibility between Windows horrible insistence on the use of backslashes and the forward slashes of Linux and macOS. Sending Windows scene files over to a Linux based render farm requires manual swapping out of file paths. Could this be handled automatically somehow?
Lastly, when can we expect GI cache file sequences to be handled correctly? Right now it's not very smart and only gathers the single cache file you've pointed towards in the 'Read GI cache file(s)' field of the 'Render GI settings' node. So every time I have to remember to manually copy over the other GI cache files to the 'Project_Assets' folder.
I know it's not the sexy new feature you guys rather be working on, but these are frustrating road blocks in a professional studio pipeline that you guys really can't afford to keep inflicting on your customers. Please, smooth out these issues and don't let them linger indefinitely.
Many thanks!
Quote from: DutchDimension on February 20, 2020, 10:56:13 PMcould we please get a better naming convention for the 'Export Gathered Project' function? Right now it adds the ' (gathered)' suffix, but using blank spaces and parenthesis seems to be causing difficulties on our Linux based render farm dispatcher.
I can change this. I'm thinking something like '_gathered'.
QuoteThen is also the slash incompatibility between Windows horrible insistence on the use of backslashes and the forward slashes of Linux and macOS. Sending Windows scene files over to a Linux based render farm requires manual swapping out of file paths. Could this be handled automatically somehow?
Gathered assets are referenced in the TGD file using something like "Project_Assets/texture.tif", so they should work on Linux and Mac. Non-gathered asset references aren't modified at the moment, but I could do that. I was planning to add some automatic conversion of paths to forward slashes in other places that I know of where the backslashes are added, and I'll increase the priority on that. Are you finding this problem with references to gathered assets as well, or just non-gathered assets? Can you give an example so I don't miss something?
QuoteLastly, when can we expect GI cache file sequences to be handled correctly? Right now it's not very smart and only gathers the single cache file you've pointed towards in the 'Read GI cache file(s)' field of the 'Render GI settings' node. So every time I have to remember to manually copy over the other GI cache files to the 'Project_Assets' folder.
I will take another look at this soon.
Matt