• 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 proper way to do antialiasing?

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

## Recommended Posts

I read this post recently: http://www.gamedev.net/community/forums/topic.asp?topic_id=107637 and the problem the first author had is the exact problem I am having now. I made a large object composed of hundreds of quads and I see thin lines along the joints of the textured object when I tried this antialiasing technique. Unfortunately the only response in the thread is not helpful. I do not want to force antialiasing through some control panel outside my application (this does work though). What other approach can I try? I am aware of the jitter technique with the accumulation buffer in the red book, but from what I read elsewhere it sounded like performance would be rather poor for that. How is opengl antialiasing done in real world applications? It seems like every approach I read about online has some fundamental problems or is an unofficial way of doing it.

##### Share on other sites
Well, the only response to that other thread does mention the solution, eventhough it's poorly worded: you need to enable multisampling. ARB_multisample used to be the only way of doing this. It essentially does the same as changing the settings through the driver panel, but controlled by your application.

Nowadays, however, there is a much more flexible, powerful and simple way to achieve fullscreen antialiasing: EXT_framebuffer_multisample. The idea is to create a special multisampled FBO, and render your scene to it. You can very easily enable multisampling on FBOs, and control the quality (and performance) of the antialiasing. This approach also allows you to switch between different multisample qualities on the fly. For example, render to a lower quality multisample buffer while the player is moving fast (he is less likely to notice the artifacts in quick game action), and render to a high quality buffer when he stops or moves very slowly.

Once your scene was rendered to such an FBO, you need to resolve the multisample buffer to the screen (or to another FBO). EXT_framebuffer_blit will do this.

##### Share on other sites
As far as I know, there's best to use multisampling (example - http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=46), but I recommend to do all antialiasing on your own using shaders in postprocess phase. Why? When you're using frame buffer object (FBO), you can do antialiasing just on NVidia GPUs, not ATI GPUs (and I've got ATI). Jitter antialiasing - well you can try, but I recommend supersampling (very high quality antialiasing, it's processing not just geometry, but even transparent objects) or multisampling (medium quality antialiasing, cause it's processing just geometry - used as extension). Anyway something about jitter antialiasing is here http://www.cse.msu.edu/~cse872/tutorial5.html

##### Share on other sites
Quote:
 Original post by Vilem OtteWhy? When you're using frame buffer object (FBO), you can do antialiasing just on NVidia GPUs, not ATI GPUs (and I've got ATI).

According to marketing

"All anti-aliasing features compatible with HDR rendering"

that ATI GPU can do it and it can do it with fp16 or maybe fp32 RTT.
This only means one thing : their GL drivers doesn't expose the feature but the feature works with D3D9

##### Share on other sites
Yes, thats true - but this is OpenGL forum - so no antialiasing and FBO on ATI yet :(

##### Share on other sites
Quote:
 Original post by Vilem Ottebut I recommend to do all antialiasing on your own using shaders in postprocess phase. Why? When you're using frame buffer object (FBO), you can do antialiasing just on NVidia GPUs, not ATI GPUs

This is not a valid reason. Why would you discard a perfectly fine, pretty much industry standard method of doing FSAA, just because one manufacturer is too incompetent to add it to their drivers ?

So ATI users won't get good AA. That's life. Let them complain to ATI, maybe they will react one day by releasing a driver that actually works. Or better, let them buy a good graphics card instead. sounds harsh ? Maybe. But I'm just sick of having to resort to bad workarounds just because of ATI.

Quote:
 Original post by Vilem Otte(and I've got ATI). Jitter antialiasing - well you can try, but I recommend supersampling (very high quality antialiasing, it's processing not just geometry,

Modern large tap multisampling is generally much higher quality than any type of practical supersampling. Realistically, you can only do 2x2 supersampling on todays resolutions, maybe 3x3 (at an extremely high performance cost). That's not enough for good quality. True, SS will also AA shaders and such, but other methods exist for this, in conjunction with MS, that are generally much higher quality and better performance.

Quote:
 Original post by Vilem Ottebut even transparent objects)

Transparency works fine with multisampling (alpha to coverage).

##### Share on other sites
Quote:
 Original post by Yann LSo ATI users won't get good AA. That's life. Let them complain to ATI, maybe they will react one day by releasing a driver that actually works. Or better, let them buy a good graphics card instead. sounds harsh ? Maybe. But I'm just sick of having to resort to bad workarounds just because of ATI.

I don't suppose you have anything to share about the 'best workaround' to do this in OpenGL on ATI cards?

##### Share on other sites
Quote:
 Original post by dmatterI don't suppose you have anything to share about the 'best workaround' to do this in OpenGL on ATI cards?

Don't do any advanced AA at all on ATI (advanced in this context means anything other than standard LDR AA on the framebuffer). Show a popup saying that advanced AA options are only supported on NVidia at this time, and explain why in laymans terms. Suggest updating the ATI drivers, just in case ATI/AMD fixed it by then (although the chances that our universe suddendly quantum tunnels into a world where ATI doesn't exist are probably much higher than this...)

##### Share on other sites
I should add that I am trying to do this through jogl. I am having trouble with the extensions such as GL_ARB_multisample and anything with WGL. I cannot say for sure, but I do not think these are accessible through the jogl api. I'm new to opengl and I don't want to start learning about shader languages if I can help it. If all I can reasonably get with supersampling is 2x, that isn't the approach I want to take. Also unless someone can challenge this, I am under the impression that using the accumulation buffer is slow, which means it isn't acceptable for real-time AA.

I would like the antialiasing to be compatible on whatever platform an average person could be expected to use. This means it should run on nvidia/ati and windows/mac os at least. It's not that critical for it to be compatible with any other configurations.

I hope my situation doesn't eliminate all the AA methods available. If you know how to use multisampling extensions in jogl I would apprecaite the help.

##### Share on other sites
Quote:
 This is not a valid reason. Why would you discard a perfectly fine, pretty much industry standard method of doing FSAA, just because one manufacturer is too incompetent to add it to their drivers ?

No, I would NOT discard it - It needs to conact ATI about support and discuss this with them.

Quote:
 So ATI users won't get good AA. That's life. Let them complain to ATI, maybe they will react one day by releasing a driver that actually works. Or better, let them buy a good graphics card instead. sounds harsh ? Maybe. But I'm just sick of having to resort to bad workarounds just because of ATI.

I'm too getting sick of them with their drivers and OpenGL support, really thinking about buying NVidia in next-generation (after many years).

Quote:
 Modern large tap multisampling is generally much higher quality than any type of practical supersampling. Realistically, you can only do 2x2 supersampling on todays resolutions, maybe 3x3 (at an extremely high performance cost). That's not enough for good quality. True, SS will also AA shaders and such, but other methods exist for this, in conjunction with MS, that are generally much higher quality and better performance.

Well, we can discuss quality here - I can do multisampling F.e. up to 8x filter in standart scene (etc. with normalmapping, HDR, complex models, reflections, ...) at F.e. 50 - 70 fps. I can too so Supersampling at 8x filter (this would probably need some tricky way, but it's possible), F.e. at 5 - 15 fps. Supersampling will have much higher quality, but very very bad performance. I'm most interested in raytracing - realtime raytracing and there supersampling is way (very slow way, but decent quality way).

Quote:
 Transparency works fine with multisampling (alpha to coverage).

It works fine using sampling alpha to coverage. I'm now much more interested in antialiasing technique, that wouldn't be so slow as supersampling (for realtime raytracing) - so it'd be achieveable in realtime with raytracing (this means no graphics card - for me, cause I'm using just CPUs).