Insights, workflows and technical explorations across 3D production, ArchViz, AI-assisted pipelines and next-generation CG tools.

Posted on by — Leave a comment

AI-Assisted ArchViz: Beyond the Hype

A grounded look at how AI-assisted workflows, hybrid pipelines and technical artists are reshaping Architectural Visualization production.

Something Is Quietly Changing in ArchViz Pipelines

There’s a version of the AI conversation in ArchViz that lives entirely on social media — dramatic demos, instant photorealism, the promise that prompts will make geometry irrelevant. And then there’s what’s actually happening in production. The two don’t quite match.

What you notice, if you pay attention to the right places — the forums, the GitHub threads, the workflow posts from working artists rather than their polished showcase feeds — is something more specific and more interesting than a revolution. AI is entering real pipelines. Not by replacing them, but by attaching itself to them at particular friction points. The 3D scene still exists. Clients still request revisions. The render still needs to be consistent across eight or twelve coordinated views.

The shift happening right now is quieter than the headlines suggest, and considerably more instructive. This article is an attempt to describe it honestly.

Why ArchViz Is Fertile Ground for AI-Assisted Workflows

Architectural visualization has always demanded more than visual talent. A strong set of deliverables — exteriors, interiors, aerials, close-ups, all coherent and revision-safe — involves a level of technical discipline that sits somewhere between craft and engineering. Scene organization, asset management, material accuracy, lighting setups, render optimization, postproduction, version control: these are the unglamorous realities behind the polished images.

Because of that, the field has always attracted practitioners who care about systems. Long before the current AI cycle, ArchViz had a strong scripting and automation culture. Technical artists were building custom utilities, batch processes, render managers, and specialized plugins. Automation was not a foreign concept. It was survival. AI did not arrive in an industry unfamiliar with toolmaking — it arrived in one that was already hungry for better ways to reduce friction.

At the same time, ArchViz exposes AI’s limitations faster than almost any other discipline. A concept artist can get away with a single compelling image. A professional visualization studio cannot. The requirement for consistency, precision, and revision-safe output isn’t going away — and in many ways, it’s precisely what separates serious architectural visualization from the broader category of “AI-generated architectural imagery.” Those are different things, with different production standards and different professional accountability.

This is what makes ArchViz such a useful lens for understanding where AI actually helps and where it still falls short.

The New Hybrid Pipeline: 3D as Control Layer, AI as Enhancement Layer

The most honest description of how AI is entering serious ArchViz production isn’t a single tool or a single workflow — it’s a structural pattern. The 3D scene remains the source of truth. Geometry, camera position, proportions, material assignments, scene structure: these still come from the model. What’s changing is what gets built on top of that foundation.

AI is inserting itself at increasingly specific points: concept exploration and moodboard alignment before significant modeling begins, material and texture development, postproduction for denoising and upscaling, inpainting to add entourage without manual placement, atmosphere or relighting work on top of an already-rendered base image. The structure stays intact. The AI layer touches specific outputs at specific moments, guided by the geometry the scene provides.

Hybrid 3D + AI workflow using material IDs and controlled masking for consistent ArchViz outputs.

Iván Zabalza González, archViz expert and CEO at Señapaula SL, described his actual production workflow this way: render passes — wirecolor, material IDs — tell the AI precisely which zones correspond to which finish, what materials to apply, where geometry and composition must remain untouched. His assessment: “the system is quite consolidated, works very reliably, and — when well set up — does not fail.” That kind of confidence doesn’t come from a demo. It comes from production repetition.

It’s worth being clear about what this model doesn’t include. Prompt-only generation is not a production workflow for client-facing ArchViz. For projects requiring controlled revisions, consistent multi-view output, and professional accountability — which describes most serious studio work — purely text-driven image generation is still unsuitable as a primary pipeline. That’s not a forecast. It’s a description of where the technology is right now.

The hybrid model also clarifies where the most valuable AI tools actually sit. Not the ones generating the most spectacular standalone images — but the quietest ones: a denoiser that cleans a medium-sample render to delivery quality, a material generator that produces a usable PBR starting point from a reference photo, an upscaler that brings a viewport capture to presentation resolution. These are not headline features. They are workflow compressions. And that’s exactly why they get adopted.

Tools and Ecosystems Worth Watching

Approaching the current AI landscape as a list of tools is a good way to produce content that’s outdated in three months. A more durable approach is to look at ecosystems: the clusters of tools, workflows, and technical patterns forming around specific production problems.

The most immediately relevant ecosystem for professional ArchViz is AI embedded directly in render engines. V-Ray, Corona, and Enscape have all been systematically adding AI features — denoising, upscaling, material generation, atmosphere matching — into products professionals already use and already pay for. The adoption barrier for these features is near zero: they don’t require a new pipeline. They arrive inside the tool you already know.

Closely related is the emerging category of BIM-connected AI rendering. Chaos Veras — available as a plugin for Revit, SketchUp, Rhino, Vectorworks, Archicad, and now bundled with Enscape Premium — grounds AI output in the actual project geometry rather than generating from text prompts alone. The results are still subject to drift at higher creative override settings, but the approach is structurally more compatible with professional architecture workflows than pure prompt-based tools. This category is maturing faster than most.

