Cargo + Unreal 5.3 only Imports the meshes and the materials do not translate into the engine.
D
Dimitar Asenov
I have managed to connect Cargo with Unreal manually by copying the contents of the plugin for the appropriate version to my project's plugins folder. However now it only Imports the meshes and the materials do not translate into the engine.
D
The plugin that I managed to manually install be it with the drawback of not translating materials just deleted itself somehow. The obvious answer for me how to solve this would be to manually override the default engine installation folder set in the configuration of Cargo
Phil Kuzmicz
Hi Dimitar Asenov!
I would recommend you remove all Cargo installations you currently have and start a fresh install so we can walk you through any issues you may have with installing it the recommended way.
I believe that Cargo is meant to go into your base Unreal's plugin's folder instead of the project specific one. Putting it directly into the Project's plugin folder might cause errors, including the inability to package your project.
D
Dimitar Asenov
Phil Kuzmicz: Hey Phil, sure but the setup requires a directory of a .uproject file because quote: "The Unreal 5.3 Plugin needs to be installed on a per project basis. Please locate the UProject file that you would like to connect Cargo to, or create a new project. Please wait while we install all the necessary files."
Phil Kuzmicz
Dimitar Asenov: I actually just checked my Cargo install and it looks like they moved the plugin from the engine to to project directory! It used to be hosted in the engine files...
Regardless, I would run through the regular installation process to make sure the cargo app is syncing properly.
Another place to check to make sure your files are being referenced properly is the Download Folder. Some users have changed this to be inside their project, which has caused issues. Make sure it is in a place that stores temporary files, like the default AppData\Roaming folder.