• 15
• 15
• 11
• 9
• 10
• ### Similar Content

• By elect
Hi,
ok, so, we are having problems with our current mirror reflection implementation.
At the moment we are doing it very simple, so for the i-th frame, we calculate the reflection vectors given the viewPoint and some predefined points on the mirror surface (position and normal).
Then, using the least squared algorithm, we find the point that has the minimum distance from all these reflections vectors. This is going to be our virtual viewPoint (with the right orientation).
After that, we render offscreen to a texture by setting the OpenGL camera on the virtual viewPoint.
And finally we use the rendered texture on the mirror surface.
So far this has always been fine, but now we are having some more strong constraints on accuracy.
What are our best options given that:
- we have a dynamic scene, the mirror and parts of the scene can change continuously from frame to frame
- we have about 3k points (with normals) per mirror, calculated offline using some cad program (such as Catia)
- all the mirror are always perfectly spherical (with different radius vertically and horizontally) and they are always convex
- a scene can have up to 10 mirror
- it should be fast enough also for vr (Htc Vive) on fastest gpus (only desktops)

Looking around, some papers talk about calculating some caustic surface derivation offline, but I don't know if this suits my case
Also, another paper, used some acceleration structures to detect the intersection between the reflection vectors and the scene, and then adjust the corresponding texture coordinate. This looks the most accurate but also very heavy from a computational point of view.

Other than that, I couldn't find anything updated/exhaustive around, can you help me?

• Hello all,
I am currently working on a game engine for use with my game development that I would like to be as flexible as possible.  As such the exact requirements for how things should work can't be nailed down to a specific implementation and I am looking for, at least now, a default good average case scenario design.
Here is what I have implemented:
Deferred rendering using OpenGL Arbitrary number of lights and shadow mapping Each rendered object, as defined by a set of geometry, textures, animation data, and a model matrix is rendered with its own draw call Skeletal animations implemented on the GPU.   Model matrix transformation implemented on the GPU Frustum and octree culling for optimization Here are my questions and concerns:
Doing the skeletal animation on the GPU, currently, requires doing the skinning for each object multiple times per frame: once for the initial geometry rendering and once for the shadow map rendering for each light for which it is not culled.  This seems very inefficient.  Is there a way to do skeletal animation on the GPU only once across these render calls? Without doing the model matrix transformation on the CPU, I fail to see how I can easily batch objects with the same textures and shaders in a single draw call without passing a ton of matrix data to the GPU (an array of model matrices then an index for each vertex into that array for transformation purposes?) If I do the matrix transformations on the CPU, It seems I can't really do the skinning on the GPU as the pre-transformed vertexes will wreck havoc with the calculations, so this seems not viable unless I am missing something Overall it seems like simplest solution is to just do all of the vertex manipulation on the CPU and pass the pre-transformed data to the GPU, using vertex shaders that do basically nothing.  This doesn't seem the most efficient use of the graphics hardware, but could potentially reduce the number of draw calls needed.

Really, I am looking for some advice on how to proceed with this, how something like this is typically handled.  Are the multiple draw calls and skinning calculations not a huge deal?  I would LIKE to save as much of the CPU's time per frame so it can be tasked with other things, as to keep CPU resources open to the implementation of the engine.  However, that becomes a moot point if the GPU becomes a bottleneck.

