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

未關閉
#139 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
42/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
linux

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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

主要語言
C++
星號
54
分支
8
平均合併
16 天 19 小時
30 天內合併 PR
4

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

CodeZombie/goodluckOS 的其他 Issue

查看 CodeZombie/goodluckOS 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。