Clips not being detected? Check these three things first before reading further:
- Stream is tagged as Marvel Rivals — not just “Gaming”
- Stream visibility is set to Public
- No overlays are covering the kill feed or ability HUD
Configure your stream correctly so Eklipse AI detects highlight moments automatically. Proper configuration allows the platform to read your game state and generate clips in real time. You can view our full list of supported titles on the Eklipse Games List.
STEP 1: TAG YOUR STREAM AS MARVEL RIVALS #
Eklipse detects highlights based on your stream category. It must be set to Marvel Rivals specifically — not just “Gaming” or another game title.
- Twitch: Creator Dashboard → Stream Manager → Edit Stream Info → set Category to Marvel Rivals
- YouTube: YouTube Studio → Go Live → Edit → Category: Gaming → Game title: Marvel Rivals
- Facebook Gaming: Start Live Stream → under Gaming → select Marvel Rivals
STEP 2: SET STREAM VISIBILITY TO PUBLIC #
Eklipse cannot process private or unlisted streams. Set visibility to Public before going live — not after.
STEP 3: KEEP CRITICAL HUD ELEMENTS VISIBLE #
HUD stands for Heads-Up Display — the layer of information your game shows on screen during gameplay. This includes health bars, kill counters, score displays, ability icons, objective markers, and anything else that tells you the current state of the game.
Eklipse AI reads your HUD in real time to detect highlight moments. It does not watch gameplay the way a human does — it identifies clips by detecting specific on-screen signals. If those signals are covered by stream overlays such as your facecam, alert notifications, or chat box, Eklipse cannot detect the event and the clip will not be generated.
(To learn more about how HUDs work across different games, read our general guide: What is a HUD in Streaming?)
| HUD category | What it includes | Why Eklipse needs it |
|---|---|---|
| Kill and event feed | Elimination notifications, assist confirmations, match events | Main trigger for highlight clips |
| Score and match status | Kill count, match score, round timer, point totals | Identifies high-stakes moments worth clipping |
| Health and resource bars | HP bar, shield meter, mana, energy, or stamina | Survival context — low health clutch moments are prime clips |
| Ability and skill indicators | Cooldown icons, skill charges, ultimate charge meter | Ability activations are a key detection signal |
| Objective markers | Capture progress, mission trackers, zone control indicators | Needed for objective-based highlight detection |
Safe to cover: Decorative or social elements that do not reflect gameplay state — in-game text chat panels (this is the chat panel inside Marvel Rivals itself, not your Twitch or YouTube stream chat overlay), cosmetic UI elements, or ambient flavor text. If you are not sure whether something is safe to cover, leave it visible.
- The general rule: If covering an element would make you worse at the game, do not cover it. Those are exactly the elements Eklipse is reading.
- Marvel Rivals HUD positions: In Marvel Rivals, the kill feed streams down the top-right corner, while the scoreboard and match progress bar sit centered at the top. Your hero’s health, shield bars, and portrait are located in the bottom-left corner. Ability icons, cooldown timers, and the ultimate ability meter are positioned in the bottom-right corner.
STEP 4: PLACE STREAM OVERLAYS CORRECTLY #
Place overlays here:
- Top-left corner
- Middle-left edge
- Center (for short alert notifications)
Do not place overlays here:
- Top-right corner (Kill Feed) — covering this prevents Eklipse from logging eliminations, team combos, and multi-kills.
- Bottom-left corner (Health & Shield Bars) — covering this obscures crucial low-health and survival triggers.
- Bottom-right corner (Ability & Cooldown HUD) — covering this blocks ultimate activation signals and key ability usage triggers.
STEP 5: USE ENGLISH AND DEFAULT HUD SETTINGS #
- Set in-game language to English. Eklipse AI reads on-screen text to identify highlight events — non-English characters reduce text recognition accuracy and will cause missed clips.
- Keep HUD at default style and colors. Custom UI skins or interface mods that change how text and icons render will reduce detection reliability.
