Blender 4.1.1 compatibility testing on FARPY RTX 3090 workers

Blender 4.1.1 on registered RTX 3090 workers.

Runtime: Blender 4.1.1
Platform: Linux x86_64
Device: Cycles OptiX
CPU: disabled for GPU qualification and positive GPU render tests

Blender binary SHA-256: d5cf60563644ed770c5c13952624a0fa8ad076920bbc524275c0044029e36286

Exactly one selected GPU; the other GPU excluded from each direct qualification.

Four positive workload classes completed.

Six expected rejection behaviors passed.

These six tests prove controlled rejection and failure classification behavior. They do not count as successful compatible render workloads and do not increase the positive ready-workload count of four.

All four registered NVIDIA GeForce RTX 3090 GPUs passed direct physical-device qualification for controlled, local, isolated Blender 4.1.1 research. Each qualification selected one OptiX GPU, disabled the CPU and the other GPU, proved activity on the selected device, detected no activity on the excluded device, and confirmed idle state before and after. The original positive and negative compatibility fixtures ran on one qualified GPU. BLEND-012 separately repeated the canonical still on three additional target GPU runs spanning three unique RTX 3090 GPUs across two nodes.

BLEND-012 repeated the canonical still on three unique RTX 3090 GPUs across two nodes. All three target renders completed and matched the canonical decoded-pixel SHA-256.

Canonical decoded-pixel SHA-256: 7478f289798febe4c141c7e6c4d182f69042b517586fbb608deba9184612ea86

This proves cross-GPU and cross-node determinism only for the exact baseline still fixture, Blender 4.1.1 runtime, OptiX configuration, and tested RTX 3090 environment. It does not prove arbitrary Blender determinism, cross-version determinism, cross-runtime determinism, or cross-driver determinism.

• Blender 4.1.1 on Linux x86_64, installed as an isolated side-by-side research runtime.
• Exact Blender binary SHA-256: d5cf60563644ed770c5c13952624a0fa8ad076920bbc524275c0044029e36286.
• Cycles OptiX where applicable, with CPU disabled for GPU qualification and positive GPU render tests.
• Exactly one selected GPU; the other GPU excluded from each direct qualification.
• Idle compute-process checks before and after execution.
• Runtime and fixture hashes captured for identity and repeatability.
• Standard output, standard error, GPU telemetry, and postflight process-cleanup evidence captured.
• No production job, queue claim, money action, receipt, artifact delivery, webhook, worker configuration, scheduler configuration, or service restart was created by the positive workload runs.

Structural visual review covered 8 images from 4 fixtures. Global visual result: PARTIAL.

• BLEND-BASELINE-VALID-STILL: visible, nonblank, coherent output.
• BLEND-002: three complete frames with visible animation progression.
• BLEND-003: packed colored asset visibly present.
• BLEND-011: three visually identical outputs with one decoded-pixel hash.

No independent reference images were available, pixel-perfect reference matching was not performed, and arbitrary Blender visual correctness was not established.

This is not a general RTX 3090 compatibility claim.

• Only the documented fixtures and failure modes were tested.
• Broader Blender compatibility remains incomplete.
• Structural visual review passed for the four reviewed positive fixtures; independent reference matching and arbitrary-project visual correctness remain unproven.
• Production eligibility has not been granted.
• These results do not establish support for arbitrary Blender projects.
• ORBX testing remains blocked.
• Negative tests verify rejection behavior, not rendering capability.
• GPU qualification applies to isolated Blender 4.1.1 research execution.

What Blender version was tested?
Blender 4.1.1 on Linux x86_64, using the isolated runtime whose binary SHA-256 is d5cf60563644ed770c5c13952624a0fa8ad076920bbc524275c0044029e36286.

How many GPUs were qualified?
Four of four registered NVIDIA GeForce RTX 3090 GPUs qualified for controlled, isolated Blender 4.1.1 research execution.

What successfully rendered?
Exactly four controlled workload classes: one valid still, one packed-asset still, one three-frame animation, and one deterministic-repeat workload.

What failure modes were tested?
Missing external asset, missing external Blender library, no camera, non-Cycles render engine, corrupt or unreadable blend input, and invalid frame range.

Do negative tests count as compatible workloads?
No. They verify controlled rejection and classification behavior and do not increase the positive ready-workload count.

Is arbitrary Blender project support proven?
No. Only the documented fixtures and failure modes were tested, so broader Blender compatibility remains incomplete.

Was visual correctness reviewed?
Yes, structurally for the four reviewed fixtures. The global state is PARTIAL because independent reference-image matching and arbitrary-project visual correctness were not proven.

Is this production ready?
No. Production eligibility is NOT_GRANTED; GPU qualification applies only to isolated research execution.

Is ORBX supported?
No. ORBX testing remains blocked and this research grants no ORBX support.

The identifiers name the frozen internal evidence bundles used for this report. Raw bundles are not linked because they contain private worker and infrastructure data. Public-safe proof material is available through the approved FARPY proof index; this page publishes only scoped findings and safe hashes.

BLEND-BASELINE-VALID-STILL

BLEND-002

BLEND-003

BLEND-011

BLEND-012

BLEND-004

BLEND-005

BLEND-006

BLEND-007

BLEND-008

BLEND-009

blender-negative-readiness-update-20260729T002440Z

blender-visual-correctness-review-20260729T041420Z

blend-012-cross-gpu-node-ingest-20260729T042237Z