• Hello!
I would like to introduce Diligent Engine, a project that I've been recently working on. Diligent Engine is a light-weight cross-platform abstraction layer between the application and the platform-specific graphics API. Its main goal is to take advantages of the next-generation APIs such as Direct3D12 and Vulkan, but at the same time provide support for older platforms via Direct3D11, OpenGL and OpenGLES. Diligent Engine exposes common front-end for all supported platforms and provides interoperability with underlying native API. Shader source code converter allows shaders authored in HLSL to be translated to GLSL and used on all platforms. Diligent Engine supports integration with Unity and is designed to be used as a graphics subsystem in a standalone game engine, Unity native plugin or any other 3D application. It is distributed under Apache 2.0 license and is free to use. Full source code is available for download on GitHub.
Features:
True cross-platform Exact same client code for all supported platforms and rendering backends No #if defined(_WIN32) ... #elif defined(LINUX) ... #elif defined(ANDROID) ... No #if defined(D3D11) ... #elif defined(D3D12) ... #elif defined(OPENGL) ... Exact same HLSL shaders run on all platforms and all backends Modular design Components are clearly separated logically and physically and can be used as needed Only take what you need for your project (do not want to keep samples and tutorials in your codebase? Simply remove Samples submodule. Only need core functionality? Use only Core submodule) No 15000 lines-of-code files Clear object-based interface No global states Key graphics features: Automatic shader resource binding designed to leverage the next-generation rendering APIs Multithreaded command buffer generation 50,000 draw calls at 300 fps with D3D12 backend Descriptor, memory and resource state management Modern c++ features to make code fast and reliable The following platforms and low-level APIs are currently supported:
Windows Desktop: Direct3D11, Direct3D12, OpenGL Universal Windows: Direct3D11, Direct3D12 Linux: OpenGL Android: OpenGLES MacOS: OpenGL iOS: OpenGLES API Basics
Initialization
The engine can perform initialization of the API or attach to already existing D3D11/D3D12 device or OpenGL/GLES context. For instance, the following code shows how the engine can be initialized in D3D12 mode:
#include "RenderDeviceFactoryD3D12.h" using namespace Diligent; // ...  GetEngineFactoryD3D12Type GetEngineFactoryD3D12 = nullptr; // Load the dll and import GetEngineFactoryD3D12() function LoadGraphicsEngineD3D12(GetEngineFactoryD3D12); auto *pFactoryD3D11 = GetEngineFactoryD3D12(); EngineD3D12Attribs EngD3D12Attribs; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[0] = 1024; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[1] = 32; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[2] = 16; EngD3D12Attribs.CPUDescriptorHeapAllocationSize[3] = 16; EngD3D12Attribs.NumCommandsToFlushCmdList = 64; RefCntAutoPtr<IRenderDevice> pRenderDevice; RefCntAutoPtr<IDeviceContext> pImmediateContext; SwapChainDesc SwapChainDesc; RefCntAutoPtr<ISwapChain> pSwapChain; pFactoryD3D11->CreateDeviceAndContextsD3D12( EngD3D12Attribs, &pRenderDevice, &pImmediateContext, 0 ); pFactoryD3D11->CreateSwapChainD3D12( pRenderDevice, pImmediateContext, SwapChainDesc, hWnd, &pSwapChain ); Creating Resources
Device resources are created by the render device. The two main resource types are buffers, which represent linear memory, and textures, which use memory layouts optimized for fast filtering. To create a buffer, you need to populate BufferDesc structure and call IRenderDevice::CreateBuffer(). The following code creates a uniform (constant) buffer:
BufferDesc BuffDesc; BufferDesc.Name = "Uniform buffer"; BuffDesc.BindFlags = BIND_UNIFORM_BUFFER; BuffDesc.Usage = USAGE_DYNAMIC; BuffDesc.uiSizeInBytes = sizeof(ShaderConstants); BuffDesc.CPUAccessFlags = CPU_ACCESS_WRITE; m_pDevice->CreateBuffer( BuffDesc, BufferData(), &m_pConstantBuffer ); Similar, to create a texture, populate TextureDesc structure and call IRenderDevice::CreateTexture() as in the following example:
TextureDesc TexDesc; TexDesc.Name = "My texture 2D"; TexDesc.Type = TEXTURE_TYPE_2D; TexDesc.Width = 1024; TexDesc.Height = 1024; TexDesc.Format = TEX_FORMAT_RGBA8_UNORM; TexDesc.Usage = USAGE_DEFAULT; TexDesc.BindFlags = BIND_SHADER_RESOURCE | BIND_RENDER_TARGET | BIND_UNORDERED_ACCESS; TexDesc.Name = "Sample 2D Texture"; m_pRenderDevice->CreateTexture( TexDesc, TextureData(), &m_pTestTex ); Initializing Pipeline State
Diligent Engine follows Direct3D12 style to configure the graphics/compute pipeline. One big Pipelines State Object (PSO) encompasses all required states (all shader stages, input layout description, depth stencil, rasterizer and blend state descriptions etc.)
To create a shader, populate ShaderCreationAttribs structure. An important member is ShaderCreationAttribs::SourceLanguage. The following are valid values for this member:
SHADER_SOURCE_LANGUAGE_DEFAULT  - The shader source format matches the underlying graphics API: HLSL for D3D11 or D3D12 mode, and GLSL for OpenGL and OpenGLES modes. SHADER_SOURCE_LANGUAGE_HLSL  - The shader source is in HLSL. For OpenGL and OpenGLES modes, the source code will be converted to GLSL. See shader converter for details. SHADER_SOURCE_LANGUAGE_GLSL  - The shader source is in GLSL. There is currently no GLSL to HLSL converter. To allow grouping of resources based on the frequency of expected change, Diligent Engine introduces classification of shader variables:
Static variables (SHADER_VARIABLE_TYPE_STATIC) are variables that are expected to be set only once. They may not be changed once a resource is bound to the variable. Such variables are intended to hold global constants such as camera attributes or global light attributes constant buffers. Mutable variables (SHADER_VARIABLE_TYPE_MUTABLE) define resources that are expected to change on a per-material frequency. Examples may include diffuse textures, normal maps etc. Dynamic variables (SHADER_VARIABLE_TYPE_DYNAMIC) are expected to change frequently and randomly. This post describes the resource binding model in Diligent Engine.
The following is an example of shader initialization:
To create a pipeline state object, define instance of PipelineStateDesc structure. The structure defines the pipeline specifics such as if the pipeline is a compute pipeline, number and format of render targets as well as depth-stencil format:
// This is a graphics pipeline PSODesc.IsComputePipeline = false; PSODesc.GraphicsPipeline.NumRenderTargets = 1; PSODesc.GraphicsPipeline.RTVFormats[0] = TEX_FORMAT_RGBA8_UNORM_SRGB; PSODesc.GraphicsPipeline.DSVFormat = TEX_FORMAT_D32_FLOAT; The structure also defines depth-stencil, rasterizer, blend state, input layout and other parameters. For instance, rasterizer state can be defined as in the code snippet below:
// Init rasterizer state RasterizerStateDesc &RasterizerDesc = PSODesc.GraphicsPipeline.RasterizerDesc; RasterizerDesc.FillMode = FILL_MODE_SOLID; RasterizerDesc.CullMode = CULL_MODE_NONE; RasterizerDesc.FrontCounterClockwise = True; RasterizerDesc.ScissorEnable = True; //RSDesc.MultisampleEnable = false; // do not allow msaa (fonts would be degraded) RasterizerDesc.AntialiasedLineEnable = False; When all fields are populated, call IRenderDevice::CreatePipelineState() to create the PSO:
Shader resource binding in Diligent Engine is based on grouping variables in 3 different groups (static, mutable and dynamic). Static variables are variables that are expected to be set only once. They may not be changed once a resource is bound to the variable. Such variables are intended to hold global constants such as camera attributes or global light attributes constant buffers. They are bound directly to the shader object:

