Description

Typically, useTres().camera.value holds a camera. But the type includes undefined.

This leads to extra, otherwise unneeded reactivity and type checking.

Suggested solution

• Define a dummy camera. If no user camera is currently defined, fall back on the dummy camera.
• Remove undefined from the type.

Alternative

No response

Additional context

R3F defines a dummy camera so that the state always includes a camera.

Validations

• I agree to follow this project's Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.