• 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?

Archived

This topic is now archived and is closed to further replies.

OpenGL OpenGL and SDL. Is there an easy way?

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

Recommended Posts

A couple weeks ago I decided to spend my winter break teaching myself 3D/Game programming. So, I started out by looking for a good website that contained all the information that I would need. I then went through and looked into what 3D, windowing, and input APIs I would need. From what I have found there are two options: Direct X (with Direct 3D) and SDL (with OpenGL). So I then went and looked for some tutorials on how to get all this working. Seeing as how I am a big fan of cross platform compatability I decided to go with SDL/OpenGL. That was where my problems began. What I was hoping for was to be able to just sit down and start coding. What I ended up doing instead was spending the next 3 days tring to figure out how to get a bare bones program to compile using anything other than MSVC++. Everywhere I go there are tutorials for how to do this and that in MSVC++. Meanwhile, here I am, with my connection to the internet, a copy of CodeWarrior and a distinct dislike for MSVC. Teaching myself the art of compiling was not what I had in mind for my break. My question is this (finally): Is there an easy way to write and compile SDL/OpenGL applications without all the hassle of beefed up IDEs and optimizing compilers? What I''m imagining is writing my program in a text editor, telling a command line compiler where the required headers, libraries, and DLLs can be found, and then compiling and running my program. So far, after going through various tutorials, forums, websites, etc, all I have found are a collection of tutorials discribing how to get SDL/OpenGL working in MSVC++, and a couple tutorials that tell you to download their package that has everything setup for you and not learn to do it yourself. The reason I want the basics is because I want to learn what all is going on when I compile my programs, I don''t want to just "trust" that everything is going as planned and that MS or a guy with a website set everything up correctly. MORE RANTING: Why can''t it be like ANSI C where you write you program and compile it. No fuss. No worries. If you have libraries you want to use just let the compiler know where to find them and all is well. Sorry, this turned into quite the rant. I am very frustrated with all the MSVC++ stuff I''m finding. Even the people that are against the usage of MS and Direct X/3D use MSVC++ to write their programs which is even more frustrating. -Micah the Frustrated

Share on other sites
The best solution to your problem would be to quit using windows... it sucks (hardcore) and no self-respecting developer will use it in this day and age.

If you /really/ can''t switch to Linux,BSD,etc (and that would only be if you''re coding in a public library or school or something), then check out MinGW (http://www.mingw.org)... it''s a port of gcc for windoze... then you can compile at the command line like you wanted to. Also, if you really are going to use windoze, there are a couple of editors that are great for programming (ported from Linux): Emacs and Vim (search google, i don''t feel like looking up another url, hehe)

Share on other sites
Hey

Yeah, definetly stop using windows, but thats not the advice he wants, right?
Im using windows right now for myself and im using SDL/OpenGL

There is still loads of stuff I need to learn about OpenGL and SDL, but I got the bare bones working pretty soon.
Try looking under Nehe productions, he has an SDL basecode too.
It didnt work right away under Dev C++ (Uses mingw) but after some tweaking it did and its a lot easier than Direct X for sure.

Otherwise, try looking at the examples in on www.libsdl.org there is a part about opengl on the site with some of the Nehe tuts as well

Share on other sites
You have to do some weird stuff to get it to work in MSVC. As the first poster said: It''s easier with GCC, preferably in a unix shell; but, understandably, not everyone has that option . I''m not going to go so far as to say the "no self respecting developer part," since many do and will continue to in the future. Anyway, here''s what I do:
• Setup a Win32 Application project.

1. Check "Ignore all default libraries.
2. Paste this into the Library/object modules text box: msvcrt.lib libc.lib libcp.lib kernel32.lib sdlmain.lib sdl.lib opengl32.lib glu32.lib

• Remember that you must use int main(int argc, char *argv[]) as your entry point (don''t leave out the parameters). You may also need to prefix it with extern "C"
If you have any problems, feel free to ask .

[Resist Windows XP''s Invasive Production Activation Technology!]

Share on other sites
Hey

Is that for code warrior?
With Dev C++ it will never work if you dont use the standard Windows entry point (winmain)
Anyways, the reason I use SDL is to avoid the complications of Windows programming

Share on other sites
Maybe I''ll try getting it all working under linux. I''m not a big fan of windows by any extent and I guess it''s time I honed my Linux skills anyway.

/me dreams of being able to create text file, write a program, compile it, and run it without having to spend hours before hand setting it up...

-Micah

Share on other sites
search for kdevelop for kde (very simple to setup + compile)

http://uk.geocities.com/sloppyturds/gotterdammerung.html

Share on other sites
Just use the recently posted msvc++ sdl tutorial on gamedev.net and port it to work with codeworrier. All you have to do is point your project to link with the correct libs and then your good to go. And under linux it is even eaiser IMHO (especiall with debian and apt

It is foolish for a wise man to be silent, but wise for a fool.

Matthew
WebMaster
www.Matt-Land.com

All your Xbox base are belong to Nintendo.

Share on other sites
(MichahM -- you may want to skip past my rant below and get to the bottom, where I hope I've helped to answer your real question)

No self respecting developer uses Windows?

Are you off your rocker? Please list some game development houses (since this is a game development related forum) that don't use Windows as their primary (usually its their ONLY) development platform?

I don't always like Microsoft as a company, because they do some underhanded things, but Visual C++ is by far the best C++ IDE I've used.

For the record, I actually grew up using/programming for the C64, then Amigas and UNIX systems (owned a SPARC-2 running SunOS 4.x for a long time), I also do a lot of contractual server-based backend programming for Solaris, AIX, FreeBSD and Linux currently, with gcc, emacs, vi, KDevelop, etc, so I'm completely aware of what is available for those systems.

Using Linux for political purposes (boycotting Microsoft) or for a free, high-quality server-side OS is fine and dandy, but IMO anyone who faults Microsoft for the quality of their OSes or desktop software is still living in 1998. Since Windows 2000 (and now XP) Microsoft makes solid OSes and great development tools, they also provide excellent development reference documentation for free.

To get back on-topic:

1) You can use MSVC++ from the command-line. Though the IDE hides this from the developer, MSVC++ has a full set of command-line tools which do the actual compiling and linking, just like UNIX based systems do. It also has a full make-like program (nmake) for those who like to do that stuff hands-on. So, you CAN use MSVC++ from the command-line...The only reason not to use it would be price (don't want to pay for it) or general dislike of Microsoft...In that case, there are alternate (free) compilers like the gcc ports, and Borland's free command-line version of C++ Builder:

http://www.borland.com/bcppbuilder/freecompiler/

If you need more information on using SDL with these alternate free compilers, check the SDL FAQ:

http://www.libsdl.org/faq/FAQ-Win32.html

2) You mentioned you use CodeWarrior. As far as I know SDL ships with CodeWarrior project files, but they are Mac format. I have no idea if they are compatible with the Windows version of CodeWarrior and/or what changes you might need to make to make them compatible.

Edited by - gmcbay on December 30, 2001 4:26:26 PM

Share on other sites
Click the last link in my profile sinature, and take tutorial number one. Ernest Pazera wrote a good tutorial on setting up SDL with MSVC++ under Windows.

Next go here. Section 2.7 and 2.8 I believe are on using OpenGL and SDL together.

Good luck. If you have any SDL problems post in the Cone3D forum.

------------------------------
Simple DirectMedia Layer:
Main Site - (www.libsdl.org)
Cone3D Tutorials- (cone3D.gamedev.net)
GameDev.net's Tutorials - (Here)

Edited by - Drizzt DoUrden on December 30, 2001 4:30:49 PM