Getting odd results with filter.hue

Solar2D Advanced Graphics
#1

I am getting odd colored results on my Nexus 4 when using filter.hue 

Is this a platform problem? It looks fine on the simulator. Haven’t tested on other devices…

Thanks,

Gullie

#2

Hi Gullie,

I have been trying to get answers on this one for a long time - see http://forums.coronalabs.com/topic/47176-fixed-hue-filter-issue/

There is a bug filed, but no update. The repo is extremely easy - add a hue filter to any image on a 1st gen Nexus 7 with hue angle set to 0 and the image is incorrect. It seems to behave on some other platforms, but we are unable to add to our app until we are confident it isn’t messing up on other android devices.

David

#3

Can you print out the value of:  system.getInfo( “gpuSupportsHighPrecisionFragmentShaders” )

and see what it shows on your device. 

Also what happens if you set the color angle to 360 instead of 0?

Rob

#4

Hi Rob,

So the Nexus 7 1st gen returns false for the fragment shaders, and the 2nd gen returns true.

Now hue is a basic filter, and is not listed in the “may not work properly” section in the filters doc (http://docs.coronalabs.com/guide/graphics/effects.html), based on GPU requirements.

Setting to 360 instead of 0 makes no change.

Offsetting to other numbers does effect the result, but not sure how you would do this if it is a per device problem.

Simplest repro is to draw the corona icon to screen - if you apply a hue of 0 or 360 to it, it renders green on Nexus 7 gen 1.

Any further thoughts on a direction forward here?

Thanks

David

#5

Hey Rob, 

On my Google Nexus 4 system.getInfo( “gpuSupportsHighPrecisionFragmentShaders” ) returns true. Some of the other filters seem to be working fine BTW. 

Setting angle from 0 to 360 has no effect. 

In my case the angle of the filter.hue is shifted every few seconds. The first angle looks to be correct. The following angles on the same image are not. (image is red… is shifted to green and looks ok. Further angles produce odd coloration.)

#6

Hey Rob,

Any word on this filter.hue issue??

#7

Can I get you to file a bug report for Engineering?  Make sure to include a config.lua, and build.settings in addition to any assets that are needed to show the problem.  Use the “report a bug” link at the top of the page.

You will get an email with a case #.  Please post that here as a reference.

Thanks

Rob

#8

Here is a screenshot of he issue. Left= Sim; Right = Nexus 4

Bug #: I will update when I get the reply email.

Notice the two-toned effect. The default image is a red gradient

Relevant Code:

fishOriginal.fill.effect = "filter.hue" fishOriginal.fill.effect.angle = math.random( 360 )
#9

So, I created the bug but never received an email with the bug number. Should I submit another one?

#10

There is only one open bug in the bug tracker with your email address and it’s documentation related.  I would suggest re-submitting it.

Rob

#11

I submitted again and I still don’t see a number. I am working from the Philippines on a horrible internet connection so there is that…

At what point am I supposed to receive a bug tracking number?

The text of the bug is:

As the title suggests, filter.hue yields undesired results on my Google Nexus 4.  

In my case I am tinting a red gradient and 1) The image becomes 2-toned in appearance at some angles. 2)When it isn’t 2-toned in appearance the colors are not reflected accurately.

#12

The bug # comes in an email and I think it’s only in the subject of the email.  You can check your spam to see if you got it.  But I searched for you email address in the bug tracker and don’t see any filed bug reports.

Rob

#13

I have submitted it about 10 times. No dice. I have not gotten a single email confirming a bug submission. I don’t think it is working. The Title of the last few submissions has “hue.filter” or “Hue Filter” in it.

It’s making me feel crazy.

It does take me to the following page so something is happening. Any other suggestions?

"Corona Issue/Bug Submission

Thank you for your submission. We will do our best to evaluate your case and respond as quickly as possible."

 

#14

I still can’t find anything by your address, but there is a bug filed on this:

Case# 35892

Rob

#15

Is there a way for me to see the bug?

Also, how can I track progress? Or do I just look for a note in the builds released?

#16

Visibility into the bug tracker isn’t very good.  We generally will post back to the thread when we’ve solved it, if the thread is part of the bug submission.  It should get listed in the release notes.

However, I know the engineering team has been asked to look at this, but I’ve not seen any responses about it yet. 

Rob

#17

Hi Gullie,

I have been trying to get answers on this one for a long time - see http://forums.coronalabs.com/topic/47176-fixed-hue-filter-issue/

There is a bug filed, but no update. The repo is extremely easy - add a hue filter to any image on a 1st gen Nexus 7 with hue angle set to 0 and the image is incorrect. It seems to behave on some other platforms, but we are unable to add to our app until we are confident it isn’t messing up on other android devices.

David

#18

Can you print out the value of:  system.getInfo( “gpuSupportsHighPrecisionFragmentShaders” )

and see what it shows on your device. 

Also what happens if you set the color angle to 360 instead of 0?

Rob

#19

Hi Rob,

So the Nexus 7 1st gen returns false for the fragment shaders, and the 2nd gen returns true.

Now hue is a basic filter, and is not listed in the “may not work properly” section in the filters doc (http://docs.coronalabs.com/guide/graphics/effects.html), based on GPU requirements.

Setting to 360 instead of 0 makes no change.

Offsetting to other numbers does effect the result, but not sure how you would do this if it is a per device problem.

Simplest repro is to draw the corona icon to screen - if you apply a hue of 0 or 360 to it, it renders green on Nexus 7 gen 1.

Any further thoughts on a direction forward here?

Thanks

David

#20

Hey Rob, 

On my Google Nexus 4 system.getInfo( “gpuSupportsHighPrecisionFragmentShaders” ) returns true. Some of the other filters seem to be working fine BTW. 

Setting angle from 0 to 360 has no effect. 

In my case the angle of the filter.hue is shifted every few seconds. The first angle looks to be correct. The following angles on the same image are not. (image is red… is shifted to green and looks ok. Further angles produce odd coloration.)