Homebrew TWPatcher - DS(i) mode screen filters and patches

[seriffic]

Haven't tried open_agb_firm yet? It works exactly like GBA's VC (GBA games run natively on the console) and it has its own scaling method. Maybe you like it (or maybe you don't). It's still WIP, so it might get better for you later on.

I've checked out that thread, from what I've read it still uses 1.5x scaling but with a sharpened interpolation, while I'm being rather picky and would prefer 1.25x scaling (which is how GBARunner displays GBA games since it's displaying GBA games 1:1 in DS mode, and the DS mode image is upscaled to the 3DS screens so it's a 1.25x scale from the original GBA image). Good to know there's some work being done on AGB_FIRM though

 

[playsaves3]

I've checked out that thread, from what I've read it still uses 1.5x scaling but with a sharpened interpolation, while I'm being rather picky and would prefer 1.25x scaling (which is how GBARunner displays GBA games since it's displaying GBA games 1:1 in DS mode, and the DS mode image is upscaled to the 3DS screens so it's a 1.25x scale from the original GBA image). Good to know there's some work being done on AGB_FIRM though

so should I wait on that and if so can you update me on when they get it 1.25?

 

[Mike_890]

How come it won’t let me download either the stable or experimental version? I click both links but it doesn’t load them at all

 

[r0achtheunsavory]

How come it won’t let me download either the stable or experimental version? I click both links but it doesn’t load them at all

I have the experimental version saved from 9/03. Should be this file I saved named "TWPatch.cia"

https://mega.nz/file/V88C1Kpa#Xor9mam256k4al1oZnMFOffnACWY1m9l3tLOIGnT_ZI

 

[Mike_890]

I have the experimental version saved from 9/03. Should be this file I saved named "TWPatch.cia"

Thank you so very much I wasn’t sure why the links weren’t working for me

 

[Nutez]

I've added a PoC "TwlBg Quick Switcher" feature to Rosalina in this custom Luma build. It lets you switch between custom named TwlBg.cxi files (e.g. wide.cxi, nightMode.cxi) stored in the "/luma/sysmodules" directory. It basically just renames the selected .cxi file to TwlBg.cxi and saves the previous name to a file so that it can be reverted on the next switch. Source if anyone would like to do a code review (C newbie here so feel free to get basic).

 

[Sono]

Sorry for not replying, I've lost track of who asked what. If you have asked somthing after september 7th and didn't get a reply, please quote this message and ask your question again.

 

[Deleted member 323844]

I've added a PoC "TwlBg Quick Switcher" feature to Rosalina in this custom Luma build. It lets you switch between custom named TwlBg.cxi files (e.g. wide.cxi, nightMode.cxi) stored in the "/luma/sysmodules" directory. It basically just renames the selected .cxi file to TwlBg.cxi and saves the previous name to a file so that it can be reverted on the next switch. Source if anyone would like to do a code review (C newbie here so feel free to get basic).

Thank you. It could be interesting if Luma3DS itself renames the old patches every time you create a new one, appending a number, at least.

But it's pretty cool.

Edit: I'm a bit confused with the TXT thing

 

[Nutez]

Thank you. It could be interesting if Luma3DS itself renames the old patches every time you create a new one, appending a number, at least.

But it's pretty cool.

Edit: I'm a bit confused with the TXT thing

Yeah I think to add an increment on each new TwlBg you'd need to edit the patcher itself? But unless you could input a custom name at the time of patching you would probably still want to rename the TwlBg-232.cxi (or whatever) file to something more meaningful. I go in an rename with FBI or 3DShell after I create each patch.

The text file is what stores the previous .cxi file name. So if you find that the names are getting messed up then delete that text file. I should probably try to explain how it's supposed to work a bit better...

Ideally, you start off with no "TwlBg.cxi" in the "/luma/sysmodules" directory. Instead, have a few that you renamed such as "widescreen.cxi", "redshift.cxi" etc. Just make sure they all still have the file extension ".cxi".

Each time you create a new TwlBg.cxi patch:

1. Make sure to manually rename the old TwlBg.cxi to avoid overwriting it
2. Manually rename the newly created TwlBg.cxi file
3. Delete the twlbgName.txt file (as this will still hold the previous name of the old TwlBg.cxi)

Sorry, I've got to used to how it works so I forget it needs a bit of explaining. I was trying to keep it as a "simple" switcher and have the setup done with a proper file management homebrew.

 

[BETA215]

Hey @Nutez, I would recommend you to create a new thread for your custom Luma build. I have a question but don't wanna be off-topic here, you know. Maybe the same happens to other guys.

 

[PrincessLillie]

I've added a PoC "TwlBg Quick Switcher" feature to Rosalina in this custom Luma build. It lets you switch between custom named TwlBg.cxi files (e.g. wide.cxi, nightMode.cxi) stored in the "/luma/sysmodules" directory. It basically just renames the selected .cxi file to TwlBg.cxi and saves the previous name to a file so that it can be reverted on the next switch. Source if anyone would like to do a code review (C newbie here so feel free to get basic).

Cool. Can't say I really have a use for it (yet), but with enough work and reworking of the switching system, maybe this could be split into a separate app or even added to upstream Luma. I doubt it, but it's never an impossibility.

 

[r0achtheunsavory]

Just saw Twilight Menu++ got updated and widescreen mode was changed somehow. Does this cause any issues for TWpatcher 9/03 experimental build?

 

[ccfman2004]

Just saw Twilight Menu++ got updated and widescreen mode was changed somehow. Does this cause any issues for TWpatcher 9/03 experimental build?

Actually the 09.03 build is what causes the problems. It doesn't always make the widescreen work. Out the dozen or tries I only got it work once. Went back to an easier build that worked every time.

 

[r0achtheunsavory]

Actually the 09.03 build is what causes the problems. It doesn't always make the widescreen work. Out the dozen or tries I only got it work once. Went back to an easier build that worked every time.

It works for me, but I didn't update Twighlight Menu yet, which is why I asked if the new Twilight Menu release blows it up somehow.

 

[ccfman2004]

It works for me, but I didn't update Twighlight Menu yet, which is why I asked if the new Twilight Menu release blows it up somehow.

If you never deleted Widescreen.cxi before using the 09/03 build it's probably why it still works as the updated TwiLightMenu doesn't use Widescreen.cxi anymore. I have tried over a dozen or so time to get widescreen working on the 09/03 build and only had it work once. This was independent of my build of TwiLightMenu

 

[RadoMiami]

I've got 2 questions about TWPatch and DS widescreen in general:
1. Did anything happen with the 768*240 mode?
2. I've always wondered why instead of the widescreen being the full 5:3 of the 3DS, it's 16:10. Is there some technical or scaling reason why it couldn't be the full 5:3? Or did no one write any 5:3 codes for DS games?

 

[RocketRobz]

I've got 2 questions about TWPatch and DS widescreen in general:
1. Did anything happen with the 768*240 mode?
2. I've always wondered why instead of the widescreen being the full 5:3 of the 3DS, it's 16:10. Is there some technical or scaling reason why it couldn't be the full 5:3? Or did no one write any 5:3 codes for DS games?

1. Sono couldn't get it working properly.
2. The MTX scaler chip in the 3DS doesn't support scaling to the full 400x240 resolution.

 

[DyCerBR]

Just found out about this amazing piece of software when trying to run WarioWare Twisted with gyro controls.

Initially I freaked out that my 3ds' ds mode would brick because I use TwilightMenu++ just a little too much. But now, let me see if I understand: the anti-wear patch turned out to be unnecessary and we still have no idea what causes the wifi flash chip to go bad, right? Would it have any downside if I kept it enabled just in case anyway?

Is there any way or tool to check if my 3ds is writing to it unnecessarily and/or excessively?

Thanks a lot for this!

 

[playsaves3]

1. Sono couldn't get it working properly.
2. The MTX scaler chip in the 3DS doesn't support scaling to the full 400x240 resolution.

will you be able to make the image as sharp as a 4:3 with 16:10 without gpu scaling

 

[RocketRobz]

will you be able to make the image as sharp as a 4:3 with 16:10 without gpu scaling

That's not possible, afaik.
It's one of the reasons why GPU scaling is a thing.