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

Abierto
  • ¿Algo no está bien?
#495 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
csharp, unity
Área
game-dev, performance

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
C#
Estrellas
33
Forks
1
Merge medio
1 d 21 h
PR fusionados (30 d)
56

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Gothic-Unity-Project/Gothic-Unity

Todos los issues de Gothic-Unity-Project/Gothic-Unity

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.