maxime-modulopi

Not being able to set `TRACY_ENABLE` to OFF makes the `tracy` port basically useless for real projects as there is no way to disable Tracy for production builds. This issue...

Yes but Tracy already supports creating a `TracyVkCtx` with host resets via `TracyVkContextHostCalibrated` (which already calls `vkResetQueryPool` in its constructor). Similarly to this, I would have expected to be able...

I'm also experiencing this issue, to a lesser extent. Sometimes, the `Calibrate` call will take a very long time (e.g. 16ms), with hundreds of `vkGetCalibratedTimestampsEXT` calls being emitted.

I've had success working around this issue by collecting in a separate thread, but I'm not 100% sure this is thread-safe on the Tracy size

@sean-mcmanus It happens when running the `CMake: Configure` command from the CMake Tools extension (for context, I use `$ENV{VCPKG_ROOT}` in my CMakeLists.txt). It seems to be a problem with this...

@sean-mcmanus No, this issue happen even with a fresh CMake cache (by entirely deleting the build directory or with this command)

Here are CMake files that can reproduce the issue: CMakeLists.txt ```cmake cmake_minimum_required(VERSION 3.28) project(Test) message("VCPKG_ROOT: \"$ENV{VCPKG_ROOT}\"") ``` CMakePresets.json ```json { "version": 3, "configurePresets": [ { "name": "Debug", "binaryDir": "${sourceDir}/build/${presetName}", "generator":...

Configure is working fine now, thank you!

Yes it is allowed in SPIR-V, my question was if it was also officially allowed in GLSL or if I'm relying on glslang's UB, given that glslang is the reference...

By "depending on target" you mean GLSL targeting GL drivers vs SPIR-V, right? If so, is it something that could be documented in the extension spec?