client: what native draws for a UI image whose texture failed to load

Ouverte
#3,416 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
18/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript, wasm
Domaine
frontend, game-dev

Piste de recherche

Start in resources.ts, where a manifest-absent image is sent to missing and its quad is left blank, and compare that with the native path described in the issue (CTextBoard_SetTexturePath, CIFWnd_RenderTexturedFace, CIFWnd_RenderBackgroundTexture). The first open question is the UI texture stage-0 colour/alpha state, which the issue says is not yet traced, so it must be traced before any port change. Done means the device calls before 0x53F584 are documented and the port draws the same for an absent image, with a test, or the issue is closed with the trace showing native draws nothing.

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

Description

area: client bug priority: critical

Found while tracing #3407 in the v1.150 client.

The port draws nothing for a UI image the build lacks (resources.ts: a manifest-absent image goes to missing and its quad is blank). Native keeps drawing the face:

  • CTextBoard_SetTexturePath 0x53FF00 stores ResourceManager_GetTextureByPath's result at +0xD8 (null for a missing file) and sets the path flag +0xFC.
  • CIFWnd_RenderTexturedFace 0x5405DF draws when +0xFC is set, whether or not the texture loaded.
  • CIFWnd_RenderBackgroundTexture 0x53F4E1→0x53F4F8 binds +0xD8 as is (null included) and draws the quad (0x53F584).

So with no texture, native draws the quad with no texture bound. What that looks like (vertex colour, white or black) depends on the texture stage state the UI sets for stage 0, which hasn't been traced yet.

Done when

  • The UI's stage-0 colour/alpha ops are traced (the device calls before 0x53F584), so we know what a null-texture quad shows in native.
  • The port draws the same for an absent image, with a test. If native shows nothing, close with that trace instead.
Langage dominant
Go
Étoiles
97
Forks
61
Merge moyen
4 h 14 min
PR mergées (30 j)
913

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 opensro-dev/opensro

Toutes les issues de opensro-dev/opensro

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

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