# Why does renaming a Texture Parameter to "Heightmap" change the output?

**URL:** <https://forums.unrealengine.com/t/why-does-renaming-a-texture-parameter-to-heightmap-change-the-output/399417>\
**Category:** Rendering\
**Tags:** weird, unreal-engine, heightmap, question\
**Created:** [June 28, 2017, 10:02pm UTC](https://forums.unrealengine.com/t/why-does-renaming-a-texture-parameter-to-heightmap-change-the-output/399417 "2017-06-28T22:02:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thegreenjag1](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@thegreenjag1](https://forums.unrealengine.com/u/thegreenjag1)\
**Post date:** [June 28, 2017, 10:02pm UTC](https://forums.unrealengine.com/t/why-does-renaming-a-texture-parameter-to-heightmap-change-the-output/399417/1 "2017-06-28T22:02:42Z")

</div>

![201523-weird+thing.jpg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/5/a/4/5a486f90d7c1411fa71a6388a7e5f055fcb41447.jpeg)

My question is pretty straightforward. Whenever I rename my Texture Parameter to “Heightmap,” it shows as some weird texture within the viewport. Is this a part of UE4’s coding? I couldn’t find it in the documentation.

Thanks in advance guys!

---

<div class="post-metadata">

**Author:** ![Shadowriver](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Shadowriver](https://forums.unrealengine.com/u/Shadowriver)\
**Post date:** [June 29, 2017, 3:57am UTC](https://forums.unrealengine.com/t/why-does-renaming-a-texture-parameter-to-heightmap-change-the-output/399417/2 "2017-06-29T03:57:29Z")

</div>

I find the corprit:

[https://github.com/EpicGames/UnrealEngine/blob/f794321ffcad597c6232bc706304c0c9b4e154b2/Engine/Source/Runtime/Landscape/Private/LandscapeEdit.cpp#L145](https://github.com/EpicGames/UnrealEngine/blob/f794321ffcad597c6232bc706304c0c9b4e154b2/Engine/Source/Runtime/Landscape/Private/LandscapeEdit.cpp#L145)

It’s landscape editor setting parameters probably for it’s shader code, it uses “EditorOnly” functions so this only will work in editor.

I know there sometimes unexpected collisions with internal HLSL code causing some strange behavior in material editor, so sometimes you might find something like this, but this using parameter system in material same as blueprints.

Hmmm, i gonna move this to “Bug Raport”, as i don’t think this is intended feature aspecially if it’s editor only. This way we should get Epic word on it faster too.
