• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Hassanbasil

DX11
failed to create device with feature level 11

10 posts in this topic

Hello,

I've bought a new laptop with an nVidia Geforce GT540M card, which supports DX11, for some reason i can't seem to be able to create a device with feature level 11.0, i looked at the device caps and feature level 11 is listed there, i have the nVidia latest driver, though, there's a problem that the dxdiag (dx diagnostic tool) dialog shows info about intel HD graphics - so i'm somewhat confused, in the system tab it shows "DirectX Version: DirectX 11", but the Display tab shows the intel driver information.

is the problem from the hardware side or my code? here's how i create my device:
[code] D3D_FEATURE_LEVEL level;
D3D_FEATURE_LEVEL desiredLevels[1] = { D3D_FEATURE_LEVEL_11_0 };
HX_PRINTERR_HR ( D3D11CreateDevice ( __Impl__->DXGIPrimaryAdapter, D3D_DRIVER_TYPE_UNKNOWN, NULL, __Impl__->registerDesc->deviceLayers,
desiredLevels, 1, D3D11_SDK_VERSION, &__Impl__->D3DDevice, &level, &__Impl__->D3DDeviceContext ), HX_UNABLETOCREATEDEVICE );[/code]

this fails with no errors from the debug layer, also, if i leave the feature levels to NULL, it works but the returned "level" is 10.1, what is the problem?

Thanks for your time.
0

Share this post


Link to post
Share on other sites
The problem is, that your program starts with the default graphics chip, which is the integrated intel one.
Heard about nVidia optimus?

Simply start your application from the dedicated nVidia card, or go into the nVidia control panel and add your exe to the high performance profile, so your program always starts with the nvidia card.

Maybe there is also a way to explicitly force the nvidia card (nvidia extension/SDK or so?)
0

Share this post


Link to post
Share on other sites
Enumerate the available DXGI adapters. One of these will correspond to the intel card, and another will correspond to the nvidia card. You can probably work out which is which by checking the amount of dedicated video memory each card has (use IDXGIAdapter::GetDesc())
1

Share this post


Link to post
Share on other sites
[quote name='hupsilardee' timestamp='1328318386' post='4909392']
Enumerate the available DXGI adapters. One of these will correspond to the intel card, and another will correspond to the nvidia card. You can probably work out which is which by checking the amount of dedicated video memory each card has (use IDXGIAdapter::GetDesc())[/quote]

There's only one adapter enumerated, which is unfortunately, the intel HD graphics

[quote name='Vertex333' timestamp='1328312769' post='4909371']
The problem is, that your program starts with the default graphics chip, which is the integrated intel one.
Heard about nVidia optimus?

Simply start your application from the dedicated nVidia card, or go into the nVidia control panel and add your exe to the high performance profile, so your program always starts with the nvidia card.

Maybe there is also a way to explicitly force the nvidia card (nvidia extension/SDK or so?)
[/quote]

yeah looks like i can explicitly choose which programs are forced to use the nVidia GPU through the panel, kinda annoying but guess i'll have to live with it

thanks for the replies
EDIT: though, using Visual Studio's Debug/Release runs cannot be explicitly ran with the nVidia graphics, is it possible to run applications with nVidia graphics forced from within VS?
0

Share this post


Link to post
Share on other sites
[quote name='iedoc' timestamp='1328337812' post='4909445']
change your battery mode to high performance
[/quote]

It is on high performance already
0

Share this post


Link to post
Share on other sites
ok i just mentioned that because sometimes if a laptop is not plugged in or on high performance, it will use the integrated graphics card instead of the more powerful one
0

Share this post


Link to post
Share on other sites
try checking out this topic

[url="http://www.gamedev.net/topic/617965-directx-11-cant-find-all-of-my-graphics-adapters/"]http://www.gamedev.net/topic/617965-directx-11-cant-find-all-of-my-graphics-adapters/[/url]
0

Share this post


Link to post
Share on other sites
thank you for the link, i figured out all the points he concluded there, though, after using IDXGIFactory1, now it enumerates both adapters, but only the intel HD adapter has available outputs, the caps viewer is looking weird also..here's a screenshot (second NVIDIA card is selected below)
[img]http://img196.imageshack.us/img196/7449/captureomw.jpg[/img]
both cards has the same names there, but clicking them shows this: first one: description says intel HD graphics, dsecond one: description says nVidia geforce 540M
but the second one, which is supposed to be the good GPU, has only "outputs" listed under it and it cannot be expanded, meaning there are no outputs, which is the problem, now another thing is, the first one, which is described as intel HD graphics, has DirectX11 listed in it, and it supports feature level 11, so im a little bit confused
0

Share this post


Link to post
Share on other sites
ok, It sounds like you know what your looking for, but i'll just explain it in detail juuust in case. So when you first open up the caps view, on the left side, under the DXGI 1.1 devices, you should see 3 folders, one is for your nvidia graphics card, another for your integrated gpu, and the third is the reference device. of course the one you are interested in is the nvidia graphics card, so expand that folder. Under it, you should see at least 4 folders, first being outputs, second Direct3D 10.0, third Direct3D 10.1, and last being Direct3D 11. and of course we are interested in D3D 11, so expand that folder. the first folder you see under that is the HIGHEST feature level. Whatever this folder says is the highest feature level your graphics card handles. On my laptop right now, it says D3D_FEATURE_LEVEL_10_0 (my card doesn't support feature level 11). If your card says D3D_FEATURE_LEVEL_11_0, then that's good.