m_pPSO->CreateShaderResourceBinding(&m_pSRB); Dynamic and mutable resources are then bound through SRB object:
m_pSRB->GetVariable(SHADER_TYPE_VERTEX, "tex2DDiffuse")->Set(pDiffuseTexSRV); m_pSRB->GetVariable(SHADER_TYPE_VERTEX, "cbRandomAttribs")->Set(pRandomAttrsCB); The difference between mutable and dynamic resources is that mutable ones can only be set once for every instance of a shader resource binding. Dynamic resources can be set multiple times. It is important to properly set the variable type as this may affect performance. Static variables are generally most efficient, followed by mutable. Dynamic variables are most expensive from performance point of view. This post explains shader resource binding in more details.
Setting the Pipeline State and Invoking Draw Command
Before any draw command can be invoked, all required vertex and index buffers as well as the pipeline state should be bound to the device context:
// Clear render target const float zero[4] = {0, 0, 0, 0}; m_pContext->ClearRenderTarget(nullptr, zero); // Set vertex and index buffers IBuffer *buffer[] = {m_pVertexBuffer}; Uint32 offsets[] = {0}; Uint32 strides[] = {sizeof(MyVertex)}; m_pContext->SetVertexBuffers(0, 1, buffer, strides, offsets, SET_VERTEX_BUFFERS_FLAG_RESET); m_pContext->SetIndexBuffer(m_pIndexBuffer, 0); m_pContext->SetPipelineState(m_pPSO); Also, all shader resources must be committed to the device context:
m_pContext->CommitShaderResources(m_pSRB, COMMIT_SHADER_RESOURCES_FLAG_TRANSITION_RESOURCES); When all required states and resources are bound, IDeviceContext::Draw() can be used to execute draw command or IDeviceContext::DispatchCompute() can be used to execute compute command. Note that for a draw command, graphics pipeline must be bound, and for dispatch command, compute pipeline must be bound. Draw() takes DrawAttribs structure as an argument. The structure members define all attributes required to perform the command (primitive topology, number of vertices or indices, if draw call is indexed or not, if draw call is instanced or not, if draw call is indirect or not, etc.). For example:
DrawAttribs attrs; attrs.IsIndexed = true; attrs.IndexType = VT_UINT16; attrs.NumIndices = 36; attrs.Topology = PRIMITIVE_TOPOLOGY_TRIANGLE_LIST; pContext->Draw(attrs); Tutorials and Samples
The GitHub repository contains a number of tutorials and sample applications that demonstrate the API usage.

