About NodeFlow / Founders
Current NodeFlow Compatibility
Supported Materials
NodeFlow currently converts the most commonly used Corona materials from 3ds Max into native Blender Cycles node setups.
Supported materials:
- Corona Physical Material
- Corona Legacy Material
- Corona Layered Material
- Corona Blend Material
- Corona Light Material
Supported Texture Maps
NodeFlow currently supports automatic conversion of the following texture nodes:
- Corona Bitmap
- Standard Bitmap Texture
- Corona Mix
- Corona Color Correct
- Corona Normal
- Corona Bump
- Corona Color
- Corona Ambient Occlusion
- Composite Texture (Normal, Overlay, Screen, Multiply)
- Falloff (Perpendicular / Parallel)
- RGB Multiply
- Color Map
- Noise
- Gradient
- Gradient Ramp
- Cellular
- Output
Current Status
The current beta version is focused on reliable conversion of the materials and texture maps most frequently used in architectural visualization workflows.
Many production scenes already convert successfully and require little or no manual shader adjustment after import.
In Development
Work is currently underway on support for additional Corona maps and advanced material features, including:
- Corona MultiMap
- Corona Triplanar
- Corona UVW Randomizer
- Corona Distance
- Corona FrontBack
- Corona Round Edges
- Corona Curvature
- Corona Tile Map
- Corona Pattern
- Additional procedural and utility maps
Compatibility is continuously expanding based on beta testing feedback and real production scenes.
About NodeFlow
Built from Real Production Needs
NodeFlow was born from a real production challenge — not from theory.
It is built upon years of hands-on experience with professional 3D workflows, production pipelines, and process automation.
For many years, I worked in architectural visualization and 3D production, including large-scale studio environments where efficiency, data organization, and pipeline reliability are critical.
The Problem
In real-world production, asset exchange between different tools such as 3ds Max and Blender is still fragmented, manual, and often unpredictable.
Every studio solves this problem differently — or doesn’t solve it at all.
As a result, artists spend countless hours rebuilding materials, reconnecting textures, fixing assets, and repeating the same technical tasks project after project.
The Birth of NodeFlow
NodeFlow started as a personal system designed to eliminate repetitive work involved in preparing and transforming 3D assets.
Over time, it evolved into a structured platform for asset transformation, workflow automation, and the creation of efficient 3D production pipelines.
What began as an internal tool gradually became a larger vision for connecting different parts of the 3D ecosystem.
Mission
The mission of NodeFlow is to become a universal layer for structured 3D asset exchange and production workflow automation.
Not just another plugin — but a system layer that helps bridge software, workflows, and production environments.
Built from real production experience.
Designed for scalable pipelines.
Focused on practical results.
Team
NodeFlow is developed by a small team that combines practical 3D production expertise with software engineering and system architecture experience.
Evgeny Litvyakov
Founder / Product & System Design
Responsible for product vision, pipeline architecture, workflow design, and integration logic.
Professional experience in 3D production and architectural visualization since 2006.
Andrey Bezpalenko
Technical Development / Backend Systems
Responsible for backend architecture, infrastructure, and implementation of core system components.