Regarding Packaging Unreal Engine Scenes

I am trying to build custom scenes with unreal engine and I am able to compile and run the scene executable using scene 3D configuration block.

I want to build these scenes so that they run on another system without the requirement of opening through the scene 3D configuration block.

How can this be done?

Answer 1

[Nishan Nekoo]

Hi Ketan,

I understand that you are building a custom scene in the Unreal Editor, and that you are currently compiling that scene into an executable and calling it from the Scene Configuration block using the 'Unreal Executable' selection as a Scene Source.

It sounds like you want to continue building these scenes in the Unreal Editor but maybe you don't want to have to open the Unreal Editor via the Scene Configuration block while you are on a different system? If this is what is being asked, then the solution is to disable the MathWorks plugin in the Unreal Editor when you are not doing co-simulation with Simulink. Then, the Unreal project can be opened without using the Scene Configuration block.

I hope that helps and if that didn't answer your question, please let me know!

Nishan

[Ketan]

Hey Nishan

Not exactly, I want to build an executable which can be launched like any other UE executable, without needing Matlab. It is for a simulation that we want to use to test our algorithms, but the scene contains matlab plugins.

[Nishan Nekoo]

Hey Ketan, I see! It sounds like you want your Unreal Engine scene along with your Simulink model and Simulation 3D blocks compiled into an executable. Unfortunately, Simulation 3D blocks do not support code generation for now as mentioned on our limitations page, so this workflow is not supported. Know that we are keenly aware of this limitation and may consider supporting this workflow in a future release.

One potential workaround is to use UDP or ROS to transmit data between Simulink and Unreal instead of Simulation 3D blocks. Then compile the Simulink model (without Simulation 3D blocks) into a DLL and call this from Unreal instead. The downside is that you will need to set up your own communication interfaces and it may not be possible to have lock-step, deterministic simulations.

At a high level can you tell me more about what your use case is for building an executable? Is the executable intended for use by other people? I'd love to learn more about your workflow and project!

[Ketan]

The aim behind building an executable is to allow multiple people to test the algorithm without needing the matlab installed on every computer. I'll try the suggested procedure.