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

D3D11 WARNING: ID3D10Device::CopyResource

8 posts in this topic

HI

 

D3D11 WARNING: ID3D10Device::CopyResource: This ID3D10Device[1] method of the immediate context is locked out because an ID3D11Device[1] device context state is active. [ STATE_SETTING WARNING #3145945: DEVICE_LOCKEDOUT_INTERFACE]
 

Have you ever seen before this warning message in output window ?

What the hell....?!

In My All source there is no CopyResource
I Don't know where to find that error message.

Is that no big trouble ?
That warning comes out my program slower.
I guess that warning is big problem !!!

How can I fix that warning ?

Thanks in advance. smile.png
 

 

Edited by AquaMacker
0

Share this post


Link to post
Share on other sites

Please don't pass indifferencely.
 

I use multithread. Is related to that warnning ?

Come on Guy !!!

0

Share this post


Link to post
Share on other sites

Somehow you are calling a D3D10 Device method.  Behind the COM interface is an object that may or may not implement multiple of the device interfaces, so it isn't alarming to see this type of message.  My guess is that you have accidentally acquired a D3D10 device when you meant to get an 11 device.

 

Can you show the code where you create your device, and the declaration of the device COM pointer that is causing this warning message to come up?

1

Share this post


Link to post
Share on other sites

In the directx-control panel, in the Direct3D 10.x/11-tab, go to "Break Settings" an "Enable break on functionality", also tick "warning". Now you should see at least the line where this warning is issued, unless you got any other warnings that are issued before that.

 

EDIT: You also need to add your application to the list in "Edit list" on that page.

Edited by Juliean
2

Share this post


Link to post
Share on other sites

Thanks I found !!!

hr = 
D3DX10CreateMesh( pDevice, stVertex::pInputElementDesc, stVertex::nNumElements,
stVertex::pInputElementDesc[0].SemanticName,
36, 12,
D3DX10_MESH_32_BIT,
&pMesh );

pMesh->SetVertexData( 0, vertices );
pMesh->SetIndexData( indices, nIndexCount );

pMesh->GenerateAdjacencyAndPointReps( 0.001f );
pMesh->Optimize( D3DX10_MESHOPT_ATTR_SORT | D3DX10_MESHOPT_VERTEX_CACHE, 0, 0 );
pMesh->CommitToDevice() !!! <- that warning point 

This part is so simple box making source. so simple so simple.
Vertex number 36, index number is 12.
Vertex values is wrong ? hr is S_OK.

I don't understand.


I use ID3D10Device1* pDevice. Is related ?

Edited by AquaMacker
0

Share this post


Link to post
Share on other sites


D3DX10CreateMesh

 

This is DirectX10 functionality, so thats at least why the DX10-function in the warning is called. I don't think this function still works for DX11, from what I know DX11 doesn't have a default mesh class, you have to write yourself one and do the vertex buffer loading manually, or use e.g. DXUT-mesh or something like that.

1

Share this post


Link to post
Share on other sites

Thank you very much, Juliean.

But my english is so bad.

I use DX10.1 (
ID3D10Device1) not DX11.

Am I change Device to 
ID3D10Device ?

and that source is I loading VB manually.

I'm sorry for my bad english...

0

Share this post


Link to post
Share on other sites

[size=3]Thank you very much, Juliean.

I use DX10.1 (
[/size][background=#fafbfc]ID3D10Device1) not DX11.

Am I change Device to [/size][/background]

[background=#fafbfc]ID3D10Device ?[/size][/background]

Use D3D10CreateDeviceAndSwapChain1 which creates an ID3D10Device1

Though there is absolutely no good reason to use DirectX 10. The only OS that supports 10 but not 11 is early un-patched Vista. You can use Direct3D11 on older hardware by setting a feature level, so you can ask Direct3D11 to limit itself to features supported by D3D9, D3D10, or D3D10.1 features. When doing so, you are still using the Direct3D11 API and cannot mix in old Direct3D10 code.
1

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