AntTweakBar sample demonstrates how to use AntTweakBar library to create simple user interface.

Atmospheric scattering sample is a more advanced example. It demonstrates how Diligent Engine can be used to implement various rendering tasks: loading textures from files, using complex shaders, rendering to textures, using compute shaders and unordered access views, etc.

The repository includes Asteroids performance benchmark based on this demo developed by Intel. It renders 50,000 unique textured asteroids and lets compare performance of D3D11 and D3D12 implementations. Every asteroid is a combination of one of 1000 unique meshes and one of 10 unique textures.

Integration with Unity
Diligent Engine supports integration with Unity through Unity low-level native plugin interface. The engine relies on Native API Interoperability to attach to the graphics API initialized by Unity. After Diligent Engine device and context are created, they can be used us usual to create resources and issue rendering commands. GhostCubePlugin shows an example how Diligent Engine can be used to render a ghost cube only visible as a reflection in a mirror.

• By Yxjmir
I'm trying to load data from a .gltf file into a struct to use to load a .bin file. I don't think there is a problem with how the vertex positions are loaded, but with the indices. This is what I get when drawing with glDrawArrays(GL_LINES, ...):

Also, using glDrawElements gives a similar result. Since it looks like its drawing triangles using the wrong vertices for each face, I'm assuming it needs an index buffer/element buffer. (I'm not sure why there is a line going through part of it, it doesn't look like it belongs to a side, re-exported it without texture coordinates checked, and its not there)
I'm using jsoncpp to load the GLTF file, its format is based on JSON. Here is the gltf struct I'm using, and how I parse the file:
glBindVertexArray(g_pGame->m_VAO);
glDrawElements(GL_LINES, g_pGame->m_indices.size(), GL_UNSIGNED_BYTE, (void*)0); // Only shows with GL_UNSIGNED_BYTE
glDrawArrays(GL_LINES, 0, g_pGame->m_vertexCount);
So, I'm asking what type should I use for the indices? it doesn't seem to be unsigned short, which is what I selected with the Khronos Group Exporter for blender. Also, am I reading part or all of the .bin file wrong?
Test.gltf
Test.bin