The open-source ecosystem around ComfyUI, ControlNet, and foundation models like FLUX and SDXL occupies a different position: not the most stable, but arguably the one with the highest ceiling for technical artists willing to invest in it. The ability to combine depth passes, material ID masks, style references, and custom generation pipelines in a node-based interface is genuinely powerful — and real workflows are being built here, not just demos.

Image-to-3D tools like Meshy and Tripo deserve a mention, not because they’re production-ready — they aren’t, for most DCC workflows — but because the direction of travel is worth watching. The gap between an impressive-looking mesh in a demo and a production-usable asset with clean topology remains significant. For static background elements, some of these tools are already useful. For anything requiring animation or precision, not yet.

Node-based ComfyUI workflow for AI-assisted architectural visualization and image-to-video generation.

Reality Check — What These Tools Still Can’t Do

The most useful thing this article can do is be honest about the gap between what gets shown and what gets used. That gap is substantial.

The most critical limitation in professional ArchViz is multi-view consistency. A single AI-generated image can be extraordinary. But a real project requires eight to twelve coordinated views of the same building — matching materials, consistent geometry, identical context, and the ability to handle client revisions across the full set. Current generative AI cannot maintain this coherence reliably. Materials shift. Windows appear at different proportions. The building that looks convincing from one angle may have structurally impossible balconies in the next.

Joël Feyaerts, co-founder at Blacksquid and a longtime voice in the CGarchitect community, named this plainly: “The balcony sits two floors higher than on the plan. The railing turns into a wall halfway across. A window that repeats identically in every neighboring unit, because AI does not understand what a grid is. The architects see this. I am sure of that.” And he drew a distinction that deserves wider circulation: “An AI render in the concept phase is exceptional. Faster, cheaper, freer. An AI render in the sales phase, with broken balconies and inconsistent rhythm, is not a workflow. It is a deferred problem.”

The revision workflow problem follows from this. In traditional 3D production, changing a curtain wall color or adjusting a balcony depth propagates from the model through all renders. AI regeneration doesn’t work that way — a revision means regenerating the image, and the elements already approved may not survive intact. For client-facing work with multiple feedback rounds, this is a fundamental limitation.

There’s also what might be called the hidden cleanup economy. The polished AI showcase images rarely reflect the actual effort behind them: the failed generations, prompt iterations, Photoshop corrections for inpainting artifacts, broken nodes, hours spent trying to reproduce a result that worked once. Independent studio research consistently puts realistic workflow acceleration from AI at 20–35% overall — meaningful, but considerably more modest than the 80–90% figures that appear in marketing. The gap is almost entirely explained by invisible work that demos don’t show.

AI-Assisted Development and the New Technical Artist

One of the less discussed consequences of the current AI moment isn’t about image generation at all. It’s about who gets to build tools.

For years, the technical artist in an ArchViz context was constrained by the time and expertise required to build anything substantial from scratch. A useful utility might take days. An API integration with real UI might take weeks. LLMs are changing that calculation — not by replacing programming knowledge, but by compressing the distance between having an idea and having a working prototype. For artists who understand the workflow problem and have enough scripting background to verify the output, the time cost of building a custom tool has dropped significantly.

Consider: Francisco Palomo Montes, an architect and visualizer who describes himself explicitly as not a programmer, identified a friction point many DCC users would recognize — the constant context-switching required to use image-to-3D services. Leave the application. Open a browser. Upload the image. Wait. Download the file. Import it. Adjust materials. Repeat for every asset. He built a plugin called Caliper using Claude as a coding assistant, connecting 3ds Max directly to the Tripo AI API and eliminating the steps that broke his concentration. His reflection on the experience: “The interesting thing isn’t the tool itself. It’s what having built it changes: the software went from being something I suffer to something I have control over.”

That shift — from user to builder, without becoming a full software developer — is one of the most meaningful patterns emerging in the technical artist space right now. It’s producing a growing ecosystem of micro-tools, custom integrations, and workflow utilities: built by artists solving their own specific problems, shared quietly in Discord servers and GitHub repositories. Not revolutionary products. Just a lot of small frictions, getting removed.

The implication for the technical artist role is real. The value isn’t shifting from “can write code” to “can prompt AI.” It’s shifting toward understanding the production system well enough to know which problems are worth solving and how to connect the tools that solve them. That kind of knowledge is hard to acquire and hard to replicate. AI can help implement a solution. It doesn’t automatically know which problem needs solving in the first place.

Custom 3ds Max plugin integrating AI-generated 3D assets directly into production workflows.

Where to Start — Practical Orientation for ArchViz Artists and TDs

The instinct when facing a fast-moving landscape is to try to follow all of it. That instinct is worth resisting. The AI tool space changes quickly enough that investing heavily in any specific platform before understanding its production relevance is a reliable way to waste time. A more useful approach: start from your own workflow and work outward.

