Research index: performance, graphics and compatibility findings (reference)

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cpp
Área
documentation

Línea de trabajo

This issue is a reference index linking existing research notes, including issues #502–#507 and comments on #53 and #418. Read the linked notes to revalidate findings or find topics where new data is welcome; the index itself describes a standard measurement matrix. There is no specific change or completion criteria requested, so clarify the intended contribution before starting.

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

Descripción

documentation in progress tracking

A single entry point for the read-only research that is safe to share. Each note says what is verified, what is inferred and what is untested, so a reader can revalidate cheaply and then continue instead of re-deriving work.

Topic Where
AMD handheld performance — defaults, ruled-out items, next measurements #502 (pinned)
AMD handheld deep dive — Wine RAM gauge, present mode / Gamescope, frame limiter #502 comment
Temporal upscalers (FSR 3.1 / FSR 4, DLSS / DLAA) — camera, masks, options and order #53 comment
Launcher lag on Linux + NVIDIA — cause, fix and before/after numbers #503 (patch in the comments)
Native Steam Controller 2 support — what works, what is missing #504
Crossplay with pokopia-native — protocol comparison and options #505
Linux native build — clang compile probe (132/213 TUs pass) #506
Windows dependency catalog for the Linux port #507
4:3 / narrower-than-16:9 backdrops — the existing pane mechanism and coverage #418 comment
How to use these
  • Revalidate a "verified" row if you doubt it; most are a file read or one log line away.
  • Do not re-derive a "ruled out" item — the reason is in the note.
  • "Unknown" is where new data is welcome, not a gap to fill by guessing.
  • Any real measurement needs the standard matrix: same save, scene and route, camera, activity, settings, cap and power mode; warm cache unless the test is about a cold one; alternating runs; frame-time percentiles and variance; driver and build recorded; and a stability outcome.
What is deliberately not here

Game-internals and reverse-engineering notes, and security findings, stay private. More information — the full evidence ledgers, raw measurements, and the notes that are not safe to publish — is available to the team on request.

Lenguaje dominante
C++
Estrellas
224
Forks
0
Sin PR fusionados en 30 d

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 featureJosh/Recompia

Todos los issues de featureJosh/Recompia

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.