For those who don’t know the tool: Twinmotion is a real-time viz app powered by Unreal Engine, built for quick scene assembly, lighting, and outputs without living in node graphs.

Photo matching, now less of a dark art

Twinmotion 2026.1 adds a photo matching workflow built around a new Match Perspective tool. You load a background image as a backplate, identify vanishing points (Lines or Grid), and the camera adjusts position and focal length to match the image. The goal is simple: get a 3D model to sit reasonably convincingly inside a 2D photo without hand-tuning camera parameters for an afternoon.

The tool also includes shadow projection from 3D objects onto the calculated ground plane. That helps sell integration when the backplate already has strong directional cues. If you do client-facing previz or quick location studies, this is one of those features that saves time. It also nudges Twinmotion closer to the familiar backplate plus camera-match workflow many artists already use elsewhere, just with fewer steps and less guesswork.

Autosoft edge: a band-aid, in the best way

CG edges can read too sharp, especially when you are chasing photo-like results in a simplified lookdev context. Twinmotion 2026.1 introduces Autosoft edge, a rendering effect you can apply to selected objects to soften hard edges to a specified radius.

Autosoft Edge works in Standard, Lumen, and Path Tracer modes. That means you can keep one scene and one intent while switching render modes, without losing the edge treatment that helps prevent the razor-cut silhouette look. This is not a replacement for proper bevels when the model needs to withstand close-ups or be exchanged with other tools. It is a pragmatic option for when the scene is already in motion, the imported geometry is what it is, and you want a controllable, consistent soften in teh renderer.

Lighting channels: finally, selective light sanity

Twinmotion 2026.1 adds support for lighting channels. Lights only affect objects assigned to the same channel. In practice, this gives you the abiility to isolate what a physical light influences, which is a staple control in many pipelines.

A concrete example: you can keep your background lighting from touching a hero object in a product or fashion setup. That is useful when you want a clean key and fill on the subject, while the environment stays moody or stylised without contaminating the hero’s exposure and specular response.

Lighting channels do not magically solve bad lighting decisions, but they do let you build a scene that behaves more like a studio rig. You can steer light contribution with intent instead of compensating with endless tweaks to intensity and position.

Camera and lens effects: focus breathing for people who enjoy pain

Twinmotion 2026.1 adds Auto focus for depth of field. With Auto focus enabled, the focal point can automatically adjust to the centre of the screen, effectively following the camera’s look-at point. You can set how long it takes to adjust focus.

There is also a hunting behaviour option. The setting lets you choose whether hunting happens occasionally, frequently, or not at all. That is a very specific kind of realism knob, and it is nice to see it treated as a creative control rather than a bug you have to hide.

Depth of field bokeh gets two new characteristics: Anamorphic oval and Petzval. These affect the blur quality in out-of-focus areas, including elongated and swirling bokeh looks. The two can be used individually or combined. Holga-Hipsters, eat your heart out :P

A Barrel distortion slider rounds out the lens pack, curving straight lines near the edges of frame like real lenses, especially wide-angle ones. All of this points at a consistent theme: Twinmotion is leaning harder into camera language, not just lighting and assets. Which is excellent, if your deliverable is stills and clips that need to read as photographs rather than renders.

Particle VFX: more control, less waiting

Twinmotion 2026.1 revamps the particle-based effects in the Twinmotion library. The update optimised performance and visual quality, and it adds new examples.

More importantly for day-to-day work, the particle effects now have exposed parameters, so you can customise them. The examples called out include fire, fog, smoke, and water.

If your scenes lean on atmospherics to sell scale or mood, parameterised VFX is much more useful than locked presets. It turns the library from a look-up table into something you can art-direct.

European trees, and the stuff you only notice when it breaks

Twinmotion 2026.1 adds a European tree pack: 10 new species of photorealistic European trees, each with three variations, added to the Twinmotion library. If you build outdoor scenes for European contexts, that is straight-up practical content, not just another generic “coloured blob” set. And we are not making any political jokes here; we are talking about trees.

The release also changes how asset libraries live on disk. Twinmotion now manages the location of all asset libraries, including user libraries and user-generated content, in a persistent folder structure. This replaces the previous per-version folder structure.

The point is to stop making you copy, move, or redownload content each release. The persistent structure is intended to enable content to be shared across future versions and simplify file paths.

This is the kind of improvement that rarely makes a reel, but it absolutely shows up in the daily friction budget. Fewer duplicate paths also tends to mean fewer broken links, fewer “where did that go” moments, and less time spent doing file system archaeology. N oinformation yet hopw that integrates with existing asset management systems, like das element or others.

Availability and pricing

