Does this mean neither A14 nor A15 support metal ray tracing? What so special characteristics do the Intel GPUs have?

Could it be that you are including that header in a non-metal (ie: being compiled with clang or gcc) module? If that is the case and the header is being included in both a metal and a non-metal module, maybe you are missing a guard like: "#if METAL_MACOS || METAL_IOS" wrapping the var declaration?

That's what I was looking for. I only had to translate the swift KVO to objective-c. Thank you very much mmmetal.

Cool. The confusion comes from the previous sentence: sample_compare performs a comparison of the compare_value value against the pixel value (1.0 if the comparison passes and 0.0 if it fails) Thank you very much

Thanks. But my question was about the identification of the buffer. I found that setting id::label will show that label instead of the hex id

Am I right assuming that the GPU Time after capturing is the one in the Summary as shown above?

Worked on Version 14.2 (14C18)