Screen goes saving mode during games if not touching mouse/keyboard

[fugazi84]

Hi all,

I'm scratching my head to find the problem.

So I have quiet 'low' screen timeout ( 1 minute ) - whenever I play games and for some time I won't touch mouse/keyboard - for example intro/cut-scene etc. my screen will turn-off after 1 minute.
When I move mouse or press keyboard - screen wake-up and things are normal.
Now I wonder if this is actually normal for Windows 10 to enable screen timeout in games?
For example watching movies won't cause this - just in games :|

Now here is my bigger problem - I have joystick connected to play DCS - for some reason Thrustmaster 1600M is not detected by Windows properly as gamepad device and I see it only in HID menu in device manager - from that field I can't change it power management settings and for example make my joystick to wake-up windows.
So whenever I play DCS and playing on joystick my screen go out after 1 minute and I need to press keyboard/mouse to wake-it up

So my query is - is this normal that Windows 10 enable screen timeout in games - for example watching cut-scenes cause this as I don't press mouse/keyboard.

So I wondering what is wrong - is there a way to tell windows 10 to not enable screen power saving mode during games? or am I missing some setting?

Please note I want to keep 1 minute screen timeout value so my screen will go to sleep after 1 minute of inactivity.

If I increase my screen timeout it will sort out games cut-scenes etc. but will leave me with problem during DCS gameplay and Thrustmaster 1600M - should I look to fix my Thrustmaster driver somehow?

Any hint/advice is welcome.

 

[fugazi84]

Found some cheap workaround of creating simple batch script which turns screen timeout to 0 and run game, after game quits it re-enable screen timeout to 1 minute again.

Here it is:

powercfg -Change -monitor-timeout-ac 0
cd /d "F:\Program Files\Eagle Dynamics\DCS World\bin"
start /W DCS.exe
start powercfg -Change -monitor-timeout-ac 1

Maybe someone will need it as well.
Note there is a catch - if your original .exe spawn new process or new .exe file - then above won't work - so make sure your .exe does not spawn another one.
In DCS example - exe used for launcher is either Run.exe or Updater.exe - which won't work as later on DCS will run new process which execute (Install_dir)\bin\DCS.exe