# DX11 Moving graphics engine to DLL project

## Recommended Posts

I tried to make my graphics engine into a DLL by moving all code from the DirectX example project to a new DLL project in Visual C++ 2005.
I have made a working connection between the DLL and a testing project in the same visual studio solution so that simple calls can be made.
Now I have both DXUT.h and stdafx.h included in the whole engine but only stdafx.h is forced to be included.
I have checked that the DirectX libs and stuff are included in Visual Studio.

Here are the link errors after solving many regular errors:
1>------ Build started: Project: GameEngine, Configuration: Release Win32 ------1>Compiling...1>stdafx.cpp1>Compiling...1>SDKmisc.cpp1>Model.cpp1>IntegerArray.cpp1>DXUTmisc.cpp1>DXUTDevice11.cpp1>DXUTcamera.cpp1>DXUT.cpp1>StringMethods.cpp1>GameEngine.cpp1>Linking...1>   Creating library C:\Users\David\Documents\Visual Studio 2005\Projects\GameEngine\Release\GameEngine.lib and object C:\Users\David\Documents\Visual Studio 2005\Projects\GameEngine\Release\GameEngine.exp1>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXMatrixMultiply@121>GameEngine.obj : error LNK2001: unresolved external symbol _D3DX11CompileFromFileW@441>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXMatrixOrthoOffCenterLH@281>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXVec3Normalize@81>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXVec3Transform@121>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXVec3TransformCoord@121>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXMatrixTranspose@81>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXMatrixScaling@161>GameEngine.obj : error LNK2001: unresolved external symbol _D3DXMatrixTranslation@161>DXUT.obj : error LNK2001: unresolved external symbol __imp__InitCommonControls@01>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXQuaternionMultiply@121>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXMatrixRotationQuaternion@81>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXMatrixLookAtLH@161>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXMatrixInverse@121>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXMatrixPerspectiveFovLH@201>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXMatrixRotationYawPitchRoll@161>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXQuaternionRotationMatrix@81>DXUTcamera.obj : error LNK2001: unresolved external symbol _D3DXVec3TransformNormal@121>DXUTmisc.obj : error LNK2001: unresolved external symbol _DXTraceW@201>DXUTmisc.obj : error LNK2001: unresolved external symbol _D3DX11SaveTextureToFileW@161>SDKmisc.obj : error LNK2001: unresolved external symbol _D3DX11GetImageInfoFromFileW@161>SDKmisc.obj : error LNK2001: unresolved external symbol _D3DX11CreateTextureFromFileW@241>C:\Users\David\Documents\Visual Studio 2005\Projects\GameEngine\Release\GameEngine.dll : fatal error LNK1120: 22 unresolved externals1>Build log was saved at "file://c:\Users\David\Documents\Visual Studio 2005\Projects\GameEngine\GameEngine\Release\BuildLog.htm"1>GameEngine - 23 error(s), 0 warning(s)========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Have anyone seen that before?

Is there any good general method for solving link errors?

##### Share on other sites
It looks like you don't have the lib files for the D3DX functions linked into your DLL; check which files the DLL project is linking against and compare that to your exe/original project/another D3D project which uses D3DX functions.

##### Share on other sites
Thanks, it solved it.

Solution for anyone with the same issue:
Project's property page - Configuration Properties - Linker - Input
d3dcompiler.lib dxerr.lib dxguid.lib d3dx9.lib d3d9.lib winmm.lib comctl32.lib dxgi.lib d3dx11.lib d3d10.lib

##### Share on other sites
I have one problem remaining. I have an HLSL supershader and a header for named constant definitions used by both the HLSL shader and the engine DLL.
I don't want the user to see the HLSL file because the user would start to modify it and be unable to upgrade to another version of my engine.
If I include the shader as a static string then it can't reach the header file because that won't be released with the engine.

How can I place both files in the engine without duplicating code or making an included mess for the user?

##### Share on other sites
Have the file names declared in the header file, but defined in cpp files, not header files. So when you compile your dll, they will be in the dll, not the header.

##### Share on other sites
Quote:
 Original post by smasherprogHave the file names declared in the header file, but defined in cpp files, not header files. So when you compile your dll, they will be in the dll, not the header.

What would the file names refer to?

##### Share on other sites
You said you had some constants that you want hidden from users, as well as a shader. Declare them in the header, and define them in your cpp file.

