Fizeau - Adjust color of your Switch screen

averne · Aug 31, 2020

I've finally been able to test for myself in docked mode. I've fixed a few scaling bugs in the client and officially released 2.0.0:
https://github.com/averne/Fizeau/releases/tag/v2.0.0

UltimateFight · Aug 31, 2020

Great update!

I have some suggestions for the overlay.
In the Fizeau overlay, pressing tesla's hotkey or touching a blank part of the screen will bring it back to the tesla menu, that's weird, why not just close the overlay like any other overlay?
Can the "Filter" option be placed at the bottom?I don't think it's an option that needs to be used more often than the "gamma"and "luminance".
Can you set a key to reset the value? Like press Y on the "luminance" and then reset it back to 0.00?

drrastovac · Sep 2, 2020

The latest version is working fine. Thank you.

W0NDERwaffle3 · Sep 4, 2020

Anyone have any good presets they can share , im too dumb to get this to work.

HideoKojima · Sep 8, 2020

Any luck of this working with SX?

mattyxarope · Sep 9, 2020

Shalashaska98 said:
Any luck of this working with SX?

Nope

notimp · Sep 14, 2020

W0NDERwaffle3 said:
Anyone have any good presets they can share , im too dumb to get this to work.

Install the latest atmosphere, then install all the prerequisites as stated in the github readme (If the atmosphere version is too old, the switch will now be in a bootloop back to the bootloader, shut the switch off, remove the sd card and delete the two folders you added in /atmosphere/contents/ - then the switch will boot again. After that update atmosphere, for real now..

).

Also Switch might need to be on firmware 9.0.0 or higher to use the current version of all stated prerequisites (Tesla Menu).

Boot up the switch, then start the fizeau nsp. It has a universal toggle, set that to active), then move over to color, set color temperature to max kelvin, brightness to 30 (or something reasonable) for both day and night periods.

Set both luminance sliders to default (center, so 0.0) positions. Gamma can be left at 2.4

Go back to the first tab and hit apply.

Now the overlay should basically be 'transparent'. At all times of day.

Then go over to color once more and slide the color temperature slider to the left. Go overboard at first - so you really see a difference. Then move back to the first screen, and hit apply.

Now your screen should really show a difference..

If all you want is to remove the blue tint on a Switch v1 screen, go back to the colors tab and select 6124 K for both day periods, then go back to the first screen and hit apply.

This should get rid of the blue tint on a Switch v1.

(To use 'blue filter mode' for night, just move the 'night' color temperature slider further to the left (and adjust brightness for that time window as needed). And hit apply.)

I havent measured color accuracy yet, I could, and I may do so in the future.

Adjusting gamma, would adjust - gamma (curve 'from black to white'), but as deactivating the overlay shows no adjustments in that curve, when set to 2.4 - its best to leave it at 2.4 (again, without having measured a grayscale ramp at different brightnesses yet.

).
Also - according to the diagram it would do that by only reducing the color green channel, which means, if you do that too much, white balance would get out of whack.

Luminance would decrease peak brightness (also by modifying the light output of the green channel), and there is absolutely no need to do that without a colormeter.

So the color temperature slider is your friend, really - all others (without a meter) should be left at the stated (default/transparent) values.
--

Also, thank you very much for coding this, the blue tint was really distracting while playing retro games. This helped immensely.

tnecniv43208 · Sep 14, 2020

I'm on latest atmosphere with fizeau 2.0, everytime I launch it my switch crashes with fatal error abort at 0x100, I have no sys modules on other than fizeau, are there any thoughts of what might be wrong? Other homebrews work perfectly

notimp · Sep 14, 2020

I'm on firmwre 9.2.0, latest atmosphere (0.14.2), latest fuse-primary.bin (make sure you also updated that), latest hekate bootloader (v5.3.2).

(Reboot payload in atmosphere switched to hekate v5.3.2, but you dont have to.)

Boot chain is hekate booting fuse-primary.bin (so basically fuse-primary.bin is the payload that gets used to boot up hekate).

Everything except replacing the reboot payload was left at default values. I've set up all of it today - and it worked.

edit:
BCT.ini in my case looks like this (current default one has all the exosphere entries removed), but I doubt that its that. But then again, this is something thats different from default in my case as well.

BCT0
[stage1]
stage2_path = atmosphere/fusee-secondary.bin
stage2_mtc_path = atmosphere/fusee-mtc.bin
stage2_addr = 0xF0000000
stage2_entrypoint = 0xF0000000

[exosphere]
; Note: Disabling debugmode will cause parts of ams.tma to not work, in the future.
debugmode = 1
debugmode_user = 0
; Note: Disabling usermode exception handlers will cause atmosphere to not fail gracefully under error conditions.
; Support will not be provided to users who disable these. If you do not know what you are doing, leave them on.
disable_user_exception_handlers = 0
; Note: It's currently unknown what effects enabling the usermode PMU register access may have on official code.
enable_user_pmu_access = 0

[stratosphere]
; To force-enable nogc, add nogc = 1
; To force-disable nogc, add nogc = 0

; To opt in to using Atmosphere's NCM reimplementation, add enable_ncm = 1

edit2: Also launching the app through album works as well as launching it (/homebrew launcher) through a game.

tnecniv43208 · Sep 15, 2020

Thanks for the reply, unfortunately after I updated Hekate and atmosphere it still doesn't work, BCT.ini looks exactly like yours without exosphere. The attached is the fatal error report created by launching fizeau, maybe someone would like to give it a look.

notimp said:
I'm on firmwre 9.2.0, latest atmosphere (0.14.2), latest fuse-primary.bin (make sure you also updated that), latest hekate bootloader (v5.3.2).

