Don't require ARB_separate_shader_objects on replay

* If it's not available we must also emulate program introspection to get proper
  reflection data.
This commit is contained in:
baldurk
2019-03-13 11:48:24 +00:00
parent 4d60276ea0
commit e1d39ef23b
7 changed files with 136 additions and 177 deletions
+3 -5
View File
@@ -19,13 +19,11 @@ On OpenGL ES, any context version 2.0 and above is supported.
Replay requirements
-------------------
RenderDoc assumes a certain minimum feature set on replay. On desktop this means you must be able to create a 3.2 context with the ``GL_ARB_separate_shader_objects`` extension available.
RenderDoc assumes a certain minimum feature set on replay. On desktop this means you must be able to create a 3.2 core context.
Theis extension should not require newer hardware than the base 3.2 context, but it might need an updated driver to be listed as available.
Also note that this is the *minimum* required functionality to replay, some analysis features will be disabled unless you have more capable hardware features such as GL_ARB_shader_image_load_store, GL_ARB_compute_shader and GL_ARB_gpu_shader5.
Also note that this is the *minimum* required extension set to replay, some analysis features will be disabled unless you have more capable hardware features such as GL_ARB_shader_image_load_store, GL_ARB_compute_shader and GL_ARB_gpu_shader5.
On OpenGL ES, you must be able to create a GLES 3 context to replay, again with the above ``GL_ARB_separate_shader_objects`` extension.
On OpenGL ES, you must be able to create a GLES 3 context to replay.
Multiple contexts & multithreading
----------------------------------