{"id":113225,"date":"2024-01-29T12:50:31","date_gmt":"2024-01-29T10:50:32","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-gtk-dobavleny-novye-dvizhki-otrisovki-dlya-opengl-i-vulkan"},"modified":"2024-01-29T12:50:31","modified_gmt":"2024-01-29T10:50:32","slug":"v-gtk-dobavleny-novye-dvizhki-otrisovki-dlya-opengl-i-vulkan","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-gtk-dobavleny-novye-dvizhki-otrisovki-dlya-opengl-i-vulkan","title":{"rendered":"New rendering engines for OpenGL and Vulkan added to GTK","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The developers of the GTK library have announced the readiness of two new rendering engines \u2014 'ngl' and 'vulkan', utilizing the OpenGL (GL 3.3+ and GLES 3.0+) and Vulkan graphic APIs. The new engines are included in the experimental release of GTK 4.13.6. In the experimental branch of GTK, the ngl engine is now used by default, but if significant issues are discovered, the old 'gl' rendering engine will be reinstated in the next stable branch 4.14. <\/p>\n
The new engines are positioned as unified and built from a single codebase. The essence of the unification is that the Vulkan API is used as the foundation, on top of which a separate abstraction layer for OpenGL has been created, taking into account the differences between OpenGL and Vulkan. This approach has allowed both engines to utilize a shared infrastructure for handling the scene graph, transformations, texture caching, and glyphs. Unification has also significantly simplified the maintenance of the codebase of both engines and their upkeep in an up-to-date and synchronized state. <\/p>\n
Unlike the old 'gl' engine, which used a separate simple shader for each type of rendering node and performed periodic data re-sorting during offscreen rendering, the new engines apply a complex shader (ubershader) that interprets data from the buffer instead of offscreen rendering. Currently, the new implementation lags behind the old one in terms of optimization levels, as the main focus at this stage is on the correctness of operation and ease of maintenance. <\/p>\n
New features that are not available in the old 'gl' engine: <\/p>\n
\n
Anti-aliasing \u2014 allows for the preservation of fine details and results in smoother contours.
<\/center>\n
Formation of arbitrary gradients, which can use any number of colors and anti-aliasing (the 'gl' engine only supported linear, radial, and conical gradients with 6 color stops).
<\/center>\n
Fractional scaling, allowing for non-integer scale values; for example, using a 125% scale for a 1200\u00d7800 window will allocate a buffer of 1500\u00d71000, rather than 2400\u00d71600 as in the old engine.\n
Support for DMA-BUF technology for using multiple GPUs and offloading separate operations to another GPU.\n
Many rendering nodes that had issues in the old implementation are now handled correctly. <\/ul>\n
The limitations of the new engines include the lack of support for positioning with fractional values and glshader nodes, which were heavily tied to the features of the old engine and are no longer necessary after the addition of support for nodes with masks and textures with transparency. Also mentioned is the potential for issues with graphic drivers due to changes in the way drivers are handled. <\/p>\n
In the future, based on the new unified model, the creation of rendering engines utilizing Metal on macOS and DirectX on Windows is not ruled out, but developing such engines is complicated by the use of different languages for shaders (the 'ngl' and 'vulkan' engines use GLSL, so for Metal and Direct, shaders will either need to be duplicated or a wrapper based on SPIRV-Cross will need to be used). <\/p>\n
Future plans include support for HDR and tools for accurate color management, GPU-side path rendering capabilities, glyph rendering, off-main thread rendering, and performance optimization for older and low-powered devices. Currently, the performance of the Vulkan engine is close to that of the old GL engine. The NGL engine lags behind the old GL engine in performance, but the existing metrics are sufficient for rendering at rates of 60 or 144 FPS. It is expected that the situation will improve following optimization. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
![\"New](\"\/wp-content\/uploads\/2024\/01\/dc690b87095af7bca8d2826ebb3a9584.png\")
<\/center>\n![\"New](\"\/wp-content\/uploads\/2024\/01\/331c81cddc35e00e08db425a38d90dca.png\")
<\/center>\n