Eeeek . We don’t want Overheating . Work makes Heat so it is Over Working .
no, I’m saying I don’t know 
What I think is probably the different things you saw are because of one of the random bugs in the app. I don’t think anyone manually flips a switch. But I really don’t know.
1 Like
no, but Facer has determined that these shaders have hardware requirements that a lot of the older watches do not meet. So I think the app either gets the info from your watch or based on what you select and will show it as available or not accordingly. There is a page somewhere in the Facer website that has more specifics about which watches are supported. I don’t have that link handy though.
1 Like
As far as I know this is all that has been published .
I have not searched the Documentation .
I think the Production of these Faces is Exclusive to the Partners so they must have some other information .
.
.
My watch is on the compatibilty list that Facer provides.
1 Like
@BillieJackFu . Well done finding and posting that . Looks to me like you have to contact Little Labs . Have you tried one of the other SHADER faces . It might be just that one that has a Bug .
.
.
It should work. But there are still some bugs around the implementation of the shaders. Be sure you have the Pixel selected in the Facer app settings. Also try logging out of the app and back in. Possibly re-booting your watch… these are some of the usual fixes for random glitches.
1 Like
So I found a workaround.
If I try to load the face from the website or on the phone app it won’t allow me, but if I use the watch app and select the watch face it works fine. So the watch has no problem with the face itself. Seems to be a hiccup between the web/app.
3 Likes
@kvansant
Only partner watchfaces are for sale. All of my premium faces are only a gateway to sell the premium upgrade. Since I have two accounts, one free and this one pro upgraded, I can test for things like that. 
2 Likes
ah, I did not know that, but it makes sense.
2 Likes