- May 6, 2019
- 48
- 122
This one is weird, and when I searched around, the only relevant comment I found was my own comment from a while ago when I had this problem with a different game. That game was Leap of Faith
Today I tried both Betrayed and Milfy City and had the same problem. I haven't had the problem with other games in the past. I think something on my system has changed, because it seems to be happening with other renpy games I had already downloaded. I don't remember having this problem between playing Leap of Faith and today.
---------------------------------------------------------
The problem is that when I set a game to fullscreen in the preferences, it causes some instances where the monitor will detect no signal and turn off. It usually doesn't happen on the menu screen, itself, but once I'm in the game, looking at a static screen. I can watch my FPS counter in the corner tick down to 5. That makes sense. The engine doesn't have to draw new frames for a static screen, so the FPS counter only bounces back up when I click something to change the game state.
So intuitively, it seems like the game is rendering so few frames that it stops sending any frame changes at all to the monitor. The monitor detects no signal and turns off. Then it has to boot back up for a second as soon as it detects a signal again because the game decided to finally draw a new frame.
--------------------------------------------------------
I'm using a GTX 1070 and a 144hz monitor with GSync. Probably unrelated, but I also had
Of course, windowed mode works perfectly fine. As long as the screen is being updated, by another window, or by the game itself, the monitor continues reading a signal.
Today I tried both Betrayed and Milfy City and had the same problem. I haven't had the problem with other games in the past. I think something on my system has changed, because it seems to be happening with other renpy games I had already downloaded. I don't remember having this problem between playing Leap of Faith and today.
---------------------------------------------------------
The problem is that when I set a game to fullscreen in the preferences, it causes some instances where the monitor will detect no signal and turn off. It usually doesn't happen on the menu screen, itself, but once I'm in the game, looking at a static screen. I can watch my FPS counter in the corner tick down to 5. That makes sense. The engine doesn't have to draw new frames for a static screen, so the FPS counter only bounces back up when I click something to change the game state.
So intuitively, it seems like the game is rendering so few frames that it stops sending any frame changes at all to the monitor. The monitor detects no signal and turns off. Then it has to boot back up for a second as soon as it detects a signal again because the game decided to finally draw a new frame.
--------------------------------------------------------
I'm using a GTX 1070 and a 144hz monitor with GSync. Probably unrelated, but I also had
You must be registered to see the links
at the top which was solved by turning on threaded optimization. No change to the fullscreen issue though.Of course, windowed mode works perfectly fine. As long as the screen is being updated, by another window, or by the game itself, the monitor continues reading a signal.