Fri Sep 04, 2020 10:26 am
_mental_ wrote:Regarding lags, could you please compare both versions with the following stats enabled in console?
Fri Sep 04, 2020 1:12 pm
Fri Sep 04, 2020 5:25 pm
drfrag wrote:Seems upscaled textures now take up much more ram. Certainly there was a recent major refactor of the upscaling code.
https://github.com/coelckers/gzdoom/com ... 9797c9c32c
Still not solved: Material layers need explicit control, not only for scaling but also for filtering.
Execution could not continue.
Could not submit command buffer: device lost
Sat Sep 05, 2020 12:52 am
I tried to understand, why new code should take 9x more RAM, but didn't get it. But found next:
Sat Sep 05, 2020 2:41 am
theleo_ua wrote:2) If I change to vulkan instead of OpenGL (I mean future (with full vulkan support without critical issues) poilshed versions, not current), will it take less RAM?
Sat Sep 05, 2020 2:58 am
vsonnier wrote:Give a try to reduce gl_texture_hqresize_maxinputsize to see if affects RAM consumption.
vsonnier wrote:You can also get a hint in Vulkan VRAM consumption by using 'vk_memstats' on the console.
vsonnier wrote:* There is a CVAR option controlling the max texture size to be resized (no need to resize already high enough resolution) : gl_texture_hqresize_maxinputsize = 512 (by default)
which means the texture is NOT resized if height * width > gl_texture_hqresize_maxinputsize * gl_texture_hqresize_maxinputsize
_mental_ wrote:theleo_ua wrote:2) If I change to vulkan instead of OpenGL (I mean future (with full vulkan support without critical issues) poilshed versions, not current), will it take less RAM?
Please stop posting nonsense about major issues with Vulkan renderer. The only important thing it doesn't do at the moment is graceful handling of out-of-VRAM condition. Apparently, you encountered it with all these high resolution textures.
Sat Sep 05, 2020 3:54 am
vsonnier wrote:o be confirmed, but it could explain the RAM/ VRAM inflation.