In-game performance view (FPS graph on back of right hand)

Ouverte
  • Quelque chose ne va pas ?
#495 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
csharp, unity
Domaine
game-dev, performance

Piste de recherche

Start by reviewing the existing Core services, VR hand adapters, and toggle configuration entry points; the issue does not name specific files or tests. Agree on the metrics and toggle location first, then collect frame timing data and build the wrist view. Done means the agreed view and toggle work, and its cost has been checked on Quest 2.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

feature

Description

Should we have an in-game performance view for VR? Today, checking performance in the headset means the Unity Profiler, OVR Metrics Tool or log files. A small widget in the game would let testers see slowdowns where they happen (camps, world loading, fights) and give better reports, e.g. for #230.

Idea: a small panel on the back of the right hand, a bit like a smartwatch. Turn your wrist and you see it; in normal play it stays out of view.

Content (kept small so it's readable at arm's length):

  1. FPS graph over time: a sparkline of the last ~10 s, with a line at the target refresh rate (72/90 Hz). Current, min and avg values as text.
  2. CPU / GPU frame time (ms): shows which side is the bottleneck. Unity's FrameTimingManager provides this on Quest/Pico and PC.
  3. (optional) Active NPCs / loaded VOBs: our most likely hotspot (see #230), so we can link a drop to what's around.

Other options instead of 3: memory used (managed + native), or draw calls / batches.

Open questions
  • Where should the toggle live: Marvin menu, DeveloperConfig, or a game setting so players can use it too?
  • Should Flat mode get the same view as a screen overlay?
  • Update rate: the graph should be cheap. Redraw a few times per second instead of every frame, and avoid allocations so the widget doesn't skew the numbers on Quest 2.

TODOs

  • Agree on content and toggle location
  • Collect frame data in a Core service (ring buffer, no per-frame allocations)
  • VR adapter: panel attached to the right-hand back, visible when the wrist is turned towards the camera
  • Hook up the toggle (Marvin / DeveloperConfig)
  • Check the widget's own cost on Quest 2
Langage dominant
C#
Étoiles
33
Forks
1
Merge moyen
1 j 21 h
PR mergées (30 j)
56

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Gothic-Unity-Project/Gothic-Unity

Toutes les issues de Gothic-Unity-Project/Gothic-Unity

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.