# GroomComponent with vVisibleInSceneCaptureOnly=false do not render in SceneCapture 

**URL:** <https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274>\
**Category:** Rendering\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [September 23, 2026, 7:15pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274 "2026-09-23T19:15:37Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [September 23, 2026, 7:15pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/1 "2026-09-23T19:15:37Z")

</div>

Hello,

I am investigating an issue where some Groom Components do not render in a Scene Capture when “bVisibleInSceneCaptureOnly=true”. The tldr is that we are not running the HairGuideInterpolation dispatch for those components. It’s only run on the main view, where groom components with “bVisibleInSceneCaptureOnly” are culled. This eventually turns into NaN in some input buffer when rendering the hair material.

My quick fix is to not skip the call to “RunHairStrandsBookmark(EHairStrandsBookmark:ProcessGuideInterpolation)” for Scene Capture views (see below). It does ensure that the groom components are correctly updated.

Is this a known issue? Is anyone aware of a potentially better / safer fix?

Thank you.

```auto
void FSceneRenderer::PreVisibilityFrameSetup(FRDGBuilder& GraphBuilder)
{
  // ...
  if (GetRendererOutput() == ERendererOutput::FinalSceneColor)
  {
    FHairStrandsBookmarkParameters Parameters;
    bool bHasHairStrandsBookmarks = false;
  		
    if (Views.Num() > 0 && !ViewFamily.EngineShowFlags.HitProxies)
    {
      CreateHairStrandsBookmarkParameters(Scene, Views, AllViews, Parameters, false /*bComputeVisibleInstances*/);
      Parameters.TransientResources = AllocateHairTransientResources(GraphBuilder, Scene, Views);
      if (Parameters.HasInstances())
      {
        if (Scene && IsHairStrandsEnabled(EHairStrandsShaderType::All, Scene->GetShaderPlatform()))
        {
          // Need GPUSkinCache results to be available in order to get correct skel. mesh data
          Scene->GetGPUSkinCacheTask().Wait();

          // 1.Update binding surfaces
          // Prepare surface data (MeshLODData)
          RunHairStrandsBookmark(GraphBuilder, EHairStrandsBookmark::ProcessBindingSurfaceUpdate, Parameters);

          // 2. Prepare surface data for guides
          // BEGIN_CHANGE - Run the Hair Guide Interpolation on the SceneCapture View as well to fix incomplete update of GroomComponents with bVisibleInSceneCaptureOnly.
          //if (Views[0].AllowGPUParticleUpdate())
          if(!Views[0].bIsPlanarReflection && !Views[0].bIsReflectionCapture)
          // END_CHANGE - Run the Hair Guide Interpolation on the SceneCapture View as well to fix incomplete update of GroomComponents with bVisibleInSceneCaptureOnly.
          {
            RunHairStrandsBookmark(GraphBuilder, EHairStrandsBookmark::ProcessGuideInterpolation, Parameters);
            bHasHairStrandsBookmarks = true;
          }

```

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [September 23, 2026, 7:15pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/2 "2026-09-23T19:15:41Z")

</div>

**Steps to Reproduce**

1. Create a new project with Metahuman support.
2. Create a Metahuman character with hair and import it into your project.
3. Place your Metahuman character in a scene.
4. Add a ScreenCaptureComponent2D and make it face the character. You should now see the character correctly rendered in the RenderTexture you created.
5. Modify the Hair Groom component to be “VisibleInSceneCaptureOnly”. Notice that the hair disappears in both the main viewport and the captured scene.  
[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![Charles](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/charles/32/924314_2.png) [@Charles](https://forums.unrealengine.com/u/Charles)\
**Post date:** [September 24, 2026, 6:44am UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/3 "2026-09-24T06:44:22Z")

</div>

Hi,

Thanks for reporting that. If you do not skip the interpolation part, I believe the issue is that, if a scene capture and a regular view run, then the interpolation will run several times, and this will cause issue down the line (invalid motion vector and else).

/Charles.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [September 28, 2026, 7:07pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/4 "2026-09-28T19:07:35Z")

</div>

Hey Charles,

Thank you for the reply. You were correct, updating the ProcessGuideInterpolation for all views fails when a hair geometry is visible in both capture and regular views.

I am now testing an alternative, which is to delay the culling of hair strands with bVisibleInSceneCaptureOnly at the end of the ProcessGuideDeformation bookmark (and before the hair strands are actually rendered):

1. Added a new flag to the FHairGroupInstance to mark instances that should only run until the HairGuide Interpolation and Deformation
2. In RunHairLODSelection(), if a hair instance with bVisibleInSceneCaptureOnly=true is hidden, do not cull it and mark it to be culled after the HairGuide Update.
3. At the end of the ProcessGuideDeformation, cull instances that were previously marked in RunHairLODSelection. The HairGuide buffer are now updated with valid information for when they’ll be rendered in the captured scene.

```auto
// GroomInstance.h
struct FHairGroupInstance : public FHairStrandsInstance
{
  // ...
  // BEGIN_CHANGE ================================
  bool bForceHairGuideUpdate = false;
  // END_CHANGE ==================================
}

```

```auto
// GroomManager.cpp
static void RunHairLODSelection(/*...*/)
{
  // ...
 
  // LOD selection & load resources
  for (FInstanceData& InstanceData : InstanceDatas)
  {
    // ...
 
    // Cull instance if it is not visible in any View
    {
      const FPrimitiveSceneProxy* Proxy = InstanceData.Instance->Debug.Proxy;
      check(Proxy != nullptr);
      bool bVisibleInView = false;
      for (const FSceneView* View : Views)
      {
        if (Proxy->IsShown(View) || Proxy->IsShadowCast(View))
        {
          bVisibleInView = true;
          break;
        }
      }
      if (!bVisibleInView && !Proxy->AffectsIndirectLightingWhileHidden())
      {
        // BEGIN_CHANGE =======================================================
        // InstanceData.Instance->GeometryType = EHairGeometryType::NoneGeometry;
        // InstanceData.Instance->BindingType = EHairBindingType::NoneBinding;
        if (Proxy->IsVisibleInSceneCaptureOnly())
        {
          // Force the HairGuide Interpolation and Deformation for proxies which are hidden in this view, but potentially visible in another.
          InstanceData.Instance->bForceHairGuideUpdate = true;
        }
        else
        {
          InstanceData.Instance->GeometryType = EHairGeometryType::NoneGeometry;
          InstanceData.Instance->BindingType = EHairBindingType::NoneBinding;
        }
        // END_CHANGE =========================================================
      }
    }
  }
}

```

```auto
// GroomManager.cpp
static void RunHairStrandsDeformation_Guide(/*...*/)
{
  //...
 
  // BEGIN_CHANGE ========================================================== 
  for (FGuideInstanceData& InstanceData : InstanceDatas)
  {
    // We can now safely cull instances that are only visible in a scene capture view
    if (InstanceData.Instance->bForceHairGuideUpdate)
    {
      InstanceData.Instance->GeometryType = EHairGeometryType::NoneGeometry;
      InstanceData.Instance->BindingType = EHairBindingType::NoneBinding;
    }
  }
  // END_CHANGE ============================================================ 
}

```

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![Charles](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/charles/32/924314_2.png) [@Charles](https://forums.unrealengine.com/u/Charles)\
**Post date:** [October 2, 2026, 12:49pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/5 "2026-10-02T12:49:50Z")

</div>

Hi,

I guess that could work, but I’m not sure this is something we would integrate back. Does it solve your issue at least?

Cheers,

/Charles.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 5, 2026, 5:18pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/6 "2026-10-05T17:18:19Z")

</div>

Hey Charles,

It does solve the issue. The hairs are now correctly updated and rendered in all views. However, the one important drawback is that I fear we are now always updating the hair guides for all groom components with “_bVisibleInSceneCaptureOnly=true_”, for as long as they are loaded and regardless of visibility. Ideally, we would only update the hair instances which we know are actually visible in a current scene capture view.

The main technical hurdle is that the _ProcessLODSelection_ is run separately for the main view and the capture view, which are both running on separate renderer instances. Therefore when a hair instance with “_bVisibleInSceneCaptureOnly=true_” is processed for the main view, it is always considered as hidden, and we cannot test it against the scene capture view (which is not in the array of views for that renderer instance).

I worked around this limitation by considering all such hair instances as potentially visible in a capture view. The rest is described in my previous post: I mark those instances to be processed until the end of

_ProcessGuideInterpolation_, which is the last hair bookmark within

_FDeferredShadingSceneRenderer::PreVisibilityFrameSetup()_. Then I cull the instances so that they are not rendered in the main view. Sadly, I have not tested this for other renderers.

An alternative is to communicate hair visibility between renderers. We could use a global data structure to mark the hair instances that are visible in a scene capture view. We would write to it when running ProcessLODSelection on the capture view, and we would read it the next time we run ProcessLODSelection on the main view.

Do you know of an existing mechanism to communicate across renderers which we could use to that effect? If you wanted to implement that feature, would you also consider some sort of global? Do you know if there is a fix planned for this bug?

Thank you!

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![Charles](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/charles/32/924314_2.png) [@Charles](https://forums.unrealengine.com/u/Charles)\
**Post date:** [October 9, 2026, 1:56pm UTC](https://forums.unrealengine.com/t/groomcomponent-with-vvisibleinscenecaptureonly-false-do-not-render-in-scenecapture/2852274/7 "2026-10-09T13:56:46Z")

</div>

This is a tricky one based on the current implementation, as the underlying resources are per instance, but the update paths are handled by different renderers as you described it. I’m not aware of particular mechanics for cross renderer communication. The only data structure which is shared between the two renderers is the Scene.

/Charles.

[Attachment Removed]
