Thanks Unwinder, excellent work!

Added power user oriented profile setting, allowing you to customize framerate denominator for the built-in framerate limiter. The denominator can be customized to adjust the limit in fractional steps (e.g. denominator 10 to adjust the limit in 1/10 FPS steps)

http://i.imgur.com/y8s30Qx.gif :banana: Awesome! Will need to try that out ASAP. Being able to finally fine-tune the capper for 59.94Hz and 119.88Hz monitors is great news! Thank you!

http://i.imgur.com/y8s30Qx.gif :banana: Awesome! Will need to try that out ASAP. Being able to finally fine-tune the capper for 59.94Hz and 119.88Hz monitors is great news! Thank you!

could somebody explain me how to do this? I'm apparently too stupid to find it out myself 🙂

[Image] :banana: Awesome! Will need to try that out ASAP. Being able to finally fine-tune the capper for 59.94Hz and 119.88Hz monitors is great news! Thank you!

I'm no math person but I gave it a try, probably screwed it up but. -> [Framerate] Limit=60000 LimitDenominator=1001 In-game it now shows a 59.9(4) cap. (Tried lower values but couldn't get it to stick or limit 60 and denominator 0.9991 would have given a similar end result, but this works too.) (Instead that makes it a bit over 120 FPS.) EDIT: Heh knew something would be wrong, ah so it's in integers and not float so full values only then, good to know for future references. (Similar end results but a less extreme value heh well it's nice to learn new things.) (And yeah too focused on 59.94 specifically, 599 to 59.9 would have been a far simpler method, whoops.) (EDIT: Or as I also missed when reading the below reply 5994 to 59.94) (EDIT: I suppose looking it up properly instead of just treating it as a multiplication initially instead of a division would have also helped...again something to try to remember.)

fresh install on w7 (64bit) on program startup: https://snag.gy/hD5VvM.jpg dump analysis: http://pastebin.com/J8qsP0cP dump file: https://expirebox.com/download/4cf4360851739a4909acf3b0f87facb8.html back to 6.4.0 -> works any new prerequisite libraries since 6.5.x that are not included?

