Hello Kevin,

We noticed that "Import Mesh LODs" option is not checked when importing characters.

The mechanism of LOD build-up is handled by Unreal. If you export characters with LOD meshes, you have to manually tick the checkbox of "Import Mesh LODs" in Unreal Engine.

Ah yes it works now! This - make - so - much - sense - now, in the beta you all had the LODs Seperated in seperate files and now its all imbedded inside the mesh! I was trying different things for about 6 hours going crazy! lol the only sucessful import i had was when I only had 1 LOD set in the LOD window so i was wondering if I was setting the LOD settings wrong in CC3. But this makes so much more sense. Yes! Time to continue forward full blast! 

Sorry about that!  We are still working on the updated tutorial. 

Besides, we plan to fix the design of auto-setup tool in the coming version, it shouldn't crash Unreal in any cases.

I know you are close to release but will it also be usable in c++ projects? The beta works in my c++ project but as for the current release, I have to make a seperate blueprint only project and migrate characters over to my main c++ based project. Which works for now at least i can migrate them over. But i was wondering if thats something that will be supported further down the line. 

The key issue comes from the action of "building" project, and there seems not much we can do after Unreal Engine updated.

You can have characters in your C++ project, but every time you build the project, you have to remove auto-setup plugin.
The suggested process will be:

• Delete the folder "Auto_Setup_1.XX" under your Plugins folder
• Build project
• Copy the folder "Auto_Setup_1.XX" back

Looking at your Build.CS there are a few things that I see missing that the epic games marketplace have us add a a requirement for release builds before submitting plugins I believe this is the cause of your issue for this. 

From the forums: 

From 4.20.x onward you can deploy and use a Plugin without any source files in it (no header and no cpp) as long as:
- It has been packaged from the Plugin window (click Package under the plugin)
- There is an Intermediate folder from the packaging, which contains all precompiled objects and other auto generated files
- It still contains the plugin Build.cs file inside (but all Private/Public folders can be removed)
- The build file contains the statement: bUsePrecompiled = true;
- There is Binaries folder with the plugin dll
- There is a Resource folder with the plugin icon
- There is a Content folder if the plugin contains any content

I my self have a plugin as well on the market place and my build.cs has these as part of the build rules in the build.cs: 

using UnrealBuildTool;

using System.IO;

public class RPGEngineToolKit : ModuleRules

{

   

    private string ThirdPartyPath

    {

        get { return Path.GetFullPath(Path.Combine(ModuleDirectory, "../ThirdParty/")); }

    }

   public RPGEngineToolKit(ReadOnlyTargetRules Target) : base(Target)

   {

        bEnforceIWYU = true;

        bEnableExceptions = true;

        PCHUsage = ModuleRules.PCHUsageMode.NoSharedPCHs;

IWYU (Incude what you use) has been required since 4.16 as they want to make sure your plugin is not including global headers and bloat compile time. 
PCHUsage is the thing I think you all would need to avoid that issue with compile. 

When I get back from work I will do a test compile of my plugin with out source to verify the process and let you all know so it might help you going forward. There are a lot of things epic doesn't really share until you run into the issue. So if I see any other oddness with other releases ill see if I can help you all out as a fellow developer. 

As for the c++ project's: 

This morning I did a test to move your Plugin from the local directory of the project\plugins to the plugins\marketplace directory for normal custom plugins: 
C:\Program Files\Epic Games\UE_4.22\Engine\Plugins\Marketplace\

This allowed me to compile the c++ project without running into the compile issue since the plugin is not in the project directory. The plugin also appears in the plugin section in the editor with no issue. If you want to do this going forward that would be a solution for both project types. But if you want to keep the plugin locally to the project I'll look into it and let you all know as well. 

Thanks again for the note on the import settings.I wish you luck with 4.23!

Thanks Kevin!!
One of the reason why we don't suggest using engine-level installation in the official release is to keep the flexibility for those who may use different versions of plug-in and shader for different projects.

bUsePrecompiled = true;
This is what we tried before, which may work for engine-level installation, but not for project-level one.  We will discuss and do some experiment internally. Thank you again!

Understood. That's one reason I did my test fully local to make sure it matches your desired method of deployment. Hope everything helps! Happy Deving! 

Ue4 crash 4.231 one character 2080ti gpu 16 GB OF RAM