x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Office Holiday

Epic Games' offices will be on holiday from June 22nd to July 7th. During this period support will be limited. Our offices will reopen on Monday, July 8th. 

[Closed] Texture does not wrap on Android ES2

Hello,

We are encountering a problem in UE 4.12 on Android ES2 where textures do not wrap correctly, instead acting as if they're clamped. This has been tested on two Nexus 6Ps running Android N, a Samsung Galaxy S7 running Android 6.0.1, and a Samsung Galaxy Note 4 running Android 5.1.1. The Samsung devices are the Snapdragon equipped American versions.

This only occurs on the actual devices, appearing normally when previewed with the Android ES2 rendering level in the editor. This seems to happen regardless of texture dimensions, compression settings, mipmap settings, or power of two mode. When run with ES3.1, the problem does not occur.

Tiled texture on Windows On Windows, the 64x64 texture tiles just fine, even when set to the ES2 preview level.

Tiled texture on Android On Android ES2, the same texture behaves as though it is clamped, even though wrapping is selected in the texture settings.

Assuming this isn't intended behavior, is there any way to work around this? Using ES3.1 isn't an option for us right now, unfortunately.

Product Version: Not Selected
Tags:
more ▼

asked Sep 08 '16 at 03:12 PM in Packaging & Deployment

avatar image

Answers.Archive STAFF
1.9k 206 312 684

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Sep 08 '16 at 03:17 PM by AndrewHurley for the following reason:

The question is answered, right answer was accepted


1 answer: sort voted first

What are the UV ranges? This could be a too high a repeat rate (6 bits of precision used just for integer if x64). And make sure you don't go too far from the origin (0,0) as this will also lower the bits for fraction. Try turning on "Use Full Precision" in the Mobile section on the material and see if it helps.

more ▼

answered Sep 08 '16 at 03:12 PM

avatar image

Answers.Archive STAFF
1.9k 206 312 684

avatar image Answers.Archive STAFF Sep 08 '16 at 03:12 PM

Upon closer inspection, this problem only seems to happen when the Google VR plugin is enabled. With it enabled, the problem even arises in things like the official Sun Temple and Strategy Game demos.
To answer your questions, though, the model in the images is the standard template floor, which seems to have UVs between (0,1) and (10, -9). The model is centered around the origin, so I don't think that it would be getting into precision problems, even with half precision.
I cannot seem to find an option to enable full precision in the Mobile settings (just "Fully Rough", "Use Lightmap Directionality", "High Quality Reflections", and "Planar Reflections"). Is there somewhere else I should be looking?
The problem seems to occur whenever a texture is sampled outside of the zero to one range. Maybe the Google VR plugin is overriding the tiling settings for textures or something similar?

avatar image Answers.Archive STAFF Sep 08 '16 at 03:12 PM

Sorry, the Full Precision is a new setting for 4.13. You can find it in github master if you want to try it, but the extra information about Google VR plugin seems more likely.

It probably has to do with their library setting texture addressing separate from our state caching in GoogleVRHMDRender.cpp.

avatar image Answers.Archive STAFF Sep 08 '16 at 03:12 PM

Is this something we should look into fixing ourselves? We can try and come up with a workaround, but if there's a fix in the works already by the plugin developers, we might just wait until that's available and devote manpower elsewhere for now.

avatar image Answers.Archive STAFF Sep 08 '16 at 03:12 PM

It turns out this is a known bug and is fixed in an update to the SDK. It should be added to Dev-VR this week.

avatar image Answers.Archive STAFF Sep 08 '16 at 03:12 PM

Hey Chris,

We took a look at the latest GoogleVR integration from HSL, CL #3033004, and this problem appears to persist in 'Daydream-only' builds (but does not occur in 'Cardboard + Daydream' builds). Our target is 'Daydream-only', as that is all that appears to support the Daydream controller.

avatar image Answers.Archive STAFF Sep 08 '16 at 03:12 PM

This CL looks to be more about iOS support; I don't see an update to the SDK itself for Android.

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question