Cesium for UE 5.1

Kostya · November 4, 2022, 9:55pm

Anyone had any luck compiling Cesium for UE 5.1 Preview 2?

I’ve spent a day trying to make it compile but no luck so far as the errors are beyond my level of C++ knowledge. Cesium native compiled without any problems but the cesium plugin itself is the one I’m struggling with. I’ve used latest from ue5-main branch.

When trying to compile the plugin I’m getting following errors:

1>Building 10 actions with 10 processes…
1>[1/10] Link UnrealEditor-CesiumEditor.lib cancelled
1>[2/10] Compile Module.CesiumEditor.cpp
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumEditor\Private\CesiumPanel.h(5): fatal error C1083: Cannot open include file: ‘Dialogs/CustomDialog.h’: No such file or directory
1>[3/10] Compile Module.CesiumRuntime.6_of_6.cpp
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\ScreenCreditsWidget.cpp(221): error C4668: ‘ENGINE_MAJOR_VERSION’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\ScreenCreditsWidget.cpp(226): warning C4996: ‘UTexture2D::PlatformData’: Use GetPlatformData() / SetPlatformData() accessors instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\ScreenCreditsWidget.cpp(227): warning C4996: ‘UTexture2D::PlatformData’: Use GetPlatformData() / SetPlatformData() accessors instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\ScreenCreditsWidget.cpp(251): error C4668: ‘ENGINE_MAJOR_VERSION’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\ScreenCreditsWidget.cpp(256): warning C4996: ‘UTexture2D::PlatformData’: Use GetPlatformData() / SetPlatformData() accessors instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\ScreenCreditsWidget.cpp(257): warning C4996: ‘UTexture2D::PlatformData’: Use GetPlatformData() / SetPlatformData() accessors instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.
1>[4/10] Compile Module.CesiumRuntime.2_of_6.cpp
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.h(25): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>[5/10] Compile Module.CesiumRuntime.4_of_6.cpp
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.h(25): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\LoadGltfResult.h(23): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\LoadGltfResult.h(50): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CreateGltfOptions.h(11): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CreateGltfOptions.h(22): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\Cesium3DTileset.cpp(48): fatal error C1083: Cannot open include file: ‘IPhysXCookingModule.h’: No such file or directory
1>[6/10] Compile Module.CesiumRuntime.5_of_6.cpp
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.h(25): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(292): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(292): error C2143: syntax error: missing ‘;’ before ‘:’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(292): error C2143: syntax error: missing ‘;’ before ‘)’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(347): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(748): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(747): error C2143: syntax error: missing ‘;’ before ‘:’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(748): error C2143: syntax error: missing ‘;’ before ‘)’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(772): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(771): error C2143: syntax error: missing ‘;’ before ‘:’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(772): error C2143: syntax error: missing ‘;’ before ‘)’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(795): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(794): error C2143: syntax error: missing ‘;’ before ‘:’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(795): error C2143: syntax error: missing ‘;’ before ‘)’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(816): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumEncodedMetadataComponent.cpp(825): error C2039: ‘FunctionExpressions’: is not a member of ‘UMaterialFunctionMaterialLayer’
1>C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Engine\Classes\Materials\MaterialFunctionMaterialLayer.h(16): note: see declaration of ‘UMaterialFunctionMaterialLayer’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\LoadGltfResult.h(23): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\LoadGltfResult.h(50): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CreateGltfOptions.h(11): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CreateGltfOptions.h(22): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.cpp(54): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.cpp(308): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.cpp(1197): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.cpp(2068): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>C:\Dev\cesium-unreal-samples\Plugins\cesium-unreal\Source\CesiumRuntime\Private\CesiumGltfComponent.cpp(2420): error C4668: ‘PHYSICS_INTERFACE_PHYSX’ is not defined as a preprocessor macro, replacing with ‘0’ for ‘#if/#elif’
1>[7/10] Link UnrealEditor-CesiumRuntime.lib cancelled
1>[8/10] Link UnrealEditor-CesiumRuntime.dll cancelled
1>[9/10] Link UnrealEditor-CesiumEditor.dll cancelled
1>[10/10] WriteMetadata devEditor.target cancelled
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.MakeFile.Targets(44,5): error MSB3073: The command ““C:\Program Files\Epic Games\UE_5.1\Engine\Build\BatchFiles\Build.bat” devEditor Win64 Development -Project=“C:\Dev\cesium-unreal-samples\CesiumForUnrealSamples.uproject” -WaitMutex -FromMsBuild” exited with code -1.
1>Done building project “CesiumForUnrealSamples.vcxproj” – FAILED.

One of the issues seems to be that there’s no PhysX available in UE5.1. I have edited the cesium plugin code to not use PhysX but other issues still remain which I’m struggling to fix.

Anyone got any pointers on how to proceed?

Cheers

Darb_Dude · November 17, 2022, 2:54am

Is the CesiumForUnreal Plugin not updated for 5.1 yet?
I ran into a similar issue in Preview 1 but will be trying it out again.

Kevin_Ring · November 17, 2022, 4:42am

