Homebrew Retroarch Emulation Thread (Nightly Builds Included)

  • Thread starter Thread starter Stack3r
  • Start date Start date
  • Views Views 1,554,718
  • Replies Replies 7,032
  • Likes Likes 64
I'm not sure what do you mean ?
you are aware of the resolution of the 3ds and its pixels size, right ?

When you run a rom at its native size it looks clean and accurate. When you change its size to become bigger or adjust to a full screen it isn't at its native size anymore. The problem is that with bilinear filtering off (if you upscale any rom from its native size you will always want this off, otherwise it will be a blurry mess) the upscaling is very poor. (Inaccurate pixels, just a mess, very unappealing to the eye). I've used retroarch on my iPad to play gba games and the upscaling is crisp and clean. What I'm trying to get at here is why is the upscaling on the 3DS on retroarch so poor? I would think it would be a priority unless it just isn't possible. So maybe one of the devs (@aliaspider please?) could provide an answer?
 
When you run a rom at its native size it looks clean and accurate. When you change its size to become bigger or adjust to a full screen it isn't at its native size anymore. The problem is that with bilinear filtering off (if you upscale any rom from its native size you will always want this off, otherwise it will be a blurry mess) the upscaling is very poor. (Inaccurate pixels, just a mess, very unappealing to the eye). I've used retroarch on my iPad to play gba games and the upscaling is crisp and clean. What I'm trying to get at here is why is the upscaling on the 3DS on retroarch so poor? I would think it would be a priority unless it just isn't possible. So maybe one of the devs (@aliaspider please?) could provide an answer?

No. Upscaling works great on my iPad using retroarch gba. It should work well for N3ds,too.
 
No. Upscaling works great on my iPad using retroarch gba.

No to what? :wacko:
And I'm sorry but did you even read this:
I've used retroarch on my iPad to play gba games and the upscaling is crisp and clean

It should work well for N3ds,too.
Yes, this is what I'm getting at, there should be clean upscaling on the 3DS with retroarch.
Frankly I don't understand the reason for your reply.
 
Last edited by mungry,
When you run a rom at its native size it looks clean and accurate. When you change its size to become bigger or adjust to a full screen it isn't at its native size anymore. The problem is that with bilinear filtering off (if you upscale any rom from its native size you will always want this off, otherwise it will be a blurry mess) the upscaling is very poor. (Inaccurate pixels, just a mess, very unappealing to the eye). I've used retroarch on my iPad to play gba games and the upscaling is crisp and clean. What I'm trying to get at here is why is the upscaling on the 3DS on retroarch so poor? I would think it would be a priority unless it just isn't possible. So maybe one of the devs (@aliaspider please?) could provide an answer?
Upscaling is poor because the 3DS's resolution is poor. Pixels cannot be scaled to a clean multiple.
 
Upscaling is poor because the 3DS's resolution is poor. Pixels cannot be scaled to a clean multiple.

So essentially if you want the cleanest, and crispest emulation we will just have to stick with native on the 3DS? Pretty upscaling is basically not possible?
 
So essentially if you want the cleanest, and crispest emulation we will just have to stick with native on the 3DS? Pretty upscaling is basically not possible?
Not without filtering, as far as I know. There are some nicer filters, like the scale2x option implemented in GameYob, but they are more CPU intensive, and frame rates would take a big hit.
 
  • Like
Reactions: mungry
the 8/16 bits systems you're probably considering run in the 200-256 lines (high) range, the process you're considering is multiplying those by and integer nunber and displaying them on the right amount of lines :
the 3DS screen displays 240 lines, the latest iPad Pro has 2048 lines.

it's physically impossible.

your problem here is that those pixels are HUGE, especially on the XL.

that being said, on the XL, it's like there's some natural scanlines, I don't really need upscaling, those pixels look 1:1.
(but width can be a problem, because game devs were taking into account that thos games where going to be displayed on 4:3 CRT tvs anyways, so in some systems, pixel were never design to be displayed as "squares", problem is on lcds (and by extension, the 3DS, pixels are square)
 
Last edited by Azel,
  • Like
Reactions: mungry
So essentially if you want the cleanest, and crispest emulation we will just have to stick with native on the 3DS? Pretty upscaling is basically not possible?

basically, the reason it looks so crisp on your ipad is that it has such a h
Hey.

How good is GBA emulation on an O3DS now? I don't have one anymore.

basically unplayable. 20, rarely 30 fps and less on the more demanding games.
 
  • Like
Reactions: Seriel
When you run a rom at its native size it looks clean and accurate. When you change its size to become bigger or adjust to a full screen it isn't at its native size anymore. The problem is that with bilinear filtering off (if you upscale any rom from its native size you will always want this off, otherwise it will be a blurry mess) the upscaling is very poor. (Inaccurate pixels, just a mess, very unappealing to the eye). I've used retroarch on my iPad to play gba games and the upscaling is crisp and clean. What I'm trying to get at here is why is the upscaling on the 3DS on retroarch so poor? I would think it would be a priority unless it just isn't possible. So maybe one of the devs (@aliaspider please?) could provide an answer?

Upscaling without bilinear filtering works better on iPad because the Retina Display has so many more pixels packed at a higher density so it doesn't matter if the scaling isn't a perfect integer value. Unfortunately the 3DS doesn't have that luxury. :(
 
  • Like
Reactions: mungry
Recently updated from 10.2 -> 10.3 as an Ironhax user on O3DS. Do I just need to get the most recent build of QuickNES etc from the Nightly to get them to work again? Now they load onto a black screen. Previously working on 10.2/2.5
 
Last edited by Krusiv,
Tried out PocketSNES on O3DS as .cia. Pretty slows till, 40fps on Mario World. Oh well. At least we have blargSNES, which is still being worked on.
 
Recently updated from 10.2 -> 10.3 as an Ironhax user on O3DS. Do I just need to get the most recent build of QuickNES etc from the Nightly to get them to work again? Now they load onto a black screen. Previously working on 10.2/2.5
get the latest starter.zip from the op, and reinstall ironhax...
 
get the latest starter.zip from the op, and reinstall ironhax...
Yes I did that. Updated my Ironhax payloads and now the retroarch stuff loads to a black screen. I'm asking if there is a fix for this or do I just need to be patient?
 

Site & Scene News

Popular threads in this forum