Unreal Engine Issues

"Find Collision UV" does not work with "Get Hit result under cursor"

The Hit result from "get hit result under cursor" does not appear to be working with "find collision UV" Using "Line Trace by Channel" hit result works as intended. ...

Mover MoveDirectionIntent can be 0 due to interpolation

If two states have MoveDirectionIntent vectors that are opposite to each other, interpolating between these states can result in MoveDirectionIntent being 0. This may cause issues for animation blue ...

Crash launching ARSampe onto iOS

ARSample from WWDC is crashing when attempting to launch onto an iOS device Originally hit this on an iOS 11 iPad, but it also reproduced on an iOS 10 iPhone 6+ ...

Blueprint inherited from StaticMeshActor will fail to compile if StaticMesh is NULL

Some developers reporting incorrect Preview in VR resolution for Steam VR

VR Preview Window is the wrong resolution, just showing the top left portion of the entire view. Somewhat similar symptoms to -[Link Removed]-, not exactly the same though.   This issue has not be ...

ZenGarden's game sequence doesn't play on device

Zen Garden loads, then the screen fades in and out as if it's ready to begin play. But when the player taps the screen, the only thing that moves are some lensflares, and the level never transitions ...

When using StringToBytes() it returns an incorrect value

When using the StringToBytes() function it returns one less byte due to the -1 at the end of the return. The function takes a string and converts it to bytes but it always returns one less byte than ...

Stop using power of 2 RTs for landscape edit layers

Result : all the RTs allocated for edit layers (in global merge mode) will be padded to the next power of 2 for no good reason, which can lead to out-of-VRAM (as reported by [Link Removed]) ...

Modifying an H/ISM instance will cause selection highlights to be inaccurate

Exposure Is More Extreme In High-End Mobile Preview Modes

In high-end mobile preview modes the exposure will return much more exaggerated results. This is related to the new default tone mapper settings since changing r.TonemapperFilm to 0 solves the issue ...