# ArgumentException: CommandBuffer: Invalid ComputeBuffer name (null or empty)

- **ID:** `unity/rendering-command-buffer-invalid`
- **Domain:** unity
- **Category:** runtime_error
- **Verification:** ai_generated
- **Fix Rate:** 96%

## Root Cause

A CommandBuffer.SetComputeBufferParam call was made with a null or empty string as the shader property name.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Unity 2022.3 | active | — | — |
| Unity 2023.2 | active | — | — |
| Unity 6000.0 | active | — | — |

## Workarounds

1. **Ensure the property name passed to SetComputeBufferParam matches the name in the compute shader's [numthreads] or buffer declaration.** (97% success)
   ```
   Ensure the property name passed to SetComputeBufferParam matches the name in the compute shader's [numthreads] or buffer declaration.
   ```
2. **Add a null check before calling SetComputeBufferParam to avoid passing empty strings.** (99% success)
   ```
   Add a null check before calling SetComputeBufferParam to avoid passing empty strings.
   ```

## Dead Ends

- **** — The shader property name must be consistent between C# and the shader code; arbitrary names cause shader binding failures. (95% fail)
- **** — This workaround removes the functionality instead of fixing the root cause. (60% fail)