Jump to content

View more

Image of the Day

Working on an auto spawn system. #gamedev #indiedev #screenshotsaturday https://t.co/Mm2kfekz7b
IOTD | Top Screenshots

The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.


Sign up now

SetFullScreenState

4: Adsense

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
2 replies to this topic

#1 BornToCode   Members   

1185
Like
0Likes
Like

Posted 24 February 2014 - 10:42 AM

I have multiple outputs. When i go to fullscreen, DXGI seems to black out all of my other ouputs. This is a problem because i have a menu on the other outputs and they just become invisible. I try creating the menu before going to fullscreen and after. It makes no difference. As anyone ran into similar issues with DXGI and what was your solution. It only happens when you go fullscreen, and it is a requirement for the software i am working on.



#2 Erik Rufelt   Members   

5901
Like
0Likes
Like

Posted 24 February 2014 - 10:56 AM

Try using MakeWindowAssociation to set one window as the one DXGI checks for state changes. I assume you mean that you have multiple monitors and want to go to fullscreen on all of them simultaneously?



#3 BornToCode   Members   

1185
Like
0Likes
Like

Posted 28 February 2014 - 12:34 AM

Try using MakeWindowAssociation to set one window as the one DXGI checks for state changes. I assume you mean that you have multiple monitors and want to go to fullscreen on all of them simultaneously?

That was not my question. I can already go fullscreen in all of them. The problem is that when i go fullscreen on 3 out 4 monitor the 4 monitor goes black as well even though i am not going fullscreen in that IDXGIOuput. It then occluded anything i had on that window, until i go back to window mode. I did a test in windows 8 and it works, so i guess it is a win7 bug.






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.