For most artists, the most practical entry point is already inside the tools they’re using. V-Ray, Corona, Enscape, and D5 Render all have AI-powered features embedded in current versions — denoising, upscaling, material generation, atmosphere matching — with no additional pipeline and minimal learning curve. Understanding what these features actually do in practice, and where the productivity gain is real versus overstated, is more valuable than jumping into a ComfyUI stack on day one.

For concept and brief alignment, AI image generation is genuinely useful — but only with a clear distinction between concept support and production deliverable. Generating ten or twenty visual directions to help a client articulate their aesthetic before significant modeling begins: real value. Using the same tools as substitutes for final controlled deliverables: where professional liability starts to appear. That line is worth drawing clearly.

For technical artists and advanced users, AI-assisted scripting is probably the highest-leverage area to explore right now. Not because every artist needs to build a custom plugin, but because identifying one or two specific workflow friction points and using LLM assistance to address them is a realistic short-term experiment. The key is starting with a clearly defined problem — not “integrate AI” as a general ambition.

And one recommendation that applies across all of the above: don’t abandon traditional 3D skills. The current landscape, if anything, reinforces their value. The artists who understand both structured 3D production and AI-assisted workflows are in a far stronger position than those who have bet on prompts alone. The AI layer needs something reliable to work with. That something is still the 3D pipeline.

A New Production Layer, Not a Replacement

After examining the current state of AI in Architectural Visualization closely — through industry surveys, production workflow documentation, forum discussions, GitHub threads, and the quiet evidence of what actually ships versus what gets demoed — the picture that emerges is not the one that dominates public discourse.

This is not a story of replacement. It’s a story of layering.

AI is becoming an enhancement layer, an acceleration layer, a postproduction layer, a toolmaking layer. It’s inserting itself into the spaces around the traditional ArchViz pipeline and changing how artists move between ideas, images, tools, and deliverables. The 3D scene remains structurally central. What’s growing is the AI-assisted infrastructure that connects it to faster outputs, richer concepts, and more fluid iteration cycles.

The most meaningful innovation may not come from large platforms competing for the prompt-to-image market. It may come from many small, highly specific tools built by people who understand the everyday friction of production. That’s what a production layer looks like from the inside: not a revolution, not a replacement, but a gradual accumulation of specific tools making specific painful tasks less painful.

For ArchViz, this moment carries both genuine opportunity and real risk. The opportunity is compression — of concept time, iteration cycles, postproduction effort, toolmaking barriers. The risk is the normalization of AI outputs in contexts where their limitations aren’t visible to clients but are visible to professionals: the geometry errors, the inconsistent revisions, the deferred problems that accumulate when speed is prioritized over accuracy.

Traditional ArchViz is not disappearing. But the way it gets built, enhanced, and delivered is clearly beginning to change. That change deserves more honest attention than most of the current conversation around it provides.

AI-assisted staging and cinematic walkthrough generation from simple text prompts.

References & Further Reading

This article draws on a broader research process completed in May 2026.

Industry Reports & Surveys

Studio & Practitioner Research

Tools & Ecosystems

Open-Source & Development

  • GitHub: ADN-DevTech/3dsMax-Python-HowTos (active 2024–2025)
  • Apatero.com: ComfyUI troubleshooting documentation (October–November 2025)
  • Autodesk Developer Blog: pymxs and 3ds Max SDK notes (through May 2025)

Practitioner Posts (LinkedIn, May 2026)

  • Joël Feyaerts (Blacksquid / CGarchitect) — on AI geometry errors in sales-phase renders
  • Francisco Palomo Montes — on building the Caliper plugin (3ds Max + Tripo AI API)
  • Iván Zabalza González (Señapaula SL) — on hybrid DCC + ComfyUI production workflow
  • Chiang Ning (ARBV/PMP) — on “AI for atmosphere, 3D for accuracy”
  • Rodrigo Zacharias — on prompt engineering as creative direction
  • Chaos V-Ray official — V-Ray 7 AI feature announcement
  • Wes McDermott (Adobe Firefly Foundry) — on DCC viewport as AI conditioning input
  • Sanmiraa Group — on client decision-making and AI brief alignment

Written by Hernán A. Rodenstein, Founder of Spline Dynamics.

This article is part of an ongoing research and experimentation process around AI-assisted workflows, technical tool development and production automation at Spline Dynamics.

Studios interested in custom 3ds Max tools, workflow automation or pipeline optimization can learn more about our Custom 3ds Max Script Development Services.

Affiliate Disclosure
Some links in this article may be affiliate links. If you decide to purchase through them, we may earn a small commission at no extra cost to you. These commissions help support the creation of free tutorials, articles, and tools on Spline Dynamics. All opinions expressed are our own, and we only recommend products that we believe provide real value to the CG and ArchViz community.

Share
Posted on by — Leave a comment

Cleaning and sanitizing broken or bloated 3ds Max scenes

Cleaning & sanitizing broken or bloated 3ds Max scenes
Cleaning & sanitizing broken or bloated 3ds Max scenes

Understanding what “scene cleanup” really means in 3ds Max

Most artists only start thinking about scene cleanup when something goes wrong.

A file that suddenly grows in size, takes far longer to open or save than it used to, throws warnings without a clear explanation, or becomes increasingly unstable over time is often described as “heavy” or “slow”. The instinctive reaction is usually to blame geometry, textures, or render settings.

In practice, many of these problems have a different origin: internal scene contamination.

Over time, a 3ds Max scene accumulates invisible data that has nothing to do with what you see in the viewport. Legacy nodes left behind by deleted objects, callbacks registered by scripts that are no longer present, corrupted references from CAD or BIM imports, redundant dummies, deeply nested groups or hierarchies, obsolete modifiers, broken links to external assets, embedded scene scripts, or malformed data blocks can all live quietly inside a file.

Deleting visible objects does not remove this data. Neither does collapsing stacks or hiding layers. The scene may still appear functional, but its internal structure slowly degrades.

This is what scene sanitization is about: restoring the structural health of a 3ds Max file.

It is important to be clear about scope. Scene cleanup is not viewport optimization, polygon reduction, or proxy management. Those are separate problems, with separate solutions. This article focuses exclusively on identifying and removing hidden or problematic data that compromises scene stability and long-term usability.

Different layers of scene contamination

One of the reasons scene cleanup is confusing is that problems tend to overlap. A single scene can suffer from multiple issues at once, but they live at different layers.

At one level, there is internal scene data: nodes, controllers, callbacks, legacy references, or corrupted objects that exist entirely inside the file. Tools that operate at this level attempt to sanitize the scene structure itself.

At another level, there are external dependencies: textures, proxies, XRefs, and other assets referenced by file paths. Broken or outdated paths can dramatically slow down scene loading and trigger warnings, even if the internal data is otherwise clean.

Finally, there are structural integrity issues: malformed data introduced by CAD/BIM imports, incompatible plugins, or malicious scripts. These issues often require diagnosis before cleanup, because blindly deleting data can make things worse.

The tools covered in this article each address a different layer of this problem. Understanding that distinction is essential to choosing the right one.

A curated selection of tools for scene cleanup and sanitization

The following tools are not presented as a direct comparison between similar solutions. Instead, they form a curated selection of the most effective tools available for cleaning and sanitizing 3ds Max scenes, each addressing a different layer of the problem.

The selection is based on a set of practical criteria that matter in real production environments: how clearly each tool is focused on a specific type of issue, what it actually does to the scene in practice, how safe and predictable its behavior is, how much technical understanding it requires, its compatibility with modern versions of 3ds Max, and its licensing model.

Rather than ranking these tools, the goal is to clarify when and why each one makes sense, so artists can choose the right approach based on the nature of the problem they are facing.

Prune Scene – by 3D Ground

Primary focus

Removal of scripted viruses and accumulated scene garbage.

What it does in practice

Prune Scene is primarily an antivirus and garbage-cleaning tool for 3ds Max scenes. Its core purpose is to detect and remove scripted malware, malicious callbacks, and residual data that can accumulate invisibly over time.

In practice, the tool targets known scripting viruses, invalid or missing objects, obsolete custom attributes, broken references to plugins or bitmaps, empty layers, and other forms of internal junk that contribute to scene bloat or instability. By removing this accumulated garbage and malicious code, Prune Scene can significantly reduce scene file size and, in many cases, improve saving times and overall stability.

Key features

  • Detection and removal of common 3ds Max scripting viruses
  • Cleanup of accumulated internal garbage and invalid scene data
  • Removal of missing or broken references (bitmaps, plugins, effects)
  • Optional batch processing and recovery tools under license

Ease of use

Moderate. The interface is straightforward, but the number of cleanup options requires basic understanding of what is safe to remove in a given context.

Strengths

Prune Scene is particularly effective in scenarios where scenes are suspected to be infected by scripting viruses or polluted by residual data from external sources. Its active protection and batch-cleaning capabilities make it valuable in shared environments and legacy projects.

Limitations and risks

Cleanup operations can be aggressive. While this is often necessary for virus removal, changes may be destructive if applied without care. Working on backups and validating results is essential. Advanced recovery and batch features require a paid license.

Compatibility

Modern versions of 3ds Max.

Price and licensing

Paid license at a very affordable price. Shareware version is also available.

Cleaner – by Andreas Meissner

Primary focus

General-purpose internal scene cleanup.

What it does in practice

Cleaner is a collection of MaxScript routines designed to remove common forms of scene residue left behind during everyday work. It targets practical, surface-level issues such as empty or unused layers, obsolete helpers, invalid controllers, leftover animation data, and various elements that no longer serve a purpose after heavy editing, importing, or iterative changes.

Cleaner does not attempt deep scene recovery or diagnostics. Instead, it provides a broad, pragmatic sweep of frequent cleanup tasks that many artists would otherwise perform manually or ignore entirely.

Key features

  • Multiple cleanup routines covering common scene elements
  • Simple interface grouping different cleanup actions
  • Fully open-source MaxScript

Ease of use

Moderate. While the interface is simple, the impact of individual cleanup actions is not always obvious. Users benefit from understanding what each operation affects before applying it broadly.

Strengths

Cleaner remains useful as a lightweight, no-cost cleanup tool for routine scene maintenance. Its open-source nature makes it valuable for technical users who want transparency or wish to adapt parts of the script to their own workflows.

Limitations and risks

The script has not been actively maintained for several years and offers no official support. Some cleanup operations can be destructive if used indiscriminately, particularly on complex or legacy scenes. Thorough testing and backups are strongly recommended.

Compatibility

Works in modern versions of 3ds Max, though manual installation and verification are required.

Price and licensing

Free (open-source MaxScript).

Tools for cleaning and sanitizing 3ds Max scenes - Prune Scene, Cleaner

ECleaner – by Ehab Kandil Designs

Primary focus

Cleanup and correction of external asset paths.

What it does in practice

ECleaner does not sanitize internal scene data. Instead, it focuses on identifying, fixing, and normalizing file paths for external assets such as textures, proxies, XRefs, and other referenced files.

Scenes that have been moved between computers, studios, or servers often contain broken or outdated paths. Each missing reference forces 3ds Max to search for files during load, significantly increasing opening times and generating warnings. ECleaner addresses this specific but very common problem.

Key features

  • Detection and correction of broken asset paths
  • Batch processing of external references
  • Lightweight and focused design

Ease of use

High. The tool is straightforward and designed around a clear, narrow task.

Strengths

ECleaner is highly effective at reducing scene load times caused by missing assets. It is free, simple to use, and solves a problem that many artists misattribute to scene complexity.

Limitations and risks

ECleaner does not remove internal scene junk, corrupted data, or legacy nodes. It should be seen as complementary to internal cleanup tools, not a replacement.

Compatibility

Modern versions of 3ds Max.

Price and licensing

Free.

Forensic – by SiNi Software

Primary focus

Scene inspection, diagnostics, and corruption detection.

What it does in practice

Forensic is designed to analyze a scene before attempting cleanup. It inspects internal data structures, imported CAD/BIM content, embedded scripts, and potentially malicious or incompatible elements. Rather than aggressively deleting data, it provides reports that help identify where problems originate.

This makes Forensic particularly useful for scenes that crash, refuse to open, or behave erratically, where blind cleanup could cause further damage.

Key features

  • Deep inspection of scene structure
  • Detection of corrupted or potentially malicious data
  • Analysis of problematic imports and legacy content
  • Optional extended relinking capabilities when used within the IgNite Collection

Ease of use

Moderate to advanced. The interface is accessible, but interpreting results requires some technical understanding of 3ds Max internals.

Strengths

Forensic excels at diagnosis. It allows users to understand what is wrong with a scene before deciding how to fix it, which is critical in professional or high-risk environments.

Limitations and risks

The free version includes banner advertising and is limited in extended functionality. Advanced features such as relinking a wide range of external file types require the IgNite Collection, where Forensic integrates with SiNi’s Unite plugin. As a diagnostic tool, it is not intended to replace dedicated one-click cleanup scripts for routine maintenance.

Compatibility

Modern versions of 3ds Max.

Price and licensing

Free version available with limited functionality. Full functionality is included as part of the paid SiNi IgNite Collection.

Tools for cleaning and sanitizing 3ds Max scenes - ECleaner, Forensic

Hierarchy Guardian – by Spline Dynamics

Primary focus

Safe cleanup of complex hierarchy structures in imported CAD/BIM scenes.

What it does in practice

Hierarchy Guardian is designed to analyze and safely clean scene hierarchies generated by technical imports. CAD and BIM models often produce extremely deep nested structures, placeholder nodes, CAD blocks, and other artifacts that make scenes difficult to manage inside 3ds Max.

Instead of blindly collapsing or deleting hierarchy elements, the tool first performs a structural analysis of the scene. It evaluates hierarchy depth, node counts, and overall structural complexity before applying cleanup operations.

This approach allows users to simplify imported hierarchies while preserving important relationships such as instancing, transforms, and scene organization.

Key features

  • Hierarchy analysis with detailed structural metrics and estimated cleanup impact
  • Safe hierarchy depth reduction with configurable maximum depth
  • Simplification of complex group structures (group-to-hierarchy conversion)
  • Removal of technical placeholders and leftover import nodes

Ease of use

High. The tool includes thoughtful presets and is designed as a guided workflow that allows anything from full cleanup automation to precise control over every step of the process.

Strengths

Hierarchy Guardian focuses specifically on one of the most common sources of bloated scenes: imported CAD and BIM hierarchies. By combining scene analysis with controlled cleanup operations, it helps reduce hierarchy complexity while minimizing the risk of breaking the scene structure.

Limitations and risks

The tool focuses primarily on hierarchy cleanup rather than full scene diagnostics. Issues related to corrupted files, broken assets, or missing external references still require other troubleshooting approaches.

Compatibility

Modern versions of 3ds Max.

Price and licensing

Paid license with affordable options. A fully functional trial is available.

Cleaning and sanitizing broken bloated 3ds Max scenes - Hierarchy Guardian 3ds Max plugin

Native workflows and manual cleanup in 3ds Max

Before relying on third-party tools, it is worth acknowledging that 3ds Max itself provides several native workflows for diagnosing and mitigating scene-related issues. While these workflows are rarely sufficient on their own for deeply contaminated or corrupted files, they form an important first line of defense and, in some cases, can resolve performance problems entirely.

Autodesk’s own technical guidance highlights several common causes of slow scene opening and saving times, including missing external assets, network paths that are no longer accessible, excessive callbacks, outdated references, and heavy scene states. Many of these issues can be identified or partially addressed using built-in tools such as the Asset Tracking dialog, Scene Explorer, XRef management, Layer Manager, and careful use of Merge workflows instead of incremental Save As chains.

Manual cleanup techniques — such as merging clean geometry into a new empty scene, rebuilding materials rather than copying them blindly, or selectively re-linking external assets — remain some of the safest and most transparent ways to restore scene health. They are slower and require more discipline, but they give the artist full control over what is kept and what is discarded.

However, these native and manual approaches have clear limits. They offer little visibility into low-level scene contamination, hidden legacy data, or malformed structures introduced by scripts, plugins, or complex imports. Once a scene reaches that stage, manual workflows alone become inefficient or unreliable, which is precisely where specialized cleanup and diagnostic tools become valuable.

Choosing the right approach

Scene cleanup is rarely about finding the “best” tool. It is about identifying the layer at which the problem exists.

Native workflows and manual cleanup should always be considered first. They are safe, transparent, and often sufficient for resolving issues related to missing assets, bloated save histories, or poorly managed references. They also provide a clearer understanding of how and why a scene has degraded over time.

When problems persist beyond what manual methods can realistically address, third-party tools become essential. Internal scene bloat and legacy data call for sanitization tools such as Prune Scene or Cleaner. Broken external references require a focused solution like ECleaner. Unstable or corrupted scenes benefit from diagnostic tools like Forensic before any destructive action is taken. Excessively deep or chaotic hierarchies in imported CAD/BIM scenes can be addressed with specialized hierarchy cleanup tools such as Hierarchy Guardian.

In many real-world cases, these approaches are not mutually exclusive. The most robust workflows combine careful manual practices with targeted tools, always supported by versioned backups and incremental testing.

Final thoughts

Scene cleanup is preventative maintenance. When ignored, problems accumulate quietly until they become expensive to fix.

Understanding what each tool actually does — and what it does not — is far more important than running every cleanup script available. A clean scene is not just smaller or faster; it is predictable, stable, and easier to maintain over time.

Sources and references

The information in this article is based on a combination of official documentation, developer-provided descriptions, and long-term practical use of 3ds Max in production environments. Key references include:

  • Autodesk Support – 3ds Max scene file takes a long time or is slow to open: official guidance on common causes of slow loading and saving, asset management, and native diagnostic workflows.
  • Prune Scene documentation and product description: feature set, virus removal capabilities, and cleanup scope as described by the developer.
  • Cleaner (ScriptSpot): original script documentation, user feedback, and inspection of the open-source MaxScript code.
  • ECleaner documentation: tool focus and behavior related to external asset path cleanup.
  • Forensic documentation and official video material: tool scope, diagnostic capabilities, and differences between the free version and the IgNite Collection integration.
  • Hierarchy Guardian documentation and product page: reference material on hierarchy analysis and safe cleanup workflows for complex CAD/BIM and SketchUp imports in 3ds Max.

Where appropriate, conclusions are informed by real-world production experience and community-reported behavior rather than marketing claims.

Share
Posted on by — Leave a comment

9 Helpful Free 3ds Max Scripts from ArchVizTools

When you work with 3ds Max every day—especially in Architectural Visualization—small tools can make a huge difference in speed, clarity, and overall workflow efficiency.
Today, I’m sharing a curated list of nine free scripts from ArchvizTools, one of the most active developers in the ArchViz scripting community. These tools are lightweight, easy to install, and extremely practical for everyday production work.

Each script is compatible with 3ds Max 2018 and higher, and all of them can help you save time, clean messy files, create better-looking scenes, or automate tasks that usually require several manual steps.

Here’s the full list, along with descriptions and links.

1. Layer Manager Extension

A practical enhancement for the standard 3ds Max Layer Manager.
This script helps you keep large scenes organized by expanding the default layer tools and making it easier to manage complex layer structures.

If you work with heavy ArchViz files, imported CAD drawings, or multi-asset scenes, a better layer workflow quickly becomes essential.

Download on Gumroad: Layer Manager Extension – ArchvizTools

2. Fire Flame Generator

This tool automatically creates flame, fire, or smoke-like shapes using procedurally generated splines.
It’s perfect for:

  • fireplaces
  • candles
  • torches
  • outdoor fire pits
  • atmospheric elements for interior scenes

You get quick, customizable fire effects without relying on heavy simulations or particle systems.

Download on Gumroad: Fire Flame Generator – ArchvizTools

3. Carpet Generator

A surprisingly powerful script that generates realistic carpets and rugs using parametric controls.
You can adjust:

  • dimensions
  • pile height
  • density
  • pattern
  • color
  • and more

Ideal for interior designers, ArchViz artists, and anyone who regularly builds styled interior sets.

Download on Gumroad: Carpet Generator – ArchvizTools

4. Baluster Picker