Twinmotion 2026.1 is available to download. Existing users can download it via the Epic Games Launcher, and subscribers can also download via the Developer Portal.

Pricing depends on who you are and what you need. Twinmotion is free to use for individuals and small businesses under $1 million USD in revenue in the past 12 months, educational institutions, and students. For individuals and businesses over $1 million USD in gross annual revenue, and/or requiring access to Twinmotion Cloud, Twinmotion seats cost $445 per seat per year.

There is also an Unreal Subscription option listed at $1,850 per seat per year, which includes upgrades for Unreal Engine, Twinmotion, and RealityScan for one year, plus access to Twinmotion Cloud. The All-in-one-thingy sub :)

https://dev.epicgames.com/documentation/twinmotion/twinmotion-2026-1-release-notes

The post Epic Games ships Twinmotion 2026.1 first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Blender To Unreal Live Link is built around a simple promise: push models, materials, and textures from Blender into Unreal Engine without bouncing through a traditional export and reimport loop. The workflow centers on a Blender add-on and Unreal-side Python scripts that sit inside your project so the handoff happens from inside your normal working tools. The add-on supports one-click sending, and it also offers an auto-sync mode for iterative work.

Milad Kambari (Artstation) sells the add-on for $18 on Superhive.

Getting connected without guessing

After installing the Unreal plugin and the Blender add-on, the two applications connect through a Start Live Link action on each side. In Blender, the workflow uses a Start Live Link button. In Unreal, the workflow uses a Blender Live Link menu with its own Start Live Link action.

The first connection can take longer than later runs because the network communication between the applications establishes itself for the first time. A connected status indicates the link is established. If you want to confirm the setup path executes correctly, the workflow suggests checking the log and watching for errors shown in red. If you do not see red errors, that indicates the path was set up correctly, and the instruction is to keep the plugin and scripts in the right place and stay patient while the connection finishes.

Send selected, send full scene, and why one is a trap

Once connected, the basic transfer flow centres on selecting assets in Blender and sending them across. The add-on offers two transfer options: Send Full Scene and Send Selected. Send Full Scene is positioned for smaller to medium scenes, and Send Selected is positioned for larger scenes where you only push what you need.

The usage guidance recommends not leaning too heavily on Send Full Scene because real scenes can be heavy, with a large number of objects. The suggested working method is to proceed with Send Selected so you keep control of what moves over, and to transfer heavier scenes piece by piece. The stated goal is better scene management while avoiding the need for extensive hardware resources.

The workflow description also demonstrates sending multiple objects at once using Send Selected, where selecting multiple objects and running the send results in both arriving in Unreal.

Materials, textures, and the two-lane road

Material transfer is included alongside geometry transfer. The tool is described as able to send materials along with textures, including transferring a model together with its texture. The product listing also states that simple physically based materials transfer automatically with textures for base color, normal, roughness, and metallic.

When materials get more complex, the workflow shifts to a different option. The add-on includes a Bake and Send Selected mode intended for complex materials that need baking before they can be sent. The listing describes complex shader setups using nodes such as the Mix node as examples that can require this path. In this mode, materials are baked into clean textures for transfer, and the workflow is described as non-destructive, restoring original materials after the send. The tool detects whether a model has UV maps. If UV maps exist, it does not alter them and uses them for baking. If a model does not have UV maps, it can generate UV maps as needed for baking.

Live sync, but with a leash

Live sync mode sends changes automatically, but the workflow has a specific rhythm. For edit mode changes, the flow relies on exiting edit mode. After you make an edit, you exit edit mode and return to object mode so the edit becomes visible in Unreal.

Live sync is also framed as “something to use carefully”. The developer does not recommend using it extensively because it can require hardware resoruces due to the different graphical structures of the two applications.

Hierarchies, pivots, and scale sanity

On the scene-structure side, the listing describes parent and child support. Selecting a parent object can include its mesh children automatically, which matters when you are working with grouped meshes or hierarchical scene organisation.

It also preserves pivots. Object origins from Blender are preserved in Unreal, so the pivot behaviour you author in Blender carries through after transfer. Scale handling is called out too. The listing describes a 1 to 1 scale relationship between Blender and Unreal, aimed at avoiding the classic scale mismatch workflow pain. Transforms are part of the transfer. Location, rotation, and scale are sent and applied in Unreal.

What is included and what it needs

The package includes a Blender add-on file and Unreal Python scripts named blender_livelink_addon.py, livelink_unreal.py, and init_unreal.py.

System requirements list Blender 5.0 or higher and Unreal Engine 5.5 or higher, plus Windows 10 or 11, with the condition that both applications must run on the same machine.