• That means how do I use base DirectX or OpenGL api's to make a physics based destruction simulation?
Will it be just smart rendering or something else is required?

# OpenGL opengl 4 tessellation linker error

This topic is 2146 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hi,

I'm trying to do some basic tessellation, but I've ran into a strange problem. My glsl code compiles fine, but when I try to render some geometry with it, I get the invalid operation error. I tried to debug this issue with gdebugger, and interestingly it gives me a AP_PROGRAM_LINK_FAILED_ERROR. This is strange because I do check if the linking went right (GL_LINK_STATUS), and I get no errors even if I directly check the linking with glGetError. The geometry that I tried to render works fine with other shaders.
I followed this tutorial: http://prideout.net/blog/?p=48

Here's the glsl code:
 [vertex shader] #version 410 in vec4 in_vertex; //incoming vertex attribute in object space out cross_shader_data { vec3 position; } o; void main() { o.position = in_vertex.xyz; //pass the data to the TC shader } [tessellation control shader] #version 410 layout(vertices = 3) out; //a patch should consist of 3 vertices, thus essentially defining a vertex in cross_shader_data { vec3 position; } i[]; out cross_shader_data { vec3 position; } o[]; uniform float tess_level_inner; uniform float tess_level_outer; void main() { o[gl_InvocationID].position = i[gl_InvocationID].position; //pass the vertex data to the TE shader if(gl_InvocationID == 0) //define tessellation levels { gl_TessLevelInner[0] = tess_level_inner; gl_TessLevelOuter[0] = tess_level_outer; gl_TessLevelOuter[1] = tess_level_outer; gl_TessLevelOuter[2] = tess_level_outer; } } [tessellation evaluation shader] #version 410 layout(triangles, equal_spacing, ccw) in; //process triangles, using equal spacing, and they'll be in counter-clockwise order in cross_shader_data { vec3 position; } i[]; out cross_shader_data { vec3 position; vec3 patch_distance; } o; uniform mat4 modelviewproj; void main() { vec3 p0 = gl_TessCoord.x * i[0].position; vec3 p1 = gl_TessCoord.y * i[1].position; vec3 p2 = gl_TessCoord.z * i[2].position; o.patch_distance = gl_TessCoord; o.position = normalize(p0 + p1 + p2); //create the new vertex gl_Position = modelviewproj * vec4(o.position, 1); //do the transformation before passing to the geometry shader } [geometry shader] #version 410 layout(triangles) in; //process triangles layout(triangle_strip, max_vertices = 3) out; //spit out triangle strips that consist of max 3 vertices in cross_shader_data { vec3 position; vec3 patch_distance; } i[3]; out cross_shader_data { vec3 face_normal; vec3 patch_distance; vec3 tri_distance; } o; uniform mat3 normal_mat; void main() { vec3 a = i[2].position - i[0].position; vec3 b = i[1].position - i[0].position; o.face_normal = normal_mat * normalize(cross(a, b)); //transform face normal into view space o.patch_distance = i[0].patch_distance; o.tri_distance = vec3(1, 0, 0); gl_Position = gl_in[0].gl_Position; EmitVertex(); o.patch_distance = i[1].patch_distance; o.tri_distance = vec3(0, 1, 0); gl_Position = gl_in[1].gl_Position; EmitVertex(); o.patch_distance = i[2].patch_distance; o.tri_distance = vec3(0, 0, 1); gl_Position = gl_in[2].gl_Position; EmitVertex(); } [pixel shader] #version 410 in cross_shader_data { vec3 face_normal; vec3 tri_distance; vec3 patch_distance; } i; out vec4 color; float amplify(float d, float scale, float offset) { d = scale * d + offset; d = clamp(d, 0, 1); d = 1 - exp2(-2 * d * d); return d; } void main() { vec3 n = normalize(i.face_normal); vec3 l = vec3(0, 1, 0); float ndotl = max(dot(n, l), 0); vec3 result = ndotl * vec3(1, 1, 1); //do some lighting float d1 = min(min(i.tri_distance.x, i.tri_distance.y), i.tri_distance.z); float d2 = min(min(i.patch_distance.x, i.patch_distance.y), i.patch_distance.z); result *= amplify(d1, 40, -0.5) * amplify(d2, 60, -0.5); //just some edge outlining color = vec4(result, 1); } 

