Is it ok to mix Unity Pro features into things used by Unity (non Pro) users?

News & General Discussion
1

Hi,

I made an asset for Unity Free users and I want to add a feature set for those who switch to unity pro or try the Unity Pro Trial.

For this I have some core components and to enable the features when Unity pro is available I added to these components the OnRenderImage method. Everything works like a charm so far, Unity Free users can use the component and Unity Pro users gain the benefits from unity pro and can use my component too, plus the things OnRenderImage offers them.

But, there is a single problem, after the first start in the editor (and in the Build) at the unity Free users, an error message appears in the log:

I understand the message but I am not happy that this message appears (only once in the editor as long as the editor runs, again when the editor is restarted). The asset knows that it is not capable to use the features in the Unity Free case and will not rely on the Unity Pro features.

Removing the OnRenderImage methods from the component is a no go for me, as I want to keep the maintenance from user side at a minimum. I cant use any PreProcessor directive (no #if UNITY_PRO as it doesn’t exist).

For now I have 2 options:

  1. Display a counter log message ala “Unity Free mode enabled, please ignore the error message regarding missing RT capabilities.”

or

  1. Use custom PreProcessor directives which the user needs to activate inside the UnityEditor settings for it.

I want to stick to point #2, with a message dialog which tells the Unity pro user how to activate that. What do you think, did I overlook something?

tl/dr: Can I tell the user that an Unity error is not bad at all and was expected from the asset which invoked the error?

2

This page:

talks about an internal editor script API that tells you if you have Pro. I don’t know if it still works.

3

Can you wrap the pro-only stuff in some kind of compiler directive so it ignores it on free?

4

@Graham Dunnett:

I use SystemInfo.supportsRenderTextures which returns false for Unity Free users and works in Edit and Build/Play mode, but this doesn’t help me to prevent the error message for just having the OnRenderImage method in my component.

I think I will go with my second point and that what ImaginaryHuman suggested. i will add preprocessor directives and tell the user how to activate these, its a little bit work for the user, but I think its reasonable and only needed one time.