No, it has not been updated for 5.1 yet. We hope to do that soon. In the meantime, if you’re able to figure it out we would welcome a pull request.

Dominik_Gomolka · November 18, 2022, 10:38am

Hi all, Kevin, can you please give any estimation to how soon can we expect this update from your team? I do understand it has to take some work, but I am pressured by a deadline in a project - haha a lot depends on your update now!

Kevin_Ring · November 19, 2022, 12:32pm

Hi @Dominik_Gomolka,

I don’t think the Cesium team will be able to work on this in time for the early December release, which means it unlikely to be available in an official release before early January. Sorry it’s not better news.

Kevin

Dominik_Gomolka · November 19, 2022, 4:17pm

Hello @Kevin_Ring Thank you for the clear answer here! I’ll find a work-around for this one and be back with Cesium in the future

Kevin_Ring · November 20, 2022, 12:38pm

I’ve just opened a pull request that gets the plugin working in UE 5.1:

We don’t have any UE 5.1 automated build set up yet, though, so you’ll have to build it yourself. If you try it out, let me know how it works.

Kostya · November 22, 2022, 9:58am

Just built it on my machine from the latest commit on UE51 branch. Compiled without any problem. Plugin seems to be working fine so far. Thanks for your efforts!

Nishant_Ambekar · November 23, 2022, 4:09pm

Hello,

I am a newbie and have never built a plugin from source. I have a tight deadline and I really have to get Cesium working with UE 5.1. Can you please please help me with how to build this plugin and make it work inside UE 5.1 ? I will much appreciate this support. Please help !

Darb_Dude · November 23, 2022, 9:22pm

The Documentation for building from source is located here.
Overview and Windows and Packaging

I’m still having some various issues but managed to get my project to open for 5.1 with some tweaking, although i still couldn’t fully compile for Windows/Linux. This is what i tried.

I cloned the ue51 branch recursively to also get the required cesium-native content
git clone -b ue51 https://github.com/CesiumGS/cesium-unreal.git --recursive
I used VS2019 on the local folder cesium-unreal\extern
Then, in the “Solution Explorer - Folder View”, right-click on the root CMakeLists.txt and select “Install”

At this point I believe the cesium-unreal\Source\ThirdParty folder is populated with the required headers and libraries.

I set my working directory to where my installation is, in this case
N:\UnrealEngine-5.1.0-release\Engine\Build\BatchFiles
and execute the following command

./RunUAT.bat BuildPlugin -Plugin='C:\Users\Workstation\Documents\Github\cesium-unreal\CesiumForUnreal.uplugin' -Package="../packages/CesiumForUnreal" -CreateSubFolder -TargetPlatform=Windows

I get various warnings and errors during this processes, i think because i don’t have all the OS Platforms ready (i.e Android, Linux, etc)
However, after it’s done a new Folder is created at
N:\packages\CesiumForUnreal\HostProject\Plugins\CesiumForUnreal
I copy this folder to my Projects /Plugins folder.

However, I still run into issues
UATHelper: Packaging (Linux): [1/5] Compile Module.CesiumRuntime.1_of_6.cpp
UATHelper: Packaging (Linux): In file included from C:/Users/Workstation/Documents/Unreal Projects/arnobeta_v5.1/Intermediate/Build/Linux/B4D820EA/arnocMain/Development/CesiumRuntime/Module.CesiumRuntime.1_of_6.cpp:6:
UATHelper: Packaging (Linux): In file included from C:/Users/Workstation/Documents/Unreal Projects/arnobeta_v5.1/Intermediate/Build/Linux/B4D820EA/arnocMain/Inc/CesiumRuntime/UHT/CesiumBoundingVolumeComponent.gen.cpp:8:
UATHelper: Packaging (Linux): In file included from C:/Users/Workstation/Documents/Unreal Projects/arnobeta_v5.1/Plugins/cesium-unreal/Source\CesiumRuntime/Private/CesiumBoundingVolumeComponent.h:5:
UATHelper: Packaging (Linux): In file included from C:/Users/Workstation/Documents/Unreal Projects/arnobeta_v5.1/Plugins/cesium-unreal/Source/CesiumRuntime/Private/CesiumViewExtension.h:6:
UATHelper: Packaging (Linux): In file included from .\Runtime/Renderer/Private/ScenePrivate.h:33:
UATHelper: Packaging (Linux): In file included from .\Runtime/Renderer/Private/LightSceneInfo.h:15:
UATHelper: Packaging (Linux): In file included from .\Runtime/Renderer/Private/SceneRendering.h:29:
UATHelper: Packaging (Linux): In file included from .\Runtime/Renderer/Private/SkyAtmosphereRendering.h:15:
UATHelper: Packaging (Linux): N:\UnrealEngine-5.1.0-release\Engine\Source\Runtime\Renderer\Private\VirtualShadowMaps\VirtualShadowMapArray.h(7,10): fatal error: ‘MeshDrawCommands.h’ file not found
UATHelper: Packaging (Linux): #include “MeshDrawCommands.h”
UATHelper: Packaging (Linux): ^~~~~~~~~~~~~~~~~~~~
UATHelper: Packaging (Linux): 1 error generated.
PackagingResults: Error: ‘MeshDrawCommands.h’ file not found

