Jump to content

  • Log In with Google      Sign In   
  • Create Account


(solved) Present possible? loader texts d3d


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
1 reply to this topic

#1 cozzie   Members   -  Reputation: 1445

Like
0Likes
Like

Posted 23 December 2012 - 08:34 AM

Hi, I'm trying to show some initialization texts while starting my d3d engine, loadings meshes, shaders etc.. When I run in windowed mode, my drawtext (LP3DXFONT) all works fine and the result is visiblhe through "present" calls. However when I do the same fullscreen, I get either: - no texts shown - and/or D3D debug errors saying assertion failed with bPresentSubmitted (probably because I'm trying to present something while not ready yet). It looks like initizing fullscreen (device) takes longer then windowed, causing this to happen. I tried to add a check for TestCooperativeLevel before 'printing' and presenting the load texts, this didn't help. What I know is that adding a sleep(100) somehere in the startup, solves the problem. But that's the cheap way I guess. Do you have experience with this/ and or do you know if there's a d3d function to check if calling dev->present will bring something on screen? (testcooperativelevel seems to give D3D_OK anyway, even when the screen ísn't presenting anything/ able to present) It by the way also happens when I load my meshes into d3dpool_managed instead of systemmem. Found it that adding a Sleep(20) in my render function, right before present, also solved it here. Probably missing something as check before 'presenting' the BackBuffer. Any help would be appreciated, it might be quite simple but for now very annoying...


Edited by cozzie, 25 December 2012 - 11:02 AM.


Sponsor:

#2 cozzie   Members   -  Reputation: 1445

Like
0Likes
Like

Posted 25 December 2012 - 11:02 AM

Most likely found it, i'm passing through the d3d device as * (pointer) in several functions, which is basically a pointer to a pointer.

This would explain why using systemmemory pool is working OK and GPU ram isn't.

Will try it out.






Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS