Mark A. Ropper comments

Repositories
Issues
Comments

Results 2 comments of


                                            Mark A. Ropper

NShader not working initially in VS2017

Would like to reiterate what @Swyter said, SPIRV-VSExtension seems to be conflicting/blocking NShader from kicking in.

Vulkan function loader feature might conflict with app's similar functionality

To expand on @artyomd's solution, if you are using volk with "optimised device calls" (`volkLoadInstanceOnly` + `volkLoadDevice`) you might want to use `vkGetDeviceProcAddr` rather than `vkGetInstanceProcAddr` for all requested functions....