Comparing devices - Current state A core feature of all my GPU databases (Vulkan, OpenCL, OpenGL and OpenGL ES) is the possibility to compare reports. This lets you quickly see how the implementations differ, e.g. regarding extension support or api limits.| Sascha Willems
Comparing devices - Current state A core feature of all my GPU databases (Vulkan, OpenCL, OpenGL and OpenGL ES) is the possibility to compare reports. This lets you quickly see how the implementations differ, e.g. regarding extension support or api limits.| Sascha Willems
Comparing devices - Current state A core feature of all my GPU databases (Vulkan, OpenCL, OpenGL and OpenGL ES) is the possibility to compare reports. This lets you quickly see how the implementations differ, e.g. regarding extension support or api limits. For this you check the reports (or devices) to compare from the currently visible list: And after pressing “compare” you’ll get a side-by-side comparison of the selected reports: But the current implementation has an annoying limitati...| Sascha Willems
Version 1.2 of the OpenGL Hardware Capability Viewer is now available for all Windows and Linux. This version adds support for reading the list of supported SPIR-V extensions. These will be displayed on a new tab, and will also be uploaded to the database so you can view and compare them across multiple devices. Note that this only works with devices suppoting GL_ARB_spirv_extensions, and that even with that extension present implementations are free to report an empty list of no SPIR-V exten...| Sascha Willems
After reworking the OpenGL ES hardware database some time ago (which was in dire need of an update to be usable again) I have also released a substantial update to the OpenGL hardware database. Server-side processing Biggest change is the use of server-side processing (as with the Vulkan and OpenGL ES databases), so gone are the days where each request to the report listing page would fetch all reports at once, and had the client do the heavy lifting, resulting in a long delay before any filt...| Sascha Willems
Upon popular request I finally got around combining android device data from my Vulkan and OpenGL ES hardware databases into a convenient table. This should be handy if you plan on supporting both apis on Vulkan or if you just need to check for general device support. The new page can be reached via https://android.gpuinfo.org/ It combines all android device reports from the Vulkan database with all reports from the OpenGL ES database and also uses google’s official device list for translat...| Sascha Willems