Best regards,
Yours3!f Edited by Yours3!f

##### Share on other sites
Hi!

For some reason passing structs between shader stages doesn’t work anymore (at least the way you/I did it…). At some point it did. I remember it fairly well, since I was very happy to see that GLSL finally allowed it, too (like HLSL). But with current drivers it doesn’t work anymore. I had to rewrite some of my old shaders, too. Maybe it just wasn’t specification compliant and only nVidia drivers allowed it.

If you follow the tutorial you linked above, you should be fine. So, something like:
in vec3 i_position[]; out vec3 o_position[];
And so on.

And yes, I was also confused that the GLSL compiler doesn't complain at all.

Cheers!

##### Share on other sites

Hi!

For some reason passing structs between shader stages doesn’t work anymore (at least the way you/I did it…). At some point it did. I remember it fairly well, since I was very happy to see that GLSL finally allowed it, too (like HLSL). But with current drivers it doesn’t work anymore. I had to rewrite some of my old shaders, too. Maybe it just wasn’t specification compliant and only nVidia drivers allowed it.

If you follow the tutorial you linked above, you should be fine. So, something like:
in vec3 i_position[]; out vec3 o_position[];
And so on.

And yes, I was also confused that the GLSL compiler doesn't complain at all.

Cheers!

Thank you Tsus for the reply

I tried to convert the interface blocks to traditional in-outs but somethings still wrong... What am I missing?

drivers... I even made a segfault to the compiler while converting the shaders... (I mean it segfaulted when linking, and the last function in the stack was somewhere in the catalyst drivers... 12.4 64bit linux)

