When we click on a node in Event Viewer: see renderdoc\qrenderdoc\Windows\APIInspector.cpp:
void APIInspector::OnSelectedEventChanged(uint32_t eventId)
{
ui->apiEvents->saveExpansion(ui->apiEvents->getInternalExpansion(m_EventID), 0);
ui->apiEvents->clearSelection();
fillAPIView();
m_EventID = eventId;
ui->apiEvents->applyExpansion(ui->apiEvents->getInternalExpansion(m_EventID), 0);
}
I built Vulkan samples for Windows as follows:
set MY_VS_GENERATOR="Visual Studio 17 2022"
set MY_DRIVE=D:
%MY_DRIVE%
cd \dev\build\v
set MY_CMAKE_EXE=%MY_DRIVE%\dev\tools\cmake-3.24.2-windows-x86_64\bin\cmake.exe
%MY_CMAKE_EXE% ..\..\repos\Vulkan -G %MY_VS_GENERATOR% -A x64
rem Open generated vulkanExamples.sln and build.
and launched bloom.exe with RenderDoc:
I cloned RenderDoc’s repository:
git clone https://github.com/baldurk/renderdoc.git
easily built renderdoc\renderdoc.sln with MSVC2022 on my home machine, opened my Lines Game built on Windows with OpenGL:
Cloned the repository:
git clone https://github.com/SaschaWillems/Vulkan.git
git submodule init
git submodule update
Updated assets:
python.exe download_assets.py
I downloaded Vulkan SDK and installed Vulkan Hardware Capability Viewer at C:\VulkanSDK\1.3.236.0\Bin\vulkanCapsViewer.exe:
The basic commands for using apitrace with an OpenGL application are:
apitrace trace --api=gl MyApp qapitrace MyApp.trace apitrace dump --blobs MyApp.trace
The last command generates blobs that can be inspected with the following command, for example:
tail -c $((12*10)) ~/repos/MyApp/build/blob_call2325.bin | xxd -g1
Or by writing a simple C++ program that converts them into CVS format:
To learn OpenGL I wrote a simple game that utilizes the most of basic OpenGL ES 2.0 (and partially 3.0) techniques:
In my previous post Testing XAML App for OpenGL ES on Windows 10 Mobile Device I described the changes I made to UWP application based on “XAML App for OpenGL ES (Universal Windows)” template to demonstrate some strange effect related to the transparency of the image drawn with OpenGL ES in SwapChainPanel. But I did yet another experiment with this application and got some beautiful pictures that demonstrate what happens if I make the scene completely transparent with the following code:
void SimpleRenderer::Draw()
{
glEnable(GL_DEPTH_TEST);
glClearColor(0.0f, 0.0f, 0.0f, 0.0f);
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
...
}
Today I played a bit with a UWP application based on “XAML App for OpenGL ES (Universal Windows)” template and realized that there is some specific bug probably related to the interaction between SwapChainPanel and OpenGL surface. First, I made the cube transparent by changing two lines of code in the vertex shader:
const std::string vs = STRING
(
uniform mat4 uModelMatrix;
uniform mat4 uViewMatrix;
uniform mat4 uProjMatrix;
attribute vec4 aPosition;
attribute vec3 aColor;
varying vec4 vColor;
void main()
{
gl_Position = uProjMatrix * uViewMatrix * uModelMatrix * aPosition;
vColor = vec4(aColor, 0.1);
}
);
Typically ANGLE library is used with OpenGL 2.0, but I successfully tried to enable OpenGL 3.0:
const EGLint contextAttributes[] =
{
EGL_CONTEXT_CLIENT_VERSION, 3,
EGL_NONE
};
and used some OpenGL 3.0 features in my Universal Windows App. But today I tried to compile my application with the new version of ANGLE library and got EGL_BAD_CONFIG error while creating the OpenGL context. The source code that returns this error checks some EGL_OPENGL_ES3_BIT_KHR that is not set in the new version:
if (clientMajorVersion == 3 && !(configuration->conformant & EGL_OPENGL_ES3_BIT_KHR))
{
return Error(EGL_BAD_CONFIG);
}