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

Abierto
#139 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux

Línea de trabajo

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.

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

Descripción

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.)

Lenguaje dominante
C++
Estrellas
54
Forks
8
Merge medio
16 d 19 h
PR fusionados (30 d)
4

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 CodeZombie/goodluckOS

Todos los issues de CodeZombie/goodluckOS

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.