this is how the shaders look like now:
 [vertex shader] #version 410 in vec4 in_vertex; out vec3 v_position; void main() { v_position = in_vertex.xyz; } [tessellation control shader] #version 410 layout(vertices = 3) out; in vec3 v_position[]; out vec3 tc_position[]; uniform float tess_level_inner; uniform float tess_level_outer; void main() { tc_position[gl_InvocationID] = v_position[gl_InvocationID]; if(gl_InvocationID == 0) { gl_TessLevelInner[0] = tess_level_inner; gl_TessLevelOuter[0] = tess_level_outer; gl_TessLevelOuter[1] = tess_level_outer; gl_TessLevelOuter[2] = tess_level_outer; } } [tessellation evaluation shader] #version 410 layout(triangles, equal_spacing, ccw) in; in vec3 tc_position[]; out vec3 te_position; out vec3 te_patch_distance; uniform mat4 modelviewproj; void main() { vec3 p0 = gl_TessCoord.x * tc_position[0]; vec3 p1 = gl_TessCoord.y * tc_position[1]; vec3 p2 = gl_TessCoord.z * tc_position[2]; te_patch_distance = gl_TessCoord; te_position = normalize(p0 + p1 + p2); gl_Position = modelviewproj * vec4(te_position, 1); } [geometry shader] #version 410 layout(triangles) in; layout(triangle_strip, max_vertices = 3) out; in vec3 te_position[3]; in vec3 te_patch_distance[3]; out vec3 g_face_normal; out vec3 g_patch_distance; out vec3 g_tri_distance; uniform mat3 normal_mat; void main() { vec3 a = te_position[2] - te_position[0]; vec3 b = te_position[1] - te_position[0]; g_face_normal = normal_mat * normalize(cross(a, b)); g_patch_distance = te_patch_distance[0]; g_tri_distance = vec3(1, 0, 0); gl_Position = gl_in[0].gl_Position; EmitVertex(); g_patch_distance = te_patch_distance[1]; g_tri_distance = vec3(0, 1, 0); gl_Position = gl_in[1].gl_Position; EmitVertex(); g_patch_distance = te_patch_distance[2]; g_tri_distance = vec3(0, 0, 1); gl_Position = gl_in[2].gl_Position; EmitVertex(); } [pixel shader] #version 410 in vec3 g_face_normal; in vec3 g_tri_distance; in vec3 g_patch_distance; out vec4 color; float amplify(float d, float scale, float offset) { d = scale * d + offset; d = clamp(d, 0, 1); d = 1 - exp2(-2 * d * d); return d; } void main() { vec3 n = normalize(g_face_normal); vec3 l = vec3(0, 1, 0); float ndotl = max(dot(n, l), 0); vec3 result = ndotl * vec3(1, 1, 1); float d1 = min(min(g_tri_distance.x, g_tri_distance.y), g_tri_distance.z); float d2 = min(min(g_patch_distance.x, g_patch_distance.y), g_patch_distance.z); result *= amplify(d1, 40, -0.5) * amplify(d2, 60, -0.5); color = vec4(result, 1); } 

Best regards,
Yours3!f Edited by Yours3!f

##### Share on other sites
Hi!

The code you posted worked fairly well. I just changed some minor things to make it fit to my demo app, here.
In particular, I used explicit vertex attribute binding in the vertex shader:
layout(location=0) in vec3 in_vertex;

For all uniform parameters I utilized a uniform buffer object, e.g.:
layout(std140) uniform TessFactor { float tess_level_inner; float tess_level_outer; };

Eventually, I removed the normalization of te_position in your tessellation evaluation shader (barycentric interpolation doesn't require it).
//te_position = normalize(p0 + p1 + p2); te_position = p0 + p1 + p2;

It works on my end. I tested on a GeForce 460 GTX (Win 7, 64 Bit).

Good luck! Hopefully you find a way to get it running, too.
Best regards

##### Share on other sites
just a couple of questions in connection with your modifications:

The code you posted worked fairly well. I just changed some minor things to make it fit to my demo app, here.
In particular, I used explicit vertex attribute binding in the vertex shader:
layout(location=0) in vec3 in_vertex;

I use special "shader controller" files for this so I don't have to worry about which attribute belong to which location.

For all uniform parameters I utilized a uniform buffer object, e.g.:
layout(std140) uniform TessFactor { float tess_level_inner; float tess_level_outer; };
[/quote]

is that a performance win, or you just like to use uniforms this way?

Eventually, I removed the normalization of te_position in your tessellation evaluation shader (barycentric interpolation doesn't require it).
//te_position = normalize(p0 + p1 + p2); te_position = p0 + p1 + p2;
[/quote]

yeah I still need to dig deeper into the barycentric coordinates...

It works on my end. I tested on a GeForce 460 GTX (Win 7, 64 Bit).[/quote]

I guess this is the relevant bit. I have an AMD Radeon HD 5670 (Linux, 64 bit, same problem on Win 7 64 bit with same drivers) with newest drivers. So can you please verify the code on AMD as well? Because if thats the problem, then I guess I should contact the AMD dev guys to fix this...

##### Share on other sites
Hi,

I did the modifications only to get the code running in a small tessellation exercise I wrote a while back. I didn’t want to change much on the CPU side, so I just used the uniform buffer objects that were passed in already.
On the CPU side I didn’t specify the attribute binding, so I had to do it in GLSL. Doing this in GLSL is just a personal favor.

[quote name='Tsus' timestamp='1336296166' post='4937734']
For all uniform parameters I utilized a uniform buffer object, e.g.:
layout(std140) uniform TessFactor { float tess_level_inner; float tess_level_outer; };

is that a performance win, or you just like to use uniforms this way?
[/quote]
I think the performance win isn’t that big. It’s more that I like that sort of grouping as it reminds me of constant buffers in Dx.

[quote name='Tsus' timestamp='1336296166' post='4937734']
It works on my end. I tested on a GeForce 460 GTX (Win 7, 64 Bit).

I guess this is the relevant bit. I have an AMD Radeon HD 5670 (Linux, 64 bit, same problem on Win 7 64 bit with same drivers) with newest drivers. So can you please verify the code on AMD as well? Because if thats the problem, then I guess I should contact the AMD dev guys to fix this...
[/quote]
Sorry, I neither have an AMD at home nor in the lab.
I attached the code so you can test it yourself.

Yes, you should probably report this to AMD if it turns out to be some sort of bug.

Cheers!

##### Share on other sites

Hi,

I did the modifications only to get the code running in a small tessellation exercise I wrote a while back. I didn’t want to change much on the CPU side, so I just used the uniform buffer objects that were passed in already.
On the CPU side I didn’t specify the attribute binding, so I had to do it in GLSL. Doing this in GLSL is just a personal favor.

[quote name='Yours3!f' timestamp='1336304020' post='4937748']
[quote name='Tsus' timestamp='1336296166' post='4937734']
For all uniform parameters I utilized a uniform buffer object, e.g.:
layout(std140) uniform TessFactor { float tess_level_inner; float tess_level_outer; };

is that a performance win, or you just like to use uniforms this way?
[/quote]
I think the performance win isn’t that big. It’s more that I like that sort of grouping as it reminds me of constant buffers in Dx.

[quote name='Tsus' timestamp='1336296166' post='4937734']
It works on my end. I tested on a GeForce 460 GTX (Win 7, 64 Bit).

I guess this is the relevant bit. I have an AMD Radeon HD 5670 (Linux, 64 bit, same problem on Win 7 64 bit with same drivers) with newest drivers. So can you please verify the code on AMD as well? Because if thats the problem, then I guess I should contact the AMD dev guys to fix this...
[/quote]
Sorry, I neither have an AMD at home nor in the lab.
I attached the code so you can test it yourself.

Yes, you should probably report this to AMD if it turns out to be some sort of bug.

Cheers!
[/quote]

Thank you this saved me writing an example.

Well I had to do some modifications to get it running, but eventually it was running, so I guess I'm doing something wrong.
I've attached the modified code. (tessellation.dom, and Tessellation_end.cpp, plus file renamings and I added headers, libs and dlls) Edited by Yours3!f

##### Share on other sites
HEUREKA XD

SOLVED

I examined your example, and found out one thing that's entirely different: how you draw your mesh.

so I just had to include the glPatchParameter function and change the glDrawElements from GL_TRIANGLES to GL_PATCHES... this is quite stupid... so this is what a working source does to me

Thank your for the help!!! Edited by Yours3!f

##### Share on other sites
Hi,

just out of curiosity I tried the technique with interface blocks, and it worked, so that wasn't the problem seems like the newest drivers are capable of this.

another thing is that the normalization in the tessellation evaluation shader IS needed, without it the geometry won't "emerge" out of the surface. (see pictures)

##### Share on other sites
Hi,

just out of curiosity I tried the technique with interface blocks, and it worked, so that wasn't the problem seems like the newest drivers are capable of this.

Nice! Thanks for the info! I’ll give it a try again, later.

another thing is that the normalization in the tessellation evaluation shader IS needed, without it the geometry won't "emerge" out of the surface.

Wouldn't this only work for unit-spheres?
Most often, I just pick an easy tessellation scheme like phong tessellation. Edited by Tsus