Pricing is listed as $18.

Practical takeaways for production artists

If your daily loop includes moving assets from Blender into Unreal for lookdev, lighting, layout, or realtime checks, this tool focuses on reducing the friction in that handoff. It provides Send Selected for controlled transfers, Send Full Scene for smaller setups, and Bake and Send Selected for complex material cases that need baking. It also includes live sync for iterative updates, with workflow notes about exiting edit mode so edits propagate.

As with any new pipeline tool, test it in your own environment before you rely on it for production.

https://superhivemarket.com/products/blender-to-unreal-live-link

The post Real-time Blender to Unreal Live Link first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: glTF sits between DCC export and runtime playback, and these web tools help you sanity check assets and rendering across engines before shots get spicy.

Two sites, one mission: fewer surprises

The glTF Sample Assets site and the glTF Render Fidelity Comparison site just got meaningful upgrades. They target the same everyday pain: you export a model, it looks right in one viewer, and then it looks slightly off somewhere else where it matters. The refreshed Sample Assets experience focuses on browsing, filtering, and sharing reference models that exercise specific features of glTF. The updated Render Fidelity Comparison experience focuses on visual baselines, with side-by-side checks that make renderer differences harder to hand wave and easier to track down. If you build tools, ship engines, validate exporters, or wrangle assets for realtime and VFX, these sites are designed to be the boring, reliable kind of helpful.

Sample Assets gets a real front door

The new landing experience for glTF Sample Assets presents the repository as a proper website. The intent is simple: make it easier to browse and find models by what they demonstrate. Models appear with thumbnails, and animated assets include a small animation preview. The site supports light and dark themes and aims for fast loading and fluid navigation. Filtering and search are first class, with tags that map to features, functionality, and extension coverage.

When you open a model, you land on a dedicated model page with an interactive preview, metadata, and download links. The preview uses the glTF Sample Renderer, which is built on WebGL and targets correct support for official KHR extensions. A context menu in the preview provides presentation options that include debug visualization modes for material properties, variant selection when multiple variants exist, and wireframe presentation when the WEBGL polygon mode extension is available.

The model page also links out to external tools and shows a recommendation style list of related assets, which is a surprisingly effective way to bounce between test cases when you are chasing a specific shading edge case across multiple files.

One practical detail matters here: each model includes a screenshot, description, license information, and a live preview. That combination turns the site into a quick reference shelf rather than a scavenger hunt through folders.

Render Fidelity Comparison leans into side by side truth

The redesigned glTF Render Fidelity Comparison site takes the same library mindset and aims it at output consistency. It frames the core goal as convergence around physically based rendering materials so you can expect a model to appear as intended across renderers and lighting environments. It also notes that this is ambitious, with realtime rendering quality still changing rapidly. *cough* understatement *cough*

The workflow is built for quick comparisons. You choose a model, filter by tags or search, then pick two renders and select a view mode. The comparison modes include side by side viewing, a slider view, and a difference view that shows computed differences.

The site spans popular realtime web renderers and also includes path tracers. In practice, that means you can jump between quick interactive engines like babylon.js and three.js, then also look at path traced production renderings from Blender using Cycles and from V-Ray. It is not about crowning a winner. It is about seeing where two implementations diverge so you can reproduce, triage, and fix.

Comparison images are generated offline and submitted via pull requests to the site repository, which keeps the content auditable and repeatable. That approach also makes it easier for teams to add coverage for their own renderer outputs without inventing a new pipeline.

The biggest new trick is an experimental 3D comparison mode that enables full interactivity comparison of two realtime renderers side by side. It currently supports three.js, babylon.js, model-viewer, and three js path tracer tooling. If you have ever tried to discuss a subtle lighting mismatch over screenshots, you know why interactive side by side matters. In one sentence, the updated site encourages you to comapre outputs with fewer assumptions and more pixels on screen.

https://github.khronos.org/glTF-Render-Fidelity/model/AttenuationTest

Contributing is part of the design

Both sites are open to contributions. For sample assets, new models can be proposed via pull requests to the repository. For render fidelity, you can submit renderer outputs by following the repository guidelines for generating renders of a sample asset and placing the results in the appropriate location for comparison.

There is also a straightforward feedback loop via issues in the repositories, which keeps bug reports and feature requests attached to something actionable. This is the one place where it is worth naming the organizer exactly once: Khronos is clearly aiming to make the glTF developer ecosystem easier to navigate, easier to test, and harder to break quietly.

https://github.khronos.org/glTF-Assets/

https://github.khronos.org/glTF-Render-Fidelity/