##### Share on other sites
Quote:
 Original post by smasherprogYou said you had some constants that you want hidden from users, as well as a shader. Declare them in the header, and define them in your cpp file.

One header with macros is used by both HLSL and Cpp.

#define Common_MaxNumberOfDynamicPointLights 64#define Common_ObjectType_Skybox 0	// This is used by the engine to draw the sky#define Common_ObjectType_Material 1	// This is used for your objects#define Common_ObjectType_Shadow 2	// This is used to render shadows#define Common_ObjectType_Effect 3	// This is used for post effects	#define Common_NumberOfObjectTypes 4	// Last object type + 1#define Common_CascadeCount 4// The types of shaders with reused numbers in different object types to compile fewer shaders.#define Common_FirstShadowPixelShaderType 0#define Common_PixelShaderType_Shadow_Simple 0	//#define Common_PixelShaderType_Shadow_Alpha 1	// D#define Common_LastShadowPixelShaderType 1#define Common_FirstSkyPixelShaderType	 2#define Common_PixelShaderType_Sky_Simple 2	//#define Common_LastSkyPixelShaderType 2#define Common_FirstMaterialPixelShaderType 3#define Common_PixelShaderType_Material_NoTextures 3	//#define Common_PixelShaderType_Material_DiffuseOnly 4	// D#define Common_PixelShaderType_Material_Bump 5	// D N#define Common_PixelShaderType_Material_SpecularBump 6	// D N S#define Common_PixelShaderType_Material_Specular 7	// D   S#define Common_PixelShaderType_Material_Illuminated 8	// D#define Common_PixelShaderType_Material_IlluminatedBump 9	// D N#define Common_PixelShaderType_Material_IlluminatedSpecularBump 10	// D N S#define Common_PixelShaderType_Material_IlluminatedSpecular 11 // D   S#define Common_LastMaterialPixelShaderType 11#define Common_FirstEffectPixelShaderType 12#define Common_PixelShaderType_Effect_None 12#define Common_PixelShaderType_Effect_ADD_AB 13#define Common_PixelShaderType_Effect_ADD_ABC 14#define Common_PixelShaderType_Effect_ADD_ABCD	 15#define Common_PixelShaderType_Effect_Blur_Linear 16#define Common_PixelShaderType_Effect_AddArg	 17#define Common_PixelShaderType_Effect_MultiplyWithArg 18#define Common_PixelShaderType_Effect_RaiseToArg 19#define Common_PixelShaderType_Effect_GrayScale	 20#define Common_LastEffectPixelShaderType 20#define Common_NumberOfPixelShaderTypes	21 // Max pixel shader type + 1#define Common_FirstShadowVertexShaderType 0#define Common_VertexShaderType_Shadow 0#define Common_VertexShaderType_AlphaShadow 1#define Common_LastShadowVertexShaderType 1#define Common_FirstSkyVertexShaderType	2#define Common_VertexShaderType_Sky 2#define Common_LastSkyVertexShaderType 2#define Common_FirstMaterialVertexShaderType 3#define Common_VertexShaderType_Material_Flat 3#define Common_VertexShaderType_Material_Bump 4#define Common_LastMaterialVertexShaderType 4#define Common_FirstEffectVertexShaderType 5#define Common_VertexShaderType_Effect_Standard 5#define Common_LastEffectVertexShaderType 5#define Common_NumberOfVertexShaderTypes 6 // Max vertex shader type + 1

##### Share on other sites
Well, try changing them to extern const ? You are kind of stuck if you use defines and want to hide them from users in a dll.

##### Share on other sites
Quote:
 Original post by smasherprogWell, try changing them to extern const ? You are kind of stuck if you use defines and want to hide them from users in a dll.

OK, I haven't used extern constants before.
How do I reach them in both compiletime and runtime?

##### Share on other sites
Well, I havent compiled a dll and linked it to a library, so, hopefully it will work :P

extern const int NumberOfLights;

const int NumberOfLights = 10;

##### Share on other sites
That seems more complicated than having to copy the header to a constant shader string because I add values more than I change them.

Can I reach the same header as both a Visual Studio resource and a regular header?

##### Share on other sites
If you are inclined to put everything into a dll, then you must compile it each time something within it changes. So, if you want to "hide" information from people who use your dll, then you will have to recompile it each time to add/change/remove something.

