N64 from 16:9 to 4:3 instead
-
Scratched the back of my head when i opened the link to the Panfrost info, haha!
It is not correct with many things, but it did help me to identify that i had to use cat (aka the very basics) :)dietpi@DietPi:~$ cat /proc/device-tree/compatible
xunlong,orangepi-zero2wallwinner,sun50i-h618Would it be more like this?
function platform_sun50i-h618() {
cpu_armv8 "cortex-a53"
__platform_flags+=(gles gles3 gles31)
}Maybe unrelated: Would it help if I'd say the bootEnv.txt contains an overlay_prefix=sun50i-h616? (No idea what it does, I understood it is connected to the .dtb(o), and if I amend this to h618, the gpu acc stops working)
-
@Arrafart said in N64 from 16:9 to 4:3 instead:
Would it be more like this?
Yes, I think it's better;
sun50i-h618
sounds like a good name. You can try addingx11
also to the flags.Maybe unrelated: Would it help if I'd say the bootEnv.txt contains an overlay_prefix=sun50i-h616? (No idea what it does, I understood it is connected to the .dtb(o), and if I amend this to h618, the gpu acc stops working)
That's just instructs the bootloader (U-Boot) to look for any
.dtb
files under thesun50i-h616
folder. Since the H616 is the previous SOC version in the H series, it might have inherited part of that version's device tree.dietpi@DietPi:~$ cat /proc/device-tree/compatible
xunlong,orangepi-zero2wallwinner,sun50i-h618
You can use either
rangepi-zero2wallwinner
orsun50i-h618
as a device identification string, and setplatform
tosun50i-h618
. -
function platform_sun50i-h618() {
cpu_armv8 "cortex-a53"
__platform_flags+=(x11 gles gles3 gles31)
}The Orange Pi zero 3 has the same chipset, if I'm right, so they would carry the same name like that.
Not sure what to do with it, but...
I had a good day, thanks!
-
Your system should have the
gles gles3
flags instead ofx11
(which I assume it's now set by RetroPie-Setup), so that the GLES3 specific build options are applied to emulators/libretro cores.Found it: Can I apply it to the system.sh script and reinstall emulators or should update Retropie script?
-
@Arrafart You should re-install with the new flags. Don't update, since RetroPie-Setup doesn't have your modifications and it won't work anyway.
-
@mitu I have amended /home/dietpi/RetroPie-Setup/scriptmodules/system.sh but the flags did not change.
I thought, maybe a visual things since i amended myself.
No changes after re-intallation of the 4 emulators. -
@Arrafart said in N64 from 16:9 to 4:3 instead:
@mitu I have amended /home/dietpi/RetroPie-Setup/scriptmodules/system.sh but the flags did not change.
Yes, because you haven't added the detection part. Here's your
system.sh
, but with detection: https://gist.github.com/cmitu/64d7e993609a3f28b58a0a1a0267d292. Try it and see if the correct platform is detected and the flags are applied. -
Flags: Sun50i-h618 64bit aarch64 x11 gles gles3 gles31
After reinstalling
Progress on the flags
mupen64plus glide64 16:9
https://pastebin.com/BaRinFXelr-mupen64plus
Not supported / flaggedlr-mupen64plus-next (back to ES)
https://pastebin.com/2pptYP5wmupen64plus glideN64 (back to ES)
https://pastebin.com/n1gqn5ja -
@Arrafart said in N64 from 16:9 to 4:3 instead:
lr-mupen64plus-next (back to ES)
https://pastebin.com/2pptYP5wYou need to recompile RetroArch also:
[INFO] [Environ]: SET_HW_RENDER, context type: gl.
[ERROR] Requesting OpenGLES3 context, but RetroArch is compiled against OpenGL. Cannot use HW context.
[ERROR] [Environ]: SET_HW_RENDER - Dynamic request HW context failed.
[libretro ERROR] mupen64plus-next: libretro frontend doesn't have OpenGL support -
Out of interest I think I found the "get" lines in the system.sh
sun50i-h618)
__platform="sun50i-h618"
;;Victory! And in 4:3!
lr-mupen64plus-next
https://pastebin.com/ijeRkPF7I feel like i will be getting picky now, but it runs choppy vs the mupen64plus standalone (that runs smoothly), it has a black bar on top+bottom and graphics took a hit.
Anything polish able? Or is this where we should draw the line for the Orange pi zero 2w? -
@Arrafart said in N64 from 16:9 to 4:3 instead:
Anything polish able? Or is this where we should draw the line for the Orange pi zero 2w?
You can look into the core options and make sure you disable any performance demanding options (upscaling, MSAA).
-
I managed to puzzle a bit within the RetroArch menu (hotkey+north within the game), inside the core options, and restarting ES after each change. Might polish a bit more.
It came down to assuring the 1x resolution and some extra texture options for preference. It doesn't beat Mupen64plus graphics yet, but it is damn close right now.
I could also push the 4:3 top and bottom scaling within the glideN64 core options, no more black borders.
I am 95% satisfied! 🥂🙏🏻🎮
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.