Don’t Follow — Surpass! Please reconsider the strategic importance of Python support in Twinmotion

Development Rendering
, ,
1

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.

2 Likes
A Critical Moment — Python Could Be Twinmotion’s Chance to Leap Ahead
2

Five years ago, almost no one imagined AI could generate architectural or interior designs with one click — it was considered “illogical.”
Three years ago, hardly anyone believed that a single person, aided by AI, could develop software or plugins that a whole team would take years to complete.

Today, the potential of Python is clear:

  • AI will not replace designers.

  • AI will not replace design software.

  • But in the foreseeable future, AI will enhance the productivity of designers who use it,
    and enable software that integrates AI effectively to achieve much more.

competitors may already be quietly moving forward on this front
So it’s important to look beyond simply enhancing images or changing styles, and fully explore the potential of AI + Python integration.
@MC_Jut @Laudal75

2 Likes
3

before 2 year i ask integration of Artificial Intelligence after that i see python i said ooh ok thas good suddenly removed and see Ai . I need and AI and python together !!!

4

Hope the official team can see this

1 Like
5

I am writing to propose the integration of Python scripting support as a strategic pillar of the Twinmotion product roadmap, rather than as a standalone feature. This proposal is based on the long-term evolution of Twinmotion, its positioning within the Epic ecosystem, and the increasing demands of professional, technical, and enterprise users.

Python integration directly aligns with Twinmotion’s transition from a fast visualization tool to a scalable, extensible, and future-ready real-time platform.

1. Python as a Roadmap-Level Capability, Not a Feature

Across the 3D, VFX, and real-time industries, Python is not treated as an optional add-on. It is considered a core infrastructure layer that enables:

  • Automation

  • Custom tooling

  • Pipeline integration

  • Long-term extensibility

By introducing Python at the roadmap level, Twinmotion establishes a foundation upon which multiple future features can be built, rather than adding isolated capabilities that operate in silos.

2. Roadmap Alignment with Professional and Enterprise Adoption

As Twinmotion adoption grows among architectural firms, visualization studios, and multidisciplinary teams, the absence of scripting creates a ceiling for scalability.

Python support would enable roadmap initiatives such as:

  • Automated and repeatable workflows

  • Scene-driven logic and data-driven visualization

  • Enterprise pipeline compatibility

  • Technical customization without modifying core code

This allows Twinmotion to scale naturally into larger production environments, an essential roadmap goal for long-term growth.

3. Ecosystem Consistency Within Epic Games

Within the Epic ecosystem, Unreal Engine already demonstrates the value of scripting, automation, and extensibility for advanced users.

Introducing Python into Twinmotion would:

  • Strengthen conceptual alignment with Unreal Engine workflows

  • Enable smoother transition paths from Twinmotion to Unreal Engine

  • Create shared technical language across Epic tools

  • Support future interoperability initiatives

From a roadmap perspective, this reduces fragmentation and increases ecosystem cohesion.

4. Enabling Community-Driven Roadmap Acceleration

A Python API would effectively allow the Twinmotion community to extend the roadmap organically, by developing tools and workflows that address niche or emerging needs.

This would:

  • Reduce pressure on core development teams

  • Reveal real-world usage patterns and demands

  • Encourage innovation at the edges of the platform

  • Shorten feedback loops between users and product direction

In practical terms, Python allows parts of the roadmap to be co-created with the user base.

5. Roadmap Readiness for AI and Intelligent Workflows

Future-facing roadmap items—such as procedural content, smart environments, and AI-assisted creation—are tightly coupled with Python ecosystems.

With Python in place, Twinmotion becomes technically ready for:

  • AI-driven scene optimization

  • Intelligent asset placement and variation

  • External AI service integration

  • Data-informed and generative workflows

This ensures that future roadmap expansions can be implemented efficiently, without architectural redesign.

6. Suggested Roadmap-Oriented Implementation Path

A phased roadmap approach could include:

Phase 1 – Foundation

  • Embedded Python interpreter

  • Read-only scene access and basic automation

Phase 2 – Interaction

  • Full scene manipulation API

  • Event hooks and callbacks

  • Script execution management

Phase 3 – Ecosystem

  • Script marketplace or repository

  • Official documentation and examples

  • Community contribution framework

This approach minimizes risk while steadily expanding capability.

7. Strategic Conclusion

From a roadmap perspective, Python integration provides:

  • A durable technical foundation

  • Long-term flexibility without feature bloat

  • Increased professional and enterprise relevance

  • Community-driven acceleration

  • Readiness for AI-driven and data-centric futures

Python is not a short-term enhancement—it is a structural investment that future-proofs the Twinmotion roadmap and reinforces its position within the real-time visualization landscape.

Thank you for considering this proposal as part of Twinmotion’s long-term planning. I firmly believe that Python integration would represent a decisive and forward-looking step in the evolution of the platform.

Kind regards,