Hi Tim, thanks for coming back to me.
I appreciate what your saying. As a programmer myself (boring intranet and web apps), I don’t like the idea of having to read through endless documentation to manually re-adjust parameters or implement alternative solutions when the limitations and suggested workarounds are known. Surely it would be better to have these steps automatically implemented in a non-desturictive way (maybe by creating a duplicate project with the ammendments for that platform) during the packaging process, or maybe if this is not feasalbe have a pre-packaging function that checks for known incompatibilities and recommends fixes, with an apply “yes or no”?
For example, if exposure bias is increasing lighting in the editor, but is not supported in the platform being packaged for you might get a message like "post processing exposure bias is unsupported in the target platform, increase all lights/self illumination by x%? Yes/No.
I’ll post screenshots later though.
Cheers