(Reboot payload in atmosphere switched to hekate v5.3.2, but you dont have to.)

Boot chain is hekate booting fuse-primary.bin (so basically fuse-primary.bin is the payload that gets used to boot up hekate).

Everything except replacing the reboot payload was left at default values. I've set up all of it today - and it worked.

edit:
BCT.ini in my case looks like this (current default one has all the exosphere entries removed), but I doubt that its that. But then again, this is something thats different from default in my case as well.

edit2: Also launching the app through album works as well as launching it (/homebrew launcher) through a game.

notimp · Sep 16, 2020

tnecniv43208 said:
Thanks for the reply, unfortunately after I updated Hekate and atmosphere it still doesn't work, BCT.ini looks exactly like yours without exosphere. The attached is the fatal error report created by launching fizeau, maybe someone would like to give it a look.

So strange... hope you get dev attention. Have the 'always on ftp' module active (ftpd), as well as the cheat engine thingy (Edizon), but apart from that, nothing - really...

Make sure the nsp is in the default folder (unter /switch), and in no other folder you might have moved it to (maybe some paths are hardcoded).

Also make sure you enable 'show hidden files' if you are on a Mac, to copy things over - some folders in the setup start with a dot (.), which indicates to MacOS, that they are hidden. You have to move over those as well.

I used Filezilla to copy over all files via ftp, and it showed hidden files (at least has a toggle somewhere to enable that, not sure if its the default behavior), so it was easy to copy them over - even on a Macbook.

Thats about all I can think of.

SkullHex2 · Sep 16, 2020

tnecniv43208 said:
I'm on latest atmosphere with fizeau 2.0, everytime I launch it my switch crashes with fatal error abort at 0x100, I have no sys modules on other than fizeau, are there any thoughts of what might be wrong? Other homebrews work perfectly

Same issue here, tho I'm not on the latest Atmosphere and I thought that was the issue (as if)
I'll try updating as soon as the new sigpatches are out (provided they aren't already) and get back to you

Edit: can confirm it still doesn't work, Atmosphere crashes when running the app via Homebrew Launcher (non-applet mode)

mathew77 · Sep 16, 2020

averne said:
officially released 2.0.0

Confirmed it, too — the latest build for now Fizeau-2.0.0-6b72dca doesn't work with the latest AMS 0.14.3 @ OFW 10.2.0.
Gives me this:

It was all good on the old AMS 0.14.2 @ OFW 10.1.0 though.

SkullHex2 · Sep 17, 2020

mathew77 said:
Confirmed it, too — the latest build for now Fizeau-2.0.0-6b72dca doesn't work with the latest AMS 0.14.3 @ OFW 10.2.0.
Gives me this:

View attachment 225064

It was all good on the old AMS 0.14.2 @ OFW 10.1.0 though.

Have you tried rebooting? I remember the same thing happening to me right after installing Fizeau, but before rebooting my console.

Anyways, I managed to get it working by replacing the version installed via Homebrew App Store with the latest release downloaded directly from GitHub.
it still feels very WIP: lots of graphical glitches when configuring a profile that may result in Atmosphere crashing (crashed twice for me, I wasn't even able to save any changes)

mathew77 · Sep 17, 2020

Digi_Ohhh said:
Have you tried rebooting?

Yes, same..

Digi_Ohhh said:
I managed to get it working

Do you have the latest OFW 10.2.0 and AMS 0.14.4 (like my setup)?.. Thank you in advance for your help.

SkullHex2 · Sep 17, 2020

mathew77 said:
Yes, same..

Do you have the lates OFW 10.2.0 and AMS 0.14.4 (like my setup)?.. Thank you in advance for your help.

No, I'm on 10.1.0 and AMS 0.14.3
Maybe there's something wrong with the latest OFW, but I doubt it ... easiest way to get the developer's attention is to open an issue on GitHub imho

mathew77 · Sep 17, 2020

Digi_Ohhh said:
No, I'm on 10.1.0 and AMS 0.14.3

As I wrote, it was all good on 10.1.0.

Digi_Ohhh said:
Maybe there's something wrong with the latest OFW, but I doubt it ... easiest way to get the developer's attention is to open an issue on GitHub imho

Okay, I'll try!

averne · Sep 17, 2020

The problem here is not your FW version, it's your AMS version.
The sysmodule checks the exosphere API version during boot and crashes when it's found to be lower than what it was compiled with.

averne · Sep 17, 2020

https://github.com/averne/Fizeau/releases/latest

Make sure to update to AMS v0.14.4 beforehand.

UltimateFight said:
Great update! I have some suggestions for the overlay.
In the Fizeau overlay, pressing tesla's hotkey or touching a blank part of the screen will bring it back to the tesla menu, that's weird, why not just close the overlay like any other overlay?
Can the "Filter" option be placed at the bottom?I don't think it's an option that needs to be used more often than the "gamma"and "luminance".
Can you set a key to reset the value? Like press Y on the "luminance" and then reset it back to 0.00?

The reason the overlay closes and goes back to the menu is that when going hidden, the overlay doesn't free its service session. So if a user opens the applet client while the overlay is hidden, the sysmodule will crash because it only supports one session at a time.
I implemented your other suggestions.

SkullHex2 · Sep 17, 2020

averne said:
The problem here is not your FW version, it's your AMS version.
The sysmodule checks the exosphere API version during boot and crashes when it's found to be lower than what it was compiled with.

I'm not sure I get it … if he's on Atmosphere v0.14.4, how can the exosphere API version be lower than the one the sysmodule was compiled with?
Sorry to bother you but I'd like to understand better

Well-Known Member

Mell-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Lovin' life.

Well-Known Member

Lovin' life.

Well-Known Member

Lovin' life.

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum