Reply to thread

Message: <blockquote data-quote="Scythe42" data-source="post: 562495" data-attributes="member: 95833">This is a driver problem. If the correct way 24000/1001 for 23.976 is not supported - SDC_VALIDATE tests this - the code adds a SDC_ALLOW_CHANGES, which instructs the driver to pick the closest one on its own. The 23970/1000 is very common at the recent versions of Nvidia drivers, even though they use 23974. They changed it at some point and introduced a ton of more bugs (probably a developer changed, who has no clue about correct refresh rate notations). A few bugs were removed in newer versions but the 24000/1001 and the 60000/1001 bug still remains. I already prepared a bug report for Nvidia (not submitted yet). So far I have not included additional testing for these bugs, awaiting new driver versions. If they don't show up before 1.1.0 final date is close, I'll add more complex testing, e.g. first 24000/1001, 23976/1000, 23000/1000, 23/1 to cover for driver bugs. But for this I need more feedback from RC1 users what different combinations show up in the logs if people having problems with the latest working driver at that time.People should only have problems when SDC_ALLOW_CHANGES does not work properly on the driver. Selecting 24Hz should be no problem as 24000/1000 is supported on all drivers I know of. Only 23.976 and 59.994 seem to be the problematic one. I don't have ATI to test and need some ATI test results. If you can supply me with these that would be great! I really need user support here. I also have a binary for testing outside of MP for users with problems who can then test.As said I wait for feedback of RC1 before adding various try and errors for each refresh rate in hope the notation is fixed within the driver without having to rely on SDC_ALLOW_CHANGES. For Nvidia SDC_ALLOW_CHANGES works great here with all refresh rates since the last driver version. They fixed a bug where 24Hz was complete unselectable among others.So I am aware of this, and it's on my todo list. It will make the code a little bit more ugly as it iterates through the various combinations (the case statement will be replaced by some ugly if-then-else with loops inside). But it will be done before 1.1.0 if SDC_ALLOW_CHANGES creates problems with recent ATI or Nvidia drivers after RC1 is released.If you have the capability of testing ATI and Nvidia across various driver versions and cards, we can work together here putting together a list of "driver notations" for 1.1.0 final.And again thanks for working of the stuttering problem. I'm really looking forward to your patch...<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin    :D" loading="lazy" data-shortname=":D" />PS: that 24000/1000 is failing for you, is very strange. What card and driver version are you using?</blockquote>

Verification