# Editor BUG in 4.14.3&4.15p2

**URL:** <https://forums.unrealengine.com/t/editor-bug-in-4-14-3-4-15p2/381899>\
**Category:** Rendering\
**Tags:** unreal-engine, editor, Rendering, question\
**Created:** [January 15, 2017, 4:33am UTC](https://forums.unrealengine.com/t/editor-bug-in-4-14-3-4-15p2/381899 "2017-01-15T04:33:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_1521166e](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_1521166e](https://forums.unrealengine.com/u/anonymous_user_1521166e)\
**Post date:** [January 15, 2017, 4:33am UTC](https://forums.unrealengine.com/t/editor-bug-in-4-14-3-4-15p2/381899/1 "2017-01-15T04:33:16Z")

</div>

When I switch the editor to High-End Mobile/Metal(ES3.1) in Preview Rendering Level then PIE,everything works fine,then if I open map(something done in the blueprint via node open level) in game,after the new level loads,the game actually switches back to SM5 regardless of showing ES3.1 in the right corner of the viewport.So everytime I have to manually switch to feature level ES3.1 after loading a new level.  
Thanks for your help!

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6e7b421a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6e7b421a](https://forums.unrealengine.com/u/anonymous_user_6e7b421a)\
**Post date:** [January 16, 2017, 8:08pm UTC](https://forums.unrealengine.com/t/editor-bug-in-4-14-3-4-15p2/381899/2 "2017-01-16T20:08:28Z")

</div>

Hey ,

I am not getting the same results on my end when testing on a PC. Could you be sure you are following along with the documentation for this feature when enabling ES 3.1?

[https://docs.unrealengine.com/latest/INT/Platforms/Android/OpenGLES31MobileRenderer/index.html](https://docs.unrealengine.com/latest/INT/Platforms/Android/OpenGLES31MobileRenderer/index.html)

How are you determining that it has switched back to SM5, even though it says ES3\_1 in the bottom right corner?

Thank you,

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_1521166e](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_1521166e](https://forums.unrealengine.com/u/anonymous_user_1521166e)\
**Post date:** [January 21, 2017, 5:35am UTC](https://forums.unrealengine.com/t/editor-bug-in-4-14-3-4-15p2/381899/3 "2017-01-21T05:35:25Z")

</div>

Thanks for your reply!It’s easy to reproduce that.Just follow the following steps:

1.create a third person template project

2.add a postprocessing volume and set it to unbound

3.enable the depth of field:set to BokehDOF and scale to 2 or whatever above 0

4.save it and create a new level,in the levelbp create a node like the screenshot:

![123012-草图.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/f/d/e/fde55200046cc11232f6a699e798f081c47e372e.png)

5.toggle the editor to es3.1 preview rendering mode.And PIE.

6.Press F in game,after finishing opening new map,you can obviously see DOF effect is rendering correctly in the scene though the editor shows es3.1(since es3.1 doesn’t support BokehDOF) in the right corner.But if you now click settings and toggle to es3.1 preview rendering,after waiting a few seconds,the DOF effect disappears,the editor switches to the “real” es3.1 preview rendering.

That means,after loading new level,the editor switches back to SM5 though showing es3.1 in the right corner.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_6e7b421a](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_6e7b421a](https://forums.unrealengine.com/u/anonymous_user_6e7b421a)\
**Post date:** [January 27, 2017, 4:03pm UTC](https://forums.unrealengine.com/t/editor-bug-in-4-14-3-4-15p2/381899/4 "2017-01-27T16:03:59Z")

</div>

Thanks for the clear and precise repro steps. I was able to confirm what you are reporting and have gone ahead and entered a bug report for the issue. You can track the report following the link below on our public issues tracker.

**[UE-41218](https://issues.unrealengine.com/issue/UE-41218)**

Once the issue has been addressed by our engineers the ticket will be updated and reflected in the public tracker. Let me know if you have further questions or need additional assistance.

Cheers,