i had a look around the code base, everything keeps a ref to the "graphics device" which has the VkI
i had a look around the code base, everything keeps a ref to the "graphics device" which has the VkInstance as a member. 
Rkinda how I figured they would
Tah yes. _gd.Vk.callwhatever, no thanks
RI mean... you have to have some form of class to access it, you could I guess wrap the instance into a static class that would hide the API instance I guess?
Rbut thats about the best you can do
Tno thanks i'll just use a static import of terrafx
RI...
RGL has the same thing you know?
Rat least for silk
Twhat?
RYou have a GL object you have to carry around IIRC
Tyes... why did you bring that up? i specifically want to avoid such a class
RThen... idk use C?
Rno but seriously
T
RI dont think you can avoid such a class in it's entirety
Lyou kinda can tho
LGL can be static
Land should
Dan idea i conetmplated was generate extensiton methods for the
VkGraphicsDevice
Tsimple and effective
RThat is pretty terrible tho.... whatever
Ryiu do you
Ti think you just offended everyone who uses vulkan in other languages
Rprobably
Rbut TBH, I dont really care
Ti'm on team tanner; map as closely to native as possible
Rnot exactly sure what that has to do with anything?
T... the conversation about mappings?
RUltimately you are still calling
TerraFCInterop.Vulkan.VulkanvkCmdDrawIndexed()static using or not
PTerraFX just delegates to the Vulkan loader to keep the static dispatch table state
Pwe on the other hand do not want to hide state from the user
Pwe prefer correctness
Pas it stands, you’ll probably have an interesting time using TerraFX.Interop.Vulkan with multiple devices, possibly across multiple GPUs
Pas how do you tell the loader to swap out the dispatch tables when
P(Genuine question because if the Vulkan loader has some magic we don’t know about perhaps we should look into it)
Ti could try right now i guess
Tnevermind my intel igpu doesn't support vulkan
Tanyways, i do not see how the bindings depend on the dispatch tables
Tbindings that depend on the vkinstance are loaded upon device creation
Teverything else is static
Ralmost no intel iGPUs support vulkan
Rthey can
Rand do on linux third gen and up actually
Rintel just does not support it in windows for some damn reason
Twell, it claims to support dx12 but crashes when you try to create a device on it :)
Tand reading from structured buffers returns garbage in dx11 
Topengl works fine though
Fmy laptop with an igpu claims to support vulkan 1.1
Fkey word being claims