The following warnings occurred: | |||||||||||||||
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.26 (Linux)
|
Vulkan API has been released - Printable Version +- EmuNewz Network (https://www.emunewz.net/forum) +-- Forum: Official Boards for Emunews Affiliated Emu Projects (https://www.emunewz.net/forum/forumdisplay.php?fid=47) +--- Forum: Official RPCS3 Forum [archive] (https://www.emunewz.net/forum/forumdisplay.php?fid=172) +---- Forum: RPCS3 - Support & Issue Reporting (https://www.emunewz.net/forum/forumdisplay.php?fid=163) +---- Thread: Vulkan API has been released (/showthread.php?tid=174274) Pages:
1
2
|
RE: Vulkan API has been released - Ekaseo - 02-18-2016 hm... i wonder if it is much harder to code for vulkan than opengl RE: Vulkan API has been released - tambre - 02-18-2016 (02-18-2016, 03:35 PM)Ekaseo Wrote: hm... i wonder if it is much harder to code for vulkan than opengl Much harder? It's very hard. I have yet to dive into Vulkan myself, but I will soon. From what I've heard, it's basically like writing a driver. What previously would have been done by the driver you can now do yourself, thus leaving out or optimizing stuff, that otherwise would cause driver overhead. This approach also allows greater control over the rendering pipeline, which can be probably very useful in emulating many consoles' rendering techniques and features. This graph gives quite a good explanation of Vulkan vs OpenGL: RE: Vulkan API has been released - ps0ne - 02-18-2016 I will cross my fingers for vulcan development. Rpcs3 may be first emu with this backend, work woth of glory In the meantime, please dont forget Opengl. Last kd-11's commit made unbelievable speedup in some parts. Im sure there is still some space for optimization. |