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

[Sono]

I appreciate the effort, OP, but your guide is kind of a mess...

That's what I get for being too slow

But yeah, in hindsight I should've done the patcher first, not the thread

 

[TuxSH]

Maybe I could hotpatch twlbg in luma for the filters, already did that kind of stuff once or twice.

Btw I did some of your research at some point, patched some bytes (possibly the same as those described here), but did not see any apparent change. Thank you so much for properly finishing this research.

 

[Goloki]

@ahezard has implemented the deblur patch into his twl_firm_patcher.

Hmmmm. I'm getting an error trying to run this.

I'm pretty sure the file is correctly named (firmware_twl.bin), has the right size (1.64MB) and in the correct folder (input). I got it with GodMode9, following a short tutorial posted in this thread.

Any ideas?

 

[MuperMumpjanSario]

Hmmmm. I'm getting an error trying to run this.

I'm pretty sure the file is correctly named (firmware_twl.bin), has the right size (1.64MB) and in the correct folder (input). I got it with GodMode9, following a short tutorial posted in this thread.

Any ideas?

Someone didn't read the README

 

[xxNathanxx]

Thanks, man, this is really cool.

 

[BOBdotEXE]

Based on the 3 filters (1x (START+SELECT), 1.25x (default), and 1.5x (used only in GBA mode)) found inside TWL_FIRM, I reverse engineered most of the image matrix processor hardware, and made my own filters to show that sharp upscaling can be done.
-snip-
If it hardlocks then you didn't find the right pattern, or your TwlBg version is not good.
[/spoiler]

WOW, this is AWESOME, chrono trigger DS keeps getting better in better!
First, DSi mode speed, then higher FREQ sound, now better scaling!

I made a SBS comparison video, you can find that here:


(Zoomed in comparisons


Edit: CRAP! I forgot to mute the audio

 

[Sono]

-snip-

Now I see why some people are against this patch. Yeah, I can still see room for improvement on these matrixes. But some areas look undoubtedly infinitely better with the simple 1.25x matrix.

 

[BOBdotEXE]

Now I see why some people are against this patch. Yeah, I can still see room for improvement on these matrixes. But some areas look undoubtedly infinitely better with the simple 1.25x matrix.

I have yet to try the 1.5 patch, but even if the 1.5 is a bit worse, it's still nice to have the option.

Thanks for working on this!

 

[PokeNas]

I appreciate the effort, OP, but your guide is kind of a mess...

So I tried making a script to automize the extracting and rebuilding process as much as possible.

Script: https://mega.nz/#!1mYgHYRL!7YZZy_MabrmLq2hZw4IP2GKFshuk8jfMe1hUPfh3lLM
Filename: Run.bat
MD5: a064ebbb78cf22fc327b5dbb660a6e89

If you're (understandably) wary of running random scripts off of a tech forum, you're more than free to open the script in a text editor and judge its legitimacy for yourself. I've tried making using it as foolproof as possible.

Prerequisites (you will need the following):

• Access to GodMode9
• A PC and a way of moving files between it and the SD card (eg. directly or via FTP)
• A hex-editor for PC (HxD is a good one), and basic knowledge on how to use the program
• FirmTool (must be installed via Python)
• 3DSTool (must either be in script directory or system PATH)

Spoiler: Usage Guide

1. Boot into GodMode9 on your system.
2. Once loaded, go through [SYSNAND CTRNAND > title > 00040138 > *0000102 > content > ********.app] and mount the .app file.
   • The "*" is a wildcard, it can fit any alphanumerical sign.
   • Select the .app file with the highest number.
3. Once you're inside the mounted .app, enter the [exefs] folder, select the .firm file there, and copy it to [0:/gm9/out].
4. Turn off your system, remove the SD card from it and connect it to your PC (or use FTP to wirelessly transfer files, it's up to you).
5. Travel to [SD:\gm9\out\] on your PC, and copy the .firm file somewhere onto your PC (preferably in own folder).
6. Move the 'Run.bat' script (download at the top of my post) into the same directory as the .firm.
7. Rename the .firm file to "TWL.firm" and run the script.
   • If you encounter this message while trying to run the script, please make sure you have both FirmTool and 3DSTool installed and findable by the script.
   • 
8. Please read the script output, follow it carefully, and press the Y key to continue after doing so:
   • 
9. Wait until you get this wall of text:
   • 
10. Open the code.bin that appeared in the script directory in your hex-editor, apply and save the patches of your choice (as stated above), and press the number key stated to continue with the script.
11. Wait until you receive this message:
    • 
12. Check your script's directory. There should now be a "TwlBg.cxi" inside it. Copy TwiBg.cxi onto your SD (again, either directly or via FTP) under [SD:\luma\sysmodules\].
13. Reinsert the SD card into the system (or reboot it if you used FTP) and power it on while holding SELECT to enter Luma's configuration menu.
14. Ensure that these two options are ticked:
    • "Enable game patching"
    • "Enable loading external FIRMs and modules"
15. Press START to save your settings.

And that should be it.

So should we go ahead and use this patcher or wait for OPs version? Also, when running DS games after the patch, would I need to hold any buttons for it to take effect?

 

[RocketRobz]

Also, when running DS games after the patch, would I need to hold any buttons for it to take effect?

No.

 

[Sono]

So should we go ahead and use this patcher or wait for OPs version?

Yes please, wait for my patcher, I found and fixed the bug, so it'll be done in the upcoming few hours if I don't break something else.

Also, when running DS games after the patch, would I need to hold any buttons for it to take effect?

No, these are code patches, they are automatically applied from the /luma/sysmodules/ directory.

 

[Reynardine]

I'm just a newbie here, I stumbled upon your guide by accident.
Anyways, I can't thank you enough for sharing this, Sono.

I've just tried the sharp 1.25x scaling for the first time and it looks so much better.
This is just wonderful, finally I can enjoy my old ds games again.
I couldn't stand the blurriness...

I've also tried the 1.5x mode, it works, but it seems rather pointless when part of the screen area is missing.

The offsets were quite a bit further down in my code.bin, by the way.
Maybe its because I've updated to firmware 11.10.0-43E recently.

Here's the 1.5x scaling offset in my code.bin:

At 0xC9A.

And here's the 1.25x scaling offset:

At 0x4B094.

 

[goncalodoom]

I'm just a newbie here, I stumbled upon your guide by accident.
Anyways, I can't thank you enough for sharing this, Sono.

I've just tried the sharp 1.25x scaling for the first time and it looks so much better.
This is just wonderful, finally I can enjoy my old ds games again.
I couldn't stand the blurriness...

I applied the 1.25x patch and it looks even blurrier than stock. How do you make it look sharp? I'm using a new 3ds XL

 

[RocketRobz]

I applied the 1.25x patch and it looks even blurrier than stock. How do you make it look sharp? I'm using a new 3ds XL

It should look like what's in the videos in this page.

 

[MrLuigix64]

Noice work on the filter. I wanted to apply it on my O3DS, but im not sure, what version to use, can I use the x1.5 on my small O3DS? o only the x1.25 can be used?, its unique on every 3DS?

 

[RocketRobz]

Noice work on the filter. I wanted to apply it on my O3DS, but im not sure, what version to use, can I use the x1.5 on my small O3DS? o only the x1.25 can be used?, its unique on every 3DS?

Use x1.25.

 

[Sono]

Noice work on the filter. I wanted to apply it on my O3DS, but im not sure, what version to use, can I use the x1.5 on my small O3DS? o only the x1.25 can be used?, its unique on every 3DS?

It's the same resolution on any 3DS, so 1.5x will always have its right and bottom sides missing, and 1.25x is always the default.

I think you should use 1.25x, because 1.5x is very hard to play with if it uses the touchscreen.

 

[Bluespheal]

Could it be possible to use one resolution on the top screen and another on the bottom screen?

 

[Sono]

Could it be possible to use one resolution on the top screen and another on the bottom screen?

Ehh... I think the complexity of the OpenGL driver is too big for me to figure out how to size the screens independently :/

Edit: I can however move the screens up-down-left-right when in 1x mode

 

[RacsoSakuraba]

With this would it be possible to do a full screen mode on the upper screen?

EDIT: On the other hand, if I understood correctly: when using this patch x1.25, which is the same original size, applying it removes the blurring effect and weird color that comes in stock?

Edit: I can however move the screens up-down-left-right when in 1x mode

EDIT2: Oh god, this is great.