If your code is in a header, everyone can see it or modify it. If its in a cpp file, then you can compile it into your dll. That is really the end of it. Decide what you want to do. If its not convenient to recompile the dll for each change you make, then don't put it into a dll.

It is unnecessary to think you need to rebuild the dll for every little change you make . . . Just build everything using the full source code, and build your dll only when you want to release a build.

##### Share on other sites
I have configured the solution so that modified modules in the engine DLL is compiled automatically when when starting the testing project.

## Create an account

Register a new account

• ### Forum Statistics

• Total Topics
628291
• Total Posts
2981862
• ### Similar Content

• I'm attempting to implement some basic post-processing in my "engine" and the HLSL part of the Compute Shader and such I think I've understood, however I'm at a loss at how to actually get/use it's output for rendering to the screen.
Assume I'm doing something to a UAV in my CS:
RWTexture2D<float4> InputOutputMap : register(u0); I want that texture to essentially "be" the backbuffer.

I'm pretty certain I'm doing something wrong when I create the views (what I think I'm doing is having the backbuffer be bound as render target aswell as UAV and then using it in my CS):

DXGI_SWAP_CHAIN_DESC scd; ZeroMemory(&scd, sizeof(DXGI_SWAP_CHAIN_DESC)); scd.BufferCount = 1; scd.BufferDesc.Format = DXGI_FORMAT_R8G8B8A8_UNORM; scd.BufferUsage = DXGI_USAGE_RENDER_TARGET_OUTPUT | DXGI_USAGE_SHADER_INPUT | DXGI_USAGE_UNORDERED_ACCESS; scd.OutputWindow = wndHandle; scd.SampleDesc.Count = 1; scd.Windowed = TRUE; HRESULT hr = D3D11CreateDeviceAndSwapChain(NULL, D3D_DRIVER_TYPE_HARDWARE, NULL, NULL, NULL, NULL, D3D11_SDK_VERSION, &scd, &gSwapChain, &gDevice, NULL, &gDeviceContext); // get the address of the back buffer ID3D11Texture2D* pBackBuffer = nullptr; gSwapChain->GetBuffer(0, __uuidof(ID3D11Texture2D), (LPVOID*)&pBackBuffer); // use the back buffer address to create the render target gDevice->CreateRenderTargetView(pBackBuffer, NULL, &gBackbufferRTV); // set the render target as the back buffer CreateDepthStencilBuffer(); gDeviceContext->OMSetRenderTargets(1, &gBackbufferRTV, depthStencilView); //UAV for compute shader D3D11_UNORDERED_ACCESS_VIEW_DESC uavd; ZeroMemory(&uavd, sizeof(uavd)); uavd.Format = DXGI_FORMAT_R8G8B8A8_UNORM; uavd.ViewDimension = D3D11_UAV_DIMENSION_TEXTURE2D; uavd.Texture2D.MipSlice = 1; gDevice->CreateUnorderedAccessView(pBackBuffer, &uavd, &gUAV); pBackBuffer->Release();
After I render the scene, I dispatch like this:
gDeviceContext->OMSetRenderTargets(0, NULL, NULL); m_vShaders["cs1"]->Bind(); gDeviceContext->CSSetUnorderedAccessViews(0, 1, &gUAV, 0); gDeviceContext->Dispatch(32, 24, 0); //hard coded ID3D11UnorderedAccessView* nullview = { nullptr }; gDeviceContext->CSSetUnorderedAccessViews(0, 1, &nullview, 0); gDeviceContext->OMSetRenderTargets(1, &gBackbufferRTV, depthStencilView); gSwapChain->Present(0, 0); Worth noting is the scene is rendered as usual, but I dont get any results from the CS (simple gaussian blur)
I'm sure it's something fairly basic I'm doing wrong, perhaps my understanding of render targets / views / what have you is just completely wrong and my approach just makes no sense.

If someone with more experience could point me in the right direction I would really appreciate it!

On a side note, I'd really like to learn more about this kind of stuff. I can really see the potential of the CS aswell as rendering to textures and using them for whatever in the engine so I would love it if you know some good resources I can read about this!

Thank you <3

P.S I excluded the .hlsl since I cant imagine that being the issue, but if you think you need it to help me just ask

P:P:S. As you can see this is my first post however I do have another account, but I can't log in with it because gamedev.net just keeps asking me to accept terms and then logs me out when I do over and over

• I was wondering if anyone could explain the depth buffer and the depth stencil state comparison function to me as I'm a little confused
So I have set up a depth stencil state where the DepthFunc is set to D3D11_COMPARISON_LESS, but what am I actually comparing here? What is actually written to the buffer, the pixel that should show up in the front?
I have these 2 quad faces, a Red Face and a Blue Face. The Blue Face is further away from the Viewer with a Z index value of -100.0f. Where the Red Face is close to the Viewer with a Z index value of 0.0f.
When DepthFunc is set to D3D11_COMPARISON_LESS the Red Face shows up in front of the Blue Face like it should based on the Z index values. BUT if I change the DepthFunc to D3D11_COMPARISON_LESS_EQUAL the Blue Face shows in front of the Red Face. Which does not make sense to me, I would think that when the function is set to D3D11_COMPARISON_LESS_EQUAL the Red Face would still show up in front of the Blue Face as the Z index for the Red Face is still closer to the viewer
Am I thinking of this comparison function all wrong?
Vertex data just in case
//Vertex date that make up the 2 faces Vertex verts[] = { //Red face Vertex(Vector4(0.0f, 0.0f, 0.0f), Color(1.0f, 0.0f, 0.0f)), Vertex(Vector4(100.0f, 100.0f, 0.0f), Color(1.0f, 0.0f, 0.0f)), Vertex(Vector4(100.0f, 0.0f, 0.0f), Color(1.0f, 0.0f, 0.0f)), Vertex(Vector4(0.0f, 0.0f, 0.0f), Color(1.0f, 0.0f, 0.0f)), Vertex(Vector4(0.0f, 100.0f, 0.0f), Color(1.0f, 0.0f, 0.0f)), Vertex(Vector4(100.0f, 100.0f, 0.0f), Color(1.0f, 0.0f, 0.0f)), //Blue face Vertex(Vector4(0.0f, 0.0f, -100.0f), Color(0.0f, 0.0f, 1.0f)), Vertex(Vector4(100.0f, 100.0f, -100.0f), Color(0.0f, 0.0f, 1.0f)), Vertex(Vector4(100.0f, 0.0f, -100.0f), Color(0.0f, 0.0f, 1.0f)), Vertex(Vector4(0.0f, 0.0f, -100.0f), Color(0.0f, 0.0f, 1.0f)), Vertex(Vector4(0.0f, 100.0f, -100.0f), Color(0.0f, 0.0f, 1.0f)), Vertex(Vector4(100.0f, 100.0f, -100.0f), Color(0.0f, 0.0f, 1.0f)), };
• By mellinoe
Hi all,
First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.

• If I do a buffer update with MAP_NO_OVERWRITE or MAP_DISCARD, can I just write to the buffer after I called Unmap() on the buffer? It seems to work fine for me (Nvidia driver), but is it actually legal to do so? I have a graphics device wrapper and I don't want to expose Map/Unmap, but just have a function like void* AllocateFromRingBuffer(GPUBuffer* buffer, uint size, uint& offset); This function would just call Map on the buffer, then Unmap immediately and then return the address of the buffer. It usually does a MAP_NO_OVERWRITE, but sometimes it is a WRITE_DISCARD (when the buffer wraps around). Previously I have been using it so that the function expected the data upfront and would copy to the buffer between Map/Unmap, but now I want to extend functionality of it so that it would just return an address to write to.

• Trying to write a multitexturing shader in DirectX11 - 3 textures work fine, but adding 4th gets sampled as black!
Could you please look at the textureClass.cpp line 79? - I'm guess its D3D11_TEXTURE2D_DESC settings are wrong,
but no idea how to set it up right. I tried changing ArraySize from 1 to 4, but does nothing. If thats not the issue, please look
at the LightShader_ps - maybe doing something wrong there? Otherwise, no idea.
// Setup the description of the texture.
textureDesc.Height = height;
textureDesc.Width = width;
textureDesc.MipLevels = 0;
textureDesc.ArraySize = 1;
textureDesc.Format = DXGI_FORMAT_R8G8B8A8_UNORM;
textureDesc.SampleDesc.Count = 1;
textureDesc.SampleDesc.Quality = 0;
textureDesc.Usage = D3D11_USAGE_DEFAULT;