If you have tried to get a game-ready building out of a generative tool, you already know the failure modes: broken topology, unusable scale, missing UVs. A 2026 walkthrough from Smart Poly argues GPT-6 Astra cleared that bar for an airport built inside Blender, then fed the same scene into Higgsfield AI to produce a cinematic render.
This article breaks down the exact setup order, the timeline of the generation, the export path into Unreal Engine 5, and where the result still fell short.
What the GPT-6 Astra Blender workflow actually does
The test had three stages:
- GPT-6 Astra builds a complete airport terminal environment inside Blender from a reference image and a text prompt.
- The mesh is joined, exported as FBX, and imported into Unreal Engine 5 as a playable level.
- The same Blender scene is turned into a 30-second previz animation, rendered as MP4, and sent to Higgsfield AI with the Seedance 2.5 model to become a photorealistic cinematic.
The prompt used in the creator's 2026 test was specific about the end goal: "Using the provided reference image, create a complete game-ready 3D airport terminal environment inside of Blender, import in this model be exported to Unreal Engine 5 and use it as an actual playable environment."
That wording matters. Asking for "game-ready" and naming the target engine tells the tool to keep polygon counts and geometry complexity inside a realistic budget, rather than producing a dense offline-render mesh.
Setting up Blender and the Higgsfield plugin
You need Blender, the free open-source 3D creation suite, and the Higgsfield Blender add-on before the workflow starts. The add-on installs through Blender's Edit menu under Preferences, then Add-ons, using the Install from Disk option and the downloaded plugin file.
After installation a chat panel appears inside Blender and prompts you to sign in to your Higgsfield account. Only once that panel is authenticated does the GPT-6 Astra mode become selectable in the add-on's mode dropdown.
The creator's setup order was specific and worth copying:
- Install Blender from blender.org.
- Download the Higgsfield Blender plugin file.
- Open Edit > Preferences > Add-ons, click the install-from-disk icon, and select the plugin file.
- Log in to the Higgsfield account from the chat panel that appears.
- Set the add-on mode dropdown to GPT-6 Astra.
- Load the airport reference image from Downloads.
- Paste the prompt describing the game-ready terminal environment for Unreal Engine 5.
The reference image is not decoration. Astra used the photo as the shape target, so the terminals, roof line and tarmac layout follow the reference rather than an invented airport plan. If you skip this step, the tool still generates a terminal, but you lose control over the silhouette you get.
How the 18-minute generation progressed
Generation advanced in observable stages rather than appearing all at once. The airport blockout reached its basic three-terminal shape in about two minutes, still without materials or fine detail. By the five-minute mark, terminal details had appeared: windows on the walkway tubes and skylight windows on the roof. At the seven-minute mark it added the tarmac paintings, the runway lines visible in the reference image. It finished at roughly 18 minutes with materials applied.
The creator describes the sequence as a series of visible additions over roughly 18 minutes. This staging matters because it tells you the tool is doing incremental scene construction rather than one-shot mesh synthesis.
The creator's timeline:
| Time | What appeared |
|---|---|
| ~2 minutes | Three-terminal blockout, basic shape, first windows with glass material |
| ~5 minutes | Terminal details, walkway windows, roof skylights |
| ~7 minutes | Tarmac paintings and runway markings |
| ~18 minutes | Final materials applied, model complete |
One detail the creator flagged as unexpected: interior content was never requested, yet the finished model contained seating, interior lights and staircases inside the terminal. That is useful if you plan to shoot interior camera angles, but it also means you cannot assume the tool will stop at what you asked for. Extra geometry costs triangles, and it has to be either used or deleted.
The mesh statistics and what 45,000 triangles means
After generation, the creator selected all objects and joined them with Ctrl+A followed by Object Join, collapsing the scene into a single mesh. The joined model measured roughly 45,000 triangles.
That figure is the one worth arguing about. The creator calls it "pretty well game optimized," and there is a useful comparison in the video: characters usually run over 100,000 triangles. A building at 45,000 triangles, with windows, roof details, gates, skylights, air conditioning units on the roof and a furnished interior, sits comfortably below the budget a single hero character would consume.
The wireframe view shows why the count stays low. Geometry is simplified rather than dense, which is exactly what you want when the mesh will be lit in real time rather than rendered offline.
Treat 45,000 as a creator measurement from a single test, not an independent audit. The count changes the moment you add your own details, merge it with other assets, or run a decimation pass.
Exporting to Unreal Engine 5 and assembling the level
The export path is short:
- Select all objects in Blender.
- Join them into one mesh with Ctrl+A > Object Join.
- Use File > Export and save the model as an FBX file.
- Drag the FBX into an Unreal Engine 5 level.
- Replace the Blender materials with engine-side materials.
- Add airplane assets from a free asset pack.
- Press Play to run the level.
The creator used the City Sample project as the starting point because it ships with a large set of free materials. Window glass, tarmac, runway paint, and rooftop textures were all swapped for the Unreal versions. The tarmac material in particular produced puddles and reflections that the Blender version did not have, which is the single biggest jump in perceived realism in the whole workflow.
Free airplane models were dragged in to complete the scene, then the level was play-tested with the camera running through it on foot and from a bird's-eye view above the roof. It worked as a playable environment.
![N/A]
Turning the same scene into a cinematic with Seedance 2.5
The Higgsfield plugin does a second job beyond modelling: GPT-6 Astra set up cinematic camera shots over the finished airport for a previz render. The creator set the timeline to about 30 seconds and let the tool place the camera angles and movements.
That camera pass took roughly seven minutes. The creator notes you can include the render settings in the prompt if you do not want to configure them manually, which saves a step.
Rendering the previz out:
- Open the render settings and set resolution to 1080p.
- Set the frame rate to 30 FPS.
- Choose an output location for the MP4.
- Use the View menu and select Render Playblast to write out the animation sequence Astra created.
Then, on the Higgsfield AI website:
- Open the video tab and upload the MP4 previz.
- Write the prompt: generate a photorealistic cinematic airport sequence using the provided Blender animation, keeping the same camera animation and airport shape while adding lighting, ray tracing and detail absent from the Blender scene.
- Select Seedance 2.5 as the video model. Other models are available.
- Set the timeline length to 30 seconds and choose the resolution.
- Generate.
The finished render kept the exact camera angles and movement from Blender, which is the point of the whole exercise. You keep full control of the shot list and the video model handles lighting, clouds, background city detail, window reflections, and even matching audio such as airplane sounds. The output included a pan-out shot revealing the city skyline, the air traffic control tower, and a bus driving across the apron.
If you are comparing this to stack-based tools, the same idea of chaining a generator to a finishing stage shows up in the crazystack.com.br collection of engine and asset resources.
Does it hold up as a game asset?
Yes, with corrections. The creator names two problems himself.
First, the terminal gates did not line up with the aircraft doors. That is a placement and scale issue, not a topology failure, and it needs a manual pass or a follow-up Astra prompt to fix.
Second, the Blender materials were not good enough on their own. The asset only looked convincing after engine-side material replacement in Unreal Engine 5.
Neither flaw makes the mesh useless. Both mean you should budget correction time after a generation, the same way you would after any automated blockout.
If you work in Unreal Engine 5 and you have watched material from a channel like Dev Doido do canal do youtube, the pattern will look familiar: get geometry into the engine fast, then spend your hours on materials and lighting where the visual return is highest.
Where this workflow helps most
The strongest use case shown is not finished art. It is the early stage where a level needs a plausible building silhouette, correct rough scale, and interior volumes before anyone commits time to it. An 18-minute blockout at roughly 45,000 triangles fits that stage well.
It also suits city-scale work. The creator had already produced an apartment complex in a previous test and the airport in this one, and closes by saying he wants to try generating an entire city with the same method. Buildings are a good fit for this kind of generation because they are geometric, they repeat, and they can tolerate simplified topology in exchange for speed.
It suits less well when the asset has to interact precisely with other geometry. Gate-to-door alignment is the example in this video, and the same problem would appear with docking bays, modular kits, or anything that has to snap to something else.
Step-by-step workflow summary
| Stage | Tool | Time | Output |
|---|---|---|---|
| Blockout and modelling | GPT-6 Astra in Blender | ~18 minutes | Three-terminal airport, ~45,000 triangles |
| Camera previz | GPT-6 Astra in Blender | ~7 minutes | 30-second camera animation |
| Previz render | Blender Render Playblast | Not stated | 1080p, 30 FPS MP4 |
| Engine assembly | Unreal Engine 5 | Not stated | Playable level with replaced materials |
| Cinematic render | Higgsfield AI, Seedance 2.5 | Not stated | 30-second photorealistic video |
FAQ
Is the GPT-6 Astra Blender airport actually game-ready?
The creator measured roughly 45,000 triangles after joining the meshes and called it game-optimised, and the mesh ran as a playable level in Unreal Engine 5. That is a creator measurement, not an independent audit. Terminal gates did not align with aircraft doors and would need a correction pass.
How long did GPT-6 Astra take to build the airport?
The blockout reached its basic three-terminal shape in about two minutes, terminal and roof detail appeared around the five-minute mark, tarmac markings around seven minutes, and the creator reported completion at roughly 18 minutes. Camera setup for the cinematic previz took a further seven minutes.
Do I need Blender to use the Higgsfield plugin?
Yes. The workflow runs inside Blender, which is free and open source, and the Higgsfield add-on is installed through Blender's Add-ons panel using Install from Disk. A Higgsfield account login is required before the GPT-6 Astra mode becomes available.
Which video model rendered the cinematic?
The creator selected Seedance 2.5 on the Higgsfield website and set a 30-second timeline. The input was a 1080p, 30 FPS MP4 of the Blender previz rendered with Render Playblast, and the prompt asked to keep the original camera animation while adding lighting and photorealistic detail.
Does this replace a level artist?
No. The output needed material replacement inside Unreal Engine 5, a gate-alignment fix, and manual scene assembly with airplane assets. Generation handled the blockout and the camera pass; the parts that made it look finished were engine-side materials and human decisions.
Why did the model add interior details nobody asked for?
The prompt requested a complete terminal environment, so Astra filled in interiors, seating, lights and staircases on its own. Useful if you want interior shots, but the extra geometry still counts toward the triangle total and has to be kept or deleted deliberately.
What prompt structure got the best result?
The creator combined a reference image with a prompt that named the deliverable, the target engine and the intended use. That combination, rather than the prompt text alone, is what pushed the output toward simplified, exportable geometry.
Can I use a different video model than Seedance 2.5?
Yes. The creator notes on the Higgsfield video tab that you can select whichever model you prefer; Seedance 2.5 is simply the one used in this test. Timeline length and resolution are set independently of the model choice.
Is the FBX export step required?
Yes, if the goal is Unreal Engine 5. Joining the meshes with Ctrl+A and Object Join before exporting keeps the asset as a single manageable object and is also what made the 45,000-triangle count measurable in the first place.
Turning a build like this into written documentation
An 18-minute generation session and a seven-minute camera pass are easy to watch and hard to reproduce from memory. The prompt text, the setup order, the failure at the terminal gates, and the material swap inside Unreal Engine 5 are the parts other artists actually need, and they live in spoken narration.
Skala Blog turns a video like this into a written article: paste the YouTube URL, let it transcribe, and generate a structured draft from what was said.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits