## System details

- Omarchy: `4.0.3-1`
- Hyprland: `0.56.2-2`
- Kernel: `7.2.3-arch1-3`
- Architecture: `x86_64`
- Session: Wayland, Hyprland, XWayland `24.1.13`
- CPU: AMD Ryzen 9 5900HX with Radeon Graphics
- GPUs: NVIDIA GeForce RTX 3080 Mobile and AMD Cezanne integrated graphics
- Zoo Design Studio: `1.4.8` x86-64 AppImage
- Brave: `153.1.95.101`
- Firefox: `155.0.1`

## What's wrong?

Zoo Design Studio opens normally under Omarchy, but opening any cloud project leaves the viewport stuck at:

`Connecting and setting up scene`

The viewport partially reacts and may tilt, but the streamed 3D scene never becomes usable. This affects existing projects and new projects.

This is different from a no-window startup failure. The Zoo window opens, but its cloud-rendered viewport does not finish setup.

Omarchy exports these variables globally:

```text
ELECTRON_OZONE_PLATFORM_HINT=wayland
OZONE_PLATFORM=wayland
```

They are set in:

```text
/usr/share/omarchy/default/hypr/envs.lua
```

The same project works when Zoo runs through XWayland:

```bash
env -u ELECTRON_OZONE_PLATFORM_HINT -u OZONE_PLATFORM \
  "$HOME/Applications/Zoo Design Studio-1.4.8-x86_64-linux.AppImage" \
  --ozone-platform=x11
```

For this mixed-scale setup, `GDK_SCALE=1` also keeps the XWayland UI at a usable size.

This is a strong correlation, not proof that Omarchy is the root cause. The suspected affected path is Chromium/Electron native Wayland/Ozone handling of Zoo's WebRTC viewport.

## Reproduction steps

1. Use the default Omarchy Wayland session.
2. Launch Zoo Design Studio without overriding the Ozone variables.
3. Open an existing or new cloud project.
4. Observe that the viewport remains at `Connecting and setting up scene`.
5. Close Zoo.
6. Launch it with the XWayland command above.
7. Open the same project.
8. Observe that the 3D viewport loads normally.

## Comparison tests

| Test | Result |
| --- | --- |
| Zoo Desktop with native Wayland/Ozone | Viewport stays on `Connecting and setting up scene` |
| Zoo Desktop on the normal network | Fails |
| Zoo Desktop through a phone hotspot | Fails |
| New cloud project | Fails |
| Zoo Web in Brave | Fails |
| Zoo Web in Firefox | Works |
| Zoo Desktop forced through XWayland | Works |

Changing networks did not resolve the issue. Changing from Chromium native Wayland to Firefox or XWayland did.

## Expected behavior

Zoo Design Studio should load its streamed 3D viewport under Omarchy's default environment.

## Actual behavior

```text
Native Wayland/Ozone:
Zoo UI opens
→ cloud project opens
→ Connecting and setting up scene
→ viewport never initializes

XWayland:
--ozone-platform=x11
→ cloud project opens
→ streamed viewport works
```

This appears related to #7642, but the failure differs because Zoo creates a window successfully. The suspected affected path is Chromium/Electron native Wayland/Ozone handling of Zoo's WebRTC viewport.

## Workaround

```bash
env -u ELECTRON_OZONE_PLATFORM_HINT -u OZONE_PLATFORM \
  "$HOME/Applications/Zoo Design Studio-1.4.8-x86_64-linux.AppImage" \
  --ozone-platform=x11
```