#1: just finished saving postproc parameters ;)
Tested that quite extensively over the days, well, what to say - again, it makes life a lot easier but I would still prefer if those post processing presets would be somehow linked or could contain lighmix's ones too, that would be way easier to manage. If it is, for some reason, impossible to do then at least making those presets file extensions different might be a good idea and could make it a little more usable and a little more foolproof solution, so loading and saving post process preset wouldn't see lightmix's ones and vice versa thus eliminating possibility to accidentally overwrite one with the other, which happened to me a couple of times already ))
Still I think it would be better to have one type incorporating both lighmix and post presets - when saving lighmix's ones the post settings would be saved automatically with it and the other way around - if lighmix render element is not present in the scene then simply ignore those values and save only post ones, same could go for loading lighmix\post preset saved from lighmix containing scene into one where it is not enabled - corona could simply ignore those that's all )
About my earlier complaints with ram usage increase in earlier dailies - well first of the recent installer builds fixed that, so probably that was indeed some crappy versions of C# or something else installed with some other soft, well, am I glad it's fixed + now I know how to fix that if it occurs in the future and, I'm most sure, it will ))
