You did the audit. You ran the Auto-Fit tests. You bought the skin textures. You followed the step-by-step migration guide and did not rush it. And yet something is still off. Your G9 renders are not bad, exactly — but they do not feel as dialled-in as your G8 work did after the same amount of time. The skin looks slightly wrong in a way you cannot name. A lighting rig that always worked on G8 is doing something weird at the ears. An expression that looked great in the viewport is reading flat in the final render. If any of this sounds familiar, this article is the one you needed six months ago. It covers the specific problems that show up after you have done everything right — the Iray settings that behave differently than you expect, the mistakes that eat weeks without announcing themselves as mistakes, and the moment when you realise your hybrid workflow has quietly become your permanent workflow instead of a transition. If you have not done the migration prep yet and are still trying to figure out whether switching is even worth it, the honest breakdown of what the switch actually costs is probably a better starting point. This article assumes you are already mid-migration and something is not adding up. If you want someone to look at your specific setup and tell you what is going wrong, reach out and let us dig into it with you — mid-migration is exactly when outside perspective saves the most time.
Your Iray Settings Are Lying to You
Here is the thing nobody puts in the migration tutorials: G8 and G9 do not respond to Iray the same way. The mesh is different, the default material setup is different, and the skin shader assumptions are different. If you are loading your saved G8 lighting presets and your G8 custom skin shaders and expecting them to land the same way on a G9 character, they will not. The result is usually not obviously wrong — it is just slightly off in ways that are hard to locate. That is the annoying part. Something clearly needs adjusting but nothing specifically looks broken.
The wax problem
If your G9 skin looks slightly too smooth — almost plastic, a bit waxy — the subsurface scattering radius is almost certainly running too high. G9’s mesh topology is denser than G8’s in key areas, and SSS radius values calibrated for G8 geometry tend to overdo it on G9. The skin ends up looking like it is lit from inside rather than lit from outside and translucent where it should be. The fix is not complicated: reduce the SSS radius values in the Iray Uber shader, usually by 20 to 30 percent as a starting point, then adjust from there with preview renders. Do this before anything else when G9 skin looks wrong. It solves the issue about 70 percent of the time.
The glowing ears problem
This one gets people because the symptom looks like a lighting problem, so that is where they start troubleshooting. They spend an afternoon adjusting rim lights and HDRI values when the actual issue is in the skin material. G9’s translucency response to back and rim lighting is more pronounced than G8’s at default values. Strong rim lighting produces an almost radioactive glow at the ears, nose bridge, and fingertips that reads as unrealistic rather than dramatic. Before touching the lights, open the surface settings for the skin and reduce the Translucency Weight value. Start at around 0.6 and render a quick preview. If that is the fix — and it usually is — you will know within a few minutes and can calibrate from there rather than rebuilding your whole lighting setup.
Why expressions look flat in final renders
This one is subtle and it took a while for people to figure out what was causing it. In G9, strong expression morphs interact with the skin shader in a way that produces a more natural deformation response — skin stretching and compressing across expressions more convincingly than G8 managed. The catch is that this only happens with natively built G9 skin presets, not with converted G8 materials or generic Iray Uber setups. If you applied a G9 expression morph and the skin around the eyes or mouth looks strangely flat or plasticky while the rest of the face is fine, the material is not set up to respond to deformation correctly. Swapping to a properly built G9 skin preset — not just a converted one — typically fixes this immediately and visibly.
The Mistakes That Do Not Look Like Mistakes
The migration prep mistakes are easy to name and easy to avoid once you know about them. The mid-migration mistakes are harder because they do not announce themselves. You are not doing anything obviously wrong. You are just making decisions that quietly compound into a workflow that is slower and more frustrating than it needs to be.
The speculative shopping spiral
You have a Rebuild list with thirty items on it. The correct move is to work from the top — the five or six things your renders actually depend on right now — and buy those. What happens instead, very often, is that an artist sees a G9 sale, or spots something that would be useful eventually, and starts buying across the list without order. Three months later they have forty G9 assets and none of them are the specific skin set or outfit category they needed most. The G9 side of the library is wide and decorative rather than functional and deep. Nothing on the Rebuild list has actually been resolved. If you recognise this pattern in yourself, stop buying anything G9 for a month and spend that time actually rendering with what you have. The gaps that genuinely hurt your work will make themselves obvious quickly. Buy those first.
Trying to rebuild G8 characters in G9
This one is responsible for more lost hours than any Iray setting. An artist has a character they spent months developing on G8 — a specific morph combination, a skin they love, a face that reads immediately as that character. They decide to port her to G9. The morph architecture is different. The skin does not transfer cleanly. The expressions that defined her personality do not exist on G9’s rig. They spend weeks trying to get close and end up with something that is almost right, which is more frustrating than something clearly different. The actual answer is that established G8 characters live on G8. They are not broken. They are not obsolete. They are G8 characters, and G8 scenes are where they belong. G9 is for new characters who are built natively for the platform. Accepting this distinction is not giving up — it is what separates a functional hybrid workflow from a stalled one.
Feeling guilty about still buying G8 content
Nobody talks about this one because it sounds irrational, but it happens all the time. An artist has mentally committed to G9 and starts feeling like continuing to buy G8 assets is some kind of backsliding. So they stop — even when a project clearly needs a G8 asset that has no G9 equivalent. The result is that they either use something inferior on G9 or they stall the project waiting for a G9 version that may not arrive for months. There is nothing wrong with buying G8 content in 2026. The platform is not dead. The ecosystem is still being served by vendors who know their audience has not fully migrated. If a G8 asset serves your current project better than anything available in G9, buy it. Your renders do not care about your migration timeline.
When the Hybrid Workflow Stops Being Temporary
Most migration guides — including the one this article follows on from — frame the hybrid workflow as a transitional state with a clear endpoint. In practice, for a lot of artists, the hybrid workflow does not end. It just changes shape. G9 becomes the default for new work. G8 becomes the platform for maintaining existing character series and using the deep legacy library that G9 has not yet replicated. That is not a failed migration. That is a mature multi-platform workflow, and it is what most professional DAZ artists actually run. The mistake is treating it as a problem to be solved rather than a configuration to be managed.
How to tell if your hybrid phase has actually ended
Three signals that G9 has genuinely become your primary platform. First: when you start a new project, you do not think about which generation to use — G9 is just the default and you only reach for G8 when a specific asset requires it. Second: the items still missing from your G9 toolkit are occasional-use things, not core render needs. Third: when something goes wrong in a G9 scene, your first instinct is to solve it in G9 rather than falling back to G8 as the easier path. That instinct shift takes time. It cannot be forced. When it happens naturally, the hybrid phase is over.
What G8 looks like in the workflow after that
G8 does not get uninstalled. It becomes your archive platform — the place where existing character series live out their natural lifespan, where your legacy library remains available for background characters and crowd work, where you can still pull a specific outfit or prop that has no G9 equivalent. The library you built over years did not become worthless. It became specialised. That reframe matters because artists who think of their G8 library as a burden they need to eventually escape tend to make worse decisions during the transition than artists who think of it as a complementary resource with a different scope.
Where G9 Actually Earns Its Price
After months of working through the problems, there are places where G9 is genuinely and noticeably better — not just technically superior in a way that only matters in benchmark comparisons, but actually visible in the renders you are making and the time it takes to make them.
Shoulder and elbow deformation at extreme angles is the most practically useful improvement for anyone who does action poses or dynamic scenes. G8 required constant manual correction at high joint angles — the geometry at the shoulder would collapse in ways that looked wrong and needed to be hidden by camera angle or clothing. G9 handles this substantially better at the base rig level. You still need to check your poses, but you are correcting less often and less severely. For artists who do a lot of posed action work, this alone justifies the migration cost over time.
Close portrait work with HD morphs active is the other area where the improvement is hard to argue with. G9’s HD detail at maximum resolution — fine skin texture, pore structure, the subtle surface irregularities that separate a convincing face from a polished one — is ahead of what G8 could produce at equivalent settings. If portrait rendering is your primary output and you have not invested in G9 HD morphs yet, that is the single highest-return purchase you can make right now. The skin and character collections have a growing number of G9-native options in this category specifically.
Mid-Migration Reality Check: G8 vs G9 By Render Type
The standard G8-versus-G9 comparison tables focus on features. This one focuses on what actually happens when you render specific types of scenes on each platform, based on where artists consistently report the most friction and the most satisfaction.
| Render Type | G8 Mid-Migration Reality | G9 Mid-Migration Reality | Honest Recommendation |
|---|---|---|---|
| Close portrait, hero character | Still excellent if your G8 skin library is strong | Better HD detail ceiling; skin shader calibration needed first | Invest in native G9 skin + HD morphs — payoff is real |
| Action pose, dynamic scene | Shoulder and elbow correction still required at extremes | Noticeably cleaner at high joint angles out of the box | G9 wins clearly here; worth migrating action-first artists |
| Large scene, crowd, background characters | Deep asset library; fast to set up familiar characters | Thinner catalog for background types; still catching up | Keep using G8 for crowd work — no quality penalty at distance |
| dForce clothing simulation | Mature preset library; community-tested settings available | Works well but fewer shared presets; more trial and error | G8 still easier for complex dForce scenes during transition |
| Fantasy and period costume | Enormous catalog depth in niche categories | Getting better; still thin in specialist historical and fantasy | Check G9 availability per category before committing |
| Non-binary or gender-fluid character | Workable but awkward; requires manual blending between bases | Unified base handles this natively and cleanly | G9 is the correct platform for this work, full stop |
| Existing character series continuation | No friction — your library is already there | Rebuilding character consistency is time-consuming | Finish existing series on G8; start new series on G9 |
Questions That Come Up Around Month Three
My G9 skin looks fine in the viewport but wrong in the final Iray render. What is happening?
The viewport and the Iray renderer handle subsurface scattering and translucency differently. What looks balanced in the OpenGL viewport preview often renders with oversaturated SSS or excessive translucency in Iray, because the preview is approximating those effects rather than calculating them. Always judge G9 skin by quick low-sample Iray renders, not the viewport. Set up a simple portrait lighting scene specifically for skin calibration and use it every time you introduce a new skin set.
I converted a dForce outfit to G9 and the simulation is completely gone. Is there any way to recover it?
Not directly — the dForce simulation parameters do not carry over through Auto-Fit, so what you have is a static mesh in the shape of the outfit. You have two options. You can add a new dForce modifier to the converted mesh and configure the simulation settings from scratch, which gives you control but takes time and requires some dForce knowledge. Or you can look for a native G9 version of the outfit from the same vendor, which will have simulation settings already built in. For complex multi-layer outfits, the native G9 version is almost always faster than rebuilding from the converted mesh.
I tried porting my favourite G8 character to G9 and something is always slightly off. Should I keep trying?
Probably not. The morph architecture and UV layout differences between generations mean that a character designed for G8 will always have compromises when forced onto G9. The specific things that made that character feel like themselves — a particular combination of subtle morphs, a skin texture calibrated for G8’s UV — do not transfer cleanly. The better use of that effort is building a new G9 character with similar design intent from scratch on native G9 assets. Let the G8 version keep existing as a G8 character. It is not failing the migration if you just leave her where she works.
I have been in hybrid mode for eight months and it does not feel like it is moving toward G9 becoming primary. Is that a problem?
Only if it is causing friction. If you are working productively and your renders are where you want them, the pace of the transition is irrelevant. The hybrid workflow is not a failure state — it is a completely legitimate configuration for artists with large G8 libraries and specific content niches that G9 has not yet fully served. If it is causing friction — constantly managing two content systems, rebuilding the same things twice, feeling like you are stuck — then the question is whether you are still missing specific G9 assets that would resolve the bottleneck, or whether the expectation of “full migration” is itself the problem.
My G9 renders take noticeably longer than equivalent G8 scenes. Is that normal?
Slightly longer can be normal — G9’s mesh is more complex in areas like the face and hands, and if you are using HD morphs with maximum detail, render times go up. But significantly longer usually points to a specific culprit rather than a general G9 overhead. The most common causes are HD morphs being active when you do not actually need them at that render distance, G9 skin shaders with SSS settings that are driving a disproportionate number of ray bounces, or an environment that was not the issue on G8 but is interacting badly with G9’s material complexity. Check those three before assuming G9 is just slower — it should not be dramatically slower for equivalent scene complexity.
Is there a point where I should just accept I am a G8 artist and stop trying to migrate?
That is a completely valid conclusion for some workflows and some artists. G8 is not going away. The ecosystem is mature, deep, and still actively served by vendors. If the specific improvements G9 offers — HD detail at portrait distance, cleaner joint deformation, unified gender base — are not relevant to what you actually make, then the migration cost never pays off. There is nothing wrong with making that call deliberately rather than drifting into a half-finished transition that is not serving you. The decision guide at the start of this series is worth revisiting with fresh eyes if you are feeling this way — sometimes the honest answer after several months of experience is different from the answer when you were just starting out.
I bought a G9 character whose skin looks completely different from the promo renders. What went wrong?
Usually one of three things. The promo renders were made with lighting that is flattering the material in a way your lighting setup is not replicating. The skin preset requires specific Iray render settings — certain numbers of samples or specific render mode settings — that your scene is not using. Or the character’s skin has tonemapping assumptions built in that interact with your post-processing in a way the vendor did not account for. Start by rendering the character with a simple three-point light setup at the vendor’s recommended settings before introducing it into your regular scenes. That tells you what the skin is actually capable of before you start blaming the asset for problems that are in the environment.
How do I know when my G9 toolkit is actually good enough to stop the rebuild phase?
When you can start a new render idea without immediately thinking about what you do not have. The rebuild phase ends when the gaps in your G9 library stop constraining your decisions — when you can respond to a creative direction by loading assets rather than by opening a store and buying something first. For most artists this happens category by category rather than all at once. Skin sorted. Core clothing sorted. Expressions still thin. Environment more than fine. The rebuild phase ending does not mean the library is complete. It means it is functional enough that the gaps are no longer driving the workflow.
If you are six months into this and something specific is still not resolving — a particular Iray problem, a category gap you cannot fill, a render quality issue you cannot trace — that is exactly the kind of specific problem worth talking through. Mid-migration troubleshooting is much faster with someone who has seen the same issues before.
Further Reading in This Series
- How to Switch From Genesis 8 to Genesis 9 Without Losing Your Entire Library — the migration prep guide this article continues from (3D Shards Blog)
- Genesis 8 vs 9: The Truth DAZ Artists Don’t Tell You — the honest cost and ecosystem breakdown (3D Shards Blog)
- Genesis 8 vs Genesis 9: Which Should DAZ Artists Use? — the decision guide at the start of the series (3D Shards Blog)
- Best DAZ Studio Assets for Beginners: What to Download First — 3D Shards Blog
- G9-native and dual-compatible asset collections — 3D Shards Store
