Sign in to follow this  

DX11 D3DX11Effects.lib x64

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

If you intended to correct an error in the post then please contact us.

Recommended Posts

I can't build an x64 version of D3DX11Effects.lib in 2008? 2010Beta won't import the project, Win7 did something funny to the 2010Beta loader.... Why am I building this lib file anyway? Anywhere I can download this? [edit] The Visual C++ 2008 Express Edition can be used to compile .NET as well as Win32 applications immediately after installation. However, natively compiling 64-bit applications through the IDE is not supported without some involved configurations. If the freely available Windows SDK is installed, 64-bit applications can be built on the command line using the x64 cross-compiler (Cl.exe) supplied with the SDK.[9] True integration of 64bit compilers to the Visual C++ 2008 Express Edition is possible, but remains cumbersome. [/edit] Nein! I hang my head in shame.....

Share this post


Link to post
Share on other sites
Attempted to relocate to VS2010Beta......


1>Link:
1> D3DX11Effects.lib(EffectAPI.obj) : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance
1>D3DX11Effects.lib(EffectAPI.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in DirectDraw.obj
1>D3DX11Effects.lib(EffectNonRuntime.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in DirectDraw.obj
1>D3DX11Effects.lib(EffectLoad.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in DirectDraw.obj
1>D3DX11Effects.lib(d3dxGlobal.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in DirectDraw.obj
1>D3DX11Effects.lib(EffectReflection.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in DirectDraw.obj
1>D3DX11Effects.lib(EffectRuntime.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in DirectDraw.obj
1>MSVCRTD.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library
1>D3DX11Effects.lib(EffectLoad.obj) : error LNK2001: unresolved external symbol D3DGetInputSignatureBlob
1>D3DX11Effects.lib(EffectLoad.obj) : error LNK2001: unresolved external symbol D3DReflect
1>C:\Projects\DUALITY\X64\Debug\DUALITY.exe : fatal error LNK1120: 2 unresolved externals




Issues:
> What about the locking issues in the 2008 STL implementation? I have an application where the single greatest performance bottleneck is the thread locking in the STL.

In VC9 (aka VS 2008), the STL proper doesn't take locks in release mode. To clarify:

"In VC9" - we recently noticed that in VC10 Beta 1, the STL proper is taking locks in release mode. This was an unintended side effect of fusing _SECURE_SCL and _HAS_ITERATOR_DEBUGGING into _ITERATOR_DEBUG_LEVEL, and we've got a bug tracking this.

"the STL proper" - as in, things like vectors and algorithms, not iostreams. iostreams takes locks in order to allow cout to be used by multiple threads (since streaming through cout is a modifying operation).

"in release mode" - as in, /MT or /MD (with _SECURE_SCL, now _ITERATOR_DEBUG_LEVEL, set to either 0 or 1). In debug mode (/MTd or /MDd) with _HAS_ITERATOR_DEBUGGING enabled (now, _ITERATOR_DEBUG_LEVEL set to 2), locks are used to protect the bookkeeping data structures for the powerful correctness checks. If you're profiling debug mode, don't do that.

Also, this excludes whatever happens during memory allocation.

-msdn blog

Hey this could be good??? Does this mean the lib file worked lolz

Share this post


Link to post
Share on other sites
/MD => /MDd in D3DX11Effects project......


1> Generating Code...
1>D3DX11Effects.lib(EffectLoad.obj) : error LNK2019: unresolved external symbol D3DGetInputSignatureBlob referenced in function
"protected: long __cdecl D3DX11Effects::CEffectLoader::BuildShaderBlock(struct D3DX11Effects::SShaderBlock *)"
(?BuildShaderBlock@CEffectLoader@D3DX11Effects@@IEAAJPEAUSShaderBlock@2@@Z)
1>D3DX11Effects.lib(EffectLoad.obj) : error LNK2019: unresolved external symbol D3DReflect referenced in function
"protected: long __cdecl D3DX11Effects::CEffectLoader::BuildShaderBlock(struct D3DX11Effects::SShaderBlock *)"
(?BuildShaderBlock@CEffectLoader@D3DX11Effects@@IEAAJPEAUSShaderBlock@2@@Z)
1>C:\Projects\DUALITY\X64\Debug\DUALITY.exe : fatal error LNK1120: 2 unresolved externals
1>






-.- I are so close to a working core(well raw core!)

p.s. D2D is still not DX11 functional in the new SDK :( I don't want to key mutex, blah blah... I'm no good at sharing....

[Edited by - jpetrie on February 23, 2010 10:22:34 AM]

Share this post


Link to post
Share on other sites
Quote:
Original post by jpetrie
Quote:

Anybody know why all this was necessary?

It wasn't for us when we built it for SlimDX, so you must have something odd going on.


Aside from D2D, I hope not.

You had D3DX11Effects.lib already compiled in your Lib folder? There it is, I'm using x64! The x64 lib file is non existent and probably for good reason. I do have reasons for using x64..... I hope the fact that mine is 20Megs as opposed to 14 is not problematic in the future. I wonder when /MDd debugger effects is going to kick me in the ass?

"...you must have something odd going on..." <==== what are you saying?(I am currently listening to a song that is repeating "OMG Ice cream") o-o

Share this post


Link to post
Share on other sites
Quote:

Aside from D2D, I hope not.

Irrelevant to the process of building Effects11. I mean things like broken paths, etc.

Quote:

You had D3DX11Effects.lib already compiled in your Lib folder? There it is, I'm using x64! The x64 lib file is non existent and probably for good reason. I do have reasons for using x64..... I hope the fact that mine is 20Megs as opposed to 14 is not problematic in the future.

No, Effects11 is not distributed in binary form in the SDK. You have to build it yourself. I'm saying we had no real trouble making it build for both 32-bit and 64-bit platforms when we needed to do so, so something about the process you're using or the state of your toolchain is incorrect.

Quote:

I wonder when /MDd debugger effects is going to kick me in the ass?

This smacks of illogical and poorly-conceived 'shotgun debugging' -- changing a bunch of things quickly, out of frustration, without really understanding what you are changing or why. This is never a good solution to a problem.

In particular, the "problems" that are likely to arise from using /MDd are not problems with /MDd itself. /MDd links to debug runtimes, by design. You'll have trouble shipping products like that -- the problem is that you shouldn't be linking to debug runtimes, not that /MDd is broken in any fashion.

Share this post


Link to post
Share on other sites
Quote:
Original post by jpetrie
Quote:

Aside from D2D, I hope not.

Irrelevant to the process of building Effects11. I mean things like broken paths, etc.


this is why I had to switch to /MDd????

Quote:
Original post by jpetrie
Quote:

You had D3DX11Effects.lib already compiled in your Lib folder? There it is, I'm using x64! The x64 lib file is non existent and probably for good reason. I do have reasons for using x64..... I hope the fact that mine is 20Megs as opposed to 14 is not problematic in the future.

No, Effects11 is not distributed in binary form in the SDK. You have to build it yourself. I'm saying we had no real trouble making it build for both 32-bit and 64-bit platforms when we needed to do so, so something about the process you're using or the state of your toolchain is incorrect.


Oh yeah I put that there :)... As stated earlier I'm using VS2008 Express and/or VS2010Beta. Express is not released through MS with x64 compiling. VS2010Beta was not importing the 2008 project, it repeatedly crashed. I will be purchasing a full version of 2010 Professional when it is released. This last bit is kind of pointless because the chances of me successfully releasing commercial software is pretty slim. I'm also not a certified SE so putting in bids on contracts is pretty silly...... and well see Interview@Google in the lounge....

Quote:

Quote:

I wonder when /MDd debugger effects is going to kick me in the ass?

This smacks of illogical and poorly-conceived 'shotgun debugging' -- changing a bunch of things quickly, out of frustration, without really understanding what you are changing or why. This is never a good solution to a problem.

In particular, the "problems" that are likely to arise from using /MDd are not problems with /MDd itself. /MDd links to debug runtimes, by design. You'll have trouble shipping products like that -- the problem is that you shouldn't be linking to debug runtimes, not that /MDd is broken in any fashion.


I know...... D2D is causing problems I'm working around that for the moment!

"You'll have trouble shipping products like that" <=== is this a vote of confidence?

Share this post


Link to post
Share on other sites
Quote:

this is why I had to switch to /MDd????

That makes no sense. Do you even know what the /MDd flag does? You should not have to compile Effects11 with the /MDd flag in order to be able to link it with other code that is also using D2D. You're doing something wrong.

Quote:

As stated earlier I'm using VS2008 Express and/or VS2010Beta. Express is not released through MS with x64 compiling.

I know. You can, however, use the cross-compiler as you noted. That should not necessitate having to link against the debug runtimes (/MDd).

Quote:

I know...... D2D is causing problems I'm working around that for the moment!

The problems with D2D are different than the problems you have building Effects11. I would resolve those first before worrying about D2D.

Quote:

"You'll have trouble shipping products like that" <=== is this a vote of confidence?

No, it's a fact. /MDd links to the debug runtimes. This means that in order to run your code, the end-user must also have those debug runtimes. Most users don't -- only developers generally do. Furthermore, you cannot distribute those runtimes, so you must tell your users to download Visual Studio (essentially) in order to run your application.

Even if you do not intend to ship this product to anybody, this is absolutely horrid practice. You should try to figure out what the root cause of your problem is, and what options other than linking to the debug runtimes are available to you.

What happens when you attempt to compile the (virgin, unmodified) Effects11 library using the 64-bit cross compiler? What errors do you get? Et cetera? Make sure this is an unmodified version of the source, too, not something you have tampered with, no matter how trivial you believe your changes to be.

Share this post


Link to post
Share on other sites
I never had errors in the effects project, I had errors in my project which was using the effects project. The only errors I had where related to D2D, in my project(using the same compiler line as the 'virgin project' as you put it.) I haven't used the cross compiler. If you think it might fix the LNK2038 D2D was generating then I'll give it a try, it would be nice to avoid using debug runtime workaround. I had no intention on keeping the workaround a part of my project as I was somewhat aware of what I was doing, just not entirely, as would someone who has more under-stranding.

Share this post


Link to post
Share on other sites
"in release mode" - as in, /MT or /MD (with _SECURE_SCL, now _ITERATOR_DEBUG_LEVEL, set to either 0 or 1). In debug mode (/MTd or /MDd) with _HAS_ITERATOR_DEBUGGING enabled (now, _ITERATOR_DEBUG_LEVEL set to 2), locks are used to protect the bookkeeping data structures for the powerful correctness checks. If you're profiling debug mode, don't do that.

Is this not the source of the D2D LNK2038?

Share this post


Link to post
Share on other sites
Quote:

I never had errors in the effects project, I had errors in my project which was using the effects project.

The first line of your first post implies strongly that you "can't build an x64 version of D3DX11Effects.lib in 2008."

Quote:

The only errors I had where related to D2D, in my project(using the same compiler line as the 'virgin project' as you put it.) I haven't used the cross compiler.

What do you mean by "compiler line?" The command line used to invoke the compiler?

Quote:

I haven't used the cross compiler. If you think it might fix the LNK2038 D2D was generating then I'll give it a try, it would be nice to avoid using debug runtime workaround. I had no intention on keeping the workaround a part of my project as I was somewhat aware of what I was doing, just not entirely, as would someone who has more under-stranding.

I am still having an extremely difficult time understanding your problem description. Why don't you start over. If building Effects11 isn't the problem, you can still apply the same problem-solving techniques to whatever is your problem. Start with these questions: What are you trying to build, how are you trying to do it (with what tools, et cetera), what are the errors you get?

Quote:

"in release mode" - as in, /MT or /MD (with _SECURE_SCL, now _ITERATOR_DEBUG_LEVEL, set to either 0 or 1). In debug mode (/MTd or /MDd) with _HAS_ITERATOR_DEBUGGING enabled (now, _ITERATOR_DEBUG_LEVEL set to 2), locks are used to protect the bookkeeping data structures for the powerful correctness checks. If you're profiling debug mode, don't do that.

Is this not the source of the D2D LNK2038?

I don't see how, that doesn't seem related at all. I can hardly even follow that text as it is lacking any context and isn't the most clearly articulated English phrase I've ever seen.

Share this post


Link to post
Share on other sites
I couldn't build it in 2008 I had to start a clean project in 2010Beta and import the files and so on..... I did compile it in 2010. When I asked about why I had to do all that, and you replied, I was referring to building the binary; why isn't it included.

The line that isn't the most clearly articulated English phrase you've ever seen is an excerpt from a DX developers blog and I think it explains why I had to do this /MDd in relation to my doing this

D2D D3D Interoped:

HRESULT RenderingChain::InstantiateDeviceAndSwapChain()
{
HRESULT hr = S_OK;;

ID3D11Device* pDevice = NULL;
IDXGIDevice* pDXGIDevice = NULL;
IDXGIAdapter* pAdapter = NULL;
IDXGIFactory* pDXGIFactory = NULL;

UINT createDeviceFlags = 0;
#ifdef _DEBUG
createDeviceFlags |= D3D11_CREATE_DEVICE_DEBUG;
createDeviceFlags |= D3D11_CREATE_DEVICE_BGRA_SUPPORT;
#endif

hr = D3D11CreateDevice( NULL, D3D_DRIVER_TYPE_HARDWARE, NULL, createDeviceFlags, NULL, 0,
D3D11_SDK_VERSION, &pDevice, &feature_lvl, &m_pd3dDeviceContext);
if(FAILED(hr))
return hr;

hr = pDevice->QueryInterface(&m_pd3dDevice);
if(FAILED(hr))
return hr;

hr = pDevice->QueryInterface(&pDXGIDevice);
if(FAILED(hr))
return hr;

hr = pDXGIDevice->GetAdapter(&pAdapter);
if(FAILED(hr))
return hr;

hr = pAdapter->GetParent(IID_PPV_ARGS(&pDXGIFactory));
if(FAILED(hr))
return hr;

DXGI_SWAP_CHAIN_DESC desSwapChain;
ZeroMemory(&desSwapChain,sizeof(desSwapChain));
desSwapChain.BufferDesc.Width = width;
desSwapChain.BufferDesc.Height = height;
desSwapChain.BufferDesc.Format = DXGI_FORMAT_B8G8R8A8_UNORM;
desSwapChain.BufferDesc.RefreshRate.Numerator = 60;
desSwapChain.BufferDesc.RefreshRate.Denominator = 1;
desSwapChain.SampleDesc.Count = 1;
desSwapChain.SampleDesc.Quality = 0;
desSwapChain.BufferUsage = DXGI_USAGE_RENDER_TARGET_OUTPUT;
desSwapChain.BufferCount = 1;
desSwapChain.OutputWindow = hWnd;
desSwapChain.Windowed = TRUE;

hr = pDXGIFactory->CreateSwapChain(m_pd3dDevice, &desSwapChain, &m_pSwapChain);
if(FAILED(hr))
return hr;

D3D11_TEXTURE2D_DESC desTextureRT2D;
ZeroMemory(&desTextureRT2D, sizeof(desTextureRT2D));
desTextureRT2D.ArraySize = 1;
desTextureRT2D.BindFlags = D3D11_BIND_RENDER_TARGET | D3D11_BIND_SHADER_RESOURCE;
desTextureRT2D.CPUAccessFlags = 0;
desTextureRT2D.Format = DXGI_FORMAT_B8G8R8A8_UNORM;
desTextureRT2D.Width = width;
desTextureRT2D.Height = height;
desTextureRT2D.MipLevels = 1;
desTextureRT2D.MiscFlags = 0;
desTextureRT2D.SampleDesc.Count = 1;
desTextureRT2D.SampleDesc.Quality = 0;
desTextureRT2D.Usage = D3D11_USAGE_DEFAULT;

hr = m_pd3dDevice->CreateTexture2D(&desTextureRT2D, NULL, &m_pHUD);
if(FAILED(hr))
return hr;

hr = m_pd3dDevice->CreateShaderResourceView(m_pHUD, NULL, &m_pHUDRV);
if(FAILED(hr))
return hr;

D3D11_RENDER_TARGET_VIEW_DESC desRT;
ZeroMemory(&desRT, sizeof(desRT));
desRT.Format = DXGI_FORMAT_B8G8R8A8_UNORM;
desRT.ViewDimension = D3D11_RTV_DIMENSION_TEXTURE2D;
desRT.Texture2D.MipSlice = 0;

hr = m_pSwapChain->GetBuffer(0, __uuidof(ID3D11Texture2D), (LPVOID*)&m_pBackBuffer);
if(FAILED(hr))
return hr;

hr = m_pd3dDevice->CreateRenderTargetView(m_pBackBuffer, &desRT, &m_pRenderTargetView);
m_pBackBuffer->Release();
if(FAILED(hr))
return hr;

m_pd3dDevice->GetImmediateContext(&m_pd3dDeviceContext);

m_pd3dDeviceContext->OMSetRenderTargets(1, &m_pRenderTargetView, NULL);

D3D11_BLEND_DESC desBlend;
ZeroMemory(&desBlend, sizeof(desBlend));
desBlend.AlphaToCoverageEnable = false;
desBlend.IndependentBlendEnable = false;

D3D11_RENDER_TARGET_BLEND_DESC desBlendRT;
ZeroMemory(&desBlendRT, sizeof(desBlendRT));
desBlendRT.BlendEnable = true;
desBlendRT.SrcBlend = D3D11_BLEND_SRC_ALPHA;
desBlendRT.SrcBlendAlpha = D3D11_BLEND_ONE;
desBlendRT.DestBlend = D3D11_BLEND_INV_SRC_ALPHA;
desBlendRT.DestBlendAlpha = D3D11_BLEND_ZERO;
desBlendRT.BlendOp = D3D11_BLEND_OP_ADD;
desBlendRT.BlendOpAlpha = D3D11_BLEND_OP_ADD;
desBlendRT.RenderTargetWriteMask = D3D11_COLOR_WRITE_ENABLE_ALL;

desBlend.RenderTarget[0] = desBlendRT;

hr = m_pd3dDevice->CreateBlendState(&desBlend, &m_pBlendState);
if(FAILED(hr))
return hr;

m_pd3dDeviceContext->OMSetBlendState(m_pBlendState, NULL, 0xffffffff);

return S_OK;
}

HRESULT RenderingChain::Initialize2DInterface()
{
HRESULT hr = S_OK;;

hr = D2D1CreateFactory(D2D1_FACTORY_TYPE_SINGLE_THREADED, &m_pD2DFactory);
if(FAILED(hr))
return hr;

D2D1_RENDER_TARGET_PROPERTIES desRT2D =
D2D1::RenderTargetProperties(
D2D1_RENDER_TARGET_TYPE_DEFAULT,
D2D1::PixelFormat(DXGI_FORMAT_B8G8R8A8_UNORM, D2D1_ALPHA_MODE_PREMULTIPLIED),
96,
96
);

hr = m_pSwapChain->GetBuffer(0, IID_PPV_ARGS(&m_pDXGISurface));
if(FAILED(hr))
return hr;

// hr = m_pD2DFactory->CreateDxgiSurfaceRenderTarget(m_pDXGISurface, &desRT2D, &m_pD2DRenderTarget);
if(FAILED(hr))
return hr;

return S_OK;
}





Creating the Texture Resources:

#include "TextureZ.h"

ID3D11Texture2D* TexturePool::m_pTexArray = NULL;
ID3D11ShaderResourceView* TexturePool::m_pTextureRV = NULL;

const UINT num_text = 3;
HRESULT TexturePool::CreateShaderResources(ID3D11Device* pd3dDevice)
{
HRESULT hr = S_OK;;

ID3D11DeviceContext* pd3dDeviceContext;
pd3dDevice->GetImmediateContext(&pd3dDeviceContext);

ID3D11Texture2D* defaultText[num_text];
ZeroMemory(&defaultText[0], num_text * sizeof(defaultText[0]));
D3DX11_IMAGE_LOAD_INFO loadInfo;
loadInfo.Width = D3DX11_FROM_FILE;
loadInfo.Height = D3DX11_FROM_FILE;
loadInfo.Depth = D3DX11_FROM_FILE;
loadInfo.FirstMipLevel = 0;
loadInfo.MipLevels = D3DX11_FROM_FILE;
loadInfo.Usage = D3D11_USAGE_STAGING;
loadInfo.BindFlags = 0;
loadInfo.CpuAccessFlags = D3D11_CPU_ACCESS_WRITE | D3D11_CPU_ACCESS_READ;
loadInfo.MiscFlags = 0;
loadInfo.Format = DXGI_FORMAT_R8G8B8A8_UNORM;
loadInfo.Filter = D3DX11_FILTER_NONE;
loadInfo.MipFilter = D3DX11_FILTER_NONE;
loadInfo.pSrcInfo = 0;

hr = (D3DX11CreateTextureFromFile(pd3dDevice, "C:/Projects/DUALITY/Assets/TextureZ/DEFAULT.dds",
&loadInfo, 0, (ID3D11Resource**)&defaultText[0], 0));
if(FAILED(hr))
return hr;

hr = (D3DX11CreateTextureFromFile(pd3dDevice, "C:/Projects/DUALITY/Assets/TextureZ/DEFAULT2.dds",
&loadInfo, 0, (ID3D11Resource**)&defaultText[1], 0));
if(FAILED(hr))
return hr;

hr = (D3DX11CreateTextureFromFile(pd3dDevice, "C:/Projects/DUALITY/Assets/TextureZ/ModelEdit.dds",
&loadInfo, 0, (ID3D11Resource**)&defaultText[2], 0));
if(FAILED(hr))
return hr;

D3D11_TEXTURE2D_DESC desDefaultText;
ZeroMemory(&desDefaultText, sizeof(desDefaultText));
defaultText[0]->GetDesc(&desDefaultText);

D3D11_TEXTURE2D_DESC desDefaultTexArray;
ZeroMemory(&desDefaultTexArray, sizeof(desDefaultTexArray));
desDefaultTexArray.Width = desDefaultText.Width;
desDefaultTexArray.Height = desDefaultText.Height;
desDefaultTexArray.MipLevels = desDefaultText.MipLevels;
desDefaultTexArray.ArraySize = num_text;
desDefaultTexArray.Format = DXGI_FORMAT_R8G8B8A8_UNORM;
desDefaultTexArray.SampleDesc.Count = 1;
desDefaultTexArray.SampleDesc.Quality = 0;
desDefaultTexArray.Usage = D3D11_USAGE_DEFAULT;
desDefaultTexArray.BindFlags = D3D11_BIND_SHADER_RESOURCE;
desDefaultTexArray.CPUAccessFlags = 0;
desDefaultTexArray.MiscFlags = 0;

hr=(pd3dDevice->CreateTexture2D( &desDefaultTexArray, 0, &m_pTexArray));

for(size_t i = 0; i < num_text; i++)
{
for(UINT mmlvl = 0; mmlvl < desDefaultText.MipLevels; ++mmlvl)
{
D3D11_MAPPED_SUBRESOURCE* mappedTex2D = NULL;

hr = pd3dDeviceContext->Map(defaultText[i], 0, D3D11_MAP_READ, 0, mappedTex2D);

if(SUCCEEDED(hr))
{
pd3dDeviceContext->UpdateSubresource(m_pTexArray, D3D11CalcSubresource(mmlvl, UINT(i),
desDefaultText.MipLevels), 0, mappedTex2D->pData, mappedTex2D->RowPitch, 0);

pd3dDeviceContext->Unmap( defaultText[i], mmlvl );
}
else
return hr;
}
}

D3D11_SHADER_RESOURCE_VIEW_DESC desSRV;
ZeroMemory(&desSRV, sizeof(desSRV));
desSRV.Format = desDefaultTexArray.Format;
desSRV.ViewDimension = D3D11_SRV_DIMENSION_TEXTURE2DARRAY;
desSRV.Texture2DArray.MostDetailedMip = 0;
desSRV.Texture2DArray.MipLevels = desDefaultTexArray.MipLevels;
desSRV.Texture2DArray.FirstArraySlice = 0;
desSRV.Texture2DArray.ArraySize = num_text;

hr = pd3dDevice->CreateShaderResourceView(m_pTexArray, &desSRV, &m_pTextureRV);
if(FAILED(hr))
return hr;

return S_OK;
}




wish I would have fixed the Texture2D/MipMap Mapping last night :(

I'm still creating the surface or at least everything up to creating the surface in DX11 but D2D is not supported by it yet! If I understand correctly because of the _ITERATOR_DEBUG_LEVEL which whatever I am accessing which is being accessed through D3DX11Effects.lib was compiled as debug, I now have to compile my D3DX11Effects.lib as a debug runtime lib. This will allow me to at least debug my code and will give me the chance to either remove D2D or do the 11/10.1 shared workaround....

[edit]
And I'm going to use a patch for 2008 I really hate command line..... but now I need the Win7 SDK

Share this post


Link to post
Share on other sites
meh wrong one I'm really sleeping can't you tell sleep working

Direct Draw:

#include "DirectDraw.h"

HRESULT CD2D3D::RenderInterfaceElements2D(ID2D1RenderTarget* pD2DRenderTarget)
{
HRESULT hr = S_OK;;

pD2DRenderTarget->BeginDraw();
for(size_t tb_slots = 0; tb_slots < MAX_DRAW_SLOTS+DEV_TOOL_SLOT; tb_slots++)
{
if(m_pDrawCommands[tb_slots] != NULL)
{
for(size_t i = 0; i < m_pDrawCommands[tb_slots]->size(); i++)
{
Draw2D(pD2DRenderTarget, &m_pDrawCommands[tb_slots]->at(i));
}
}
}
pD2DRenderTarget->EndDraw();

return S_OK;
}

HRESULT CD2D3D::Draw2D(ID2D1RenderTarget* pD2DRenderTarget, SDrawCommand* DrawThis)
{
HRESULT hr = S_OK;

ID2D1SolidColorBrush* brush;
switch(DrawThis->Draw)
{
case DRAW_LINE:
D2D1_POINT_2F A;
D2D1_POINT_2F B;
A.x = XMVectorGetX(DrawThis->p1);
A.y = XMVectorGetY(DrawThis->p1);
B.x = XMVectorGetX(DrawThis->p2);
B.y = XMVectorGetY(DrawThis->p2);
pD2DRenderTarget->CreateSolidColorBrush(DrawThis->Colour, &brush);
pD2DRenderTarget->DrawLine(A,B,brush,DrawThis->Thickness, NULL);
break;

case DRAW_LINE_PERSPECTIVE:
{
XMVECTOR Eye, At, Up;
Camera->GetEye(&Eye);
Camera->GetAt(&At);
Camera->GetUp(&Up);

XMMATRIX View;
View = XMMatrixLookAtLH(Eye, At, Up);

XMMATRIX Projection;
float* pFOVY,* pAspect,* pZn,* pZf;
Camera->GetProjParameters(&pFOVY, &pAspect, &pZn, &pZf, NULL, NULL);
Projection = XMMatrixPerspectiveFovLH(*pFOVY, *pAspect, *pZn, *pZf);

XMFLOAT3 point1, point2;
XMStoreFloat3(&point1, DrawThis->p1);
XMStoreFloat3(&point2, DrawThis->p2);

XMVECTOR vec1, vec2;
vec1 = XMVector3Transform(DrawThis->p1, View);
vec2 = XMVector3Transform(DrawThis->p2, View);

vec1/=XMVectorGetZ(vec1);
vec2/=XMVectorGetZ(vec2);

vec1 = XMVector4Transform(vec1, Projection);
vec2 = XMVector4Transform(vec2, Projection);

vec1/=XMVectorGetW(vec1);
vec2/=XMVectorGetW(vec2);

XMStoreFloat3(&point1, vec1);
XMStoreFloat3(&point2, vec2);

D2D1_POINT_2F A;
D2D1_POINT_2F B;
A.x = width*(point1.x+1.0f)/2;
A.y = height*(-(point1.y-1.0f))/2;
B.x = width*(point2.x+1.0f)/2;
B.y = height*(-(point2.y-1.0f))/2;

pD2DRenderTarget->CreateSolidColorBrush(DrawThis->Colour, &brush);
pD2DRenderTarget->DrawLine(A,B,brush,DrawThis->Thickness, NULL);

break;
}

case DRAW_RECT:
D2D1_RECT_F R;
R.left = XMVectorGetX(DrawThis->p1);
R.top = XMVectorGetY(DrawThis->p1);
R.right = XMVectorGetX(DrawThis->p2);
R.bottom = XMVectorGetY(DrawThis->p2);
pD2DRenderTarget->CreateSolidColorBrush(DrawThis->Colour, &brush);
pD2DRenderTarget->DrawRectangle(R,brush,DrawThis->Thickness, NULL);
if(DrawThis->Fill)
{
pD2DRenderTarget->CreateSolidColorBrush(DrawThis->FillColour, &brush);
pD2DRenderTarget->FillRectangle(R, brush);
}
break;
}

return S_OK;
}

Share this post


Link to post
Share on other sites
Quote:

I couldn't build it in 2008 I had to start a clean project in 2010Beta and import the files and so on..... I did compile it in 2010. When I asked about why I had to do all that, and you replied, I was referring to building the binary; why isn't it included.

Is "it" Effects11 again? If so, the binary isn't provided because they are providing the source and expecting you to build it yourself.

Quote:

The line that isn't the most clearly articulated English phrase you've ever seen is an excerpt from a DX developers blog and I think it explains why I had to do this /MDd in relation to my doing this

I don't see how it does, and this hardly clarifies anything. Why don't you provide a link?

Quote:

I'm still creating the surface or at least everything up to creating the surface in DX11 but D2D is not supported by it yet!

This is a known and documented issue, I believe. It should be unrelated to whatever is going on with your /MDd weirdness.

Quote:

If I understand correctly because of the _ITERATOR_DEBUG_LEVEL which whatever I am accessing which is being accessed through D3DX11Effects.lib was compiled as debug, I now have to compile my D3DX11Effects.lib as a debug runtime lib. This will allow me to at least debug my code and will give me the chance to either remove D2D or do the 11/10.1 shared workaround....

This does not provide me, or anybody else, any information that is remotely useful to solving the problem. I am going to give you one more chance to try to clearly articulate your problem, and then I am going to write this off as a lost cause. You may want to read this.

This is what you've managed to, haltingly, communicate:
(1) You tried to build Effects11 with the VS 2010 beta.
(2) Something "didn't work" when you tried to link that library with your own code. I assume you also built your own code with the VS 2010 beta? If not, this is a likely source of one or more problems.
(3) You "fixed" the problem by specifying /MDd instead of /MD in the 2010 Effects11 project.

Is this correct? I am not interested in the D2D/D3D11 issues at the moment, as they do not appear to be related to this initial problem based on the information you have provided.

I assert that you should not need to use /MDd to fix whatever your original problem was. However, you have not adequately explains what your original problem was (as in, with complete error messages).

In general, using beta software for 'production' work is not recommended. You may also want to explore the cross-compiler option. I'm curious why you are even bothering to build the x64 library, since it sounds like you originally only had the 2008 Express edition and thus your own application couldn't be 64-bit.

Share this post


Link to post
Share on other sites
Quote:
Original post by Buttacup
Attempted to relocate to VS2010Beta......

*** Source Snippet Removed ***

Issues:
> What about the locking issues in the 2008 STL implementation? I have an application where the single greatest performance bottleneck is the thread locking in the STL.

In VC9 (aka VS 2008), the STL proper doesn't take locks in release mode. To clarify:

"In VC9" - we recently noticed that in VC10 Beta 1, the STL proper is taking locks in release mode. This was an unintended side effect of fusing _SECURE_SCL and _HAS_ITERATOR_DEBUGGING into _ITERATOR_DEBUG_LEVEL, and we've got a bug tracking this.

"the STL proper" - as in, things like vectors and algorithms, not iostreams. iostreams takes locks in order to allow cout to be used by multiple threads (since streaming through cout is a modifying operation).

"in release mode" - as in, /MT or /MD (with _SECURE_SCL, now _ITERATOR_DEBUG_LEVEL, set to either 0 or 1). In debug mode (/MTd or /MDd) with _HAS_ITERATOR_DEBUGGING enabled (now, _ITERATOR_DEBUG_LEVEL set to 2), locks are used to protect the bookkeeping data structures for the powerful correctness checks. If you're profiling debug mode, don't do that.

Also, this excludes whatever happens during memory allocation.

-msdn blog

Hey this could be good??? Does this mean the lib file worked lolz



I had linked the blog, you must've missed it.....

Share this post


Link to post
Share on other sites
That is explaining how values of a constant different in release and debug modes. It is not saying that the solution to your problem is to only compile in debug mode. In fact, elsewhere it is suggesting exactly what I have, that you're doing something else wrong to cause this error to manifest (mismatching dependencies, mainly). But your unwillingness to provide the relevant information seems to suggest that you don't actually care for a real solution, just the first thing that vaguely works, so... good luck.

Share this post


Link to post
Share on other sites
My use of D2D with a DX11 render target is causing the mismatch and I will be correcting that.

I've been programming what I have for three months now and VS2010Beta has been available since at least last summer.

Migrating to x64 is not like migrating to XNAMath it is comparably quite simple and I have done both.

That last point said I do not speak VM and for this I apologize I will make future attempts at presenting my internal values more clearly and opaquely and will not use lazy context-free grammar..... I lie on all of those points... well I will maintain my apology although I am not quite sure for what(oh yeah not speaking VM.) I will also maintain that it is sincere!

Share this post


Link to post
Share on other sites
I download the VC10Beta again and re-installed it. I also reinstalled the DX and Windows SDKs. After this I tried importing the VC9 Effects11 project with success. I compiled it 'as is' in VC10Beta successfully. I was still unable to build without the afore mentioned linker error(LNK2038) so I compiled the debug runtime Effects11 DLL and kept crunching.

So I started a new solution to precompile effects so I can get the IAinputSignature and ByteCode length for input layout creation and save it for general access by my buffer class. I just got to the part where I realize I need to create the device so I can get the Vertex Shader ByteCode length and not the length of the compiled effect! So I create the device and so on and I compile and


1>Link:
1> LINK : C:\Projects\Effects Pre-Compiler\x64\Debug\Effects Pre-Compiler.exe not found or not built by the last incremental link; performing full link
1> D3DX11Effects.lib(EffectAPI.obj) : MSIL .netmodule or module compiled with /GL found; restarting link with /LTCG; add /LTCG to the link command line to improve linker performance
1>D3DX11Effects.lib(EffectAPI.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>D3DX11Effects.lib(EffectNonRuntime.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>D3DX11Effects.lib(EffectLoad.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>D3DX11Effects.lib(d3dxGlobal.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>D3DX11Effects.lib(d3dx11dbg.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>D3DX11Effects.lib(EffectReflection.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>D3DX11Effects.lib(EffectRuntime.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in EPROM.obj
1>LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library
1>C:\Projects\Effects Pre-Compiler\x64\Debug\Effects Pre-Compiler.exe : fatal error LNK1319: 7 mismatches detected







same 7 mismatches and no D2D in the project..... So, my bad it had nothing to do with D2D... why it's happening not sure but Effects11 was fine until I created the Device.... I'm sure I'll figure it out soon enough just thought I would correct this in case someone reads it and wastes their time as cause of me....

kk

[edit] I really meant the call to D3DX11CreateEffectFromMemory()... feel free to throw virtual objects at me! [/edit]

[Edited by - Buttacup on February 26, 2010 8:04:35 AM]

Share this post


Link to post
Share on other sites

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

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      628675
    • Total Posts
      2984169
  • Similar Content

    • By ADDMX
      Hi
      Just a simple question about compute shaders (CS5, DX11).
      Do the atomic operations (InterlockedAdd in my case) should work without any issues on RWByteAddressBuffer and be globaly coherent ?
      I'v come back from CUDA world and commited fairly simple kernel that does some job, the pseudo-code is as follows:
      (both kernels use that same RWByteAddressBuffer)
      first kernel does some job and sets Result[0] = 0;
      (using Result.Store(0, 0))
      I'v checked with debugger, and indeed the value stored at dword 0 is 0
      now my second kernel
      RWByteAddressBuffer Result;  [numthreads(8, 8, 8)] void main() {     for (int i = 0; i < 5; i++)     {         uint4 v0 = DoSomeCalculations1();         uint4 v1 = DoSomeCalculations2();         uint4 v2 = DoSomeCalculations3();                  if (v0.w == 0 && v1.w == 0 && v2.w)             continue;         //    increment counter by 3, and get it previous value         // this should basically allocate space for 3 uint4 values in buffer         uint prev;         Result.InterlockedAdd(0, 3, prev);                  // this fills the buffer with 3 uint4 values (+1 is here as the first 16 bytes is occupied by DrawInstancedIndirect data)         Result.Store4((prev+0+1)*16, v0);         Result.Store4((prev+1+1)*16, v1);         Result.Store4((prev+2+1)*16, v2);     } } Now I invoke it with Dispatch(4,4,4)
      Now I use DrawInstancedIndirect to draw the buffer, but ocassionaly there is missed triangle here and there for a frame, as if the atomic counter does not work as expected
      do I need any additional synchronization there ?
      I'v tried 'AllMemoryBarrierWithGroupSync' at the end of kernel, but without effect.
      If I do not use atomic counter, and istead just output empty vertices (that will transform into degenerated triangles) the all is OK - as if I'm missing some form of synchronization, but I do not see such a thing in DX11.
      I'v tested on both old and new nvidia hardware (680M and 1080, the behaviour is that same).
       
    • By Doggolainen
      Hello, 
      I am, like many others before me, making a displacement map tesselator. I want render some terrain using a quad, a texture containing heightdata and the geometryshader/tesselator.
      So far, Ive managed the utilize the texture on the pixelshader (I return different colors depending on the height). I have also managed to tesselate my surface, i.e. subdivided my quad into lots of triangles .
       
      What doesnt work however is the sampling step on the domain shader. I want to offset the vertices using the heightmap.
      I tried calling the same function "textureMap.Sample(textureSampler, texcoord)" as on the pixelshader but got compiling errors. Instead I am now using the "SampleLevel" function to use the 0 mipmap version of the input texture.
      But yeah non of this seem to be working. I wont get anything except [0, 0, 0, 0] from my sampler.
      Below is some code: The working pixelshader, the broken domain shader where I want to sample, and the instanciations of the samplerstates on the CPU side.
      Been stuck on this for a while! Any help would be much appreciated!
       
       
      Texture2D textureMap: register(t0); SamplerState textureSampler : register(s0); //Pixel shader float4 PS(PS_IN input) : SV_TARGET {     float4 textureColor = textureMap.Sample(textureSampler, input.texcoord);     return textureColor; } GS_IN DS(HS_CONSTANT_DATA input, float3 uvwCoord : SV_DomainLocation, const OutputPatch<DS_IN, 3> patch) {     GS_IN output;     float2 texcoord = uvwCoord.x * patch[0].texcoord.xy + uvwCoord.y * patch[1].texcoord.xy + uvwCoord.z *                    patch[2].texcoord.xy;     float4 textureColor = textureMap.SampleLevel(textureSampler, texcoord.xy, 0);      //fill  and return output....  }             //Sampler             SharpDX.Direct3D11.SamplerStateDescription samplerDescription;             samplerDescription = SharpDX.Direct3D11.SamplerStateDescription.Default();             samplerDescription.Filter = SharpDX.Direct3D11.Filter.MinMagMipLinear;             samplerDescription.AddressU = SharpDX.Direct3D11.TextureAddressMode.Wrap;             samplerDescription.AddressV = SharpDX.Direct3D11.TextureAddressMode.Wrap;             this.samplerStateTextures = new SharpDX.Direct3D11.SamplerState(d3dDevice, samplerDescription);             d3dDeviceContext.PixelShader.SetSampler(0, samplerStateTextures);             d3dDeviceContext.VertexShader.SetSampler(0, samplerStateTextures);             d3dDeviceContext.HullShader.SetSampler(0, samplerStateTextures);             d3dDeviceContext.DomainShader.SetSampler(0, samplerStateTextures);             d3dDeviceContext.GeometryShader.SetSampler(0, samplerStateTextures);  
    • By noodleBowl
      I just finished up my 1st iteration of my sprite renderer and I'm sort of questioning its performance.
      Currently, I am trying to render 10K worth of 64x64 textured sprites in a 800x600 window. These sprites all using the same texture, vertex shader, and pixel shader. There is basically no state changes. The sprite renderer itself is dynamic using the D3D11_MAP_WRITE_NO_OVERWRITE then D3D11_MAP_WRITE_DISCARD when the vertex buffer is full. The buffer is large enough to hold all 10K sprites and execute them in a single draw call. Cutting the buffer size down to only being able to fit 1000 sprites before a draw call is executed does not seem to matter / improve performance.  When I clock the time it takes to complete the render method for my sprite renderer (the only renderer that is running) I'm getting about 40ms. Aside from trying to adjust the size of the vertex buffer, I have tried using 1x1 texture and making the window smaller (640x480) as quick and dirty check to see if the GPU was the bottleneck, but I still get 40ms with both of those cases. 

      I'm kind of at a loss. What are some of the ways that I could figure out where my bottleneck is?
      I feel like only being able to render 10K sprites is really low, but I'm not sure. I'm not sure if I coded a poor renderer and there is a bottleneck somewhere or I'm being limited by my hardware

      Just some other info:
      Dev PC specs: GPU: Intel HD Graphics 4600 / Nvidia GTX 850M (Nvidia is set to be the preferred GPU in the Nvida control panel. Vsync is set to off) CPU: Intel Core i7-4710HQ @ 2.5GHz Renderer:
      //The renderer has a working depth buffer //Sprites have matrices that are precomputed. These pretransformed vertices are placed into the buffer Matrix4 model = sprite->getModelMatrix(); verts[0].position = model * verts[0].position; verts[1].position = model * verts[1].position; verts[2].position = model * verts[2].position; verts[3].position = model * verts[3].position; verts[4].position = model * verts[4].position; verts[5].position = model * verts[5].position; //Vertex buffer is flaged for dynamic use vertexBuffer = BufferModule::createVertexBuffer(D3D11_USAGE_DYNAMIC, D3D11_CPU_ACCESS_WRITE, sizeof(SpriteVertex) * MAX_VERTEX_COUNT_FOR_BUFFER); //The vertex buffer is mapped to when adding a sprite to the buffer //vertexBufferMapType could be D3D11_MAP_WRITE_NO_OVERWRITE or D3D11_MAP_WRITE_DISCARD depending on the data already in the vertex buffer D3D11_MAPPED_SUBRESOURCE resource = vertexBuffer->map(vertexBufferMapType); memcpy(((SpriteVertex*)resource.pData) + vertexCountInBuffer, verts, BYTES_PER_SPRITE); vertexBuffer->unmap(); //The constant buffer used for the MVP matrix is updated once per draw call D3D11_MAPPED_SUBRESOURCE resource = mvpConstBuffer->map(D3D11_MAP_WRITE_DISCARD); memcpy(resource.pData, projectionMatrix.getData(), sizeof(Matrix4)); mvpConstBuffer->unmap(); Vertex / Pixel Shader:
      cbuffer mvpBuffer : register(b0) { matrix mvp; } struct VertexInput { float4 position : POSITION; float2 texCoords : TEXCOORD0; float4 color : COLOR; }; struct PixelInput { float4 position : SV_POSITION; float2 texCoords : TEXCOORD0; float4 color : COLOR; }; PixelInput VSMain(VertexInput input) { input.position.w = 1.0f; PixelInput output; output.position = mul(mvp, input.position); output.texCoords = input.texCoords; output.color = input.color; return output; } Texture2D shaderTexture; SamplerState samplerType; float4 PSMain(PixelInput input) : SV_TARGET { float4 textureColor = shaderTexture.Sample(samplerType, input.texCoords); return textureColor; }  
      If anymore info is needed feel free to ask, I would really like to know how I can improve this assuming I'm not hardware limited
    • By DiligentDev
      This article uses material originally posted on Diligent Graphics web site.
      Introduction
      Graphics APIs have come a long way from small set of basic commands allowing limited control of configurable stages of early 3D accelerators to very low-level programming interfaces exposing almost every aspect of the underlying graphics hardware. Next-generation APIs, Direct3D12 by Microsoft and Vulkan by Khronos are relatively new and have only started getting widespread adoption and support from hardware vendors, while Direct3D11 and OpenGL are still considered industry standard. New APIs can provide substantial performance and functional improvements, but may not be supported by older hardware. An application targeting wide range of platforms needs to support Direct3D11 and OpenGL. New APIs will not give any advantage when used with old paradigms. It is totally possible to add Direct3D12 support to an existing renderer by implementing Direct3D11 interface through Direct3D12, but this will give zero benefits. Instead, new approaches and rendering architectures that leverage flexibility provided by the next-generation APIs are expected to be developed.
      There are at least four APIs (Direct3D11, Direct3D12, OpenGL/GLES, Vulkan, plus Apple's Metal for iOS and osX platforms) that a cross-platform 3D application may need to support. Writing separate code paths for all APIs is clearly not an option for any real-world application and the need for a cross-platform graphics abstraction layer is evident. The following is the list of requirements that I believe such layer needs to satisfy:
      Lightweight abstractions: the API should be as close to the underlying native APIs as possible to allow an application leverage all available low-level functionality. In many cases this requirement is difficult to achieve because specific features exposed by different APIs may vary considerably. Low performance overhead: the abstraction layer needs to be efficient from performance point of view. If it introduces considerable amount of overhead, there is no point in using it. Convenience: the API needs to be convenient to use. It needs to assist developers in achieving their goals not limiting their control of the graphics hardware. Multithreading: ability to efficiently parallelize work is in the core of Direct3D12 and Vulkan and one of the main selling points of the new APIs. Support for multithreading in a cross-platform layer is a must. Extensibility: no matter how well the API is designed, it still introduces some level of abstraction. In some cases the most efficient way to implement certain functionality is to directly use native API. The abstraction layer needs to provide seamless interoperability with the underlying native APIs to provide a way for the app to add features that may be missing. Diligent Engine is designed to solve these problems. 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 C++ front-end for all supported platforms and provides interoperability with underlying native APIs. It also supports integration with Unity and is designed to be used as graphics subsystem in a standalone game engine, Unity native plugin or any other 3D application. Full source code is available for download at GitHub and is free to use.
      Overview
      Diligent Engine API takes some features from Direct3D11 and Direct3D12 as well as introduces new concepts to hide certain platform-specific details and make the system easy to use. It contains the following main components:
      Render device (IRenderDevice  interface) is responsible for creating all other objects (textures, buffers, shaders, pipeline states, etc.).
      Device context (IDeviceContext interface) is the main interface for recording rendering commands. Similar to Direct3D11, there are immediate context and deferred contexts (which in Direct3D11 implementation map directly to the corresponding context types). Immediate context combines command queue and command list recording functionality. It records commands and submits the command list for execution when it contains sufficient number of commands. Deferred contexts are designed to only record command lists that can be submitted for execution through the immediate context.
      An alternative way to design the API would be to expose command queue and command lists directly. This approach however does not map well to Direct3D11 and OpenGL. Besides, some functionality (such as dynamic descriptor allocation) can be much more efficiently implemented when it is known that a command list is recorded by a certain deferred context from some thread.
      The approach taken in the engine does not limit scalability as the application is expected to create one deferred context per thread, and internally every deferred context records a command list in lock-free fashion. At the same time this approach maps well to older APIs.
      In current implementation, only one immediate context that uses default graphics command queue is created. To support multiple GPUs or multiple command queue types (compute, copy, etc.), it is natural to have one immediate contexts per queue. Cross-context synchronization utilities will be necessary.
      Swap Chain (ISwapChain interface). Swap chain interface represents a chain of back buffers and is responsible for showing the final rendered image on the screen.
      Render device, device contexts and swap chain are created during the engine initialization.
      Resources (ITexture and IBuffer interfaces). There are two types of resources - textures and buffers. There are many different texture types (2D textures, 3D textures, texture array, cubmepas, etc.) that can all be represented by ITexture interface.
      Resources Views (ITextureView and IBufferView interfaces). While textures and buffers are mere data containers, texture views and buffer views describe how the data should be interpreted. For instance, a 2D texture can be used as a render target for rendering commands or as a shader resource.
      Pipeline State (IPipelineState interface). GPU pipeline contains many configurable stages (depth-stencil, rasterizer and blend states, different shader stage, etc.). Direct3D11 uses coarse-grain objects to set all stage parameters at once (for instance, a rasterizer object encompasses all rasterizer attributes), while OpenGL contains myriad functions to fine-grain control every individual attribute of every stage. Both methods do not map very well to modern graphics hardware that combines all states into one monolithic state under the hood. Direct3D12 directly exposes pipeline state object in the API, and Diligent Engine uses the same approach.
      Shader Resource Binding (IShaderResourceBinding interface). Shaders are programs that run on the GPU. Shaders may access various resources (textures and buffers), and setting correspondence between shader variables and actual resources is called resource binding. Resource binding implementation varies considerably between different API. Diligent Engine introduces a new object called shader resource binding that encompasses all resources needed by all shaders in a certain pipeline state.
      API Basics
      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. Graphics APIs usually have a native object that represents linear buffer. Diligent Engine uses IBuffer interface as an abstraction for a native buffer. To create a buffer, one needs to populate BufferDesc structure and call IRenderDevice::CreateBuffer() method as in the following example:
      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 ); While there is usually just one buffer object, different APIs use very different approaches to represent textures. For instance, in Direct3D11, there are ID3D11Texture1D, ID3D11Texture2D, and ID3D11Texture3D objects. In OpenGL, there is individual object for every texture dimension (1D, 2D, 3D, Cube), which may be a texture array, which may also be multisampled (i.e. GL_TEXTURE_2D_MULTISAMPLE_ARRAY). As a result there are nine different GL texture types that Diligent Engine may create under the hood. In Direct3D12, there is only one resource interface. Diligent Engine hides all these details in ITexture interface. There is only one  IRenderDevice::CreateTexture() method that is capable of creating all texture types. Dimension, format, array size and all other parameters are specified by the members of the TextureDesc structure:
      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 ); If native API supports multithreaded resource creation, textures and buffers can be created by multiple threads simultaneously.
      Interoperability with native API provides access to the native buffer/texture objects and also allows creating Diligent Engine objects from native handles. It allows applications seamlessly integrate native API-specific code with Diligent Engine.
      Next-generation APIs allow fine level-control over how resources are allocated. Diligent Engine does not currently expose this functionality, but it can be added by implementing IResourceAllocator interface that encapsulates specifics of resource allocation and providing this interface to CreateBuffer() or CreateTexture() methods. If null is provided, default allocator should be used.
      Initializing the Pipeline State
      As it was mentioned earlier, Diligent Engine follows next-gen APIs 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.). This approach maps directly to Direct3D12/Vulkan, but is also beneficial for older APIs as it eliminates pipeline misconfiguration errors. With many individual calls tweaking various GPU pipeline settings it is very easy to forget to set one of the states or assume the stage is already properly configured when in fact it is not. Using pipeline state object helps avoid these problems as all stages are configured at once.
      Creating Shaders
      While in earlier APIs shaders were bound separately, in the next-generation APIs as well as in Diligent Engine shaders are part of the pipeline state object. The biggest challenge when authoring shaders is that Direct3D and OpenGL/Vulkan use different shader languages (while Apple uses yet another language in their Metal API). Maintaining two versions of every shader is not an option for real applications and Diligent Engine implements shader source code converter that allows shaders authored in HLSL to be translated to GLSL. To create a shader, one needs to populate ShaderCreationAttribs structure. SourceLanguage member of this structure tells the system which language the shader is authored in:
      SHADER_SOURCE_LANGUAGE_DEFAULT - The shader source language matches the underlying graphics API: HLSL for Direct3D11/Direct3D12 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. SHADER_SOURCE_LANGUAGE_GLSL - The shader source is in GLSL. There is currently no GLSL to HLSL converter, so this value should only be used for OpenGL and OpenGLES modes. There are two ways to provide the shader source code. The first way is to use Source member. The second way is to provide a file path in FilePath member. Since the engine is entirely decoupled from the platform and the host file system is platform-dependent, the structure exposes pShaderSourceStreamFactory member that is intended to provide the engine access to the file system. If FilePath is provided, shader source factory must also be provided. If the shader source contains any #include directives, the source stream factory will also be used to load these files. The engine provides default implementation for every supported platform that should be sufficient in most cases. Custom implementation can be provided when needed.
      When sampling a texture in a shader, the texture sampler was traditionally specified as separate object that was bound to the pipeline at run time or set as part of the texture object itself. However, in most cases it is known beforehand what kind of sampler will be used in the shader. Next-generation APIs expose new type of sampler called static sampler that can be initialized directly in the pipeline state. Diligent Engine exposes this functionality: when creating a shader, textures can be assigned static samplers. If static sampler is assigned, it will always be used instead of the one initialized in the texture shader resource view. To initialize static samplers, prepare an array of StaticSamplerDesc structures and initialize StaticSamplers and NumStaticSamplers members. Static samplers are more efficient and it is highly recommended to use them whenever possible. On older APIs, static samplers are emulated via generic sampler objects.
      The following is an example of shader initialization:
      ShaderCreationAttribs Attrs; Attrs.Desc.Name = "MyPixelShader"; Attrs.FilePath = "MyShaderFile.fx"; Attrs.SearchDirectories = "shaders;shaders\\inc;"; Attrs.EntryPoint = "MyPixelShader"; Attrs.Desc.ShaderType = SHADER_TYPE_PIXEL; Attrs.SourceLanguage = SHADER_SOURCE_LANGUAGE_HLSL; BasicShaderSourceStreamFactory BasicSSSFactory(Attrs.SearchDirectories); Attrs.pShaderSourceStreamFactory = &BasicSSSFactory; ShaderVariableDesc ShaderVars[] = {     {"g_StaticTexture", SHADER_VARIABLE_TYPE_STATIC},     {"g_MutableTexture", SHADER_VARIABLE_TYPE_MUTABLE},     {"g_DynamicTexture", SHADER_VARIABLE_TYPE_DYNAMIC} }; Attrs.Desc.VariableDesc = ShaderVars; Attrs.Desc.NumVariables = _countof(ShaderVars); Attrs.Desc.DefaultVariableType = SHADER_VARIABLE_TYPE_STATIC; StaticSamplerDesc StaticSampler; StaticSampler.Desc.MinFilter = FILTER_TYPE_LINEAR; StaticSampler.Desc.MagFilter = FILTER_TYPE_LINEAR; StaticSampler.Desc.MipFilter = FILTER_TYPE_LINEAR; StaticSampler.TextureName = "g_MutableTexture"; Attrs.Desc.NumStaticSamplers = 1; Attrs.Desc.StaticSamplers = &StaticSampler; ShaderMacroHelper Macros; Macros.AddShaderMacro("USE_SHADOWS", 1); Macros.AddShaderMacro("NUM_SHADOW_SAMPLES", 4); Macros.Finalize(); Attrs.Macros = Macros; RefCntAutoPtr<IShader> pShader; m_pDevice->CreateShader( Attrs, &pShader );
      Creating the Pipeline State Object
      After all required shaders are created, the rest of the fields of the PipelineStateDesc structure provide depth-stencil, rasterizer, and blend state descriptions, the number and format of render targets, input layout format, etc. For instance, rasterizer state can be described as follows:
      PipelineStateDesc PSODesc; RasterizerStateDesc &RasterizerDesc = PSODesc.GraphicsPipeline.RasterizerDesc; RasterizerDesc.FillMode = FILL_MODE_SOLID; RasterizerDesc.CullMode = CULL_MODE_NONE; RasterizerDesc.FrontCounterClockwise = True; RasterizerDesc.ScissorEnable = True; RasterizerDesc.AntialiasedLineEnable = False; Depth-stencil and blend states are defined in a similar fashion.
      Another important thing that pipeline state object encompasses is the input layout description that defines how inputs to the vertex shader, which is the very first shader stage, should be read from the memory. Input layout may define several vertex streams that contain values of different formats and sizes:
      // Define input layout InputLayoutDesc &Layout = PSODesc.GraphicsPipeline.InputLayout; LayoutElement TextLayoutElems[] = {     LayoutElement( 0, 0, 3, VT_FLOAT32, False ),     LayoutElement( 1, 0, 4, VT_UINT8, True ),     LayoutElement( 2, 0, 2, VT_FLOAT32, False ), }; Layout.LayoutElements = TextLayoutElems; Layout.NumElements = _countof( TextLayoutElems ); Finally, pipeline state defines primitive topology type. When all required members are initialized, a pipeline state object can be created by IRenderDevice::CreatePipelineState() method:
      // Define shader and primitive topology PSODesc.GraphicsPipeline.PrimitiveTopologyType = PRIMITIVE_TOPOLOGY_TYPE_TRIANGLE; PSODesc.GraphicsPipeline.pVS = pVertexShader; PSODesc.GraphicsPipeline.pPS = pPixelShader; PSODesc.Name = "My pipeline state"; m_pDev->CreatePipelineState(PSODesc, &m_pPSO); When PSO object is bound to the pipeline, the engine invokes all API-specific commands to set all states specified by the object. In case of Direct3D12 this maps directly to setting the D3D12 PSO object. In case of Direct3D11, this involves setting individual state objects (such as rasterizer and blend states), shaders, input layout etc. In case of OpenGL, this requires a number of fine-grain state tweaking calls. Diligent Engine keeps track of currently bound states and only calls functions to update these states that have actually changed.
      Binding Shader Resources
      Direct3D11 and OpenGL utilize fine-grain resource binding models, where an application binds individual buffers and textures to certain shader or program resource binding slots. Direct3D12 uses a very different approach, where resource descriptors are grouped into tables, and an application can bind all resources in the table at once by setting the table in the command list. Resource binding model in Diligent Engine is designed to leverage this new method. It introduces a new object called shader resource binding that encapsulates all resource bindings required for all shaders in a certain pipeline state. It also introduces the classification of shader variables based on the frequency of expected change that helps the engine group them into tables under the hood:
      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. Shader variable type must be specified during shader creation by populating an array of ShaderVariableDesc structures and initializing ShaderCreationAttribs::Desc::VariableDesc and ShaderCreationAttribs::Desc::NumVariables members (see example of shader creation above).
      Static variables cannot be changed once a resource is bound to the variable. They are bound directly to the shader object. For instance, a shadow map texture is not expected to change after it is created, so it can be bound directly to the shader:
      PixelShader->GetShaderVariable( "g_tex2DShadowMap" )->Set( pShadowMapSRV ); Mutable and dynamic variables are bound via a new Shader Resource Binding object (SRB) that is created by the pipeline state (IPipelineState::CreateShaderResourceBinding()):
      m_pPSO->CreateShaderResourceBinding(&m_pSRB); Note that an SRB is only compatible with the pipeline state it was created from. SRB object inherits all static bindings from shaders in the pipeline, but is not allowed to change them.
      Mutable resources can only be set once for every instance of a shader resource binding. Such resources are intended to define specific material properties. For instance, a diffuse texture for a specific material is not expected to change once the material is defined and can be set right after the SRB object has been created:
      m_pSRB->GetVariable(SHADER_TYPE_PIXEL, "tex2DDiffuse")->Set(pDiffuseTexSRV); In some cases it is necessary to bind a new resource to a variable every time a draw command is invoked. Such variables should be labeled as dynamic, which will allow setting them multiple times through the same SRB object:
      m_pSRB->GetVariable(SHADER_TYPE_VERTEX, "cbRandomAttribs")->Set(pRandomAttrsCB); Under the hood, the engine pre-allocates descriptor tables for static and mutable resources when an SRB objcet is created. Space for dynamic resources is dynamically allocated at run time. Static and mutable resources are thus more efficient and should be used whenever possible.
      As you can see, Diligent Engine does not expose low-level details of how resources are bound to shader variables. One reason for this is that these details are very different for various APIs. The other reason is that using low-level binding methods is extremely error-prone: it is very easy to forget to bind some resource, or bind incorrect resource such as bind a buffer to the variable that is in fact a texture, especially during shader development when everything changes fast. Diligent Engine instead relies on shader reflection system to automatically query the list of all shader variables. Grouping variables based on three types mentioned above allows the engine to create optimized layout and take heavy lifting of matching resources to API-specific resource location, register or descriptor in the table.
      This post gives more details about the resource binding model in Diligent Engine.
      Setting the Pipeline State and Committing Shader Resources
      Before any draw or compute command can be invoked, the pipeline state needs to be bound to the context:
      m_pContext->SetPipelineState(m_pPSO); Under the hood, the engine sets the internal PSO object in the command list or calls all the required native API functions to properly configure all pipeline stages.
      The next step is to bind all required shader resources to the GPU pipeline, which is accomplished by IDeviceContext::CommitShaderResources() method:
      m_pContext->CommitShaderResources(m_pSRB, COMMIT_SHADER_RESOURCES_FLAG_TRANSITION_RESOURCES); The method takes a pointer to the shader resource binding object and makes all resources the object holds available for the shaders. In the case of D3D12, this only requires setting appropriate descriptor tables in the command list. For older APIs, this typically requires setting all resources individually.
      Next-generation APIs require the application to track the state of every resource and explicitly inform the system about all state transitions. For instance, if a texture was used as render target before, while the next draw command is going to use it as shader resource, a transition barrier needs to be executed. Diligent Engine does the heavy lifting of state tracking.  When CommitShaderResources() method is called with COMMIT_SHADER_RESOURCES_FLAG_TRANSITION_RESOURCES flag, the engine commits and transitions resources to correct states at the same time. Note that transitioning resources does introduce some overhead. The engine tracks state of every resource and it will not issue the barrier if the state is already correct. But checking resource state is an overhead that can sometimes be avoided. The engine provides IDeviceContext::TransitionShaderResources() method that only transitions resources:
      m_pContext->TransitionShaderResources(m_pPSO, m_pSRB); In some scenarios it is more efficient to transition resources once and then only commit them.
      Invoking Draw Command
      The final step is to set states that are not part of the PSO, such as render targets, vertex and index buffers. Diligent Engine uses Direct3D11-syle API that is translated to other native API calls under the hood:
      ITextureView *pRTVs[] = {m_pRTV}; m_pContext->SetRenderTargets(_countof( pRTVs ), pRTVs, m_pDSV); // Clear render target and depth buffer const float zero[4] = {0, 0, 0, 0}; m_pContext->ClearRenderTarget(nullptr, zero); m_pContext->ClearDepthStencil(nullptr, CLEAR_DEPTH_FLAG, 1.f); // 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); Different native APIs use various set of function to execute draw commands depending on command details (if the command is indexed, instanced or both, what offsets in the source buffers are used etc.). For instance, there are 5 draw commands in Direct3D11 and more than 9 commands in OpenGL with something like glDrawElementsInstancedBaseVertexBaseInstance not uncommon. Diligent Engine hides all details with single IDeviceContext::Draw() method that takes 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); For compute commands, there is IDeviceContext::DispatchCompute() method that takes DispatchComputeAttribs structure that defines compute grid dimension.
      Source Code
      Full engine source code is available on GitHub and is free to use. The repository contains two samples, asteroids performance benchmark and example Unity project that uses Diligent Engine in native plugin.
      AntTweakBar sample is Diligent Engine’s “Hello World” example.

       
      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 multiple render targets, using compute shaders and unordered access views, etc.

      Asteroids performance benchmark is based on this demo developed by Intel. It renders 50,000 unique textured asteroids and allows comparing performance of Direct3D11 and Direct3D12 implementations. Every asteroid is a combination of one of 1000 unique meshes and one of 10 unique textures.

      Finally, there is an example project that shows how Diligent Engine can be integrated with Unity.

      Future Work
      The engine is under active development. It currently supports Windows desktop, Universal Windows and Android platforms. Direct3D11, Direct3D12, OpenGL/GLES backends are now feature complete. Vulkan backend is coming next, and support for more platforms is planned.
    • By noodleBowl
      I am currently working on my first iteration of my sprite renderer and I'm trying to draw 2 sprites. They both use the same texture and are placed into the same buffer, but unfortunately only the second sprite is shown on the the screen. I assume I messed something up when I place them into the buffer and that I am overwriting the data of the first sprite.

      So how should I be mapping my buffer with an offset?
      /* Code that sets up the sprite vertices and etc */ D3D11_MAPPED_SUBRESOURCE resource = vertexBuffer->map(vertexBufferMapType); memcpy(resource.pData, verts, sizeof(SpriteVertex) * VERTEX_PER_QUAD); vertexBuffer->unmap(); vertexCount += VERTEX_PER_QUAD; I feel like I should be doing something like:
      /* Code that sets up the sprite vertices and etc */ D3D11_MAPPED_SUBRESOURCE resource = vertexBuffer->map(vertexBufferMapType); //Place the sprite vertex data into the pData using the current vertex count as offset //The code resource.pData[vertexCount] is syntatically wrong though :( Not sure how it should look since pData is void pointer memcpy(resource.pData[vertexCount], verts, sizeof(SpriteVertex) * VERTEX_PER_QUAD); vertexBuffer->unmap(); vertexCount += VERTEX_PER_QUAD;  
      Also speaking of offsets can someone give an example of when the pOffsets param for the IASetVertexBuffers call would not be 0
       
  • Popular Now