Game running in fullscreen is treated as a tabbed out game, performance wise.
Numbered Steps to Reproduce Problem:
I made a new source, added fullscreen support and then experienced serious framerate changes. When I went back to the old non-fullscreen source, it played as usual.
I then removed the lines of code from the new source and the game went back to playing as usual.
Code Snippet (if applicable) to Reproduce Problem:
winset(src,"default","is-maximized=true")
winset(src,"default","Titlebar=false")
winset(src,"default","Title=false")
winset(src,"default","menu=false")
winset(src,"default","can-resize=false")
Expected Results:
For performance to run as usual.
Actual Results:
I believe the game was treated as if it were tabbed out. I had this happen before, like if a skype message appeared my framerate would drop drastically and then pop back up when either the message bubble left or if I clicked my client.
Basically any notification that pops up over dream seeker results in severe drops in fps until I either click dream seeker or the notification goes away. Although in this forced maximized view, the fps is constitently poor.
Does the problem occur:
Every time? Or how often?
Every time.
In other games?
I don't think so.
In other user accounts?
N/A
On other computers?
No other computers to test.
When does the problem NOT occur?
When I remove the fullscreen code.
Workarounds:
Maximizing my window manually.