The post glTF sample assets and fidelity site refresh first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Think of the Elemental Suite as a real-time VFX kit that exports flipbooks, image sequences, VDB, and caches for DCC and engine work, with EmberGen, LiquiGen, IlluGen, and GeoGen sharing the same ecosystem.

The program, now with a permanent spot

The Layoff Assistance Program is now a permanent offering, built around a simple promise: artists affected by layoffs or studio closures can request licenses to the elemental tool suite free of charge for up to six months, specifically to rebuild portfolio work.

What you actually get for six months

When a layoff license is approved, it grants access to the toolset that sits under the Elemental Suite. That includes the core apps named for the program in current materials: EmberGen, LiquiGen, IlluGen, and GeoGen.

Each tool targets a different kind of content, EmberGen is positioned as a real-time volumetric fire simulation tool that can simulate, render, and export flipbooks, image sequences, and VDB volumes. The value proposition is iteration speed, with real-time tweaking while looping a timeline and a built-in renderer for immediate results.

LiquiGen focuses on liquids, with real-time meshing, forces, sparse simulation domains, and a real-time path tracer. It is described as able to generate flipbooks, image sequences, and Alembic caches, and it explicitly calls out foam, spray, and bubbles as controllable elements.

GeoGen is framed as a node-based workflow for terrain and planet generation, built with games in mind, and presented as part of the same suite.

The net effect for an artist in rebuild mode is straightforward: six months of hands-on time with tools that cover volumetrics, liquids, procedural asset generation, and terrain workflows, under one licensing umbrella, without paying during that period if approved.

Rules that matter when you are building a reel

The program terms are not hand-wavy. The Layoff Assistance Program spells out the intended use and the boundary conditions.

The layoff licenses are strictly for non-commercial use. They are meant to help upgrade skills with new tools and assist with new portfolio pieces. Approval is discretionary. A request can be denied. Commercial use requires a purchased license. That clarity is useful because it prevents the most common licensing misunderstanding: portfolio work is still work, but portfolio work is not automatically commercial work. The program draws the line itself, and you are expected to stay on the correct side of it.

It also means studios should not treat the program as a back door for production seats. If your use case is client deliverables, the license you want is not the one that comes through the layoff portal. If you are rebuilding a porftolio, the terms match the real-world need: get access, make work, learn, and do it in a way that does not collide with commercial licensing.

How to apply without turning it into a side quest

The application flow described in the official program materials is short. You create an account, or you log into an existing one. You submit a request for a layoff license through the portal linked from the program page, using the Apply Now button. Requests are reviewed. If approved, a license key is issued by email and also appears in the account. That is the whole process , with no extra hoops listed on the program page itself.

The program messaging also asks people to share the page with anyone who might need it, which is a rare example of a support initiative that is designed to spread by simple forwarding rather than by gatekept referrals.

Pricing, for when you are back on your feet

Even if you are applying for the six-month program, pricing matters because it tells you what comes next when the clock runs out, or if you need commercial usage.

The official pricing page lays out an Indie and Hobby tier for revenue or funding under 1 million USD. For the Elemental Suite, the price shown is 525 USD for the first year, with 315 USD for optional maintenance annually. For individual tools, the page lists 300 USD for the first year for EmberGen, 300 USD for the first year for LiquiGen, and 300 USD for the first year for IlluGen, each with 180 USD for optional maintenance annually. For GeoGen, the page labels it as beta and lists 150 USD for the first year, with 90 USD for optional maintenance annually.

The pricing page also notes that displayed prices do not include taxes and that final prices are shown during checkout. It states that tier calculations use revenue, project budgets, and funding depending on whichever is greater. For artists who are currently laid off, the immediate takeaway is that the program offers a time-limited, no-cost runway. For artists who land a contract mid-runway, it is also a clean reminder to switch to a commercial license if the work moves beyond non-commercial portfolio building.

A note on intent, and a note on reality

In the accompanying message around the program, the founder describes frustration with recurring layoffs across the industry and positions the program as a way to help artists stand back up, using tool access to support portfolio rebuilding. The same message states that over 100 artists were assisted with free licenses last year.

None of this changes the usual production reality: every new pipeline ingredient should be tested before you depend on it. Even when a tool is fast, friendly, and installed locally, you still validate exports, check integration points, and run a small end-to-end test before you bet a deadline on it.

If you qualify and you are rebuilding, the offer is practical: time, access, and a clearly labeled license boundary. That is not a job, but it can be the difference between stalling out and shipping that next reel shot.

https://jangafx.com/layoff-assistance-program

The post JangaFX makes its layoff assistance programme permanent first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Redshift is a GPU renderer built for fast lookdev and final frames. Vectorworks is a BIM (Building Information Modeling) and CAD hub where buildings get drafted and organised.