If your scenes include stairs, balconies, fences, corridors, or classical architecture, this script will save you time.
Baluster Picker lets you quickly browse and insert baluster models directly into your scene.

It’s especially helpful in large architectural projects where railings and decorative elements are repeated dozens of times.

Download on Gumroad: Baluster Picker – ArchvizTools

5. Spotlight Generator

A fast and convenient generator for standard and IES-based spotlights.
Great for lighting:

  • living rooms
  • kitchens
  • galleries
  • product renders
  • detail-oriented interior designs

This script helps you set up lighting structures quickly, then fine-tune them afterward with your preferred render engine.

Download on Gumroad: Spotlight Generator – ArchvizTools

6. Quick Light Generator

A complementary lighting tool that focuses on fast creation of general lights.
Perfect when you need to:

  • set up rough lighting for quick previews
  • iterate multiple lighting moods
  • prototype a scene before final materials and rendering

It’s simple, clean, and a good addition to your light setup toolbox.

Download on Gumroad: Quick Light Generator – ArchvizTools

7. Clay Mode Advanced

If you love “clay renders” or ZBrush/Mudbox-style matcaps, this script is for you.
Clay Mode Advanced applies a configurable clay material to your entire scene or selection using a library of 30 included matcaps.

Use it to:

  • evaluate shapes and proportions
  • create modeling previews
  • generate stylized clay renderings
  • speed up shading-free visualization

Excellent for modeling, look-development, or creating clean previews for clients.

Download on Gumroad: Clay Mode Advanced – ArchvizTools

8. FlatZ

FlatZ is a small but very effective tool—especially when working with CAD files imported into 3ds Max.
It flattens the vertices of shape objects, fixing common problems like:

  • uneven elevations
  • misaligned shapes
  • geometry that should be perfectly flat but isn’t

If you’ve ever imported a messy DWG and found that splines are not perfectly aligned, this script fixes the issue instantly.

A single click, and everything is flattened cleanly.

Download on Gumroad: FlatZ – ArchvizTools

9. PolyCount

PolyCount scans your entire scene, finds every geometric object, and displays a list sorted by polygon count from highest to lowest.

The script allows you to see which assets are consuming the most resources, detect heavy or unoptimized models, and instantly select the problematic objects.

From there, you decide whether to reduce the mesh, convert to proxy, or replace the asset.

It’s simple but surprisingly effective for optimization—especially helpful when you inherit a messy file from someone else.

Download on Gumroad: PolyCount – ArchvizTools

Final Thoughts

These nine free scripts from ArchvizTools are excellent additions to any 3ds Max ArchViz workflow.
Some help you clean up messy scenes, others speed up lighting or modeling tasks, and some are perfect for quickly improving overall productivity.

If you frequently work with large architectural projects—or if you simply enjoy having smart tools to streamline your daily work—these free scripts are definitely worth downloading and testing.

Feel free to try them out, mix them with your existing tools, and experiment with different workflow improvements.
And if you enjoyed this roundup, stay tuned: I’ll continue sharing useful 3ds Max resources, tools, and tips that help optimize real production pipelines.

Share
Posted on by — Leave a comment

Custom 3ds Max Tools That Transformed Real Production Workflows: Three Case Studies

Over the last few years, I’ve helped several studios improve their production pipelines by developing custom tools tailored to their real 3D workflows. Each project came with different challenges, but all of them had the same purpose: to eliminate repetitive work, reduce errors, and let artists focus on creativity instead of manual tasks.

Many ArchViz studios and 3D teams still spend countless hours performing actions that could easily be automated. When a workflow depends on repeating the same steps across dozens—or hundreds—of assets, custom 3ds Max scripting can make an enormous difference. These three real-world examples show how bespoke tools can dramatically boost efficiency inside a production environment.

Aspace (Australia): Automating Material Replacement

Aspace, an Australian manufacturer of outdoor playgrounds, uses a pipeline where detailed structures are created in Autodesk Inventor and then brought into 3ds Max for rendering. The workflow was solid—but one major issue slowed everything down: every imported material from Inventor arrived as a placeholder, and the artist had to manually replace them with the correct VRay materials.

With more than ten projects per week, this repetitive task consumed an enormous amount of time.

To solve this, I developed a custom script that automatically identifies each imported material and replaces it with the proper VRay counterpart from their internal library. The process became instantaneous, consistent and error-free.

The outcome was significant: the studio saved over 20 hours of manual work every single week, allowing their artist to spend more time improving the quality of the final renders instead of handling repetitive setup tasks.

Star Event (Malaysia): A CAD-Inspired Measurement Tool

Star Event, a multi-award-winning event marketing agency, needed a way to take accurate measurements inside complex 3ds Max scenes. They were looking for something intuitive and reliable—similar to SketchUp’s measurement workflow and the clarity of CAD annotations—but fully integrated into their 3ds Max environment.

They also needed to export all measurements to a spreadsheet (Excel or CSV) and include the dimensions directly in the final 3D renders for documentation and client presentations.

I developed a custom tool that allows users to take precise point-to-point measurements with snapping support, automatically generate readable TextPlus-based distance labels in the viewport, and manage everything from a dedicated interface. Measurements could be renamed, organized, exported and rendered directly within the scene.

