1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RTSS 6.7.0 beta 1

Discussion in 'MSI AfterBurner Overclock Application Discussion' started by Unwinder, Feb 20, 2017.

  1. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Upgrade to b2, it doesn't change anything for your specific issue (Wolf2), but it is newer than initial 7.2.1 you've got.
     
    HARDRESET likes this.
  2. HARDRESET

    HARDRESET Master Guru

    Messages:
    399
    Likes Received:
    151
    GPU:
    1080Ti G1 GAMING OC
    all set ! Thanks
     
  3. gran172

    gran172 Member

    Messages:
    23
    Likes Received:
    5
    GPU:
    Asus Strix 2060 6Gb
    This may sound dumb, but after installing RTSS 7.2.1 B2 my fonts seem smaller, any clues?
     
  4. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Refer to release notes:

    - Improved On-Screen Display hypertext formatting implementation. Variable slot 250 is no longer used to define own statistics format, now it is allowing On-Screen Display client applications to redefine default text format. Such implementation allows the client applications like MSI Afterburner to edit default text color directly inside On-Screen Display layout editor

    Font size variable slot 250 was used to define smaller font for own status only, now it is allowing to alter default font size and color. Alter it in the layout editor.
     
    toyo, The1 and Vulkan like this.

  5. gran172

    gran172 Member

    Messages:
    23
    Likes Received:
    5
    GPU:
    Asus Strix 2060 6Gb
    So all I should do is change the variable slot 250 from 80% superscript to 100% superscript? Sorry for the dumb question, thanks a lot for taking the time to answer, love both Afterburner and RTSS, keep up the good work! :)
     
    Vulkan likes this.
  6. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Yep. Or just delete it from layout.
     
  7. dsbig

    dsbig Ancient Guru

    Messages:
    4,003
    Likes Received:
    27
    GPU:
    EVGA RTX 2070
    link doesnt work for me....
     
  8. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    works for me
     
    HARDRESET likes this.
  9. ErikSwan

    ErikSwan Member

    Messages:
    11
    Likes Received:
    3
    GPU:
    GTX 1080 Ti
    Hi @Unwinder,
    What do you think about adding a feature to update the V/F frequency curve in (close to) real-time outside of the OC scanner mode (as long as the V/F curve editor window is open)? Then it would be possible to see when GPU Boost 3.0 changes the base curve due to thermal changes, etc. without having to click Apply to get the curve to update.

    I think it would help reduce user misunderstanding like the following post, because I was also seeing the V/F curve jump around when clicking Apply and I thought it was a bug in Afterburner before I did some research and read through this thread to understand that it is just how the underlying NVAPI/GPU Boost 3.0 works, and what was really happening was the base curve had changed since the last time I had clicked Apply and the V/F curve was read out.

    For example, in your video example here, at 0:37 when you hit apply, the V/F curve changes. It makes it seem like increasing the core voltage slider made the V/F curve change, but in reality, the base curve changed some time ago due to the increasing temperature, but it doesn't become visible until hitting apply.



    I think it would be nice to be able to see when the GPU changes the base V/F curve in (close to) real-time when running a bunchmark. Like I said I feel like this would make it much more obvious to users what is actually happening.

    Thank you for the work you do on Afterburner and RTSS.
     
    Last edited: Dec 5, 2018
    cookieboyeli likes this.
  10. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Automating V/F curve editor window refresh is a bad idea, it will make curve adjustment really troublesome if you try to adjust some V/F point offset and base curve is auto-altered when you're dragging the point. However, adding base curve refresh via some keyboard shortcut (e.g. F5) can be useful.
     
    cookieboyeli and The1 like this.

  11. ErikSwan

    ErikSwan Member

    Messages:
    11
    Likes Received:
    3
    GPU:
    GTX 1080 Ti
    Yeah, you are right that it could be very annoying if it updates when you are trying to edit the curve. I think a keyboard shortcut would be a good solution. Thanks!

    Also, I noticed some weird behavior in the V/F curve display when updating the curve even when the temperature is stable, so base curve should not be changing. I'm guessing the NVAPI is enforcing some limit on the maximum frequency delta between consecutive voltage points? But the thing that seems wrong to me is that instead of enforcing this in the offset values, the "base curve" which is drawn (dark gray line) also changes and is very weird looking. Is this a bug in AB or a limitation of the NVAPI?

    If you would like I can make a separate thread about this. I used an extreme example here to make it noticeable but I've had this type of behavior happen even when making smaller offsets. I think this behavior is another factor that sometimes makes the V/F curve editor feel "buggy".

     
    Vulkan and cookieboyeli like this.
  12. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Almost correct, NVAPI is correcting specified offsets to make final curve monotonically increasing and apply smoothing if necessary.
    Also, you're misunderstanding "base curve" (dark grey line). It is not a real offsetless base curve, which is not readable via NVAPI, it is final curve with offsets subtracted from each point. It is not intended for anything but seeing the points where the offsets are applied.
     
    Last edited: Dec 5, 2018
    ErikSwan likes this.
  13. ErikSwan

    ErikSwan Member

    Messages:
    11
    Likes Received:
    3
    GPU:
    GTX 1080 Ti
    Thanks for the explanation, that makes sense. So the conclusion is that all of the weird behavior is on NVAPI's side. I wish the API was more transparent about how GPU Boost 3.0 is working internally, but I guess we can only work with what we've got.

    Thanks!
     
  14. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Small update for this BattlEye related info:

    When commenting this issue in different forum, I found that I seem to forgot to implement kernel mode hardware access interface codepath for Vega GPUs in MSI AB:) So enabling it on such platform will cause bogus readings of HMB temperature, GPU power and GPU voltage. So for Vegas low-level hardware access interface should be disabled instead of switching it to kernel mode in MSI AB properties to bypass BattlEye problem. Extended hardware monitoring (HBM temp, GPU power and voltages) and voltage control will be disabled in this case. I'll add support for kernel mode hardware access interface on Vegas in the next beta.
     
  15. Tomatone

    Tomatone Member Guru

    Messages:
    133
    Likes Received:
    31
    GPU:
    Nitro+ 580 8GB
    Thanks Aleksej.
     

  16. Alberto

    Alberto Master Guru

    Messages:
    259
    Likes Received:
    64
    GPU:
    2080 Ti Lightning Z
    @Unwinder good morning, We are almost at the end of 2018, when will be available the final version of Afterburner?
    Grazie
     
  17. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    When it is done. Stop that please.
     
  18. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    Guys,

    NVIDIA recently rolled out new version of their NVIDIA Scanner API and wanted to see updated MSI AB with it ASAP, so here it is. Please take a note that I was working on different features in parallel and some of them are still in development, so treat it this build as a development beta. From NVIDIA scanner API side there are many improvements in scanning algorithm, Pascal series support and many more. From my side I added a button for launching scanner directly from main window GUI (OC button in the top left corner of application), but experienced users can still launch it from VF curve editor window like before. VF curve editor window got some improvements as well, and it is now available on AMD GPUs. And as usual there are dozens of other GUI and monitoring module usability related changes and improvements. Full changes list for MSI AB v4.6.0 and RTSS v7.2.1 includes the following (changes from the previous betas are highlighted with bold):

    MSI AB v4.6.0 beta 10

    · Added NVIDIA Turing GPU architecture support:
    o Added voltage control for reference design NVIDIA GeForce RTX 20x0 series graphics cards
    o Advanced GPU Boost control for NVIDIA GeForce RTX 20x0 series graphics cards. Extended voltage/frequency curve editor on GeForce RTX 20x0 family graphics cards allows you to tune additional piecewise power/frequency floor and temperature/frequency floor curves. Control points on those new curves allow you to control GPU Boost power and thermal throttling algorithms more precisely than traditional power limit and thermal limit sliders
    o Hardware abstraction layer has been revamped to provide support for multiple independent fans per GPU due to introducing dual fan design on reference design NVIDIA GeForce RTX 20x0 series graphics cards and due to introducing native dual fan control in NVAPI. Both fans of NVIDIA GeForce RTX 20x0 can be monitored independently in hardware monitoring module now and can be controlled synchronically in manual mode
    o Added NVIDIA Scanner technology support
    · Added Monolithic Power Systems MP2884A and MP2888A voltage controllers support
    · Added core, memory, auxiliary PEXVDD and auxiliary 1V8 voltage control for custom design MSI RTX 2080Ti Lightning series graphics cards with MP2888A + MP2888A +uP1816 voltage regulators
    · Added VRM and VRM2 temperature monitoring for custom design MSI RTX 2080Ti Lightning series graphics cards

    · Improved hardware monitoring module:
    o Added thermal offset for CPU temperature monitoring on AMD Ryzen 7 2700X processors
    o Similar CPU temperatures are now cloned for all cores on AMD CPUs to provide more convenient and unified On-Screen Display layout between Intel and AMD CPUs
    o “Pagefile usage” graph in hardware monitoring module has been renamed to “Commit charge”
    o Added group operation notifier to the caption of active hardware monitoring graphs list in “Monitoring” tab in the application properties. The notifier is informing you that you can apply a setting to all or to multiple selected hardware monitoring graphs when you hold group operation key (i.e. <crap> or <Ctrl>) and hover mouse cursor over the setting that can be applied to multiple hardware monitoring graphs at once (e.g. “Show in On-Screen Display”)
    o Added “Select by group” and “Select by type” commands to context menu of active hardware monitoring graphs list in “Monitoring” tab in the application properties. New commands allow selecting the graphs of exactly the same type (e.g. CPU1-CPU8 usage graphs on eight core CPU) or the graphs with the same OSD/LCD group name (for example, GPU clock, GPU power, GPU usage and the rest graphs with “GPU” group name). Such commands allow you to show similar items (e.g. all CPU usages) in On-Screen Display with a single click or rename a group for all child graphs in the single pass
    o Multi group edit mode is automatically selected now for group name edit field when you enable "Override group name" option while holding <Ctrl> key. You may still manually toggle this mode with <Ctrl>+<M> hotkey anytime when editing the group name
    o On-Screen Display item type (i.e. text, graph or combination of both) is now displayed in “Properties” column of active hardware monitoring graphs list in “Monitoring” tab in the application properties
    o Added programmable hotkey for clearing monitoring history
    o Added “Apply” button to application properties window. Now you may iteratively customize monitoring module without closing the properties to see the result on each step. Please take a note that some properties (e.g. application language) cannot be applied until you completely close properties window by design of application
    o Improved On-Screen Display layout editor:
    § System reserved variable slots 250-255 are now displayed as system variables in the layout editor
    § Added embedded graphs support. Embedded graphs can be displayed directly in the text in a separate column, it can be convenient for displaying per-core CPU usages
    § Added embedded graph width adjustment variable to the “Graph” property node
    § Added new “Graph placement” property node. You can use it to place each graph on top of text, on bottom or make it embedded in in text column
    § Added new variables to “Separators” property node. Now you may define independent separators for the graphs located on top of text part, for the text part and for the graphs located on bottom of text part.
    § Slightly altered interpretation of prolog and epilog separators. Please take a note that prolog separator is no longer automatically appended with new line symbol, so you must specify it manually when necessary and epilog separator is now displayed below the bottom group of graphs
    § The list of hardware monitoring items in “Add item(s)” dialog window is alphabetically sorted now
    § Added macroses for embedding any data from monitoring module into OSD text (e.g. prolog). You may use macroses to display anything available in the monitoring module, e.g. %CPU temperature%
    § Improved On-Screen Display hypertext formatting performance due to more optimal macro replace strategy
    § Revamped “modern web” layout. New layout is demonstrating new text formatting features including big custom framerate counter, custom embedded background and On-Screed Display header, custom benchmark and system time indicators and embedded CPU and GPU usage graphs
    § On-Screen Display layouts are saved in monitoring profiles now
    o Improved HwInfo plugin:
    § Added UPS load, power, input voltage and charge level data sources to default plugin configuration
    · Improved voltage/frequency editor:
    o Voltage/frequency editor window is now available on AMD GPUs. On AMD platform it allows you to edit core frequencies and voltages independently per each P-State:
    § Similar to NVIDIA GPUs, you may either adjust each point frequency or voltage independently with both mouse and keyboard or hold <Shift> and drag single point to apply similar frequency or voltage offset to all P-states
    § Read only P-States are currently not tracked, which means that you can try to adjust the frequency and voltage for it but it will be ignored when applying the curve
    § P-States locking functionality is not implemented yet
    o Slightly increased default voltage range for voltage/frequency curve. Now you may lock voltage to lower values if you’re using voltage/frequency editor to downvolt and reduce power consumption on your NVIDIA GPU. Power users may customize the range further, the voltage and frequency limits are fully adjustable via the configuration file
    o Now you may press <F5> key in the editor window to reread the curve from hardware. This feature can be useful when adjusting the curve in changing thermal environment
    o Voltage and frequency axes are dynamically scales now, so the captions do not overlap when window is too small

    · Improved hardware control shared memory interface. During the past years, external applications like MSI Remote Server were using this interface for tuning GPU hardware settings remotely from external applications. The improvements are intended to allow connecting external stress testing and automatic overclocking related applications to MSI Afterburner via this interface:
    o Now voltage/frequency curve on NVIDIA Pascal and newer NVIDIA GPU architectures is accessible via hardware control shared memory interface
    o New hardware control shared memory interface command allows MSI Afterburner to load hardware settings from external application without immediately applying new settings to GPU
    o Added notification message, allowing external applications to notify MSI Afterburner about new command written to hardware control shared memory. Without the notification, MSI Afterburner is executing external commands on each hardware polling iteration like before. Please refer to SDK and MACMSharedMemorySample source code to see notification message usage example
    o Added hardware identification info to GPU entries in hardware control shared memory. Hardware identification info allows external applications to reconcile own enumerated devices with logical GPUs enumerated by MSI Afterburner
    o Now hardware control shared memory is refreshed on delayed fan speed readback events
    · New bundled MSI Overclocking Scanner application in now included in MSI Afterburner distributive:
    o MSI Overclocking Scanner is currently supported on NVIDIA GTX 10x0 and NVIDIA RTX 20x0 series graphics cards under 64-bit operating systems only. On such systems you may activate the scanner with dedicated button from the main application window or directly from voltage/frequency curve editor window
    o MSI Overclocking Scanner is powered by NVIDIA Scanner technology, which is using proprietary algorithms to quickly and reliably test manually overclocked GPU stability or find the maximum stable GPU overclocking in automatic mode with a single click. The scanner is using embedded NVIDIA test load to stress GPU. The scanner provides you two functional modes:
    § In test mode MSI Overclocking Scanner is stress-testing your manual GPU overclocking settings during approximately 5 minutes. The result is returned as GPU stability confidence level (0% - unstable, 100% - stable)
    § In scan mode MSI Overclocking Scanner is stress-testing and slowly increasing clocks on voltage/frequency curve points and this way automatically detecting the maximum stable GPU overclocking. The result is returned as modified voltage/frequency curve and average GPU overclocking in MHz
    · Added framerate limiter compatibility settings group to “On-Screen Display” tab to the application properties. The settings include programmable hotkeys for globally disabling, enabling or toggling framerate limiting techniques of RivaTuner Statistics Server. The settings are intended to provide a way to dynamically enable or disable scanline sync technology based framarate limiting without altering application profiles, however you may use it to toggle traditional framerate limter as well
    · Fixed kernel mode hardware access interface fix for AMD Vega GPUs. HBM temperature, GPU power and GPU voltage are no longer returning bogus values when kernel mode hardware access interface is enabled on AMD Vega series graphics cards

    · Hardcoded voltage/frequency curve clock multiplier implementation has been replaced with heuristic multiplier detection in order to provide unified voltage/frequency curve control implementation for NVIDIA Pascal and newer NVIDIA GPU architectures
    · Improved realtime voltage/frequency curve editor GUI scaling. Now GUI is scaled property when adjusting skin scaling with open voltage/frequency curve editor window
    · Improved report window, fan curve editor window, monitoring window and voltage/frequency curve editor scaling for scaling ratios greater than 100%
    · Multilanguage user interface library is DPI aware now. Main window skinned interface is no longer being scaled by OS and no longer looks blurred by default when greater than 100% DPI is selected. Now main skinned window interface can be manually zoomed with skin scaling slider in “User interface” tab, and the properties are automatically scaled by OS according to selected DPI
    · Added new skin scaling mode for power users. New mode provides better scaling performance at the expense of some scaling image quality loss
    · Skin scaling implementation is now asynchronous, so increasing skin scaling ratio doesn’t increase GUI update time and doesn’t decrease GUI response time
    · Skin scaling slider range has been extended from 75%-150% to 75%-200%

    · RivaTuner Statistics Server has been upgraded to v7.2.1


    RTSS v7.2.1 Beta 4

    · Fixed issue with the latest NVIDIA Adaptive Shading update of Woflenstein II: The New Colossus locking on startup. Please take a note that now Woflenstein II: The New Colossus is presenting frames from compute queue in NVIDIA codepath similar to AMD codepath. Due to that reason, On-Screen Display rendering is performance expensive and disabled by default in such environment. Experienced users, understanding and accepting On-Screen Display related performance penalty, may reenable it with PresentFromCompute profile switch
    · Fixed black screen issue in Vulkan applications on NVIDIA Kepler GPU family under 4xx.xx series drivers family
    · Improved On-Screen Display hypertext formatting implementation:
    o Variable slot 250 is no longer used to define own On-Screen Display statistics format, now it is allowing the client applications to redefine default text format. Such implementation allows the client applications like MSI Afterburner to edit default text color and size directly inside the On-Screen Display layout editor
    o Improved subpixel precision for raster fonts provides better font scaling quality and improves rendering quality for small superscript/subscript-styled text
    o Improved font baseline positioning. Now subscript-styled text is aligned on the baseline of maximum sized font symbol in the line instead of the baseline for 100% font size
    o Improved font scaling implementation for large fonts. Now requested font size is scaled from the closest reference prerendered font size instead of 100% font size
    o Changed set of prerendered font sizes from 40%, 50%, 80% and 100% to 50%, 100% and 200%. Prerendered font sizes can be used as is without scaling and with the best possible rendering quality, any different font sizes are interpolated
    o Added background fill flag for embedded objects. Background fill is intended to simplify maximum value visualization with barchart-styled embedded graphs
    o Now it is allowed to use zero width or height in bar embedding tags to specify whole text extent
    o Embedded objects are now affected by text size and alignment tags
    o Added backspace symbols support. Backspaces are intended to be used in conjunction with bar embedding tags. Inserting backspace symbol immediately after the bar embedding tag results in returning the cursor position back to embedded bar origin. Such implementation provides simplified way of embedding custom background in the hypertext. Please take a note that backspace sequences are currently not supported, so the cursor cannot be moved beyond the previous position
    o Added new tag for displaying benchmark time
    · Added suspending support to VTable hook handlers. Suspending is used to improve reference counter tracking implementation and make it more future proof
    · Graphs are no longer displayed in On-Screen Display when Vector2D On-Screen Display rendering mode is selected
    · Multilanguage user interface library is DPI aware now. Main window skinned interface is no longer being scaled by OS and no longer looks blurred by default when greater than 100% DPI is selected. Now main skinned window interface can be manually zoomed with skin scaling slider in “User interface” tab, and the properties are automatically scaled by OS according to selected DPI
    · Added new skin scaling mode for power users. New mode provides better scaling performance at the expense of some scaling image quality loss
    · Skin scaling implementation is now asynchronous, so increasing skin scaling ratio doesn’t increase GUI update time and doesn’t decrease GUI response time
    · Skin scaling slider range has been extended from 75%-150% to 75%-200%
    · Some profile settings are treated as power user settings and they are locked by default now. Such settings include “Enable Custom Direct3D support” compatibility option and Vector2D On-Screen Display rendering mode selection. Context help was not recommending enabling those compatibility related options globally, however many users tend to enable them blindly then blame the product for inappropriate performance or 3D applications compatibility. Such settings are now ignored unless you manually unlock them at the profile level
    · Added “Enable framerate limiter” option to general application properties. This option allow controlling RivaTuner Statistics Server’s framerate limiting support globally, so you may temporarily disable it if necessary without modifying generic framerate limiter or scanline sync related settings in the profiles. The client applications like MSI Afterburner can also distantly control this option via hotkeys
    · Now RivaTuner Statistics Server hides own frametime history overlay when framerate or frametime is displayed by the client On-Screen Display application
    · Now RivaTuner Statistics Server hides own benchmark statistics when benchmark time, minimum, average, maximum, 1% low, 0.1 low framerate is displayed by the client On-Screen Display application

    · Added On-Screen Display compatibility profile for Splinter Cell Chaos Theory
    · Updated profiles list


    http://msi-afterburner.guru3d.com/MSIAfterburnerSetup460Beta10Build14218.rar

    Stay tuned, and Merry Xmas! ;)

    P.S. For those who are lazy to read changes list and will try to ask questions about fan control support for AMD Adrenaline 2019 drivers family: no, it is not supported yet. AMD still have not provided updated ADL API to AIC partners.
     
  19. toyo

    toyo Active Member

    Messages:
    81
    Likes Received:
    25
    GPU:
    Gigabyte 1070Ti 8G
    Thanks, looking forward to test the scanner on Pascal.

    Edit:

    Scanning and testing fails on 1070ti/latest drivers/DCHU. It shoots lots of errors during the scan.

    Video, only 360p for now, should get to 1080p once it's processed by YT.

    -----fixed----
     
    Last edited: Dec 26, 2018
  20. Unwinder

    Unwinder Moderator Staff Member

    Messages:
    14,408
    Likes Received:
    1,424
    That’s NV’s component, not mine, sorry. I’ll forward it to them.
     
    toyo likes this.

Share This Page