No worries, the same experience can be done with OpenGL or Vulkan, depending on the specific OS flavour and OEM drivers.

▲

jsheard 10 hours ago | parent [-]

Vulkan even made this kind of targeted hack into a first class citizen by letting the application specify the name and version number of itself and its engine during initialization. There's no reason for that besides enabling per-app driver shenanigans.

▲

kg 9 hours ago | parent [-]

Vulkan layers being system-wide feels like it's specifically asking for this class of bug. If you're lucky every system-wide layer ships with PDBs... but they probably don't. I've yet to find a bug in a layer, at least, but I've wasted time ruling it out.

	▲	gmueckl 9 hours ago \| parent [-]
		System-wide Vulkan layers definitely cause chaos. I remember unit tests for our renderer crashing on some machines and not on other nearly identical ones. The culprit was a Vulkan layer installed by a video capture software. It had a hard limit of 16 Vulkan instances that it could keep track of before overflowing an array and crashing. But our tests would recreate the Vulkan environment from scratch for each test, which is fairly unusual for a Vulkan application, to be fair. In the end, we added the list of loaded Vulkan layers to the diagnostic log of our software to help customer support spot fishy ones.