I don't think so. This actual build is based-on Luma 10.2, which isn't compatible with the latest system version 11.14Does this work with the latest firmware update yet?
Just remains to wait for a new version based-on latest Luma
I don't think so. This actual build is based-on Luma 10.2, which isn't compatible with the latest system version 11.14Does this work with the latest firmware update yet?
No worries, the "Change screen brightness" interface works similarly to the official Luma version. When you select it from the Rosalina menu there is an explanation of the controls. However, tt might be that you need to press start first so that you can see both the top and bottom screens. Then try adjusting left and right a few times to see if there is a noticeable change in brightness.I feel like an absolute fool, but I can't figure out how to activate the features included in this unofficial Luma 10.2.1 build--namely the LCD brightness customization. I have the boot.firm placed in the root of the drive and everything appears to be working, but I can't seem to adjust brightness as described. Is there a simple button combo I'm missing?
Apologies, it's not something that I test for personally so it's probably been broken for a while. I brought in some changes from Nanquitas & PabloMK7 that I had missed before. Hopefully that will have fixed it.InputRedirection not working on this build, working on the official build.
TwlBg.cxi is a file generated using Sono's TWPatcher. It allows you to choose different scaling and filters to apply in DS/i mode. Unfortunately, it's not able to turn down the actual backlight level like Rosalina can, but you are able to apply a bluelight filter and faux brightness-reduction filter.What exactly is this TwlBg? Can I use this to implement the screen brightness modifications in Rosalina to DS games?
Oh yes I remember using Sono's great LCD Tweaker before. Unfortunately, that was before I started messing around with homebrew myself, so I didn't save a copy of the (now unavailable) source code. The current brightness limits are imposed by the function used to set brightness. I don't really have experience with hardware and registers (library script-kiddie ), but maybe it can be done here?
Thanks, though I guess it's not really "full-auto" since it still needs to be applied via Rosalina first, but it does have the newer feature of being reapplied after sleep. I am interested in the idea of lowering the backlight and applying redshift as early as possible via holding a button when Luma is booting up. I'll need to experiment to see if I can get the timings right.I just remembered again that this build exists. I'll have to give it a try myself, as I actually like the idea of automatic CTR_Redshift.
I actually want to use the eShop, but I'm still on an ancient system version and ancient Luma, so I'll choose this.
Absolutely, gotta catch 'em all! Your pioneering hardware work was what got me motivated to aggregate and tweak interesting Rosalina features haha. All that stuff sounds great, I just might actually have to work out how best to make features optional with config now XD.Although I wonder, would you be interested in some of my other released and unreleased patches and system-modifying utilities?
Things like repurposing the 3D slider, software-controlled volume controls, completely disabling the 3DS speaker (headphone-jack only), etc.
I forgot to check that . Patching SetBrightnessRaw sounds like a good plan, but I wouldn't know where to start on doing it XD. I was able to get low brightness working for now though with a hacky implementation.The source code is actually still up, I just changed my github username
https://gist.github.com/SonoSooS/a1e339d67ef30b8394e572a2df6dcd27
It does use hardware regs, but the problem is that you need to patch gsp (especially on new3DS) to make it stay for more than a fraction of a second... Perhaps the better solution instead would be to patch the limitations of SetBrightnessRaw to allow the full range of brightness controls.
Yup, this Luma build is the best one.dude this is awesome thank you
Darn, I thought I had got it stable since it works on both my o3DS and n3DS consoles... Which console are you using? Have you had a screen replacement? Are you trying to use the extended limits? Could you try setting the brightness to the lowest level in the official system settings first? Does it make a difference if you press the d-pad quickly or hold it down? Putting the console to sleep is a quicker way to reset the brightness if things do go wrong.Hey, I'm having a strange issue with the latest version:
When I try to change screen brightness on Rosalina menu, the top screen reports an incorrect value (97 when it should be 48, like the bottom's) and if I change them, the top screen automatically goes to the maximum value (extended limit) and I can't change it unless I reboot the system.
Darn, I thought I had got it stable since it works on both my o3DS and n3DS consoles... Which console are you using? Have you had a screen replacement? Are you trying to use the extended limits? Could you try setting the brightness to the lowest level in the official system settings first? Does it make a difference if you press the d-pad quickly or hold it down? Putting the console to sleep is a quicker way to reset the brightness if things do go wrong.
Interesting, did you have the same problem with brightness using the official Luma build in Mario Kart 7? If you weren't using the extended limits then it shouldn't be using the extra code that I added (which is more likely to be unstable). I had a lot of trouble trying to implement the extended limits without constantly causing the max brightness bug you seem to have had. So unfortunately, I don't think I'll be able to solve that specific case and you will just need to use the workaround for now. Sorry about that...Hey! So, it actually only seems to happen when I play Mario Kart 7 and try to access the back light settings in-game. If I do it from the Home Menu or from Box Boy, it works as intended.
I have a New 3DS XL, never had a screen replacement. I didn't try using extended limits. I'll try setting the brightness to minimum in the system settings to check that, but the "set brightness on main menu first" workaround is good enough for me. Holding or tapping the d-pad doesn't change anything.
Edit: Oh yeah, I forgot to ask: what does the plugin loader do? I ask because it is set to [enabled] and I don't remember if I accidentally enabled it or what.
Interesting, did you have the same problem with brightness using the official Luma build in Mario Kart 7? If you weren't using the extended limits then it shouldn't be using the extra code that I added (which is more likely to be unstable). I had a lot of trouble trying to implement the extended limits without constantly causing the max brightness bug you seem to have had. So unfortunately, I don't think I'll be able to solve that specific case and you will just need to use the workaround for now. Sorry about that...
To use the plugin loader: you'll need to setup the "default.3gx" plugin in "/luma/plugins" so you can activate it in-game by pressing the Select button. It's probably enabled by default but you can safely switch it off and it will stay off in future. The plugin is another way to active cheats and it also let's you search the in-game memory to create your own. The best place to get up-to-date information on that would be Nanquitas' Playground since the CTRPF thread can be confusing due to outdated discussions.