demos: Change tri to not require shaderClipDistance

Change-Id: Iaa1afa361d29022388005c173054f714c64fb7d7

diff --git a/demos/tri.c b/demos/tri.c
index 847655f..1c80a22 100644 (file)
--- a/demos/tri.c
+++ b/demos/tri.c
@@ -2164,14 +2164,6 @@ static void demo_init_vk(struct demo *demo) {
     VkPhysicalDeviceFeatures features;
     vkGetPhysicalDeviceFeatures(demo->gpu, &features);
 
-    //TODO: Enable this
-#ifndef __ANDROID__
-    if (!features.shaderClipDistance) {
-        ERR_EXIT("Required device feature `shaderClipDistance` not supported\n",
-                 "GetPhysicalDeviceFeatures failure");
-    }
-#endif
-
     // Graphics queue and MemMgr queue can be separate.
     // TODO: Add support for separate queues, including synchronization,
     //       and appropriate tracking for QueueSubmit

diff --git a/demos/tri.vert b/demos/tri.vert
index 92d6436..d4788d8 100644 (file)
--- a/demos/tri.vert
+++ b/demos/tri.vert
@@ -24,6 +24,9 @@
 layout (location = 0) in vec4 pos;
 layout (location = 1) in vec2 attr;
 layout (location = 0) out vec2 texcoord;
+out gl_PerVertex {
+        vec4 gl_Position;
+};
 void main() {
    texcoord = attr;
    gl_Position = pos;