FrameGraphRenderTarget.renderTargetWrapper: Failed to get te

Error message

FrameGraphRenderTarget.renderTargetWrapper: Failed to get texture from handle. handle: ${handle}, name: ${this.name}, index: ${i}, renderTargets: ${this._renderTargets}

What it means

When FrameGraphRenderTarget builds its renderTargetWrapper, it resolves each handle in _renderTargets via the texture manager's getTextureFromHandle. If a handle does not map to an existing texture (never created, already released/disposed, or a dangling handle), the wrapper cannot be built and it throws with full diagnostic context.

Source

Thrown at packages/dev/core/src/FrameGraph/frameGraphRenderTarget.ts:60

            const textureDescription = this._textureManager.getTextureDescription(textureHandle);

            const creationOptionsForTexture: IMultiRenderTargetOptions = {
                textureCount: this._renderTargets?.length ?? 0,
                generateDepthBuffer: false,
                label: this.name,
                samples: textureDescription.options.samples ?? 1,
                dontCreateTextures: true,
            };

            this._renderTargetWrapper = engine.createMultipleRenderTarget(textureDescription.size, creationOptionsForTexture, true);

            for (let i = 0; i < creationOptionsForTexture.textureCount!; i++) {
                const handle = this._renderTargets![i];
                const texture = this._textureManager.getTextureFromHandle(handle);

                if (!texture) {
                    throw new Error(
                        `FrameGraphRenderTarget.renderTargetWrapper: Failed to get texture from handle. handle: ${handle}, name: ${this.name}, index: ${i}, renderTargets: ${this._renderTargets}`
                    );
                }

                texture.incrementReferences();

                this._renderTargetWrapper.setTexture(texture, i, false);
            }

            if (this._renderTargetDepth !== undefined) {
                this._renderTargetWrapper.setDepthStencilTexture(this._textureManager.getTextureFromHandle(this._renderTargetDepth), false);
            }
        }

        return this._renderTargetWrapper;
    }

    public equals(other: FrameGraphRenderTarget): boolean {

View on GitHub (pinned to 0592b347b8)

Solutions

Ensure every handle in the render target's _renderTargets was created by this frame graph's texture manager and not disposed.
Recreate the render target (or refresh its handles) after any frame graph rebuild or texture disposal.
Check texture reference counts and avoid disposing textures that tasks/render targets still depend on.

Example fix

// before
rt._renderTargets[i] = oldHandle; // texture already disposed
textureManager.disposeTexture(oldHandle);
const wrapper = rt.renderTargetWrapper; // throws
// after
rt._renderTargets[i] = fg.createTexture({ name: 'rt', options: { ... } });
const wrapper = rt.renderTargetWrapper;

Defensive patterns

Strategy: validation

Validate before calling

const allValid = rt._renderTargets.every((h) => frameGraph.textureManager.getTextureFromHandle(h) !== undefined);
if (!allValid) {
  throw new Error('Render target references a disposed or unknown texture handle');
}

Try / catch

try {
  const wrapper = rt.renderTargetWrapper;
} catch (e) {
  if (String(e.message).includes('Failed to get texture from handle')) {
    // rebuild handles / recreate textures before retrying
  } else {
    throw e;
  }
}

Prevention

Track and dispose textures only after their owning render target and tasks are released.
Never mix texture handles between different frame graph instances.

When it happens

Trigger: Assigning a texture handle to a render target whose backing texture was never created or was disposed (texture manager released it), then accessing renderTarget.renderTargetWrapper; using a handle from a different FrameGraph/texture manager instance.

Common situations: Disposing textures while the frame graph still references them; using handles from a previous frame graph rebuild; passing an imported texture handle that was not registered with this frame graph's texture manager.

Related errors

AI-assisted analysis of BabylonJS/Babylon.js@0592b347b8 (2026-08-30). Data as JSON: /api/errors/a0f01b7848818f39. Report an issue: GitHub.