It's whatever is supported by your monitor and it's your monitor / GPU reporting these timings to the OS. Thing is, as you can see above for timing, some modes are 60/1 24/1 and some are 60000/100/1001 which is where the 59.94 decimal comes from.ĥ9.94 is 60hz. And there were common standardised vesa modes - which is why if you remove your graphics drivers you end up with windows booting at 800 x 600 or something like that. Presumably this stuff was in inf files for windows. These days the monitor reports what modes it supports, years ago you used to have to give it modelines in linux with all the timing information on. You can see some of the entries that have more than one might say 'CENTERED PROGRESSIVE' - presumably if you delve into the directx api you'll see the calls kunos are using to get this list of modes.īasically the game is using dxgi to get a list of modes - and these modes are combination of what your GPU and monitor support. Mode 123 1920 1080 59 UNSPECIFIED PROGRESSIVE Mode 122 1920 1080 23 UNSPECIFIED PROGRESSIVE Mode 121 1920 1080 60 UNSPECIFIED PROGRESSIVEĭISPLAY MODE FOUND <- this is the one I'm using

Mode 120 1920 1080 50 UNSPECIFIED PROGRESSIVE Mode 119 1920 1080 24 UNSPECIFIED PROGRESSIVE The top of log.txt you'll see the list of modes it gets, like this :. If you look in your documents folder for assetto corsa and in there there's a logs folder. When games say '60hz' they actually always mean 59.94hz.īut why some option appears two/three times?īecause they are modes with different attributes on them (attributes which that list doesn't show) Originally posted by Paul:The problem is most likely with your recording software.

Windows 7 1920x1080 resolution missing