This project eventually evolved into 3D Measure Master, a commercial plugin now used by hundreds of 3ds Max professionals worldwide—a great example of how a custom script can grow into a full-featured production tool.

Beiga (Poland): Automating RenderStacks Workflows

Beiga, a studio specializing in photorealistic furniture visualization, often works with multiple furniture groups, material variations and both regular and transparent-background render versions. Setting up all these combinations manually inside RenderStacks(*) made their workflow slow and difficult to maintain across projects.

To streamline this, I developed a custom tool that automatically builds the entire RenderStacks structure needed for the project—creating and organizing layers, preparing cameras, setting up visibility rules and generating all required passes. Instead of manually configuring dozens of options, the user simply selects the furniture groups and cameras, chooses the material variations, and the entire render setup is generated in seconds.

RenderStacks provides deep automation capabilities through its Maxscript API, but making full use of it required studying and testing its functions thoroughly. I also consulted with RenderStacks support, who helped me work with a few advanced, undocumented functions. This made it possible to deliver a tailored and efficient solution that the studio could reuse across multiple projects.

(*) RenderStacks is a 3ds Max plugin used to manage complex multi-pass render setups. It allows artists and TDs to build structured, modular render trees, and provides a Maxscript API for workflow automation.

What All These Projects Have in Common

Although each case was unique, all of them demonstrate how custom scripting can reshape a studio’s workflow. Every tool significantly reduced manual labor, minimized the risk of human error and adapted 3ds Max to the exact needs of the production pipeline instead of forcing artists to work around limitations. Most importantly, these solutions allowed teams to shift their time from repetitive tasks to creative work—where it truly makes a difference.

Want to Improve Your 3ds Max Workflow?

If your studio could benefit from workflow automation, custom tools or pipeline optimization in 3ds Max, you can learn more about our Custom 3ds Max Script Development Services.

Share
Posted on by — Leave a comment

From Developing 3ds Max scripts to Blender addons

My First Steps into Blender: Why I Decided to Start Developing Addons

For more than a decade I’ve been fully immersed in the 3ds Max world—using it every single day for production, and building plugins and scripts under the Spline Dynamics brand to make workflows faster, smarter, and a lot less painful. 3ds Max has been my home, and honestly, I still love it. But over the past few years, it’s been frustrating to see Autodesk holding back on 3ds Max development, while Blender keeps expanding impressively across every corner of 3D production.

Like many of you, I was skeptical at first. Blender looked interesting, sure—but could it really compete with 3ds Max in professional pipelines? I’ve always believed that software is just a tool, and what really matters is what you create with it. Still, Blender kept popping up everywhere: in ArchViz, motion graphics, VFX, game development, even among freelancers and small studios that traditionally relied on Max. Why? It’s free, open source, growing super fast, and the community is insanely active.

So at some point, curiosity won. I started learning Blender on the side, playing with Geometry Nodes, digging into the Python API, and comparing it to my experience developing for Max. And here’s my honest take so far:

What I really like about Blender:

  • It’s free and open source, which lowers the entry barrier for tons of artists, and allows for continuous updates and revisions.
  • The software is really lightweight and opens in a few seconds.
  • Geometry Nodes are just brilliant. They open up procedural workflows that in Max would require either plugins or a lot of custom scripting.
  • The community is massive, helpful, and super engaged. There’s a constant flow of tutorials, addons, and experiments.
  • Development is active and transparent—you can see the roadmap, the commits, and even influence the direction.

What I still miss from 3ds Max:

  • Some workflows still feel more polished and robust in Max (especially when it comes to precision modeling and certain CAD-related tasks).
  • The modifier stack in Max is simple but extremely powerful—sometimes Blender’s approach feels a bit messy.
  • As a developer, the MaxScript environment (combined with the SDK) is very mature, while Blender’s Python API is powerful but still has quirks you need to work around.
  • Let’s be honest: switching after years in Max is not painless. Muscle memory is a thing!

After a while, I realized something important: I don’t need to choose. I can keep developing and supporting plugins for 3ds Max while also exploring Blender. Both have strengths, and many professionals (maybe you too) actually use them side by side depending on the project.

Which brings me to some exciting news: I’ve just released my very first Blender addon!

ECM, a simple and powerful Blender modifier

ECM – Extrude Curve Modifier is a non-destructive modifier built with Geometry Nodes that lets you extrude curves quickly and parametrically. If you’ve ever tried to create 3D geometry from curves in Blender, you know it’s possible but not always straightforward. ECM makes it simple, intuitive, and flexible—something I always aim for in my tools.

This is just the beginning. My plan is to keep developing addons for Blender while continuing my work in 3ds Max. I see this not as “switching sides” but as expanding the toolkit—for myself and for you, the artists who follow Spline Dynamics.

So if you’re a Blender user (or curious about becoming one), feel free to check out ECM, it’s already available on Blender Extensions and on Gumroad. I’d love to hear your feedback, suggestions, or ideas for future tools.

This is a new adventure for me, and I’m honestly excited to see where it leads.

Share