Looks like it's a clash with Actual Window Manager. Adding f.lux to its exclusions solves the problem.

Upvote. My TypeMatrix keyboard has the numpad integrated into the regular key block via [Fn]/[NmLck]. I frequently use [ALT]+NumCode to type special characters (which are not available, even on a US-intl layout with a ton of dead-keys ;) ) but f.lux somehow doesn't differentiate between [PgUp]/[PgDown] and the integrated numpad, when activated, which overlaps with those same keys.

And thanks for the useful app. :)

Hi,

This feature would be greatly appreciated for me also.
I access my computer from Remina (RDP) installed on a completely locked Raspberry (no rights).
So client install is not an option.

Thanks you so much !

@mrs-smith said in Strange pixilation:

Seriously? Is there no one here from f.lux who can help me fix this problem?

You are waiting on only 2 people, and they have busy lives between f.lux and their own personal lives. They will reply, just be patient.

Thanks, don't know how I missed that

You can have any browser you want as your default. I have Firefox set as my default (but that doesn't mean f.lux is using Firefox). I don't understand why you are seeing some sort of indication that you have to have Internet Explorer set as your default. I never saw any such indication. Where did you get f.lux from?

Choose the slowest transition speed in the f.lux options.

Hm. It looks like maybe I had "disable on full screen windows" checked. Not sure why it was doing what it was doing, but unchecking that seemed to make it stay on consistently.

Thought I'd bump this since it's been well over two weeks, 37 views and not a single response. I'll keep watching the tumbleweed blow by.

Thankyou, this solved the issue for me and I'm able to get grayscale mode working on Windows 7.

Perhaps a popup when you enable the mode on windows 7 that lets you know to change to an aero theme, with a 'don't remind me again' checkbox.

The issue only happens on 1 of my 4 screens, and the screen that is chosen is random when the bug happens.

Curious - are you at work during these hours?

The study you mention about green light is measuring light in a way I would not recommend - all the measurements are normalized to "luminance". Because they measure in cd/m2 and not equal photons, I believe they are testing 20x as much blue light as green, so it is not conclusive at all - if you are using 20 times as many photons you'd certainly expect it to make pain worse.

We have more work to do in understanding when people experience the greatest light sensitivity due to migraine, which is why there is no schedule for headaches in f.lux right now, even for removing blue light.

The few studies that have looked at the times of migraine suggest that the first half of the day is the most sensitive, but other people report that it ramps up later in the day.

If we can understand how to automate it, we will, but for now perhaps the right answer is to make the manual controls easier to use in the meantime.

Can you post your driver info here?
The GPU should not be required more than usual - we do everything through Windows.