What should happen is: Bug report, yes. Personally I'm quite bored about FP + Corona issues because they exist and mutate since ever. 1 bug fixed, 1 new surfacing. And I sometimes don't get who's QA is doing what exactly.
I can only guess that "processing hidden FP objects" is an Itoo issue, maybe even a 3ds Max one. But I'm not going to report it because I'm not using the newest plugin version (which would cost me a lot of time to update because of that crazy deployment procedure for a centralized, network based FP version), I'm not using the current 3ds Max version and I don't want to report to Itoo, Render Legion and Autodesk at once just to read from everybody that they are sorry but it's the fault of someone else (if I ever get some feedback from certain you-know-who-companies that is.).
And the issue with referenced cameras: This is not directly solvable anyway imho because it works like it should: changing the view rebuilds and optimizes the FP objects or rotates billboards. In case of IR I cannot say if the Corona team is even able to block those. It may also be unwanted in many cases that you do not get in IR what you would see in the final render and who can/should/has to react to, say a "freeze all Forest objects" or "Disable object" option inside FP?
The whole thing takes place in a triangle with complex software involved, so it's not exactly easy :) Anyway, you can have amazingly fast IR scenes full of (FP) vegetation currently with an even more amazing IR recover time if you don't fall in any of those traps.
Good Luck
« Last Edit: 2019-06-26, 15:43:18 by Frood »
Logged
Never underestimate the power of a well placed level one spell.