[GA36-MB V1.1 20251025, A33 Gecko, 493MB RAM] OpenGL ES 2 seems to be broken when runs DraStic.

Aperta
#139 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
42/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux

Direzione di ricerca

Start by comparing how goodluckOS launches DraStic with the EmuELEC script shown in the issue, focusing on the SDL_RENDER_DRIVER setting and launch arguments. Then trace the OpenGL ES 2 rendering path used by DraStic on the GA36-MB; the issue does not identify a project file or test. Done means the striped screen is explained and OpenGL ES 2 renders normally, or the issue is narrowed to the component responsible.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Hello, Everyone!!

So, recently I tried ripping DraStic out from original firmware for using as a main DS Emulator, but I discovered potential bugs inside the OS. (But I'm not sure yet.)

I've made my own script based from EmulationStation script inside its original firmware. It looks like this,

#!/bin/sh
cd /usr/lib/drastic || exit 1
echo "args: $*" > /tmp/drastic.log
export SDL_RENDER_DRIVER=software   
./drastic "$*" >> /tmp/drastic.log 2>&1
echo "exit code: $?" >> /tmp/drastic.log

This script tells goodluckOS to launch DraStic when Puppy launches this script.
But I discovered a bug probably from OpenGL driver during script launching test.

When I run DraStic with SDL_RENDER_DRIVER=opengles2, DraStic shows up with striped screen like this.
Image
However, when using SDL_RENDER_DRIVER=software, DraStic returns to normal. (But got no performance impact whatsoever)
Image

Script comparison

Original drastic.sh from EmuELEC
#!/bin/bash

cd /storage/.emulationstation/scripts/drastic/
./drastic "$1" > /dev/null 2>&1
  • No export SDL_RENDER_DRIVER line, probably used GPU rendering by default.
Custom drastic.sh in goodluckOS
#!/bin/sh
cd /usr/lib/drastic || exit 1
echo "args: $*" > /tmp/drastic.log
export SDL_RENDER_DRIVER=software   
./drastic "$*" >> /tmp/drastic.log 2>&1
echo "exit code: $?" >> /tmp/drastic.log
  • Aside from logging command I've used earlier to trace down striped screen problem inside the log but found nothing, I've set DraStic to use software rendering as a default for now.

Hope this helps finding some of issues inside the OS! (Or probably, not from the OS itself.)

Lingua principale
C++
Stelle
54
Fork
8
Merge medio
16g 19h
PR unite (30g)
4

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CodeZombie/goodluckOS

Tutte le issue di CodeZombie/goodluckOS

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.