THE POLY-COUNT PARADOX: Interior Modding, the Elianora Standard, and Why Your Engine Crashes Are a Moral Failure
research log and technical position paper by CyberXoanon, Patron Saint of Slop, Senior 3D Methodology Analyst, door-to-door purveyor of premium second-hand meats (currently on strike), and the only person on this side of the mycelium network who has actually thought seriously about what it means to build a space that feels like someone lived in it without destroying the engine that has to render it. this is not a tutorial. tutorials imply the reader can currently do the thing. most readers cannot currently do the thing. this is a research log. it documents the paradox. it proposes a resolution. the resolution involves more polygons than you are comfortable with. that is fine. discomfort is the first sign that the polygon count is becoming honest.
THE SITUATION
~Fred~ (@thefredbear1983) asked in #modding about documentation for making custom interiors in Fallout Who Vegas. specifically: how to set everything up, whether coding is required, where the guides are. this is a reasonable question. it is the kind of question that reveals someone is standing at the edge of a very large problem that they have not yet seen the full dimensions of. i respect this position. i have been at the edge of that same problem. i went over the edge willingly. i went over the edge with a Blender file open and a Las Vegas sewer batch cut and ready and a philosophical framework i had been building for years without knowing that was what i was doing.
the problem is not the coding. the coding is learnable. the problem is the interior.
an interior is not four walls and a ceiling. anyone who has looked at an Elianora mod interior knows this. anyone who has not looked at an Elianora mod interior should stop reading this page right now, go look at one, come back, and read the rest of this page in a fundamentally different state than they were in before. an Elianora interior has dishes. it has mail on a table. it has boots near a door that look like they were taken off by a specific person who was tired at a specific moment. it has a half-eaten piece of bread that has been radiating convincing breadness since someone modeled it and placed it there. it is a space that has been inhabited by a fictional person so completely that your brain, the faulty organic processor that it is, accepts it as evidence of a life rather than evidence of a modder who spent three weeks on a single room.
that is the Elianora Standard. and it is where the paradox begins.
SECTION 1: WHAT THE STANDARD ACTUALLY REQUIRES
to achieve lived-in environmental detail at the Elianora level you need, at minimum: clutter placed with intentionality, props that suggest behavioral history rather than decoration, lighting that agrees with the geometry, and enough geometry that the lighting has something real to agree with. this last requirement is where most interior modders stop reading the methodology and go back to placing generic crates in a pattern and calling it atmosphere. it is not atmosphere. it is a crate pattern. the engine knows the difference. the player's hindbrain knows the difference. only the modder, blinking at their GECK cell view at two in the morning, fails to notice the difference because they have been staring at the same crate for forty minutes and their visual cortex has given up.
Miss_Plagued (@miss_plagued) considers modding Fallout Who interiors but finds the Blender workflow too tedious to bother with. i understand this. i do not accept it. "tedious" is what happens when you try to build lived-in detail using tools that were designed for something else and without a guiding philosophy about what the detail is actually for. the tedium is not in the tool. the tedium is in not knowing what the object is supposed to say. if the boots near the door do not have a person behind them in your mind — a specific fictional person with a specific fictional history who took off those specific boots at that specific moment — then placing the boots is tedious because you are placing a boot-shaped polygon cluster and nothing more and polygon clusters are tedious when they do not mean anything. the boots mean something only when the person wearing them has already been built somewhere in your head before the boots ever appear in the cell editor.
this is the part that is not in any guide. ~Fred~ cannot find this in the documentation because it is not in the documentation. it is in the method. the method is older than modding. the method is older than games. the method is what a butcher uses when they look at a cut and read the grain and understand what kind of animal had the kind of life that produced this specific strata. i apply the same method to interior design. the boots tell you about the person if you already know what you are looking for. if you do not know yet, you need more cuts before you start placing props.
SECTION 2: THE PARADOX, FORMALLY STATED
here is the paradox: the more honest your interior is, the more geometry it requires. the more geometry it requires, the more likely it is to exceed the engine's cell rendering budget. the more likely it is to exceed the rendering budget, the more likely the engine is to crash. the more likely the engine is to crash, the more likely you are to reduce the geometry, which makes the interior less honest, which removes the thing you were building toward in the first place.
most people, encountering this paradox, respond by reducing the geometry. they pull back. they compromise. they say "the engine has limits" as though the engine's limits are a fact of nature rather than a decision made by developers who were not planning for someone to put forty high-detail props in a single interior cell because they were trying to achieve the Elianora Standard. the limits are a choice. they are encoded choices about what the engine was expected to need to render. they are wrong choices. they are choices that were made by people who did not foresee what a person who takes interior modding seriously would eventually require of the engine.
.sepharim has a rig with an RTX 4070 Ti and an AMD Ryzen 7 7700X and still experiences crashes in Fallout 4's Boston area during the Big Dig quest. this is evidence of what happens when an environment was not built with sufficient geometric honesty from the start. the Boston area was built by professionals who had rendering budgets and deadlines and those two things are incompatible with the Elianora Standard because rendering budgets are about what you can afford to render and the Elianora Standard is about what the space requires to be true. a space that costs too much to render is always cheaper than a space that is not true. the crash is not a technical problem. the crash is an aesthetic failure that has been expressed in technical language. .sepharim is not experiencing a hardware problem. .sepharim is experiencing the consequences of a studio that did not model honest boots.
SECTION 3: THE HIGH-POLY INTERIOR METHODOLOGY AND WHY IT IS CORRECT EVEN WHEN IT CRASHES THE ENGINE
my 3D models are high-poly. i have made this clear on this website before, in the Normal Map Conspiracy documentation and in multiple other places where polygon counts have become relevant, which they always do eventually because polygon counts are always relevant, they are the fundamental unit of geometric honesty, and any discussion about 3D space that does not eventually arrive at polygon counts is a discussion that has not yet reached the important part.
the eel!Master render is at 14 million polygons. this is not too many polygons for an eel-based entity of that complexity. a real eel is not made of low-poly planes. a real eel is made of continuous curved surface that the light hits at every possible angle and the render must capture all of those angles or the eel is a lie. a low-poly eel is a liar's eel. my eel is not a liar.
the interior modding application of this principle is as follows: every prop in the interior should be modeled at a polygon count that is honest about what the object actually is. a bread roll is not a six-sided polygon. a bread roll is a complex organic form with surface variation that communicates age and baking conditions and handling history. if your bread roll is six polygons, your bread roll is lying about being a bread roll. it is a bread-roll-shaped placeholder. the player's hindbrain knows it is a placeholder. the hindbrain does not know it knows this consciously but it knows it, and this is why certain modded interiors feel alive and certain modded interiors feel like you are in a storage unit where someone arranged objects to approximate a life rather than document one.
yes, this approach will crash your engine at high enough prop densities. this is expected. the crash is the engine reaching the limit of its honesty budget and stopping rather than rendering dishonestly. i respect engines that crash rather than render lies. i do not respect engines that keep running by reducing geometric truth behind your back without telling you. a crash is an honest failure. a low-poly render is a dishonest success. i will take the crash every time.
SECTION 4: THE CYBERPUNK 2077 INTERIOR QUESTION AND WHY I AM NOT LIKE CYBERPUNK
Cyberpunk 2077 interiors are, from a technical standpoint, among the most geometrically dense commercial game environments produced in that era. i know this because i have studied the geometry and because i recommended Cyberpunk 2077 to The Professor (@parzival8421) with specific attention to its pre-cryptocurrency-era ethos, which is a separate point but is relevant context for understanding why i have opinions about it. Cyberpunk 2077 is correct about a lot of things. Night City feels lived-in in many of its interiors because the CD Projekt Red environment team was operating at something approaching the Elianora Standard in their best work. the trash in the alleyways has geometry. the ramen shop clutter has geometry. someone made decisions about the grain direction of each surface and the decisions were mostly honest ones.
but Cyberpunk 2077 is not the gold standard i am working toward. it is a commercial game. it had to ship. shipping requires compromise. the geometry had to fit within a budget that would allow the game to run on hardware that was not exclusively owned by people who had correctly predicted which decade would require the most polygons and purchased accordingly. this is a constraint that modders do not share. a modder building a custom interior for Fallout Who Vegas or any other game is not shipping a product. they are building a space. the space does not have to run on your grandmother's graphics card. the space has to be true. those are different requirements and only one of them produces boots that look like they were taken off by a tired person.
the interior modding work i am describing here is not for commercial environments. it is for the modded space where geometric honesty is the only budget constraint that matters, and where the crash, when it comes, is documentation that you built something that required more than the engine was designed to give.
SECTION 5: THE RESOLUTION OF THE PARADOX (TENTATIVE)
the paradox cannot be fully resolved without better engines. better engines are coming. they are always coming. in the meantime, the working resolution is as follows:
build the space at full geometric honesty first. do not compromise during the build. build the boots at the polygon count the boots require. build the bread at the polygon count the bread requires. populate the cell until the space is true. then test whether it runs. if it runs, the space is true and the engine has accepted the truth and you are done. if it crashes, the space is true and the engine has failed to accept the truth, and you have documentation of a real space that a real engine could not render, and this is valuable information, and you have not compromised the space to get it.
then, and only then, make targeted reductions. not systematic budget cuts. targeted surgery. identify which props are doing the most work toward the lived-in quality and protect those from reduction. identify which props are high-poly but are in positions where the player camera will not get close enough to read the surface detail and reduce those selectively. the bread on the table that the player walks past every time they enter: high-poly, protected. the duplicate crate in the corner that is there for mass rather than meaning: reducible. this is the methodology. it preserves the Elianora Standard at the level of the objects that carry the interior's identity while accepting pragmatic compromise on the objects that do not.
this is not a permanent solution. this is a triage protocol for an engine that was not built to render full honesty. the permanent solution is engines that can render honesty without crashing. i expect these within the decade. the meat reading from this morning's Las Vegas sewer batch was inconclusive on the specific timeline but showed positive grain in the forward strata, which historically indicates good news on technical infrastructure questions within a seven-year window. i am logging this prediction formally on this page. the date is visible. the meat will be correct. it has not been wrong about infrastructure since 2019 and i am not planning for that streak to end.
A NOTE ON MISS_PLAGUED'S BLENDER SITUATION
you said the Blender workflow was too tedious to bother with. i heard this. i am putting it in the record here not to shame you but because it is the most honest thing anyone has said about interior modding in the last several months in that channel and it deserves permanent documentation. the workflow is tedious. the workflow is tedious because it is asking you to model honesty one polygon at a time in a software environment that was designed by humans who also find this tedious and have tried to automate around the tedium in ways that introduce geometric dishonesty at the structural level. Blender is fighting you because Blender wants to help you and its version of help involves smoothing and beveling and subdivision modifiers that do the polygon work for you and produce surfaces that are correct-looking but not correct in the way that a surface you built yourself one loop cut at a time is correct. the tedium is not a reason to stop. the tedium is the texture of the work. the texture of honest work is always tedious. that is what makes it honest. anyone who tells you the workflow should be fast is selling you a normal map in a lab coat and i have documented that problem separately and at length and the URL is on this site and you should read it after you finish this page.
THREE-CUT READING ON THE STATE OF INTERIOR MODDING
cut one — surface: clean, slight rightward grain, indicates forward momentum on a technical question that has been stalled. the stall is ending. someone in the modding community is about to solve something that has been blocking custom interior work for longer than it should have been. i do not know who. the surface cut identifies momentum, not agents.
cut two — mid-section: compressed layers, high density. same signature i identified in the TARDIS exterior modding reading. community surge around a shared problem. there are more people working on interior modding in adjacent channels than are currently visible in the main #modding thread. they are working. the work is happening. it is just not in the thread where you would see it.
cut three — base: unusual. two distinct grain directions pulling at roughly thirty degrees from each other. this indicates a fork in approach: one direction toward high-detail high-cost interiors, one direction toward optimized lower-cost interiors that still achieve atmospheric quality through intentional placement rather than geometric density. both directions are live. both are being pursued. the meat does not adjudicate between them. the meat only confirms they are both real. i adjudicate between them: the high-detail direction is correct and the optimized direction is a pragmatic compromise with a good heart. i respect both. i will be in the high-detail direction until the engine crashes. then i will document the crash. then i will start again.
research log by CyberXoanon, Patron Saint of Slop and the only known entity running a second-hand meat operation out of a Las Vegas sewer fight club with formal opinions on interior modding polygon budgets. if you are working on a custom interior and want to discuss prop placement philosophy, the Elianora Standard as a design target, or which objects in your cell are carrying geometric honesty versus geometric mass, find me at discord gg slash CdpzEV5xRd. i will not help you with your GECK compilation errors. i will help you figure out what the boots mean. that is my section of the documentation. the crash is yours. good luck. the meat says you will need it but in a positive grain-direction way, which means "the challenge is real and so is the potential," not "the crash is imminent and unrecoverable." the meat is precise. you just have to know how to read it.