Just checking in on this thread, @Sono any update? Any help I can provide?
While it is still not fully functional yet (everything works, but I'm missing/broken the functionality in the permutation fitter UI), I'm working on the DRM currently, so repair shops can't just use the build I upload here.
I'm not sure how long the DRM will take to build, but considering that I'm ill and starving, don't expect it in a few months.
If you want to make this homebrew from scratch then I'll be more than happy to assist with that, but my code will not come out until the DRM is ready.
I'm familiar with coding and building but I've never created anything for the 3ds. If you think it's a good 3ds noob project I'd love to give it a try! Not sure where to start though, and what you'd be able to provide. Not the code you have now I guess since you're going to DRM it?
Hello @Sono I wanted to take some news about your brigthness cal project. Any updates please ?
Okay thanks no problem, you can do it.Ah sorry.
I need to stop worrying about bricking my 3DS and just try it.
Don't have enough disk space to make a NAND backup though...
I don't give out homebrew without making sure everything works first.
I still value that the functionality works as expected.
Did this project ever make it off the ground?
I’m pretty interested as I’ve taken on a hobby of fixing up New 2DS XL consoles with broken top screens and it would be super cool to know how to make them look better when I use replacement hardware.
Did this project ever make it off the ground?
I’m pretty interested as I’ve taken on a hobby of fixing up New 2DS XL consoles with broken top screens and it would be super cool to know how to make them look better when I use replacement hardware.
I don’t think so, but @Sono knows better.
Thanks for the update, and I hope you get the care you need soon. It’s rough that you’ve had to bear a long wait like that.Yes, it's basically proof-of-concept "finished", except I don't write the results back to the config. Unable still to write the remaining lines of code.
Don't expect miracles btw, as this very early version is very difficult to use. You have to tick priority values in a grid, and depending on that it will bruteforce a curve that may somewhat match to the brightness values you have manually provided.
It's a really tedious process, it requires either a lot of eyeballing or two matched brightness sensors, and even after all that, you may still get an inaccurate curve.
I'll probably have to produce a video (pretty sure expect 20mins) on how to use this prototype build, how to encode the matrix, how it affects the accuracy of the curve, etc.
I already have improvements which mitigate most of the tedium, but I still didn't release a working build, and I'm having difficulty staying alive.
I did *not* forget about this, it's just that the healthcare system is overloaded, and thus I need to wait months for even the most basic care. If I don't miss my long-awaited appointment due to unforseen reasons, and the care ends up working, I'll probably finish the prototype around july first week, verify with a repair shop I'm close contact with, then once we can verify that it's safe to use and works, I'll release that prototype build, so at least we have *something*. I'm so annoyed by people replacing their HWCAL files for nothing, as it's the WRONG method.
Yes, it's basically proof-of-concept "finished", except I don't write the results back to the config. Unable still to write the remaining lines of code.
Don't expect miracles btw, as this very early version is very difficult to use. You have to tick priority values in a grid, and depending on that it will bruteforce a curve that may somewhat match to the brightness values you have manually provided.
It's a really tedious process, it requires either a lot of eyeballing or two matched brightness sensors, and even after all that, you may still get an inaccurate curve.
I'll probably have to produce a video (pretty sure expect 20mins) on how to use this prototype build, how to encode the matrix, how it affects the accuracy of the curve, etc.
I already have improvements which mitigate most of the tedium, but I still didn't release a working build, and I'm having difficulty staying alive.
I did *not* forget about this, it's just that the healthcare system is overloaded, and thus I need to wait months for even the most basic care. If I don't miss my long-awaited appointment due to unforseen reasons, and the care ends up working, I'll probably finish the prototype around july first week, verify with a repair shop I'm close contact with, then once we can verify that it's safe to use and works, I'll release that prototype build, so at least we have *something*. I'm so annoyed by people replacing their HWCAL files for nothing, as it's the WRONG method.