libretro / libretro/RetroArch

Image Viewer doesnt work on later version of Retroarch on the Wii

Open
#14,115 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

core bugs - not retroarch bugs image viewer core platform: wii/ngc
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

Image Viewer never seemed to work on Retroarch on the Wii, at all, despite working fine on the regular PC version.

Expected behavior

Images should display properly in full color

Actual behavior

On the old version of the Core, imageviewer_libretro_wii.dol which was 0.1, images just simply load in red tones, whereas on any other version of Retroarch post version 1.3.6 on the wii, the imageviewer doesnt seem to work no more, on the latest version of retroarchs, even after allowing the option to use the built-in media player, it does not open the images at all, it just crashes retroarch and either resets Retroarch or just sends you back to the Homebrew channel.

I do occasionally create sprite art, and i only have a CRT with composite input, i don't have any budget to afford an expensive GPU with display port to do any tricks to output 240p on a CRT with Component input, and sadly my only GPU and transcoder seems to be of poor quality since it just output a very flickery 480i image, which makes it worthless in my opinion, to being able to connect my PC and display pixelart on my CRT using the regular version of Retroarch.

Here's a quick sprite-work i had produce for the sake of an example (based on an image that was not mine and i take no credit for)

https://files.catbox.moe/9h4y71.jpg

The Nintendo Wii was the last console that could output 240p trough composite, which seemed to be my last choice, but so far, i got distraught, my budget is severely limited.

I don't know if is it because i am using a Wii mini or what else, but i need your help, please correct the Image Viewer in case of it still being integrated into Retroarch Wii so it doesn't crash the entire app? the idea of being able to output native 240p sounds like a good deal for me, and could it be an amazing feat for aspiring pixel artists, specially those working at different sprite resolutions such as 320x224 or 384x224

Please solve this issue as soon as possible.

Steps to reproduce the bug
  1. Open Retroarch and on File Browsing enable the Option to use Built-In Media Player
  2. Open folder with desire image files (Jpeg, PNG, etc) and load file
  3. Retroarch just crashes.
Bisect Results

When loading PNG, JPEG and BMP images, it refuses to load them properly and just simply crashes.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: Earlier version tested 1.3.6 - Newer version tested 1.10.3
Environment information
  • OS: HomeBrew Channel on the Nintendo Wii
  • Compiler: [In case you are running local builds]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Wii image viewer path, including imageviewer_libretro_wii.dol and the File Browsing option for the built-in media player. Reproduce the crash with PNG, JPEG, and BMP files on RetroArch 1.10.3, comparing with the 1.3.6 behavior. Done means images open in full color without crashing or resetting RetroArch on the Wii.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.