When it comes the new patch for widescreen ds games? I tested the previous one that you did it and I'm excited to get the two working and the same time. More screen + sharper visuals.
When it comes the new patch for widescreen ds games? I tested the previous one that you did it and I'm excited to get the two working and the same time. More screen + sharper visuals.
Isn't GBA already scaled at 1.5x by default on the 3DS? (240 x 160) => (360 x 240). It looks pretty good to me .Yeah I'm hoping GBA games can look better with a whole 50% more pixels to work with instead of 25%. I think mGBA does a pretty good job with scaling, so it would be nice to have some options closer to that in VC too.
Isn't GBA already scaled at 1.5x by default on the 3DS? (240 x 160) => (360 x 240). It looks pretty good to me .
Are you using TWiLight Menu? This happens sometimes, in certain builds of nds-bootstrap and some games. It's somewhat random and goes away if you close the 3DS and open again.so im testing this and... something doesnt seem right with certain games
so im testing this and... something doesnt seem right with certain games
It's a TWL_FIRM issue (unrelated to TWiLight Menu++ or nds-bootstrap), and can happen anywhere in DS/DSi mode, no matter the app or game.Are you using TWiLight Menu? This happens sometimes, in certain builds and some games. It's somewhat random and goes away if you close the 3DS and open again.
Still it's SOMEWHAT random. It happens only in some build of nds-bootstrap and certain games. Results may vary even if you build the same commit with a different version of the toolchain however they're consistent. If you get it once you'll get it always.It's a TWL_FIRM issue (unrelated to TWiLight Menu++ or nds-bootstrap), and can happen anywhere in DS/DSi mode, no matter the app or game.
I've had this happen some time ago using a flashcart, before nds-bootstrap was a thing. System did have Luma installed.Still it's SOMEWHAT random. It happens only in some build of nds-bootstrap and certain games. Results may vary even if you build the same commit with a different version of the toolchain however they're consistent. If you get it once you'll get it always.
I've never seen it happening in TWiLight Menu itself though, only in games.
If none of you want widescreen scaling then I could try something else, but so far I haven't been so lucky with GBA's 1.5x scaling :/ No pattern looks good. The sharp pattern has duplicate pixels, which is looks horribly bad with text.
as much as i love the GBA i remember haring horror stories about screen burn in on 3ds when you got rid of the filtersI'm really looking forward to widescreen for the DS games more than anything else. The GBA already fills most of the screen (more than the DS games do), and GBA games look pretty sharp already (sharper than the DS games at least). If there's room for improvement for the GBA VC games, I'm all for it, but widescreen and sharper picture for the DS seems more useful to me.
Thank you for all your work on this.
hmm brightening the screen was one of those edits they did since nintendo had the screen dimmed for gba gamesScreen burn is an issue with backlight levels, not filters.
Regardless, once you get it once you get it all the time if you follow the same steps. I guess it's something about the way the roms are loaded.I've had this happen some time ago using a flashcart, before nds-bootstrap was a thing. System did have Luma installed.
Nope, the backlight is provided by a led strip. An LCD screen can only filter light, not produce it.Screen burn is an issue with backlight levels, not filters.
as much as i love the GBA i remember haring horror stories about screen burn in on 3ds when you got rid of the filters
I'm assuming he's referring to 3DS getting their backlights blown out by setting them super high. (not really "burn-in".) It was supposedly a thing when CFW could set the backlight level to custom amounts.
I think that they probably meant that one issue that happens with certain GBA VC games when you remove ghosting via the color restoration process (which is completely optional). It certainly makes more sense than backlight issues.The only backlight patch I know of is unstable, and crashes after a while for unknown reason. I don't think custom backlight amounts are possible yet other than that patch, and it's definitely not widespread for this to be an issue.
Also, it's really hard to just "blow out" the backlight on the 3DS... there has to be some other problem. Also, a blown backlight would make the 3DS turn off INSTANTLY the moment the backlight dies, so yeah...
I think that they probably meant that one issue that happens with certain GBA VC games when you remove ghosting via the color restoration process (which is completely optional). It certainly makes more sense than backlight issues.
I can confirm this behavior, I had exactly that happen to me on my New 3DS XL (IPS top screen) after playing a few minutes of F-Zero without the motion blur filter enabled. It took about 15 (pretty scary) minutes before it faded.I think that they probably meant that one issue that happens with certain GBA VC games when you remove ghosting via the color restoration process (which is completely optional). It certainly makes more sense than backlight issues.