display.setDefault( "textureWrapX", "repeat" ) breaks on some devices

Solar2D Advanced Graphics
#21

Okay well I have some results. Firstly, there really isnt anything to see on the screenshots. Its all blank expect one button which manages to  load at the beginning until the graphics break. 

So I tested your example. All good. I see the texture was 256 so I swapped my stars.png. - it breaks on the Nexus7. I had a quick look again at the texture and see its 512x400. Oops I thought. Guessing this should be square so I go back to the app that broke and check that texture. Well thats square 512x512. So how come that is breaking still? I use my code  that I pasted above and that doesnt break so now im confused!. One last test is that I copy this bit from your example and paste in my breaking app, after I set up my filled objects:

–display.setDefault( “textureWrapX”, “clampToEdge” )

–display.setDefault( “textureWrapY”, “clampToEdge” )

Now it doesnt break. 

The stars.png is not used anywhere else in the game,

It seems that leaving that texture wrap setting as it is after the fill objects are set up breaks the game. 

Makes me wonder if its a good idea setting up a global graphics setting then setting it back for each object and is the wrong way and perhaps instead the texture wrapping should be set up on the object so then  your core code will automatically set it back after its set.

#22

Hi Rob,

So to confirm, the verdict is that you can fill the objects using “repeat” for the texture wrapping, and that works fine… then you can revert that setting to “clampToEdge” and the app does not crash on the Nexus7? But if you don’t revert it (you leave it as “repeat”) then it crashes?

Brent

#23

Yes it seems that way. But as it is not a problem on just that code on its own it mus be because graphics are loading after it at some point.

#24

Without any “crash”

#25

Hi Rob,

So, in your implementation, can you set the texture wrapping on just for those fills, then turn it back off immediately after, and the devices like Nexus7 run without issue? If that works, I’d suggest going that route… I’m not sure why, but perhaps the GPUs on those devices are fussy and don’t like when that setting remains enabled going forward.

Brent

#26

Yeah it seems thats one way to fix it and of course anyone else finding this same problem can now read a solution.

I still think it would have made sense to set the texture repeat on the object without setting the default and setting back.

IE parallax.fill = { type=“image”, filename=“stars.png”,textureWrapX= “clampToEdge” } 

#27

Hi Rob,

Yes, it’s hard to predict the behavior of all GPUs, but thank you for helping to diagnose a fairly reasonable solution. I remember when I first experimented with this wrapping feature when Graphics 2.0 was released, I did something similar (not resetting the wrap mode) and it was behaving oddly until I reset it to default.

To help others in the future, I will add a warning to this document under the “Texture Keys” section which points out that the mode should be reset to normal following the fills being done.

http://docs.coronalabs.com/api/library/display/setDefault.html

Take care,

Brent

#28

This is causing a very weird bug when testing on a Iphone 6. When using textureWrapX repeat, NO of the standard images (not filled, just plain images) are not loaded so the only things showing in my app when testing on iphone6 are actually the filled polygons.

Even the Widget buttons are not loaded (the button graphics are not loaded but the actual button function is loaded) so the App look terrible. I have tried setting display.setDefault( “textureWrapX”, “repeat” ); - creating my fills and then resetting to display.setDefault( “textureWrapX”, “clampToEdge” ); before creating images - But it does nothing (on my iphone 6).

#29

Hi @awesume,

Do you have any other devices to test on? I’m curious if this is only isolated to the iPhone 6.

Thanks,

Brent