# qglinternal::vkCreateFramebuffer 

**URL:** <https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822>\
**Category:** Mobile\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [May 13, 2025, 8:35am UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822 "2025-05-13T08:35:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 13, 2025, 8:35am UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822/1 "2025-05-13T08:35:31Z")

</div>

Its not happening in all the devices mostly on adreno and Mali Gpu.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 13, 2025, 8:35am UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822/2 "2025-05-13T08:35:34Z")

</div>

**Steps to Reproduce**  
`After the launch of 5.3 build, we are having crash on launch in Android platform. please find the call stack below.`

---

<div class="post-metadata">

**Author:** ![step\_jac\_eg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@step\_jac\_eg](https://forums.unrealengine.com/u/step_jac_eg)\
**Post date:** [May 13, 2025, 1:13pm UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822/3 "2025-05-13T13:13:11Z")

</div>

Hi Farhan,

Can you provide the full log so we can get more details?

Best regards.

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 13, 2025, 7:03pm UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822/4 "2025-05-13T19:03:35Z")

</div>

Here is the complete log file

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [May 15, 2025, 11:12am UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822/5 "2025-05-15T11:12:32Z")

</div>

Hi,

crash happening on this line of this function FVulkanFramebuffer::FVulkanFramebuffer

check(Texture-\>Image != VK\_NULL\_HANDLE) we found that in our device profile we are setting +CVars=r.Vulkan.DelayAcquireBackBuffer=0 but in ue5.6 source code its written that we have to use r.Vulkan.DelayAcquireBackBuffer=2 , should we use 1 or 2 in ue5.3 engine.

`EDelayAcquireImageType GVulkanDelayAcquireImage = EDelayAcquireImageType::DelayAcquire;

TAutoConsoleVariable CVarDelayAcquireBackBuffer(  
TEXT(“r.Vulkan.DelayAcquireBackBuffer”),  
1,  
TEXT(“Whether to delay acquiring the back buffer \n”)  
TEXT(" 0: acquire next image on frame start \n")  
TEXT(" 1: acquire next image just before presenting, rendering is done to intermediate image which is then copied to a real backbuffer (default) \n")  
TEXT(" 2: acquire next image on first use"),  
ECVF\_ReadOnly  
);

ue5.6  
check(Texture-\>Image != VK\_NULL\_HANDLE || !Texture-\>IsImageOwner()); // coming in, we should always have an image, except backbuffer with r.Vulkan.DelayAcquireBackBuffer=2

ue5.3  
check(Texture-\>Image != VK\_NULL\_HANDLE)`

---

<div class="post-metadata">

**Author:** ![step\_jac\_eg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@step\_jac\_eg](https://forums.unrealengine.com/u/step_jac_eg)\
**Post date:** [May 18, 2025, 10:52am UTC](https://forums.unrealengine.com/t/qglinternal-vkcreateframebuffer/2561822/6 "2025-05-18T10:52:27Z")

</div>

Hi Farhan,

I noticed that this issue was occuring upon return from the backgrounded state. Much of the window event handling has been rewritten in 5.6. It is suggested to use r.Vulkan.DelayAcquireBackBuffer=1 as workaround under 5.3.

Best regards.
