An error occurred in the Simulink and UnrealEngine 5.3 co-simulation

I configured the requirements for co-simulation in version 2024b according to the documentation, but when I tested with the official example, it couldn't be simulated normally, and as soon as I ran the model, it showed up in Unrealengine and clicked play, but it kept loading.

Finally, the "3D Simulation engine interface read error." pops up.

Answer 1

[Nishan Nekoo]

Hello! Please ensure you are following all the instructions to download and set up the support package carefully: https://www.mathworks.com/help/vdynblks/ug/customize-3d-scenes-for-vehicle-dynamics-simulations.html

This seems to point to an issue in the co-simulation interface. You mentioned that "it kept loading" - do you mean that Simulink was stuck in "initialization" or do you mean something else?

Here's a few troubleshooting steps to try for this issue:

1. Restart your PC
2. Ensure that Unreal Editor is opened using the "Open Unreal Editor" button in the Simulation 3D Scene Configuration block.
3. Try running the co-simulation with a blank model containing only the Simulation 3D Scene Configuration block.

Let me know if this helps resolve the issue!

Nishan

[香露]

Thank you very much for your suggestion, but I still have the above problem after testing, when I run the model on Simulink, it quickly pops up "In the Simulation 3D Scene Configuration block, you set the scene source to 'Unreal Editor'.

In Unreal Editor, select 'Play' to view the scene.

And I went to UE and clicked play again but there was no further reaction.

Finally, the error "MATLAB System module 'SCRReferenceApplication/Simulation 3D Scene Configuration/Simulation 3D Engine' appears when calling the 'resetImpl' method of 'Simulation3DEngine'." The error is from the '

'D:MATLAB2024btoolboxsharedsim3dblkssim3dblksSimulation3DEngine.p' at line 0

'D:MATLAB2024btoolboxsimulinkuistudioconfigm+SLStudioStartPauseContinue.p' at line 0

'D:MATLAB2024btoolboxsimulinkuistudioconfigm+SLStudioToolBars.p' at line 0'. and explain that the cause is "3D Simulation engine interface read error.".

[香露]

And I found that when the Simulink error stopped, and I shut down the stop UX, a series of errors popped up, saying that it was a Blueprint runtime error, and "no access" was being read.

[香露]

Good news for you, I successfully joined forces with Unreal Engine by removing two invalid modules from the Unreal Engine Blueprint level.

[Nishan Nekoo]

I'm glad that your issue is resolved! Can you provide any information about which invalid modules you had to remove from the Blueprint level?

Nishan