Quick update! Dev Team might revise the code a bit to make it better. 
I will provide more information tomorrow.

another good tip about using "tga(targa format) is which it can be also used to when needed reduce the number of textures cuz using tga it allow you to use the alpha(opacity) direct from the main texture.

Using photoshop or any other image editor you can go to the collor channels and on that add the "alpha channel( the black and white used in opacity), when it don't have you can add one alpha channel, among the primary channels them save it as tga and when asked save it as 32bit(to store the alpha it need to be 32bit) than in unreal instead of use another texture you can direct to the base color and grab the alpha node(the last one) and use it instead of a extra texture.

i'm not too sure if it can be used all the cases but in some cases(specially when the texture detail is fixed) it can be very helpfull, probably in cases where you want to add the details outside the base texture then have the not being on the base must be important and even in that cases you can make the alpha being part of the detail map.

here a exemple:



i've created the alpha channel for the body hair, it allow me to use the base color as alpha, because unreal like the case of AO, Rougness and metalical case where you can use the channel colors you also can add a alpha channel then use that alpha from the base color to use it instead of have a alpha texture outside and in case you would need that alpha all you would need is just open the image in a image editor like photoshop and use that channel to create a alpha texture.

Thank you Ellessarr. This is what we enhanced in CC 3.04 & Auto-Setup Plug-in v2.0.
From CC 3.04 release note, "New ORM texture option for the Unreal pipeline FBX export.  ORM textures are split by Unreal Auto-Setup Plugin into separate channel assignments for AO, Roughness, and Metallic."

Back to the error issue in tga format, we found the root cause after your explanation. Much appreciated!
There is a bad design on the current Auto-Setup Plugin, which forces to change the default setting of Sampler Type to be Linear Color when creating node. 
Due to the inconsistency, you will see the error, and have to manually fix it like this: 


The upcoming plug-in will make the setting to be what it supposes to be.
Thank you!!

Hi Kevin,

We observed the same issue after upgrading to Unreal 4.21 or later version, and we are surveying and searching for the solution.  We will keep you posted.
The workaround at the moment is to remove the plugin when building the system, and install the plugin back after system is built.
You mentioned that the installing to the engine folder works, can you double confirm that? 
As far as we know, it should have the same behavior (error) as project.

When I moved the one that error-ed out into the engine folder yes the error was the same when compiling but placing the pure files from the zip into the engine path that works and loaded. If needed I can try a blank c++ project with a cc: export verify it works and zip the files for email a mega link for you devs.

Also, make sure you have the new release/update as I know they fix things in ninja release that cause a headache for us market place plugin creators.

When imported fbx with Beta2.1, LW/HQ Shader options are grey, I cannot select them.

Hello astron10,

Have you copied the Content folder to the project? >> reference

Hello! Any idea why does it look like that after CC auto tool imports it in UE4? It looks so with LW and HQ shaders (UE 4.21)

By the way, if i use "Default" import i take much more better result