# X Component of Scale getting zeroed out on COND\_InitialOnly on Android

**URL:** <https://forums.unrealengine.com/t/x-component-of-scale-getting-zeroed-out-on-cond-initialonly-on-android/1729965>\
**Category:** Multiplayer & Networking\
**Tags:** Networking, unreal-engine, Android, bug-report\
**Created:** [March 4, 2024, 5:27pm UTC](https://forums.unrealengine.com/t/x-component-of-scale-getting-zeroed-out-on-cond-initialonly-on-android/1729965 "2024-03-04T17:27:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DentonJC](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@DentonJC](https://forums.unrealengine.com/u/DentonJC)\
**Post date:** [March 4, 2024, 5:27pm UTC](https://forums.unrealengine.com/t/x-component-of-scale-getting-zeroed-out-on-cond-initialonly-on-android/1729965/1 "2024-03-04T17:27:49Z")

</div>

I have experienced a strange bug in UE4.27 where replicating a blueprint transform via COND\_InitialOnly is zeroing out the X component of the scale ONLY on Android builds.  
The location, rotation and other scale components are correct, but the X component is always 0.

Its correct on the windows server, its correct on windows clients, but only on Android clients X scale is 0.

This is 100% reproducible for every COND\_InitialOnly transform in my project
