1 Unreal Cineware Engine
This project aims to improve integration of Cinema 4D and Unreal via the implementation of Cineware Engine. This generates thescene on-the-fly, eliminating the need for Cineware caches. Thanks to the flexibility this offers, there's a new option to modify Cinema4D attributes directly within Unreal Engine.
Please make sure to read the guide carefully. Expect errors, bugs and general frustration. There is still some unpolished behavior; before reporting a bug check the Known Issues segment at the end of this document.
The plugin is supported on both platforms Mac and Windows
If you do not have Unreal Engine installed, head over to https://www.unrealengine.com/en-US/get-now. Select your appropriatelicense, create an Epic Games Account, and download the Epic Games Launcher. Run the installer and open the launcher. Enteryour credentials and select Unreal Engine in the left, navigation menu. Select the
register Library. You should see a content area labeled Engine Versions. Click the plus sign to install the version needed.
The shipped plugin has been compiled for Unreal Editor Version 4.27.1 with BuildID 17155196. Downloading the latest version of4.27.1 should fulfil these criteria. Unzipping the received package reveals two directories which will need to be copied into the Unrealenvironment for the setup to work.
1.1.2 Copy plugins
Datasmith is a project by Epic Games to allow the company's products to import a broad range of proprietary file formats, including.c4d. Maxon partnered with Epic Games to enhance the functionality of this particular bridge. We forked an earlier state ofDatasmithC4D from Epic Games and added a significant number of changes (also means that bugs encountered in this version ofthe Datasmith importer may already have been fixed in the mainline).
These changes will be merged with Epic's current codebase and shipped natively with later versions of Unreal Engine. For now, wehave to replace the shipped DatasmithC4DImporter version.
On Windows navigate to your Unreal Engine installation, typically C:/Program Files/Epic Games/UE_4.27 (Windows)
On Mac navigate to your Unreal Engine installation, typically Macintosh HD/Users/Shared/Epic Games/ UE_4.27 (Mac)
This path will be referred to as $UE4_DIR within this document.
The DatasmithC4DImporter plugin is located at $UE4_DIR/Engine/Plugins/Enterprise/. IMPORTANT Make a backup copy of theinstalled DatasmithC4DImporter folder. We may need it later. After the storing a copy of the directory, replace it with theDatasmithC4DImporter directory we provided. The path $UE4_DIR/Engine/Plugins/Enterprise/ DatasmithC4DImporter/ should nowcontain the directories Binary, Content, Documentation, Intermediate, Resources, Source, and a .uplugin file.
This is a second plugin which stores exposed properties into an asset and allows users to edit these values via UI, Blueprints orC++. Future reimports of the imported .c4d file will apply these values to the scene. This plugin is configured to act as a (shared) project plugin. This means you can either copy this plugin to the Unreal Engine environment to have access to it across projects orcopy it to projects only. For simplicity we suggest installing it as a shared plugin and simply not enabling it for specific projects.
Typically, the path for shared plugins is $UE4_DIR/Engine/Plugins/Marketplace/. Should this directory not yet exist, please create it.This directory is also where all plugins purchased and installed from the Unreal Engine Marketplace end up.
The path $UE4_DIR/Engine/Plugins/Marketplace/CinewareForUnreal/ should now contain the directories Binaries,
Content, Intermediate, Source and a .uplugin file.
Should you decide not to install it as a shared plugin, rethink your decision... Still?
Then create a new project by launching the Unreal Engine and wait for a project hub window to appear. Create a new project withthe templates of your liking. Select a location, click create and wait until the Editor has launched. Close the Unreal Editor andnavigate to your project directory, from now on referred to as $PROJ_DIR.
$PROJ_DIR/ should contain a bunch of directories which depend on the template you selected and a .uproject file. Create a directory,name it Plugins and copy the provided CinewareForUnreal directory into it. The path $PROJ_DIR/ Plugins/CinewareForUnreal/shouldnow contain the directories Binaries, Content, Intermediate, Source and
a .uplugin file. Restart the project.
1.1.3 Check if it works
Close everything related, except the launcher. Navigate to your installed Unreal Engine version within the launcher and click thebutton labeled Launch. Descriptively, this will launch the Unreal Editor. The first start up of a freshly installed version usually hangsaround at 45% for 10 minutes while creating cashes and doing fancy preprocess work. Should the loading splash reach 100percentage points a project hub window opens. Create a new project by selecting template options and a project location. ClickCreate and wait for the Editor to open.
On first start-up the editor will begin its shader compilation process. Give it another 10 minutes to finish this. After, navigate themenu bar to Edit/Plugins. This opens a window with a list of available plugins. Use the search bar to look for Cineware for Unrealand Datasmith C4D Importer. Should one of them not be visible, make sure to click on both main categories Installed and Available in the left list. The plugins will prompt if it is ok to use a beta version, accept. After both plugins have been checked as Enabled, restart the Editor and the project. If the Editor successfully restarts you are good to go.
1.1.4 Possible Errors
The following modules are missing or built with a different engine version. Would you like to rebuild them now?
Both plugins are shipped with the source code. To make sure you don't have to manually recompile anything we also shipped thecompiled binaries for 4.27.1. As a first step please make sure you are currently working with version 4.27.1. If so, it's likely that anupdate has occurred between us compiling these plugins and you installing them. The binaries are still compatible, but they areflagged as outdated. To remedy that we'll need the back-up copy of DatasmithC4DImporter that we saved previously.
Open DatasmithC4DImporter/Binaries/Win64/UE4Editor.modules in any text editor. Our plugins have been compiled for "BuildId":"17155196". Should this number differ, copy paste it from the backup to $UE4_DIR/Engine/Plugins/Enterprise/DatasmithC4DImporter/Binaries/Win64/UE4Editor.modules.
Copy the same number to $UE4_DIR/Engine/Plugins/Marketplace/CinewareForUnreal/Binaries/Win64/ UE4Editor.modules and tryagain.
Could not be compiled. Try rebuilding from source manually.
Presumably, you encountered the above error message before and clicked Yes. If you already applied the above suggestion and stillreceived this error, you may have to delete certain directories for the compile process to complete. Navigate to $UE4_DIR/Engine/Plugins/Enterprise/DatasmithC4DImporter/ and delete the directories Binaries, Intermediate and Saved. Navigateto $UE4_DIR/Engine/Plugins/Marketplace/CinewareForUnreal and do the same. Try again.
Should you encounter any issues please visit the following website: " https://support.maxon.net1 ".
Plugin failed to load because module could not be found. Please ensure the plugin is properly installed, otherwise considerdisabling the plugin for this project.
Please switch from installing CinewareAsset as a single project plugin to a shared plugin.
1.2 How to use it
1.2.1 Cinema 4D Takes
Scene properties can be exposed to Unreal Engine via Cinema 4D's take system. A video tutorial can be found
Open the Cinema 4D take workspace and click Add new take.
Switch to the state of the take by left-clicking on it. All properties on scene objects should now be greyed out.
Right-click on the property you want to promote and click Override from the context menu. This will add the
property to the selected take.
The user can also add whole elements to the to the CinewareAsset by a right click on the element (as an example if the user wantsto add the whole cloner object and not just a single property)and then going to Take assignment > Clicking on the take that was created.
Currently supported override types are:
- Floating point
Save the file. Note that it is no longer necessary to save your project via the "Save for Cineware" command. This dramaticallyreduces the files sizes of shared .c4d files but slightly increases the time needed to import the scene.
1.2.2 Datasmith Import
Open an Unreal Engine project with the plugins enabled. In the action menu bar, you should see an icon
labeled Datasmith. Click on the button and browse for your saved .c4d file. Select the file and hit import. The import process willopen to pop-up windows. Within the first one, select the import location within the game project browser. The second window enablesyou to set your preferred Datasmith import settings.
The initial import of the session will load up the cineware engine. This process spawns a progress bar and typically takes between5 and 30 seconds. Note that for this version the progress bar is linked to the maximum timeout and not to the actual progress ofstarting up the engine. Should the progress bar reach 100 percentage points the process timed out and something went severelywrong. Send an email to the support email address should this be the case. If this is your first Cineware Engine startup on themachine you will be prompted to enter your Maxon account credentials. A Maxon account is free to create and mandatory for usingthe engine. After successfully signing in, the actual file import begins.
1.2.3 Cineware Properties Asset
An initial import of .c4d files will be imported with the default values of exposed properties as they are set within the Cinema 4Dscene. Additionally, the import creates an asset of type CinewareProperties and stores it at the location of the imported scene.This asset is filled with the properties set within Cinema 4D. Future imports of the .c4d file will read the values within the assetand apply it to your scene before translating the file into Unreal Engine file formats.
1.2.4 Edit Values
There are multiple ways to edit the stored properties stored within the asset.
220.127.116.11 Via UI
Double click the CinewareProperties asset to open up a Panel window displaying all the properties stored within the asset. TheCinewareProperties asset is linked to the Datasmith asset via the original file path. Both absolute and relative paths are consideredto make sure the project can be shared within a team. This means you can move the CinewareProperties asset anywhere withinyour project and rename it as you wish. For convenience the asset is created next to the imported Datasmith scene and named accordingly.
18.104.22.168 Via Blueprints
A CinewarePropertiesAsset can be references by Editor Blueprints. Since the assets are cooked when the project is packaged, noruntime blueprint is able to work with Cineware Properties assets. Cineware exposes several Blueprint Editor functions. It is possible to set data, read data or browse the given asset. This makes it possible to edit the values dynamically based on scene events.
Setting properties by name
It is possible to use variables of type Cineware Asset for Editor Blueprint Actors and Editor Level Blueprints. There is a few AssetSetter functionalities for the Cineware Assets. Use the same key as is displayed in the Cineware details panel. The methods returna Boolean if setting the key was successful. In the example below you can see the user converting an actor position from Unrealspace to Cinema space before applying the value.
Reading properties by name
Cineware Assets have straight forward Getter methods which return a Boolean, stating if getting the value was successful and astruct containing all information depending on the type. Every struct contains the Key, Value, Type and sorted position in theCinema 4D hierarchy. The container information varies depending on the out value.
Browsing for properties
There may be situations where you do not know the exact nature of the created asset. In these cases, you may want to browsethrough a given Cineware Asset and filter by name, value or type and apply some logic to it. Cineware Assets expose browsingproperties for this to work. Note that in the example below the first call is the Begin Iteration, this resets all iterators of the asset. Youcan then browse through it by type. Via a while loop and a switch, you may then call the appropriate Get Next functionality. It isrecommended to check the Boolean return value before accessing the returned container.
Things to consider:
- The axis' vary between Unreal Engine and Cinema. When setting Unreal Engine positions via blueprints make sure to execute the UnrealToCinema4DPosition or Cinema4DToUnrealPosition blueprint method, before setting them in a CinewareProperties asset.
- When setting properties by their name, use the name as it is printed when having Friendly Property.
Names disabled in the CinewareProperties panel. Friendly keys are currently not supported.
- Make sure to check the returned Boolean value if it is safe to access the container.
- CinewareProperty Blueprint functions can only be called in Editor Blueprints. If you do not have the option to call them, makesure you are running in an Editor This is visualized with a yellow and black bar in the Blueprint layout.
22.214.171.124 Via C++
For example, how to browse through assets, have a look within SCinewareAssetInstanceEditor.cpp and the UI construction. Naturallydirect setters and getters are also available within the C++ environment.
The cinema scene needs to be reimported for the changed properties to be applied. You can reimport the asset by right clicking theDatasmith asset and selecting Reimport Asset from the context menu, or by clicking
the Reimport button in the Cineware Editor. Automatic reimport is currently in development.
You've found us!
1.4 Known Issues
- CinewareProperty asset is not visible after import, editor needs redraw by reopening the
- UI layout inconsistent
- Some inconsistencies when importing materials
- Animated material properties
1.5 Feature list that is not supported in this Release
- Simulation tag Animations
- Animations in general that are not PSR
- PLA animations
- Skin Deformer
- Changing the number of generated objects
- Animated deformation (A static mesh must be static)
- Node materials
- Uber materials