Hi! As I did't find any GitHub repo for this to make a feature request, I'll ask here. Is it even possible to rotate both screens for games that work in book mode? Like sudoku by my brain academia
You mean, rotate by 180 degs?
Hi! As I did't find any GitHub repo for this to make a feature request, I'll ask here. Is it even possible to rotate both screens for games that work in book mode? Like sudoku by my brain academia
I tested this out just now on my New 3ds (non-xl) and I have a few observations. Firstly, in the "Bilinear+4grid" above, there appear to be exactly 4 pixels in each "box" of the grid, which is not the case in the experimental 4grid, which by my counting contains either 9 or 16 pixels (eyesight willing...).This is not a release build, don't use any patch other than rtcom.
Added experimental 4grid filters, I need some feedback.
It definitely needs tweaking, but I need to know how it looks to others as well, and if someone very well versed in emulator filters could chime in to help me tweak it so it doesn't look so off.
can 800px mode be implemented now that we have gpu scaling?Try using the link above your post, that should contain it.
--------------------- MERGED ---------------------------
MTX supports only up to 512px wide output, so without a proper GPU scaling patch it won't be possible to utilize this feature :/
can 800px mode be implemented now that we have gpu scaling?
Hey, does TWPatcher's widescreen mode support ROM hacks of certain DS games, or am I only able to use the vanilla ROMs? Because I tried to use the widescreen patch on Pokémon Renegade Platinum but it didn't work, and I double-checked to make sure Platinum was supported (and it is). I regenerated the patch at least twice after that and got the same result each time.
Then why is it compatible with the normal ROM but not the hack? Because I also have the unpatched ROM on my 3DS, and doing the exact same thing with my vanilla Platinum ROM works just fine. The ROM hack is the only one that is experiencing the issue, so while vanilla Pokémon Platinum is widescreen-ified just fine, the Renegade Platinum ROM hack, as you put it, "literally does nothing".The widescreen patch literally does nothing other than stretch the output of the DS(i)/GBA on the 3DS' display.
Games need to be patched to squish the graphics, and let them be widened again by the 3DS-side (this is called anamorphic widescreen), and it doesn't quite work in 2D games due to the limitations of the 2D engines.
In 3D games, usually only the aspect ratio value needs to be patched (afaik it's 0x5AAA or something like that), but some games need extra patches on top of that.
The widescreen cheat codes are not implemented for ROM hacks, due to the possibility of value offsets differing from the original.Then why is it compatible with the normal ROM but not the hack? Because I also have the unpatched ROM on my 3DS, and doing the exact same thing with my vanilla Platinum ROM works just fine. The ROM hack is the only one that is experiencing the issue, so while vanilla Pokémon Platinum is widescreen-ified just fine, the Renegade Platinum ROM hack, as you put it, "literally does nothing".
I was about to ask what the last four letters mean, but then I saw that you were referring to them as cheat codes - it's not cheats that I'm having problems with, it's the widescreen itself not appearing. Unless I need the BIN file to force-enable the widescreen, in which case there are three BIN files where the first four characters are exactly the same and I have no idea which one to use.The widescreen cheat codes are not implemented for ROM hacks, due to the possibility of value offsets differing from the original.
You could try adding support for the ROM hack by downloading the cheat from here, to "sd:/_nds/TWiLightMenu/extras/widescreen/", and renaming the .bin file to the ROM's full filename with only the addition of ".bin" at the end with no changes to the existing extension.
The first 4 letters represent the title ID, which can be found in TWLMenu++ by pressing the Y button for the selected ROM.
Hello everyone,
I’m facing an ongoing issue with my Nintendo New 3DS XL related to the D-Pad. This problem started after I used TWPatch multiple times to apply a widescreen patch. The D-Pad began to move the cursor on its own, without any input from me.
In an attempt to resolve this, I’ve tried the following:
1. Repeatedly reapplying the patch in TWPatch, hoping the problem would disappear. I experimented with different settings within the patching process. Sometimes this didn’t help, and other times, the issue seemed to be fixed for about 10 minutes before returning again.
2. I’ve noticed that this issue only occurs in the standard console interface and while playing games. There are no problems with the D-Pad in the TWPatch menu itself or in any homebrew applications.
I’m curious if anyone else has faced similar issues after using TWPatch for widescreen modifications. This problem seems quite specific and I haven’t been able to find a permanent fix.
Is there perhaps an option to reset everything back to its original state before the widescreen patches were applied?
Any insights, advice, or suggestions from those who might have experienced something similar would be very helpful.
Thank you for any assistance you can provide!
Have you considered filters like xBRZ or a CRT scanline filter? I'd be willing to pay you decent sum of money for either of those.
Also maybe a 2x option that crops the sides but keeps pixel perfect?
Can i in TWL Patch calibrate witch Redshift only TOP screen, not both?This is not a release build, don't use any patch other than rtcom.
Added experimental 4grid filters, I need some feedback.
It definitely needs tweaking, but I need to know how it looks to others as well, and if someone very well versed in emulator filters could chime in to help me tweak it so it doesn't look so off.
Can i in TWL Patch calibrate witch Redshift only TOP screen, not both?
In 3Ds mode i use Luma filter and as a result have two identity color brigtness screen. In DS mode upper screen too much blueish for me. Distracts)Sadly no, there is not enough memory to store curves for both screens.
What do you need it for? There might be a different way.
In 3Ds mode i use Luma filter and as a result have two identity color brigtness screen. In DS mode upper screen too much blueish for me. Distracts)