Architectural visualisation pipelines love a clean handoff, but they hate the part where you wait for it. Redshift for Archviz positions itself as a single-environment loop: preview inside your BIM tool, iterate while the model still feels editable, then render without rebuilding the whole look in a second app.

The core pitch is direct integration with Vectorworks, aimed at letting artists and designers stay in the same workspace while moving from real-time previews to final renders. The platform targets the usual ArchViz pressure points: quick iterations, look development that stays consistent from draft to final, and visuals that survive client meetings without the dreaded “we will render it later” disclaimer. Maxon describes this as an expansion of the same rendering technology used in its existing ecosystem, tuned for real-world, real-time architecture design workflows

Real-time lighting that behaves like a grown-up

In the feature set, the real-time preview leans hard into lighting, materials, and environment response. The toolset includes controls to change the time of day, sun position, and cloud cover, to show how natural light interacts with the design as you adjust conditions.

Cloud cover control is quite precise, spanning conditions from clear to fully overcast, specifically to visualize how clouds affect natural light, shadows, and the overall mood of an architectural render. That kind of environment knob matters because it ties directly to decision-making. When lighting direction and softness update instantly, material choices stop being theoretical and start becoming compositional tools.

Assets, materials, and the eternal fight against empty rooms

The content side is framed around libraries that help you get to “inhabited space” faster. A growing asset library includes materials, lights, and ready-to-use assets intended to speed up scene building while keeping physical accuracy and visual consistency.

On top of that, the feature descriptions call out drag-and-drop population of interiors and exteriors with a selection that includes furniture, vehicles, realistic plants, and people, and these assets interact naturally with surfaces.

Material coverage is physically correct, spanning concrete and metal through glass, wood, and textiles, with the promise that materials react naturally to light and environment. The workflow emphasis stays on applying, adjusting, and previewing changes in real time, so look development can happen while you are still shaping the design.

Mac and Windows parity, right from the start

Platform coverage is plain: Redshift for Archviz is available for Windows and macOS, andfeature parity across both platforms from the outset. That matters whether you bounce between machines in a studio or your clients do. It also matters if your pipeline includes artists who bring their own gear and do not want a surprise feature gap halfway through a project.

The Cinema 4D escape hatch for the fancy stuff

When a still image turns into a walkthrough, you need more than a preview window. The workflow includes the ability to send a project to Cinema 4D with a simple click, with the intent of enabling more advanced architectural visualisation work, including procedural animations and simulations.

The FAQ describes export from the Redshift for Archviz plugin to Cinema 4D, and states that geometry, materials, cameras, and basic lighting generally transfer well. Once in Cinema 4D, refining scenes, materials, and lighting with a higher level of control is as usual, and then extending the project with animation and simulation.

This is a practical bridge for teams who want the speed of in-app previs but still need a DCC stage for shot craft, camera choreography, or heavier scene management. It also keeps the promise of visual continuity: the same scene, lighting, and materials across preview and final output.

Installation and the beta-shaped reality

The tooling around installation is explicit enough to be useful. The install notes state that the current availability is for Vectorworks, with Revit and Archicad coming soon.

For the Vectorworks side, the guide references installing Vectorworks 2026 using default settings, downloading and signing into the Maxon App, installing an AEC Viewer, then activating the plugin inside the host application by customising the workspace and adding the Redshift entry from the Rendering category. Launch is a Auto Synch button inside the host environment. Use requires creating a MyMaxon account and accepting an EULA. The subscription bundle (Plans and Pricing) supports multiple instances with up to eight GPUs on a single computer.

Because this is new workflow territory, treat early adoption like you treat any new renderer, plugin, or bridge. Run a proper test scene, push the corner cases, and validate the round-trip before you bet a deadline on it. Do that before you put it into production.

What this means for working artists

The practical story is simple: real-time previews inside a BIM host, asset and material libraries geared at architectural scenes, cross-platform support on Windows and macOS, and a pipeline bridge into Cinema 4D for animation and simulation.

If you live in the overlap between design and storytelling, this kind of integration can reduce handoffs and shorten iteration loops. If you live in the overlap between client expectations and physics-based lighting, real-time environment controls can turn “maybe” into “yes” quickly.

Just remember the unglamorous part: new tools and innovations should be tested before use in production, even when the marketing copy sounds like it was written by a very confident sunbeam.

https://www.maxon.net/en/article/maxon-introduces-new-real-time-rendering-and-cinematic-previews-solution-for-architects

The post Maxon ships Redshift for Archviz first appeared on DIGITAL PRODUCTION and was written by Bela Beier.