Mohammadreza Talebi

Fargah Design Studio

A focused Windows workspace connecting 3ds Max production, camera and render controls, prompt knowledge, project history, and private AI handoff.

Explore the project

By Mohammadreza Talebi · 5 min read

Fargah Design Studio
Product preview in the desktop workspace · Actual product interface
Year
2026
Role
Product / Desktop development
Scope
Windows · 3D · Private AI
Status
In development

The project, in context

Fargah Studio is a Windows workspace for architectural design that connects 3ds Max renders, visual styles, project context, a two-dimensional planner, and estimate handoff. I designed the product and its local desktop integration so a render can continue through the next decision without losing the context that produced it.

The render was only one part of the work.

An architectural image depends on choices made across several tools: scene geometry, camera, light, style, material references, and the client's brief. When the image moves into a chat window, much of that context can disappear. It becomes difficult to explain what must stay fixed, what may change, and which version the team is reviewing.

The desktop experience also had to handle real workstation conditions. Starting a packaged app should not depend on the developer's folders or a remote font loading successfully. AI handoffs needed an honest boundary too: opening a subscribed chat product and preparing a prompt is different from executing an API request that returns an image automatically.

Keep the design context beside the image.

The native Windows host starts the local Studio service and shows the interface in WebView2. A matching 3ds Max macro prepares camera and render settings, then sends the rendered image to the local app. Style selection and project context sit beside that image, making the next handoff easier to understand and review.

The workspace extends beyond image enhancement. Project Brain receives scene snapshots and assembles a design brief; the planner uses product images and approved dimensions for early compositions; render history keeps earlier outputs available. Estimate export and CRM handoff connect the design surface to a more practical delivery path.

What I built

The parts that make this project useful in day-to-day work.

  1. A direct bridge from 3ds Max

    The Studio macro offers saved and preset cameras, resolution choices, and V-Ray setup controls. Render & Send brings the output into the local workspace, while a separate scene snapshot gives Project Brain more context than an image alone.

  2. A style library for consistent handoffs

    Prompt styles turn a repeatable visual direction into a selectable starting point. The designer combines the style with the current image and project brief, then prepares the next handoff. The interface keeps the chosen source and destination explicit.

  3. Project Brain and scene snapshots

    Project Brain collects the latest scene snapshot and turns design intent into a readable brief. The workspace shows readiness and the absence of a snapshot explicitly, so a missing connection is not presented as completed project knowledge.

  4. A two-dimensional product planner

    Company products and designer presets can be searched and placed on a planner canvas. Guide lines, snap, zoom, rotation, mirroring, and slice controls support composition. The planner can save a PNG and connect the composition to an estimate workflow.

  5. Render history and estimate output

    The local service exposes the latest render and its history so the workspace can retrieve earlier work. Product and sales catalogue data support estimate export, while the implemented CRM connection gives authorised users a route for handing over an estimate.

  6. Explicit AI modes and local secret storage

    The private-GPT handoff prepares the prompt and opens the destination; uploads still need user confirmation. An optional billed API path supports automatic processing. Documented release work protects local sensitive settings with Windows user-bound encryption and preserves user data during staged updates.

From structure to release

  1. Follow one image through the whole workflow

    I shaped the interface around the sequence from camera and scene to render, brief, style, and handoff. The entry point and readiness states help the designer understand the next required action without visiting every section first.

  2. Connect the desktop and the modelling tool

    The work spans a native Windows host, the local .NET service, and a 3ds Max macro. Their status endpoints, local render exchange, and snapshot routes make the connection inspectable instead of relying only on the appearance of a connected interface.

  3. Package for the designer's workstation

    The recorded release work includes packaged-server startup, offline font availability, compact-sidebar fixes, protected local settings, update health checks, and restoration after startup failure. The portfolio keeps the product's development status visible rather than implying a completed public rollout.

Delivery and current scope

  • A Windows desktop host, local .NET service, and companion 3ds Max macro.
  • Style library, Project Brain, planner, render bridge, and render-history interfaces.
  • Implemented product/estimate routes and an authorised CRM connection.
  • A staged installer and documented limitations for subscribed-chat and API modes.

Questions about this project

Is Studio a browser-based public service?

The reviewed product is a Windows workspace backed by a local service. Some handoffs open external services, but the Studio interface and local project exchange are designed for the workstation.

Does a Plus subscription make image processing automatic?

The documented private-GPT mode prepares a prompt and opens the chat destination; the user still confirms the upload. Automatic processing uses the optional API route and its separate account and billing requirements.

How does a render continue into the next design step?

The local bridge retrieves the latest render and its history. The designer adds project context and chooses a visual direction, then prepares an assisted handoff or continues into the planner and estimate workflow. External processing depends on the selected service mode.

Have a similar project in mind?

Tell me what you need to build and where the current experience falls short.

Start a conversation+989304330645
Next projectFargah Design OS