orklev2-fbi

Answer questions about Orkid FrameBufferInterface render target management and pixel readback.

35|16|Updated Feb 10, 2013
One-click install
npx skills add https://github.com/tweakoz/orkid --skill orklev2-fbi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orklev2-fbi
Source: https://github.com/tweakoz/orkid/tree/main/.claude/skills/orklev2-fbi
Command: npx skills add https://github.com/tweakoz/orkid --skill orklev2-fbi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides precise, discoverable answers about Orkid's FrameBufferInterface and related render-target systems so developers can understand, debug, and correctly use framebuffer operations, viewport/scissor stacks, MSAA resolve, and pixel capture workflows.

Core Features & Use Cases

  • API Reference Mapping: Maps FBI methods for clear & display, push/pop RtGroup, viewport and scissor stack operations, and frame lifecycle management.
  • Render Target Management: Explains RtGroup, RtBuffer, mip generation, MSAA blit/resolve, depth cloning, and blit/downsample operations.
  • Pixel Readback & Capture: Details synchronous and asynchronous pixel fetch, capture to file or texture, and pick buffer usage, including Python bindings for automation.
  • Use Case: Use when implementing offscreen rendering, taking async screenshots, debugging render target transitions, or wiring Python tools to the lev2 graphics subsystem.

Quick Start

Ask the skill to explain how to push and pop an RtGroup, set viewport/scissor, and capture a pixel asynchronously from a render target.

Frequently Asked Questions about orklev2-fbi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage render target lifecycles in Orkid's lev2 graphics subsystem?

Render target lifecycle management in Orkid's lev2 subsystem involves pushing and popping RtGroup and RtBuffer objects through the FrameBufferInterface. This skill maps FBI methods for frame lifecycle management, ensuring correct allocation, usage, and cleanup of render targets within your rendering pipeline.

What is the difference between MSAA resolve and blit operations for framebuffers?

MSAA resolve and blit operations differ in how they handle multisampled framebuffer data. This skill explains MSAA blit and resolve workflows, detailing how the FrameBufferInterface downsamples, clones depth, and blits between render targets to produce final framebuffer output.

How do I capture pixels asynchronously from a render target in Orkid?

Asynchronous pixel capture from an Orkid render target uses the FrameBufferInterface to fetch pixels without blocking the render loop. This skill details sync and async pixel readback, capture to file or texture, and pick buffer workflows for screenshot and debugging tasks.

Can I use Python bindings to automate framebuffer operations in Orkid?

Yes, Python bindings can automate framebuffer operations in Orkid. This skill covers Python tool integration with the lev2 graphics subsystem, including automating pixel capture, managing RtGroup transitions, and scripting pick buffer workflows for offscreen rendering tasks.

How do viewport and scissor stacks work in Orkid's FrameBufferInterface?

Viewport and scissor stacks in Orkid's FrameBufferInterface manage nested rendering regions by pushing and popping viewport and scissor rectangles. This skill explains these stack operations, allowing developers to correctly scope rendering output and manage region-specific framebuffer updates.