Windows 7? Could be related to the DirectX update as it's a bit lacking without it and other recent software also does not work unless installed. https://www.microsoft.com/en-gb/download/details.aspx?id=36805 Still not part of the default Windows Update fixes so it's either manual install or tool assisted via some "hotfix downloader" or whatever. (Meaning even if you do a manual scan and include more than the default security and critical updates and from a clean Win7 install it would find some 100+ updates and begin installing them this particular one - and a few others. - wouldn't be part of them even now some years later.) EDIT: Of course I could be entirely incorrect about this but if Unwinder in hooking into the D3D12 library made use of the newer Windows 10 SDK (Replacing the earlier stand-alone DirectX SDK.) would that not require the new instructions which would be lacking from Windows 7 without said compatibility update? (I'm probably making a mess of this explanation, in any case the update is completely removable too should that be required and if it doesn't solve a thing.)

Windows 7? Could be related to the DirectX update as it's a bit lacking without it and other recent software also does not work unless installed. https://www.microsoft.com/en-gb/download/details.aspx?id=36805 Still not part of the default Windows Update fixes so it's either manual install or tool assisted via some "hotfix downloader" or whatever. EDIT: Of course I could be entirely incorrect about this but if Unwinder in hooking into the D3D12 library made use of the newer Windows 10 SDK (Replacing the earlier stand-alone DirectX SDK.) would that not require the new instructions which would be lacking from Windows 7 without said compatibility update? (I'm probably making a mess of this explanation, in any case the update is completely removable too should that be required and if it doesn't solve a thing.)

hey jonas, thx for this hint! it's funny you show this because just last week i tried to install this KB for another reason. at least i tried to install it... to find out that i already have it in my WU installed list. but the question is still if any generic .dll that comes with DX12/WDDM2.X framework in W10 automatically (for example...) is required since v6.5.0 we'll see. or not. 🙂

Well at least we can exclude any missing DirectX functionality if that's already installed. 🙂 (The bundled VC++ runtime redist and DirectX redist should also be the only requirements.) EDIT: I did link to the right update I hope, well I think I did. EDIT: Yep that should have been the right one. - https://support.microsoft.com/en-gb/kb/2670838 (Various bits and pieces improving DirectX functionality for Windows 7 even if it does not provide full support for D3D11.1 which requires Windows 8 or later but it should be enough for newer DirectX dependent software to function correctly on Windows 7 systems.) EDIT: Far as other compatibility requirements go some recent software do use a bunch of .dll files for older OS's but I don't think that's related to this issue. (They're "api-ms-win-*.dll with * having a number of different features and files, about 40 all in all and used by e.g newer Firefox builds to name one software.) Nothing else I can suggest but I guess checking so the Visual C++ runtime installed correctly might also be useful, don't see why it would not and I am pretty sure the setup installer asks for elevated rights ("Run as admin") as required too so that shouldn't have been a problem. (But I am fairly certain VC++ has specific error messages for missing or mismatched runtime files instead of just crashing.)

Could you release updated Afterburner setup with the new RTSS please? For convenience purposes.

I'm no math person but I gave it a try, probably screwed it up but. -> [Framerate] Limit=60000 LimitDenominator=1001 In-game it now shows a 59.9(4) cap. (Tried lower values but couldn't get it to stick or limit 60 and denominator 0.9991 would have given a similar end result, but this works too.) (Instead that makes it a bit over 120 FPS.)

Denominator and limit are the integers, you cannot do what you tried. Much more correct way to define 59.9 would be setting limit to 599 and denominator to 10. 59.94 is the limit 5994 and denominator 100.

Thank you Unwinder and Hilbert ! Installing now .

Thank you Unwinder and Hilbert works fine with BF! now

Thank goodness for this... It was driving me nuts!

Wow!! New RTSS!

fresh install on w7 (64bit) on program startup: https://snag.gy/hD5VvM.jpg dump analysis: http://pastebin.com/J8qsP0cP dump file: https://expirebox.com/download/4cf4360851739a4909acf3b0f87facb8.html back to 6.4.0 -> works any new prerequisite libraries since 6.5.x that are not included?

Just installed W7 to verify that, works fine. Your exception code is 0xc06d007e, delay-loaded module not found error. All DirectX runtimes in AB are always delay loaded to allow launching application on older OSes with no modern DX support, so it can be one of DX runtimes only, and the only new delay-loaded module for 6.5.x is D3D12.dll. However, DX12 init is performed only when D3D12.dll is found in Windows system folder. So it looks like you manually copied that file from other OS to your Win7 system folder due to some reason. Is that the case?

Just installed W7 to verify that, works fine. Your exception code is 0xc06d007e, delay-loaded module not found error. All DirectX runtimes in AB are always delay loaded to allow launching application on older OSes with no modern DX support, so it can be one of DX runtimes only, and the only new delay-loaded module for 6.5.x is D3D12.dll. However, DX12 init is performed only when D3D12.dll is found in Windows system folder. So it looks like you manually copied that file from other OS to your Win7 system folder due to some reason. Is that the case?

Oh yes that analysis is exactly correct! I had the dx12 framework inside syswow64 & system32 ... let's say for a "project" 🙂 Thanks for the valuable hint and sorry for the effort you made! It starts up now.

Bug: I've put "LimitDenominator=100" in the global profile, but the GUI doesn't allow me to enter "11988". If I edit it in the file, the number is too big for the GUI box and the first digit is rendered outside the box. If I then try to change the value in the GUI again, I'm still limited to 4 digits. So it's impossible to set any cap higher than 99.99FPS :-/

That's not a bug, power user oriented denominator way was choosen exactly because of limitations of GUI and fixed 4-digit limit of edits in skin. Recreating whole skin just to allow to speciffy >100 fps limits in 0.01 fps steps directly from GUI doesn't worth the efforts.

It's pretty important to be able to do that though. Can't you at least disable the max digits check and allow us to edit the box, even if it overflows the UI?

You don't have to do everything via GUI and can bypass the limits via editing the profile directly. That's why the release notes classify the feature as power user oriented one. You may create a profile for any desired application and manually define custom limit/denominator there.