# Render issues

**URL:** <https://forum.logik.tv/t/render-issues/5103>\
**Category:** Flame Questions\
**Created:** [February 16, 2022, 5:15pm UTC](https://forum.logik.tv/t/render-issues/5103 "2022-02-16T17:15:14Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![space\_monkey](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/space_monkey/32/49_2.png) [@space\_monkey](https://forum.logik.tv/u/space_monkey)\
**Post date:** [February 16, 2022, 5:15pm UTC](https://forum.logik.tv/t/render-issues/5103/1 "2022-02-16T17:15:14Z")

</div>

I am getting some really strange render issues where the UI is in the main player and curious if anyone knows what this is from maybe graphics card failing or something? Here is a picture of what is happening it just renders the UI in the player which is super weird and not really appreciated.

 ![Screen Shot 2022-02-16 at 09.11.43](https://us1.discourse-cdn.com/flex020/uploads/thedepartmentofexternalservices/original/2X/d/df932982be5424c1d9d304f160aba01ec296f31f.jpeg)

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\
**Post date:** [February 16, 2022, 5:35pm UTC](https://forum.logik.tv/t/render-issues/5103/2 "2022-02-16T17:35:02Z")

</div>

This is a known issue, discussed here, fixed in 2022.3.

> [@Flame UI and graphics glitches while working on batch](https://forum.logik.tv/t/flame-ui-and-graphics-glitches-while-working-on-batch/4543/15):
>
> This problem has been fixed in the 2022.3 Update version.

---

<div class="post-metadata">

**Author:** ![space\_monkey](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/space_monkey/32/49_2.png) [@space\_monkey](https://forum.logik.tv/u/space_monkey)\
**Post date:** [February 16, 2022, 5:55pm UTC](https://forum.logik.tv/t/render-issues/5103/3 "2022-02-16T17:55:02Z")

</div>

considering I am running 22.3 this hasn’t been fixed.

---

<div class="post-metadata">

**Author:** ![cnoellert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/cnoellert/32/559_2.png) [@cnoellert](https://forum.logik.tv/u/cnoellert)\
**Post date:** [February 16, 2022, 5:56pm UTC](https://forum.logik.tv/t/render-issues/5103/4 "2022-02-16T17:56:25Z")

</div>

Perfect delivery

---

<div class="post-metadata">

**Author:** ![space\_monkey](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/space_monkey/32/49_2.png) [@space\_monkey](https://forum.logik.tv/u/space_monkey)\
**Post date:** [February 16, 2022, 6:44pm UTC](https://forum.logik.tv/t/render-issues/5103/5 "2022-02-16T18:44:03Z")

</div>

hey @fredwarren considering I am still getting this UI issue in 22.3 is there someone I can reach out to or alert to this issue ?

---

<div class="post-metadata">

**Author:** ![fredwarren](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/fredwarren/32/158_2.png) [@fredwarren](https://forum.logik.tv/u/fredwarren)\
**Post date:** [February 16, 2022, 7:17pm UTC](https://forum.logik.tv/t/render-issues/5103/6 "2022-02-16T19:17:16Z")

</div>

Since this is an issue with a release version please contact support.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [February 16, 2022, 7:31pm UTC](https://forum.logik.tv/t/render-issues/5103/7 "2022-02-16T19:31:10Z")

</div>

It’s like feedback. It ought to be a feature.

---

<div class="post-metadata">

**Author:** ![space\_monkey](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/space_monkey/32/49_2.png) [@space\_monkey](https://forum.logik.tv/u/space_monkey)\
**Post date:** [February 16, 2022, 7:32pm UTC](https://forum.logik.tv/t/render-issues/5103/8 "2022-02-16T19:32:32Z")

</div>

cool thanks fred, case has been opened.

---

<div class="post-metadata">

**Author:** ![hildebrandtbernd](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/hildebrandtbernd/32/3038_2.png) [@hildebrandtbernd](https://forum.logik.tv/u/hildebrandtbernd)\
**Post date:** [February 16, 2022, 7:53pm UTC](https://forum.logik.tv/t/render-issues/5103/9 "2022-02-16T19:53:53Z")

</div>

It’s a sadly common bug, that started within flame 22.2, thought they fixed it in 22.3.

It must happen within one action. To temporally fix it for a clean rendering for now at least, you need to find the corrupt actionlayer and change the transparency. once and back. You have to redo this step every time this d\*\*\* bug is starting. Extremly annoying in lager setups.

---

<div class="post-metadata">

**Author:** ![space\_monkey](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/space_monkey/32/49_2.png) [@space\_monkey](https://forum.logik.tv/u/space_monkey)\
**Post date:** [February 18, 2022, 5:47pm UTC](https://forum.logik.tv/t/render-issues/5103/10 "2022-02-18T17:47:57Z")

</div>

As an update the dev team was able to reproduce the issue and are on the case, thanks everyone
