Please reconsider removing Python support — this is a crucial chance for Twinmotion to leap ahead
Dear Twinmotion Team and Community,
I was truly disappointed to see that Python support has been removed from the development roadmap.
I understand that every team must prioritize carefully, but I believe this decision might unintentionally close the door on one of the most important opportunities in the AI era.
In 2025, removing Python support means limiting Twinmotion’s potential for AI-driven automation, customization, and innovation — the exact areas where the entire software industry is rapidly moving.
■ Why Python matters more than ever
The way we develop plugins and tools has changed completely.
Today, a single developer can create in one month what previously required multiple people working for years — thanks to AI-assisted coding.
In tools like Cinema 4D, combining AI with Python/SDK has already proven how dramatically development speed and plugin quality can improve.
Twinmotion could benefit from exactly the same evolution.
■ Five years ago, I suggested AI integration for Twinmotion — but D5 implemented it first
This is the key reason I’m writing this message.
Five years ago, I publicly suggested that Twinmotion should embrace AI.
At that time, very few people believed AI could meaningfully impact daily workflows or scene production.
But today, D5 has already taken the lead by pushing AI features into their ecosystem.
Twinmotion still has better foundations and a smoother user experience —
but only if it chooses not to miss the second opportunity: AI + Python automation.
Please don’t let this rare chance slip away again.
■ The current AI trend (image style / rendering enhancement) is already becoming “old”
Many tools are focusing on:
-
AI style generation
-
AI visual enhancement
-
AI rendering assistants
But these are already becoming common across the industry.
The real future lies in AI controlling workflows, not just images.
AI needs a scripting layer to interact with software:
That layer is Python.
■ Python + AI = the fastest, clearest, and most strategic growth path for Twinmotion
If Python is supported, AI could:
-
Automatically place lights and assign materials
-
Build animations and camera paths
-
Batch-import and update CAD/BIM data
-
Auto-generate scenes
-
Dynamically control object parameters
-
Let users build custom workflows
-
Let AI write plugins for Twinmotion
-
And most importantly:
Allow full workflow automation — the true direction of next-generation tools
This is not about AI image filters.
This is about AI-powered production pipelines.
This is the type of feature that competitors cannot easily copy.
■ Twinmotion’s lightweight nature + Python extensibility = a perfect match
Twinmotion’s biggest strength has always been its simplicity and speed.
By adding Python support, Twinmotion would evolve:
From a great visualization tool → into a flexible, intelligent real-time production platform.
This would place Twinmotion in a new category entirely.
■ A humble request to reconsider
Even limited Python support would unlock massive potential:
-
Access to the scene graph
-
Modify materials and parameters
-
Control cameras and animations
-
Trigger batch operations
-
Import/refresh workflows
-
Connect external data sources (CAD / BIM / APIs)
This would empower developers and allow AI tools to integrate with Twinmotion in incredible ways.
■ Final thoughts
AI-assisted coding + extensible scripting is not a trend —
it is the foundation of modern software ecosystems.
Removing Python from the roadmap feels like a missed opportunity,
but I truly believe the Twinmotion team listens to its users
and wants to push the boundaries of what is possible.
Please reconsider Python support.
This is the rare opportunity for Twinmotion to leap ahead, not follow.
Thank you for your time and for all the continuous work on Twinmotion.