Kevin_Ring · November 25, 2022, 10:10am

@Nishant_Ambekar as @Darb_Dude mentioned, the build instructions are available in the GitHub repo. I’d suggest using the version of the instructions for UE5, which are slightly different from the UE4 instructions Darb_Dude linked. Here are the UE5 instructions:

github.com

CesiumGS/cesium-unreal/blob/ue5-main/Documentation/developer-setup.md

## Overview

This is a summary of a setup and workflows for developers who want to work with the *Cesium for Unreal* plugin. Such a setup consists of three main components:

- [`cesium-native`](https://github.com/CesiumGS/cesium-native) : A collection of engine-independent libraries for 3D Tiles, geospatial, etc. Most of the functionality of *Cesium for Unreal* is built based on these libraries.
- [`cesium-unreal`](https://github.com/CesiumGS/cesium-unreal) : The source code of the actual *Cesium for Unreal* plugin.
- An Unreal project that uses the plugin. We will use the [`cesium-unreal-samples`](https://github.com/CesiumGS/cesium-unreal-samples) as an example here, to get started quickly. It contains sample levels for different use cases, and can therefore be used to quickly check for possible regressions of feature changes.

> Note: It is generally possible to work with `cesium-native` *independent* of `cesium-unreal`. But any modification in `cesium-native` will have to be checked carefully for possible breaking changes in the API or the build process. So the following describes the developer setup from the perspective of someone who wants to work with `cesium-native` mainly in the context of `cesium-unreal`.

## Principles

There are detailed instructions for setting up a Cesium for Unreal development environment on each platform. But if you're already used to doing this sort of thing, you can probably use whatever workflow you like as long as you follow some important principles:

- To build Cesium for Unreal, you must first compile and cmake-install cesium-native and its dependencies to `Plugins/cesium-unreal/Source/ThirdParty`.
- cesium-native is built and installed using CMake and the `CMakeLists.txt` found in the `cesium-unreal/extern` directory, _not_ the one in the `cesium-unreal/extern/cesium-native` directory. When installing from this directory, the default install path will put cesium-native where Cesium for Unreal expects to find it.
- You must use the same compiler to build cesium-native and Cesium for Unreal.
- On Windows, packaging the Cesium for Unreal plugin on Windows requires Visual Studio 2017. This means you must also build cesium-native with Visual Studio 2017 in order for plugin packaging to be successful. But if you're not concerned with packaging, you can use Visual Studio 2019 exclusively.
- The Unreal project "DebugGame" configuration tries to use the debug build of cesium-native if one is built and installed, and falls back on the release build otherwise. The "Development" and "Shipping" configurations use the release build exclusively.
- Our CI build process checks for formatting using clang, and fails if code is improperly formatted. To run clang on all source code before committing, run `npm ci` to install node modules, then `npm run format`.

This file has been truncated. show original

So start there and let us know if you run into trouble.

I hope to get our CI system building for UE5.1 soon. Once that’s done you’ll be able to just download a package rather than building it yourself. But it’ll be the end of next week at the soonest before that is ready.

Kevin

KieranCoppins · November 29, 2022, 11:06am

I have this issue as well,

I’ve done some investigating into this and turned it into an issue on the Cesium For Unreal github here. If you have any other discoveries feel free to add them to this discussion as it may help. By what I can tell, the error occurs when building for Linux. Building for Windows should work just fine.

In UE5.1 they have changed how they included some header files and my best guess is that the windows build tool has these paths inside their include directories. Whereas with the Linux build tools they don’t. This is just speculation as I am still investigating this.

KieranCoppins · November 29, 2022, 4:47pm

I have now just opened a pull request that I believe has fixed this issue.

Nishant_Ambekar · November 30, 2022, 5:08pm

@Kevin_Ring I would wait until your release scheduled this week end, as it’s very complex for me to build from source. Pl note that we are banking on this release, as we have to deliver certain tasks within our deadline. Hence, kindly ensure that the release happens this week end.

Cheers

Kevin_Ring · December 1, 2022, 1:48am

Sorry, but we absolutely cannot promise that will work out well for you. I hope to get UE5.1 support into this week’s release, but there are a great many things that could go wrong. If your business is depending on it, you need a plan B.

Nishant_Ambekar · December 7, 2022, 11:30am

Hello @Kevin_Ring ,

Want to check with you, if you can give us some timeline or an approximate range of time, in which the Cesium for UE 5.1 will be out ? We have kept our client on hold for this, as we are waiting for this update.

Thankyou.

Kevin_Ring · December 8, 2022, 12:32pm

We released it to Epic last week, but so far they haven’t reviewed it and published it on the Marketplace. But you can install it from our releases page on GitHub today:

Uninstall the existing version of the plugin using the Epic Launcher, then download the appropriate ZIP from the page above and extract it to your UE installation’s Engine/Plugins/Marketplace directory.

Note that we’ve had some reports about crashes on macOS and Linux. We expect to release a v1.21.1 to fix those problems very soon.