I just installed Pixie on a new RG35XX H and I’m getting horizontal lines when playing Pokémon yellow on GBC.
I’ve tried disabling all overlays, shaders, filters and it’s still there. It’s not there in menus when closing the content. It seems to appear over time, and it’s not showing below a certain level of brightness.
This is what it looks like
On discord there were hypothesis that this is due to anbernics shipping différent revisions of the display in that device and the timings being off for some. That’s a little above my pay grade but I’m including this info for context. See Discord
I own one of the affected devices so if something needs to be extracted from the stock OS install or whatever I’m happy to help however I can.
Unfortunately, there is not a whole lot you can do… the panels are a bit of a mixed bag.
Because we’re essentially pushing display timings right up to the edge of ~60Hz, some panels just don’t like it. It’s not uncommon to see issues like scan line banding or flickering, depending on the specific unit.
For example, on my 35PRO, I get noticeable scan line banding at full brightness, but if I lower it to a mid-range level, everything smooths out. These kinds of quirks vary unit to unit. It’s essentially the silicon lottery at play.
Now, we could offer a fallback stock panel configuration that runs at 58Hz, which avoids some of these issues. However, that comes with its own downsides. At 58Hz, you’re much more likely to notice stuttering, especially with fast motion or horizontal scrolling content. People will end up saying “the screen is stuttering” even though it’s technically running as expected.
RetroArch can sort of fake a 60Hz output internally and mask some of that, but it only works within RetroArch itself. External emulators and ports will still show obvious stuttering and frame pacing issues.
So while it might seem like a fix, using a 58Hz panel profile typically results in a worse overall experience. Your best bet is to play around with brightness levels. It’s not perfect, but it can make a big difference depending on your specific unit.
Does the stock OS that comes with the device run at 58 Hz? As the issue doesn’t seem to occur on that OS. Have seen people saying it doesn’t happen on Knulli although I haven’t tested that personally
Ive been working on finding a solution myself. It seems (so far atleast) that there is a way to tell the screen model from the ribbon cable. Mine came with 355608-A9 ive ordered the 355608-A8 from aliexpress which is the same as the one in my 35xx plus. I have tested goose on that and had none of the screen issues, im hoping the screen replacement will emulate this
Hi. I got the same problem with my RG35XX H. It works fine with Knulli here.
After checking some other places it seems it works with Knulli because they have a refresh rate of 59.94Hz, while it doesn’t work with muOS because it has a refresh rate of 59.98Hz.
