Dear Twinmotion Development Team,
I feel it is important to raise this concern once again, with a strong sense of urgency.
It appears that D5 3.0 has already taken the first step in this direction:
its built-in AI features are able to call and control D5 itself, although external interfaces are not yet open.
This clearly signals where the industry is heading — and unfortunately, it also suggests that Twinmotion may now be one step behind once again.
The real opportunity lies elsewhere
The true breakthrough is not in AI-enhanced images.
By opening Python scripting, Twinmotion could fully align with the AI era:
-
Allow countless creators to use AI to write code for Twinmotion
-
Enable AI-assisted development of scripts, tools, and plugins
-
Allow AI to directly control Twinmotion through Python
This is where real leverage begins.
Why this matters strategically
Once plugin and workflow creators enter the ecosystem, Twinmotion can be pulled into entirely new automation pipelines.
When creators integrate Twinmotion into their own closed-loop workflows,
their users will naturally follow.
We are already seeing this pattern elsewhere:
for example, AI-written plugins that send CDR / Illustrator files directly into Cinema 4D for automatic modeling and scene construction.
If Twinmotion becomes scriptable and controllable, it can become a core node in many creators’ automation workflows, rather than just a standalone visualization tool.
Please don’t focus only on AI image enhancement
Placing the main emphasis on AI image enhancement or stylistic effects will inevitably lead to a follower’s position.
These features are easy to replicate and quickly become homogeneous across products.
What defines leadership in this era is not visual AI, but AI-driven control, extensibility, and automation.
A sincere concern
What makes this moment particularly concerning is that, over the years:
-
I have repeatedly suggested forward-looking features on the forum
-
Many of these ideas were later implemented first by D5
-
Meanwhile, Twinmotion seemed to move forward without acknowledging these signals
This is not written out of frustration, but out of genuine concern for Twinmotion’s strategic direction.
A sincere hope
Opening Python is not just a technical decision.
It is a statement about what Twinmotion wants to be in the AI era:
-
A tool that follows AI trends
-
Or a platform that AI and creators can build upon
This is a rare bend in the road.
I sincerely hope Twinmotion will recognize it, seize it, and once again lead rather than follow.
Thank you for taking the time to read this, and for the continued work on Twinmotion.