We’d like to know whether it’s possible to have Motion Design default to keeping the Remote Control feature turned off. We ran into an issue where, every time we opened the scene, the engine would run “Preparing texture,” and it was very slow. After tracing it in Insights, we found that it was caused by the remotecontrolpreset, which accounted for about 80% of the Postload time.
In our scene we’re using Motion Design to create some effects but aren’t using any Remote Motion features. However, Motion Design seems to default to enabling Remote Control and points to a non‑existent remotecontrolpreset.
[Image Removed]
This causes it to get stuck on the remotecontrolpreset during the “Preparing texture” step.
Here’s a snippet of the Insights trace that demonstrates this:
https://drive.google.com/file/d/1zAKrtv_nDC6PcjwN_cRP_XenDIXa2F63/view?usp=sharing
[Image Removed]
Hello,
Which features are you using? Several features don’t require the actual Motion Design mode to be enabled after we split the features up in 5.5 and on. For example, if you make a new project and don’t enable Motion Design plugin, but you enable the Cloners and Effectors plugin, you should still be able to use cloners.
What was lost when you closed it? Also, can you post a more complete screenshot of your error logs, or just attach the logs?
Hi,
Has there been any progress on this issue?
We are definitely able to achieve this in 5.8. The development cycle for 5.7 is a bit too far along to remedy it safely.
Hi,
We mainly use it to create in game mechanisms, leveraging tools such as Cloners, Effectors, the Motion Design Sequencer, Motion Design Tool Box, Material Designer, and the like.
Some of the graphics are created by Motion Design Tool Box.
When I closed it, a lot was lost.
[Image Removed]
Hi,
After closing, some scene objects using AvaShapeActor disappeared, and the applied material, M_Toolbox_Opaque_Lit, also displayed a warning.
There were also some errors related to DefaultSequenceTags and similar issues.
[Image Removed]There were also some other warning messages.
[Image Removed]The logs are provided below.
Are you saying that around 5.8 you might consider splitting Remote Control and Motion Design?
I think the way to solve this issue could be to make Remote Control act as a switch that can be enabled or disabled selectively. That way, this problem could be avoided.