Backdrop
A blog conceived, directed and written by Gianluca Scattarella
Everything you watch and play was built by someone, on a budget, against a deadline.
Games, film, anime, 3D and the hardware underneath — read from the production side. What a decision cost, and who paid for it.
More from the blog
Browse by section
The Monday column. One argument a week about how games, film and 3D work get made, and what the industry is doing to the people making it.
Environment art, shading, rigging and the pipelines around them — Blender, Unreal, Substance, Marvelous Designer and Houdini, read from inside the job rather than from the release notes.
Hardware for people who render: GPUs, displays, workstations and the specifications that turn out to mean something different once the thing is on a desk.
Generative tools where they touch a working pipeline — what they take off an artist’s plate, what they quietly add to it, and which claims survive contact with a deadline.
Game reviews with a score, plus the craft behind them: what a design decision cost the team that built it, and why a game looks and runs the way it does.
Manga and anime, with attention to how the pages and the frames were made — adaptation choices, studio production, and the drawing itself.
Visual effects, virtual production and the shots people replay. What was practical, what was rendered, and what it took to make the seam invisible.
Advertising / PartnershipsWork with the blogDetailsClose
This is a working 3D environment and technical artist writing for other people who make things — environment and technical artists, indie and mid-size studio teams, virtual production crews, and the hardware-curious end of the games audience. Coverage runs across games, real-time graphics, hardware, AI tooling, film and TV production, and manga, with the same question underneath all of it: what did this cost to build?
Review units and hands-on
Hardware, software licences and early builds. GPUs, workstations, displays, capture and scanning kit, DCC and render tooling. I cover what I can put through real production work rather than a spec sheet.
Tool and pipeline coverage
If you build something artists use — a renderer, a plugin, an asset pipeline, a scanning workflow — I am interested in what it changes about the job, not the feature list. That tends to make a more useful piece than a launch post.
Sponsorship and placement
Section sponsorship and banner placement on the blog. I will tell you which pieces perform and which do not, because the alternative is you finding out on your own and not coming back.
How I handle it
- Anything gifted, loaned or paid for is disclosed in the piece itself.
- Sponsored and affiliate links carry rel="sponsored". I do not sell link insertions into existing articles, and I do not publish guest posts written to place a link — that is against Google’s policies and it would damage the site faster than it would pay for itself.
- Editorial control stays with me. You get the coverage, not the verdict, and I will say so up front if the answer is going to be unflattering.
- Review units get returned or disclosed as kept, whichever you prefer.






















































































































































