What's New in BetaHub — July & August 2026

This cycle covers mid-July through early September. BetaHub now tailors itself to who’s using it: a redesigned Developer Dashboard replaces the generic project overview, and the signed-in home page renders differently for reporters versus developers. Alongside that, Forms & Surveys unifies hosted forms, portals, and surveys into one branded module, the Unreal Engine 5 plugin got substantially cheaper to record with, and Discord-based communities can now bulk-import their forum history.

---

Developer Dashboard

The project overview page is now a purpose-built dashboard for developers, with two states:

• Setup (no submissions yet) — a channel-first checklist: pick how feedback will arrive (Discord bot, game SDK, hosted form, or testers), connect it, then send a test report. Progress is derived from what’s actually connected, never a stored checkbox.
• Operate (first bug, suggestion, or ticket has landed) — a 30-day activity pulse strip, a Needs your attention inbox (new tickets, items pending moderation, stale needs-more-info requests, join requests, sentiment dips, Discord bot problems, support-knowledge gaps — each one hidden when there’s nothing to show), a heat-ranked bugs card, top suggestions, and a release/members rail.

Two more cards round it out:

• Recommended for you — contextual nudges (enable Support Knowledge, add knowledge-base sources, connect an integration, publish a suggestions board, and similar), capped at three at a time and dismissible per user.
• Channels — one row per way feedback actually reaches the project (Discord, each API token, hosted form/widget, each integration), each with a real health signal instead of a static “connected” label.

Testers and the public still see the existing project page — this is developer-only.

Developer Dashboard documentation

---

Persona-Based Home Page

The signed-in home page used to show everyone the same thing. It now renders based on role:

• Reporter view (tester-only, or no role but with reports of their own) — a Needs you list of unanswered detail and retest requests, My reports with status and unread flags, and a single “Report a bug” call to action.
• Developer view (any dev/support role, or org admin) — a cross-project inbox: new bugs since your last visit, tickets waiting, details answered, retest replies, merge reviews, and anything assigned to you, followed by your projects and articles.

The change is based on the team’s own usage data: over 90 days, 93% of signed-in visitors were one-project reporters checking on their own report, while the old page led with features used by only 41 people.

---

Forms & Surveys

Hosted forms, portals, and surveys are now one module, on by default. A single builder covers bugs, suggestions, support tickets, and surveys.

• Branding — custom logo, banner image, background image, accent color, and a light/dark toggle (or respect the visitor’s preference). The “Powered by BetaHub” line can be hidden on select plans.
• Survey question types — rating scales with a customizable range, single choice, multiple choice, yes/no, short answer, number, and date.
• Submissions — anonymous responses, optional email collection, and Discord account linking. No account is required to respond.
• Content — editable title and intro text, custom field attachments, and file attachments (screenshots, video, logs, or any file type), with a live preview while building.
• Distribution & results — send to users with the tester role or share a public link. Results include a sent → opened → completed funnel, per-question breakdowns, per-wave separation for repeated surveys, and compiled text answers.

A hub can group multiple forms under a single, persistent URL that survives edits — one branded page, one shareable link.

Surveys documentation

Feedback forms documentation

---

Recording: Lower Overhead, Fewer Freezes (Unreal UE5)

Frame capture in the Unreal Engine 5 plugin moved from synchronous GPU readback to an async readback ring with on-GPU downscaling.

• Render-thread stall per capture dropped from roughly 6.5ms to 0.01ms.
• Overall recording overhead fell from roughly 18% to 6% of frame time.
• Recorded video now hits the actually-configured frame rate, instead of being silently throttled to about half of it.

Two related fixes shipped alongside it:

• Recording no longer hangs the game. A held FFmpeg pipe handle could previously block forever if FFmpeg exited early — a bad output directory, a crash, or antivirus software blocking it — freezing the game. This was reachable through ordinary actions like resizing the viewport.
• Recording now resumes after every submission. Previously, submitting a screenshot/logs-only report or a suggestion left gameplay recording stopped, so the next report could capture stale or frozen video.

An optional GPU hardware encoder (NVENC) is also available, opt-in via the WITH_BETAHUB_HWENCODE build flag and the VideoEncoderBackend setting, falling back to the bundled FFmpeg encoder automatically when unavailable. Separately, the plugin has been updated for UE 5.8 compatibility.

Unreal plugin documentation

---

Fixed: Stuck Mouse After Closing a Report (Unreal UE5)

The bug-report form previously force-restored a hardcoded input mode when it closed, which could break mouse capture and click-drag in both FPS-style and cursor-driven games. It now snapshots the game’s actual input state before opening and restores it on close, via a new EBH_InputModeRestore setting (default: Auto).

Unreal plugin documentation

---

Discord Bot Page Now Diagnoses Its Own Setup

The dashboard’s Discord Bot page now groups capabilities by player intent and live-fetches the bot’s actual configuration — listen mode, reactions, channels — instead of inferring it. It also surfaces self-diagnosed problems, like an unreachable or deleted channel, with a suggested fix at the top of the page.

Two related fixes: the /report, /suggest, and /ticket slash commands always worked regardless of channel setup — the previous copy suggested otherwise — and a channel/role refresh that could previously hang indefinitely now completes.

Discord Bot documentation

---

Bulk-Import Discord Forum Threads

Existing Discord forum discussions can now be bulk-imported as bugs or suggestions, with comments and votes back-filled from archived threads. The first 1,000 threads per project are free.

Discord Bot documentation

---

Faster Bug Triage: Multi-Select and Device Filters

Filters on Bugs and Tickets — Release, Priority, Assignee, Reported By, and Sent-to — now accept multiple values at once, and archived releases are selectable again.

The Bugs index also has new device filters, built from data BetaHub already auto-detects from testers’ devices — no manual tagging required. Useful for isolating reports tied to a specific GPU, OS version, or device model.

---

Linear Two-Way Sync

Status and priority changes made in Linear now flow back into BetaHub automatically, instead of requiring a manual re-sync.

Integrations documentation

---

Quality of Life

Sample Knowledge Base — five starter articles ship by default, so /ask has something to answer before you’ve written your own.

Improved knowledge-base answers for new projects — new projects now default to an updated /ask answer engine.

Onboarding walkthrough — corrected copy in the setup walkthrough.

Thread-mode discoverability — the bot now warns when a threads_channel is configured but inactive, with a toggle to address it.

---

That’s everything for this cycle. Questions or feedback? Find us on Discord.

— The BetaHub Team