![]() ![]() In general RenderDoc won’t support extensions unless they match one of these requirements, and this means most vendor extensions will not be supported. RenderDoc supports many ARB, EXT and other vendor-agnostic extensions - primarily those that are either very widespread and commonly used but aren’t in core, or are quite simple to support. However during frame capture all commands are serialised as if they come from a single thread, so interleaved rendering commands from multiple threads will not work. if commands come from a second thread during loading, or some time during initialisation, this will be supported. RenderDoc assumes that all GL commands (with the exception of perhaps a SwapBuffers call) for frames will come from a single thread. On OpenGL ES, you must be able to create a GLES 3 context to replay. ![]() On desktop this means you must be able to create a 3.2 core context.Īlso 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. RenderDoc assumes a certain minimum feature set on replay. On OpenGL ES, any context version 2.0 and above is supported. To be more compatible with applications, RenderDoc will still attempt to capture on a compatibility context, but it will not replay successfully unless the given subset of functionality is used. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |