# DistanceToNearestSurface node issue in MaterialEditor 

**URL:** <https://forums.unrealengine.com/t/distancetonearestsurface-node-issue-in-materialeditor/2301036>\
**Category:** Rendering\
**Tags:** distance-fields, unreal-engine, Rendering, Shaders\
**Created:** [January 24, 2025, 3:01pm UTC](https://forums.unrealengine.com/t/distancetonearestsurface-node-issue-in-materialeditor/2301036 "2025-01-24T15:01:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![FXology](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/fxology/32/1023794_2.png) [@FXology](https://forums.unrealengine.com/u/FXology)\
**Post date:** [January 24, 2025, 3:01pm UTC](https://forums.unrealengine.com/t/distancetonearestsurface-node-issue-in-materialeditor/2301036/1 "2025-01-24T15:01:43Z")

</div>

Was struggling with **DistanceToNearestSurface** node in Material Editor, cause it was kinda receiving distance field from the parent mesh itself:

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/1/d/9/1d96803cc49f7c40d163d102150e9730dc64a0bd.jpeg)  
 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/8/d/2/8d29dde9b4c4a7866fa84dc5928840093ab4b433.jpeg)

Accidentaly found this **AffectDistanceFieldLighting** checkbox in mesh details on the level

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/3/f/93fab3569856751173faf357d9d036ae17578df0.png)

Fixed my problem for now

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/0/e/2/0e2e544d4ccea639162d124ecc2a929261a43533.jpeg)

But I’m not quite sure it its a proper solution for such issue.  
Any thoughts?

---

<div class="post-metadata">

**Author:** ![Arkiras](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/arkiras/32/1008648_2.png) [@Arkiras](https://forums.unrealengine.com/u/Arkiras)\
**Post date:** [January 24, 2025, 3:37pm UTC](https://forums.unrealengine.com/t/distancetonearestsurface-node-issue-in-materialeditor/2301036/2 "2025-01-24T15:37:16Z")

</div>

> [@FXology](#):
>
> But I’m not quite sure it its a proper solution for such issue.

It’s the only solution