I know you already did all this, just was being thorough, i'm not saying all that because i think you don't know what your doing. but to me, it sounds like you need to reinstall the CORRECT driver for your card. theres a lot of different drivers, and if you install the wrong one, things can happen. I always think it's a pain installing the correct one because of all the drivers that have almost identical names, not to mention you need to make sure you install the right one depending on the version of windows you are using, like windows 7 64 bit for example.

That's probably a lot of stuff that's useless to you, so sorry. but my recommendation is to reinstall your nvidia driver, because at least for me, your explanation for what you see in the caps view sounds wrong, and that's more likely a problem with your drivers. I could be totally wrong about that, but i'm trying ;)
0

Share this post


Link to post
Share on other sites
Thanks for the reply i actually installed the correct driver and it did nothing, then after it, i installed an even newer beta driver and it also didn't work, the thing is, the caps seem somewhat confusing because the actual card's entry is empty, but the intel chip is not, although it has the same specs as the nVidia chip, which is somewhat weird, the intel GPU's specs SHOULD be able to run dx11 as it's listed there (see screenshot above), but it just doesn't work
one more final note for anyone willing to help: running my debug/release applications from the folder itself works fine, and it runs with nVidia GPU, but running it from visual studio or PIX won't work, and that's the whole thing
0

Share this post


Link to post
Share on other sites

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  
Followers 0

  • Similar Content

    • By bowerbirdcn
      hi, guys, how to understand the math used in CDXUTDirectionWidget ::UpdateLightDir 
      the  following code snippet is taken from MS DXTU source code
       
        D3DXMATRIX mInvView;
          D3DXMatrixInverse( &mInvView, NULL, &m_mView );
          mInvView._41 = mInvView._42 = mInvView._43 = 0;
          D3DXMATRIX mLastRotInv;
          D3DXMatrixInverse( &mLastRotInv, NULL, &m_mRotSnapshot );
          D3DXMATRIX mRot = *m_ArcBall.GetRotationMatrix();
          m_mRotSnapshot = mRot;
          // Accumulate the delta of the arcball's rotation in view space.
          // Note that per-frame delta rotations could be problematic over long periods of time.
          m_mRot *= m_mView * mLastRotInv * mRot * mInvView;
          // Since we're accumulating delta rotations, we need to orthonormalize 
          // the matrix to prevent eventual matrix skew
          D3DXVECTOR3* pXBasis = ( D3DXVECTOR3* )&m_mRot._11;
          D3DXVECTOR3* pYBasis = ( D3DXVECTOR3* )&m_mRot._21;
          D3DXVECTOR3* pZBasis = ( D3DXVECTOR3* )&m_mRot._31;
          D3DXVec3Normalize( pXBasis, pXBasis );
          D3DXVec3Cross( pYBasis, pZBasis, pXBasis );
          D3DXVec3Normalize( pYBasis, pYBasis );
          D3DXVec3Cross( pZBasis, pXBasis, pYBasis );
       
       
      https://github.com/Microsoft/DXUT/blob/master/Optional/DXUTcamera.cpp
    • By YixunLiu
      Hi,
      I have a surface mesh and I want to use a cone to cut a hole on the surface mesh.
      Anybody know a fast method to calculate the intersected boundary of these two geometries?
       
      Thanks.
       
      YL
       
    • By hiya83
      Hi, I tried searching for this but either I failed or couldn't find anything. I know there's D11/D12 interop and there are extensions for GL/D11 (though not very efficient). I was wondering if there's any Vulkan/D11 or Vulkan/D12 interop?
      Thanks!
    • By lonewolff
      Hi Guys,
      I am just wondering if it is possible to acquire the address of the backbuffer if an API (based on DX11) only exposes the 'device' and 'context' pointers?
      Any advice would be greatly appreciated
    • By MarcusAseth
      bool InitDirect3D::Init() { if (!D3DApp::Init()) { return false; } //Additional Initialization //Disable Alt+Enter Fullscreen Toggle shortkey IDXGIFactory* factory; CreateDXGIFactory(__uuidof(IDXGIFactory), reinterpret_cast<void**>(&factory)); factory->MakeWindowAssociation(mhWindow, DXGI_MWA_NO_WINDOW_CHANGES); factory->Release(); return true; }  
      As stated on the title and displayed on the code above, regardless of it Alt+Enter still takes effect...
      I recall something from the book during the swapChain creation, where in order to create it one has to use the same factory used to create the ID3D11Device, therefore I tested and indeed using that same factory indeed it work.
      How is that one particular factory related to my window and how come the MakeWindowAssociation won't take effect with a newly created factory?
      Also what's even the point of being able to create this Factories if they won't work,?(except from that one associated with the ID3D11Device) 
  • Popular Now