![]() ![]() You'd need OpenCL 2.0 to do a decent job though and OS X is on OpenCL 1.2 as of Mavericks. You could implement a limited, non-conformant and feature restricted version of GL_ARB_compute_shader using OpenCL as the back-end and wrapping all the necessary OpenGL objects but Regal doesn't do this. GL_ARB_compute_shaders, none of which you will get from using Regal on OS X. The three most important extensions (for me at least) from 4.2 & 4.3 of the top of my head would be GL_texture_view, GL_ARB_shader_image_load_store and (* Something of an understatement, Regal's code is quite clever in itself and tries to emulate these features in as efficient a way as possible). still use the 2.1 & earlier fixed-function pipeline) or that make use of the Direct State Access extension API, both of which Regal emulates. The primary reason to use Regal on the Mac would be to share code with platforms that use a GL 3.2+ Compatibility context (i.e. Regal merely (*) wraps the platform OpenGL and provides API compatibility for a minority of OpenGL extensions that can be supported by emulating them using the existing platform's features. ![]() Regal will not enable you to access OpenGL 4.2 or 4.3 hardware features that aren't supported by Apple's OpenGL. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |