• 12
• 12
• 9
• 10
• 13
• ### 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 Major OpenGL happiness =)

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

## Recommended Posts

Yes, it´s true it´s making me unhappy - and plenty of =))) Joking aside, I have horrible performance problems and don´t know what I am doing wrong. I spent some time to set everything up with shaders, vertex buffers etc. and have focused more on framework development rather than pumping triangles to the gfx cards, trusting everything would be fine. Nevertheless I was curious and have done some stress test to find out how many batches I can actually push per frame, inspired by threads that were floating round here in the forum in the past days *wink* Unfortunately NOT many ! What I do is I put a simple texture mapped (shader) cube into a vertex buffer and create an index buffer and repeat the vertices of the cube all over for 400 times. So a cube with 12 verts is rendered with 400x overdraw. The reason for that is I haven´t got a mesh loader yet :-) Then I will go on and render these buffers with 10x calls to glDrawRangeElements, so we get 4000x cube overdraw - a cake isn´t it !? Well no... performance is as low as 10fps I have got an AMD 2GHz / Geforce 6800LE 128MB. 400 x 12 x 10 = 48.000 triangles <- that´s ridiculous, I would bet glBegin/glEnd could do THAT, damn ! Life is soo hard sometimes. I had fears that it could be java, that is soo slow (although i know it is definetly not slow), but a quick profiling convinced me that the application is hanging around over 80% of its time in glFlush(). Is this a typical performance pattern for OpenGL ? I can hardly imagine. At this point I would really appreciate some help... I have tried to apply everything I read here on gamedev and else about vbo usage etc. But unfortunately performance is that bad. Here comes a glIntercept log, so you can check if I do something really stupid =)
===============================================================================
GLIntercept version 0.5 Log generated on: Mon Jun 16 22:31:17 2008

===============================================================================

wglChoosePixelFormat(0x95010de0,0x90fb20)
----->wglDescribePixelFormat(0x95010de0,1,0,0x0000)=102 =7
wglSetPixelFormat(0x95010de0,7,0x90fb20)
----->wglDescribePixelFormat(0x95010de0,7,40,0x90f9c0)=102 =true
wglCreateContext(0x95010de0)
----->wglGetPixelFormat(0x95010de0)=7
----->wglDescribePixelFormat(0x95010de0,7,40,0x90f9c8)=102
----->wglGetPixelFormat(0x95010de0)=7
----->wglDescribePixelFormat(0x95010de0,1,0,0x0000)=102 =0x10000
wglMakeCurrent(0x95010de0,0x10000)
----->wglGetPixelFormat(0x95010de0)=7
----->wglGetPixelFormat(0x95010de0)=7
----->wglDescribePixelFormat(0x95010de0,1,0,0x0000)=102 =true
glEnable(GL_DEPTH_TEST)
glEnable(GL_TEXTURE_2D)
glTexParameterf(GL_TEXTURE_2D,GL_TEXTURE_WRAP_S,10497.000000)
glTexParameterf(GL_TEXTURE_2D,GL_TEXTURE_WRAP_T,10497.000000)
glTexEnvf(GL_TEXTURE_ENV,GL_TEXTURE_ENV_MODE,8448.000000)
glDepthFunc(GL_LESS)
glDisable(GL_CULL_FACE)
glEnableClientState(GL_INDEX_ARRAY)
glGetIntegerv(GL_MAX_ELEMENTS_VERTICES,0x2ef6090)
glGetString(GL_VENDOR)="NVIDIA Corporation"
glViewport(0,0,640,480)
glClearColor(0.000000,0.000000,0.500000,0.000000)
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glCreateProgram()=3
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetUniformLocation(3,"modelviewProjection")=0
glGetAttribLocation(3,"color")=1
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glCreateProgram()=6
glGetError()=GL_NO_ERROR
glGetError()=GL_NO_ERROR
glGetUniformLocation(6,"modelviewProjection")=0
glGetAttribLocation(6,"texcoord")=1
glActiveTexture(GL_TEXTURE0)
glGenTextures(1,0x90fb58)
glBindTexture(GL_TEXTURE_2D,1)
glTexParameterf(GL_TEXTURE_2D,GL_TEXTURE_MAG_FILTER,9729.000000)
glTexParameterf(GL_TEXTURE_2D,GL_TEXTURE_MIN_FILTER,9729.000000)
glTexImage2D(GL_TEXTURE_2D,0,GL_RGBA,128,128,0,GL_RGBA,GL_UNSIGNED_BYTE,0x22a237c4)
glGenBuffers(1,0x90fbf8)
glBindBuffer(GL_ARRAY_BUFFER,1)
glBufferData(GL_ARRAY_BUFFER,160,0x2a74000,GL_STATIC_DRAW)
glGenBuffers(1,0x90fbf8)
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,2)
glBufferData(GL_ELEMENT_ARRAY_BUFFER,57600,0x2aca000,GL_STATIC_DRAW)
glGenBuffers(1,0x90fbf8)
glBindBuffer(GL_ARRAY_BUFFER,3)
glBufferData(GL_ARRAY_BUFFER,192,0x2ac9000,GL_STATIC_DRAW)
glBindBuffer(GL_ARRAY_BUFFER,1)
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER,2)
glEnableClientState(GL_VERTEX_ARRAY)
glVertexPointer(3,GL_FLOAT,20,0x0000)
glEnableVertexAttribArray(1)
glVertexAttribPointer(1,2,GL_FLOAT,false,20,0x000c)
glUseProgram(6)
glActiveTexture(GL_TEXTURE0)
glBindTexture(GL_TEXTURE_2D,1)
glUniformMatrix4fv(0,1,false,[1.000000,0.000000,0.000000,0.000000,0.000000,1.000000,
0.000000,0.000000,0.000000,0.000000,1.000000,1.000000,0.000000,0.000000,0.000000,1.000000])
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glFlush()
wglSwapBuffers(0x95010de0)=true
glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT)
glUniformMatrix4fv(0,1,false,[0.998401,0.001599,0.056508,0.056508,0.001599,0.998401,
-0.056508,-0.056508,-0.056508,0.056508,0.996802,0.996802,0.000000,0.000000,2.000000,3.000000])
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glDrawElements(GL_TRIANGLES,14400,GL_UNSIGNED_SHORT,0x0000) GLSL=6  Textures[ (0,1) ]
glFlush()
...

I even come to think that it may be in software... although the vendor string is clearly NVIDIA, so that should be fine. Other GL applications, that means not written by me *lol*, run fine. One even states that it performes 10000 draw calls per frame and does well... so there I am with my 10 calls... I would really appreciate help, because this damn performance thing is sucking my motivation for my gaming project. So you won´t let that happen, wouldn´t you ;-) Frederick [Edited by - Frederick on June 19, 2008 2:44:36 AM]

##### Share on other sites
You shouldn't be doing glFlush before a swap (or pretty much ever, really). The driver is happiest when it can buffer a few frames forward. I dunno if that would cause that much of a slowdown, though.

Also, how big are these cubes? Are they all in the center of the screen? If each one takes up 400x400=160000 pixels, with 4000x overdraw, that's 640 megapixels per frame, and 10 fps sounds downright speedy for that.

##### Share on other sites
Yeah sounds like you're fill rate limited. Try reducing the size of the cube so that its the size of a postage stamp on the screen, and repeat the test and see if performance improves.

##### Share on other sites
glEnableClientState(GL_INDEX_ARRAY)

probably a mistake there. This is for color indexing.

##### Share on other sites
You're making a fundamental mistake here: you're stressing fillrate, and you complain about geometry performance.

By repeating the same cube, the pixels on the cube will be drawn over and over. In Snetfel's scenario, it's the equivalent of drawing.. 813 full screens @ 1024x768... *every frame*. Hardly slow.

Y.

##### Share on other sites
Good morning everybody, at least on this side of the planet =)
And thanks for the answers ! I apologize, I was out yesterday night and could not answer...

Quote:
 Also, how big are these cubes? Are they all in the center of the screen? If each one takes up 400x400=160000 pixels, with 4000x overdraw, that's 640 megapixels per frame, and 10 fps sounds downright speedy for that.

Yesss, exactly - you guessed even the size very well =)) Actually its is a little bit smaller, but the backside gets drawn too. Very good observation, thank you very much. When I was setting this up, I wanted to test how many game objects I would be able to draw, thought that 4800 triangles is kinda okay for a game model.
What I forgot about is, that actual game polygons will (or should) never be so large, yes I believe I fill the screen several times =)
Is it right to say that modern hardware may draw millions of triangles, but when using that amount, the triangles should be more or less pixel-sized ?
So I have actually the decision between: 1) detail achieved by lots and lots of vertices and 2)detail achieved by lesser vertices but heavier shaders ?
Ok enough questions...

Quote:
 You shouldn't be doing glFlush before a swap (or pretty much ever, really). The driver is happiest when it can buffer a few frames forward. I dunno if that would cause that much of a slowdown, though.

Unfortunately that does not work, i removed the glFlush and nothing is drawn at all. So should I triggerd it every third frame or so, or is there another option ?

Quote:
 glEnableClientState(GL_INDEX_ARRAY)probably a mistake there. This is for color indexing.

Thanks a lot for checking the gl-calls V-Man =) Yes that is indeed a mistake... wonder why the program doesn´t crash.

Quote:
 Yeah sounds like you're fill rate limited. Try reducing the size of the cube so that its the size of a postage stamp on the screen, and repeat the test and see if performance improves.

I tried that and actually it went faster. I am relieved - so it is not my bad coding and a gfx card is not that wonder-cake that will just eat everything one throws at it, i just believed so =)
So I will continue my work and hopefully everything will be alright.

Quote:
 By repeating the same cube, the pixels on the cube will be drawn over and over. In Snetfel's scenario, it's the equivalent of drawing.. 813 full screens @ 1024x768... *every frame*. Hardly slow.

*looool*

813 screens =))))
Actually I did not realize that, believe me the result is an unimpressive rotating cube, just no sign that pixels to fill 813 screens are being pushed ;-)))

Cool, so I learned another thing, hope you don´t bother - everybody needs to make his / her experiences and filling 813 screens is quite funny isn´t it.

So one question remains: what to do with the glFlush() ? Maybe I need to set a parameter, that enables the driver to decide sovereignly (hope thats an english word :-P) when to flush its queue ?

Cheers and lots of thanks to you,
Frederick

##### Share on other sites
There shouldn't be any reason to call glFlush unless you have a very specific reason to. Just delete it.
IIRC SwapBuffers() calls it implicitly? Can someone verify this?

##### Share on other sites
Quote:
 Original post by MARS_999There shouldn't be any reason to call glFlush unless you have a very specific reason to. Just delete it.IIRC SwapBuffers() calls it implicitly? Can someone verify this?

SwapBuffers doesn't call glFlush. SwapBuffers sends a command to the driver that it is time swap.
Obviously you can't just swap the buffer all of a sudden. All commands just sitting in the commands buffer must be flushed, in other words sent to the driver and at the end, a swap command is inserted.

##### Share on other sites
Quote:
 Unfortunately that does not work, i removed the glFlush and nothing is drawn at all. So should I triggerd it every third frame or so, or is there another option ?

You need to use glFlush if you are doing single buffered rendering.
With double buffer, just use SwapBuffers.
I imagine there are a lot of bugs in your program and you need to spend a few days analyzing before you talk about performance issues.

##### Share on other sites
Quote:
 You need to use glFlush if you are doing single buffered rendering.With double buffer, just use SwapBuffers.

I am sorry that was my mistake I did the last test in a hurry... and some parts of the system were unfortunately not recompiled by my IDE. So nothing was drawn because it was a horrible slow version, i had running before =) And yes it is double-buffered - No problem with removing the glFlush().

...and the performance characteristics have changed now 80 percent of runtime is spend in glDrawRangeElements - does that sound right ?

I am able to push 4000 glDrawRangeElements calls in about 5 fps, this time not fillrate limited - I moved the cubes far away and put only one cube in each buffer =), still not too good, I believe.

Quote:
 I imagine there are a lot of bugs in your program and you need to spend a few days analyzing before you talk about performance issues.

Well, may be, but let me assure you, that I have written every part of it very carefully - I know every line and do lots of error checking. This is definetly not a nehe-type of project. Also I am a cs student in the last year, so actually my programming is hopefully not too bad, at least I know a thing or two.
Nevertheless there are unknows in the project as I never really pushed OpenGL before. Second it is a mixed-language project. C++/OpenGL for the very low-level part and java for everything else. Of course, there always may be errors but I already spent some time on this. The mistake with GL_INDEX_ARRAY may be the result of a thoughtless moment (it is confusing isn´t it) but that doesn´t apply to the project in general.

I am still not too happy... 1000 draw calls -> 20fps, so I will be restricted to the 300 suggested by NVIDIA, realistically I believe... is this good enough, or is there room for improvements ?