Jump to content

MSI Afterburner


Recommended Posts

4 hours ago, wilkinson said:

ეგ განახლება კარგია, მაგრამ პროცესორების ტემპერატურის მაჩვენებელი გაასწორეს?

უბრალოდ ეხლა მუღამის გამო ჩავწერ და ვნახავ,წინა ბეტები აშკარად იტყუებოდნენ

ხო მგონი რომ ნაკლებ ტემპერატურას აჩვენებდა ვიდრე სინამდვილეში იყო

Link to comment
Share on other sites

55 minutes ago, Gobro said:

ხო მგონი რომ ნაკლებ ტემპერატურას აჩვენებდა ვიდრე სინამდვილეში იყო

ჩემთან პირიქითაა,უფრო მაღალ ტემპერატურას აჩვენებს და რეალურად უფრო დაბალია,AIDA64-ით ვამოწმე და აშკარად შეცდომა აქვს RivaTuner-ს

Link to comment
Share on other sites

ჩემთან სწორათ აჩვენებს ბირთვებზე ტემპერატურას, სანამ მაგის გამოყენებას დავიწყებდი სპეციალურათ შევამოწმე სხვა უტილიტებით და სხვაობა მაქს 1 გრადუსის ფარგლებში ქონდა, ეხლაც გადავამოწმე სპიდფანზე და Сoretemp-ზე და ფაქტიურათ იგივე აჩვენა რაც მანდ, ანუ მე ვენდობი და მაგითი ვტესტავ ხოლმე, აი რამის მოხმარებას ზოგ თამასში იძახიან ხანდახან არასწორათ აჩვენებსო, რამდენათ მართალია არ ვიცი, თან მე პეიჯფაილი მთლიანათ გათიშული მაქვს 16გბ რამზე და შეიძლება ეგრე ნაკლებათ ეშლებოდეს უფრო მაგის გამოთვლა, რაც არ უნდა იყოს არცერთ თამასში არ ასულა 10გბ-ზე ზევით ჩემთან რამის მოხმარება 1080P-ზე ამ ახალ სისტემაზე, თუმცა 6-7 თამასშე მეტი მგონი არც დამიხურია რაც ეგ სისტემა ავაწყვე 2014 წლის შემოდგომაზე

Link to comment
Share on other sites

MSI Afterburner 4.4.0 beta 15 გამოვიდა შემდეგი ჩეინჯლოგით:

- Active bus clock monitoring for Intel CPUs. Previous version measured Intel bclk just once on startup, so if you use software CPU overclocking via adjusting bus clock on the fly, wrong CPU clock speed could be displayed. Now bus clock is measured on each hardware polling period.
-Added OverdriveN X2 overclocking API support for 17.7.2 AMD display drivers.
- Unofficial overclocking API is currently broken in 17.7.2. drivers (applying the clocks with it makes GPU stuck in lowest P-state till reboot) so MSI Afterburner is forcibly disabling unofficial overclocking mode and always using official ADL overclocking codepath on 17.7.2 and newer drivers. However, unofficial overclocking mode can still be manually unlocked via configuration file on 17.7.2 and newer drivers if AMD decide to provide a fix for unofficial overclocking mode in the future.

ესეც გადმოსაწერი ლინკი: http://office.guru3d.com/afterburner/MSIAfterburnerSetup440Beta15.rar

Link to comment
Share on other sites

RTSS 7.0.0 beta 28 დაიდო შემდეგი ფიქსით:

- Added OpenGL context validation algorithm to improve compatibility of raster 3D On-Screen Display rendering mode with OpenGL applications, which dynamically recreate the context (e.g. on display mode switching)

ესეც გადმოსაწერი ლინკი: http://office.guru3d.com/afterburner/RTSSSetup700Beta28.rar

Link to comment
Share on other sites

  • 1 month later...

MSI Afterburner 4.4.0 beta 17 გამოვიდა შემდეგი ჩეინჯლოგით:

The major key features of new release are:

- Hardware monitoring plugins support, now you can monitor more data out of box and can create your own sensors and share your work with community
- OSD layout editor. Now you can customize modern OSD layout in details
- Improved programmable critical thresholds in hardware monitoring module. Now you can configure you system to play sound alarm or perform emergency actions (e.g. downclock GPU, boost fan speed or even power down the system) when some monitored parameter reach critical value

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/MSIAfterburnerSetup440Beta17.rar

ისე მე 16 ბეტა მყენებია და როგორც ჩანს აქ დადება დამავიწყდა უბრალოთ

Link to comment
Share on other sites

MSI Afterburner 4.4.0 Beta 18 გამოვიდა: http://www.guru3d.com/files-get/msi-afterburner-beta-download,32.html

 

 

  • Upvote 1
Link to comment
Share on other sites

და RTSS 7 beta 29 აქვს შიგნით საინსტალაციოში

Link to comment
Share on other sites

ნორმალურათ უბერავს ეგ ბეტა, დეფოლტზე კი ეხლა ეს სკინი აქვს:

vff1tJT.png

ამის სკრინების გადამღები არ ვიცი მაგრამ ბანდიკამი დღეს ცოცხალი თავით ვერ ავამუშავე ვერსად სანამ გეიმინგ რეჟიმში არ გადავიყვანე ახალი ვერსია რომ გამოუშვეს განახლებული ინტერფეისით, მარტო მერე დაინახა მასს ეფექტ 3, ისე ვერ ხედავდა რატომღაც, შეიძლება დრაივერთან აქვს რაღაც შეუთავსებლობა და ახალი დრაივერი ჭირდება WDDM 2.3 საპორტით, ან თვითონ აქვთ რაღაცა შესასწორებელი, გეიმ მოდით უკვე ეგრევე ამუშავდა

Link to comment
Share on other sites

სულ მალე ფინალური ბილდიც გამოვაო, ეს კიდე წინა ბეტას ჩეინჯლოგი:

Changes list includes:

- Partial AMD Vega support:
+ Fan control for Vega is supported now. Please take a note that Vega doesn’t provide native support for traditional PWM duty cycle based fan control (i.e. it doesn’t allow setting desired fixed fan speed in % directly). So fan speed percent scale in MSI Afterburner is internally linearly mapped to RPM scale.
+ Low-level voltage control via direct access to SMC is currently not implemented for Vega, so voltage is controlled via AMD ADL API. Which means that you cannot set voltages higher than allowed by Wattman’s. Honestly I’m not sure if it worth implementing low-level voltage control for those cards, they are really power hungry and power limited even on default clocks/voltages.
- Now drag and drop is supported for multiple selected graphs in active hardware monitoring graphs list in “Monitoring” tab. So it is a bit easier to rearrange the graphs list now.
- Now you may right click active hardware monitoring graphs list in “Monitoring” tab and select “Reset order” command from the context menu to reset default active graphs order.
- Added Prolog and Epilog properties to “Separators” property node in OSD layout editor. Prolog and epilog allow you to display any custom text info above and below OSD (e.g. branding text, URL, your system specs etc). Both prolog and epilog support macro variables, allowing you to insert desired system specs automatically. The list of supported macro variables includes: %CPU%, %FullCPU%, %RAM%, %GPU%, %FullGPU%, %Driver% and %Time%.
- Added new “Group separator” property node to OSD layout editor. Group separators can be used to vertically split the groups if necessary.
- Added new “modern web” OSD layout to OSD. The layout is using new prolog and epilog to render branding text and system specs in OSD and group separators to split GPU, CPU/RAM and 3D application related statistics in OSD.
- Both MSI Afterburner and RTSS installers are preserving installation path now.

Link to comment
Share on other sites

ველოდები ფინალურს

 

Link to comment
Share on other sites

კიდე ახალი ბეტა ბილდი გამოვიდა შემდეგი ჩეინჯლოგით:

Changes list includes:

· Added low-level AMD Vega 10 graphics processors family support. This means that now MSI AB can access this GPU directly without AMD ADL API, so more powerful voltage control (no longer limited by AMD ADL API) and extended and more efficient low-level hardware monitoring are available for Vega now
· Core voltage control for reference design AMD Vega series cards is now performed via low-level access to on-die SMC microcontroller. Voltage is adjusted in offset form now, applied to all P-states (just like it was on Fiji/Polaris) and full -100..+100 range is available
· Added GPU power draw graph to hardware monitoring module for AMD Vega series graphics cards
· Added HBM memory temperature graph to hardware monitoring module for AMD Vega series graphics cards
· Improved voltage offset calculation accuracy for AMD Fiji, Ellesmere and Baffin GPU families
· Improved voltage offset programming reliability on AMD Ellesmere and Baffin GPU families
· Fixed stuck GPU usage and memory controller usage monitoring on AMD Radeon RX 500 series under 17.6.1 and newer drivers
- Fixed issue with opening wrong graph properties under certain conditions when right clicking a graph in hardware monitoring window and selecting “Properties” command from the context menu
- Fixed issue with wrong alarm threshold visualization on the graph label in OSD for monochrome OSD layouts
- Improved plugins:
+ Data sources exported by plugins no longer share the same MONITORING_SOURCE_ID_UNKNOWN data source identifier, which means that now you can define independent custom formatting (e.g. group colors) for plugin specific data sources in OSD layout editor
+ PerfCounter plugin has been improved to handle corrupted registry performance counters list on some systems and to be able to access at least the part of performance counters available on the system in such case
- I've temporarily signed both installer and application executable with my own signature.
 

ესეც გადმოსაწერი ლინკი: http://www.guru3d.com/files-get/msi-afterburner-beta-download,32.html

აგრეთვე ცალკე დაიდო RTSS 7.0 Beta30 ბილდი შემდეგი ცვლილებით:

This build of RTSS introduces OSD support for D3D11 applications using 12.x feature levels, so it should work with Middle Earth : Shadow of War:

http://download-eu2.guru3d.com/rtss/[Guru3D.com]-RTSSSetup700Beta30.zip

Link to comment
Share on other sites

  • 2 weeks later...

ახალი ბეტა ბილდი გამოვიდა კიდე შემდეგი ჩეინჯლოგით:

- Downvoltage limits have been increased from -100mV to -200mV for AMD Vega series
- Added new "Graph separator" properties to OSD layout. Similar to existing "Group separator" properties, they allow you to insert custom text (e.g. a few new line symbols) right before any displayed graph and this way easily separate some graphs vertically in OSD if necessary
- Improved PerfCounter plugin configuration file, units of "Network download rate" and "Network upload rate" have been changed from KB/s to MB/s. Also now the plugin supports displaying network download and upload rate performance counters for up to 4 network interfaces instead of the first network interface in the previous version config
- Bundled RTSS distributive have been upgraded to 7.0.0 beta 30 with "Middle Earth : Shadow of War" OSD support, beta 30 installer has been slightly updated (a few more built-in profiles added)

ესეც გადმოსაწერი ლინკი: http://office.guru3d.com/afterburner/MSIAfterburnerSetup440Beta20.rar

Link to comment
Share on other sites

მგონი ბოლო ბეტა ბილდი გამოვიდა ფინალურ რელიზამდე შემდეგი ჩეინჯლოგით:

Minimum voltage offset has been extended to -200mV for AMD Fiji and Ellesmere GPU families
· Improved drag and drop implementation for the list of active hardware monitoring graphs. Now it is possible to drag and drop items below the bottom edge of the list to move the graphs to the end of the list
· Improved multiple selection functionality in monitoring properties:
· When multiple graphs are selected you may press <Ctrl>+<M> inside group name edit field to apply group name changes synchronically to all selected graphs
· Now “Override graph name” and “Override group name” checkboxes are also affected by multiple selection functionality, so you may hold <Shift> when toggling those options to toggle it synchronically for all graphs or hold <Ctrl> when toggling those options to toggle it synchronically for all selected graphs
· Now group names support macro definitions (the same as prolog/epilog in OSD layout editor), so for example you may override group name for GPU temperature and set it to %GPU% to utomatically display your GPU name as a group name in OSD
· Added %GPU1%..%GPU8% and %FullGPU1%..%FullGPU8% macro names support for mGPU systems
· Now alarm zone is visualized on monitoring graph instead of displaying just the threshold. This simplifies visual identification of min/max thresholds 
· Now you can define closed alarm range if specified maximum alarm threshold is less than minimum

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/[Guru3D]-MSIAfterburnerSetup440Beta21.zip

Link to comment
Share on other sites

MSI AfterBuner 4.4.0  ფინალური ვერსია გამოვიდა უზარმაზარი ჩეინჯლოგით :

Version 4.4.0 

Added core voltage control for reference design NVIDIA GeForce GTX 1070 Ti series graphics cards
Added core voltage control for reference design NVIDIA GeForce GT 1030 series graphics cards
Added core voltage control for reference design NVIDIA GeForce GTX TITAN Xp series graphics cards
Added core voltage control for reference design NVIDIA GeForce GTX 1080 Ti series graphics cards
Added support for NVIDIA GPUs working in TCC (Tesla Compute Cluster) mode
Hardware abstraction layer architecture has been revamped to allow implementation of memory temperature sensors via direct access to GPU on-die voltage controllers (e.g. AMD Vega 10 SMC) in addition to previously supported external memory temperature 
sensors connected to GPU via I2C bus
Added AMD Vega 10 graphics processors family support
Added core voltage control for reference design AMD Vega series cards with on-die SMC voltage controller
Added GPU power draw graph to hardware monitoring module for AMD Vega series graphics cards
Added HBM memory temperature graph to hardware monitoring module for AMD Vega series graphics cards
Added linear RPM-based fan speed control for reference design AMD Vega series graphics cards. Please take a note that traditionally fan speed adjustment scale is not linear and it is not directly mapped to RPM, traditional fan speed percent on other hardware is a PWM duty cycle. !MD Vega fan controller doesn’t support duty cycle based fan control mode, so specified fan speed percent is linearly mapped to maximum RPM percent
Improved voltage offset calculation accuracy for AMD Fiji, Ellesmere and Baffin GPU families
Improved voltage offset programming reliability on AMD Ellesmere and Baffin GPU families
Minimum voltage offset has been extended to -200mV for AMD Fiji and Ellesmere GPU families
Fixed stuck GPU usage and memory controller usage monitoring on AMD Radeon RX 500 series under 17.6.1 and newer drivers
Revamped voltage control layer gives additional freedom to extreme overclockers with new custom design MSI graphics cards with Quad Overvoltage™ technology support. Now MSI Afterburner is able to control up to 4 independent voltages on custom design MSI graphics cards
Improved 5-channel thermal monitoring module architecture provides support for up to 20 independent thermal sensors per GPU (up to 5 independent GPU, up to 5 independent PCB, up to 5 independent memory and up to 5 independent VRM temperature sensors) on future custom design MSI graphics cards
Added NCT7802Y thermal sensors support to provide compatibility with future custom design MSI graphics cards
Added core, memory, auxiliary PEXVDD and auxiliary 1V8 voltage control for custom design MSI GTX1080Ti Lightning Z series graphics cards with IR3595A+IR3570B+uP1816 voltage regulators
Added VRM, VRM2, VRM3, VRM4 and PCB temperature monitoring for custom design MSI GTX1080Ti Lightning Z series graphics cards with NCT7511Y thermal sensors
Improved hardware database format. New database subsections support provides more compact database definition for multiple graphics card models sharing similar hardware calibration info
New cached I2C device detection algorithm improves application startup time on the systems with multichannel voltage controllers or multichannel thermal sensors
Improved third-party voltage control mode functionality. Now third-party hardware database can also include extended thermal sensors calibration and mapping info for third-party custom design graphics cards
Added AMD Overdrive Next X2 overclocking API support for AMD Crimson 17.7.2 display drivers
The unofficial overclocking mode is currently broken in AMD Crimson 17.7.2 display drivers, so MSI Afterburner is forcibly disabling unofficial overclocking mode and always using official ADL overclocking codepath on 17.7.2 and newer drivers. However, unofficial overclocking mode can still be manually unlocked via configuration file on 17.7.2 and newer drivers if AMD decides to provide a fix for unofficial overclocking mode in the future
Improved PCI bus scanner provides support for low-level GPU access for the secondary graphics cards in Crossfire configuration on some platforms
Fixed system freeze issues when starting MSI Afterburner on AMD Hawaii GPU while playing hardware accelerated video
Fixed issue with opening wrong graph properties under certain conditions when right clicking a graph in hardware monitoring window and selecting “Properties” command from the context menu
Improved voltage/frequency curve editor for GPU Boost 3.0 capable NVIDIA graphics cards: 
o Toggling locked curve point state with <L> key is working properly now and no longer resulting in setting a lock to a minimum clock/frequency point 
o Now you may hold <Alt> key while adjusting the offset of any point with mouse to move the curve up/down. That’s equal to adding fixed offset to each point’s offset
Various parts of the hardware monitoring module have been pumped up to improve hardware monitoring usability and flexibility. Some new portions of old hardcore functionality from original RivaTuner are now available in MSI Afterburner: 
o Added clock monitoring for Intel CPUs 
o CPU temperature graph is now displaying data from dedicated package sensor on modern Intel CPUs instead of maximum core temperature. On older Intel CPUs with no dedicated package sensor the graph is still displaying the maximum core temperature 
o Added temperature and clock monitoring for AMD Ryzen CPUs 
o Added new “benchmark” tab allowing you to use hidden RivaTuner Statistics Server’s benchmarking engine, which was previously available to reviewers only. The engine is providing you the following features:
You may define a hotkey for beginning framerate statistics recording. Once the recording begun, it stays active for all subsequently started 3D applications, even after rebooting the system
While recording is active you may enable showing own statistics in RivaTuner Statistics Server to see minimum, average and maximum framerate in the On-Screen Display
While recording is active you may press “_egin recording” hotkey one more time to restart the recording and reset the statistics
While recording is active you may press “End recording” hotkey once to end recording and save benchmark results to a text file, but keep the results shown in On-Screen Display. You may press the hotkey one more time to hide the results from the On-Screen Display
Statistics saved to a benchmark results file includes per-application total benchmarking time, total rendered frames number, global average, instantaneous minimum and instantaneous maximum framerates. Benchmark statistics file can be optionally either overwritten or appended on each recording session
Per-frame frametime statistics is being pushed to a named pipe so reviewers can use their own client software to collect and display it in realtime while any benchmark is running without system slowdown, which is typical for traditional per-frame frametime logging approach o New flexible On-Screen Display customization features powered by RivaTuner Statistics Server’s text formatting tags and embedded objects:
Added On-Screen Display layouts support. Layouts allow you to change On-Screen Display formatting and appearance style. Now you may switch between traditional classic On-Screen Display layout or new modern column-oriented On-Screen Display layout. Built-in layout editor allows you to customize pre-defined layout parameters in details
New On-Screen Display item type selection settings allow you to display each item in On-Screen Display as a text or graph. The graphs displayed in the On-Screen Display can be useful to visualize frametime history and GPU usage history, and so on
The maximum text length for “Override group name” setting is no longer limited by 8 symbols. Now you may embed new RivaTuner Statistics Server’s text formatting tags directly into your custom group name, e.g. “<C=FFFFFF>GTX 1080<S=-50=1<S=<C=” to display it in On-Screen Display in white color and with 50% size subscript index
Now it is allowed to override group names for “Framerate” and “Frametime” graphs, so you may append default application 3D API <APP> tag with some custom text or replace it completely if necessary
Exactly the same flexible level of On-Screen Display customization output is available to any other RivaTuner Statistics Server client applications like AIDA, HWiNFO and others and will be available shortly
Original RivaTuner’s task scheduler functionality is back! Now you may define optional minimum and (or) maximum thresholds for any graph in hardware monitor module to track the most critical hardware health parameters, to be notified on reaching a critical threshold and to program some emergency actions (e.g. system shutdown) to be performed in this case:
User-defined thresholds are displayed on each graph to allow you to control each parameter safety zone visually
When the threshold is reached blinking warning icon is displayed in top left corner of monitoring window and in Logitech keyboard LCD if graph LCD display mode is selected
When the threshold is reached you can see the name of graph triggering the alarm in hardware monitoring status line
When the threshold is reached background of the graph triggering the alarm is highlighted with color to allow you to identify it visually
When modern On-Screen Display layout is selected, parameters triggering the alarm are highlighted by color in On-Screen Display to allow you to identify it easily
You may enable option alarm sound notification to be played when the threshold is reached
You may configure MSI Afterburner to launch any external application when the threshold is reached. This feature allows you to implement many different scenarios, e.g. perform emergency system shutdown or apply safe profile with reduced overclocking, maximized fan speed etc. In addition to selecting any custom external applications, built-in predefined applications browser allows you to select some common typical usage scenarios, such as command line based MSI Afterburner profile activation or system shutdown 
 o Original RivaTuner’s user extendable hardware monitoring plugins architecture is back! Now you may extend the list of hardware monitoring data sources with built-in or third party plugin modules, develop your own plugins to provide support for custom hardware sensors and share your work with community, and many more:
The plugins can use full set of MSI !fterburner’s low-level hardware access functionality: enumerate GPUs, access GPU registers, enumerate GPU I2C buses and access I2C devices, access CPU MSR registers, access IO ports and PCI configuration space registers. This way you can easily create your own plugins providing hardware monitoring functionality for any custom hardware. You can also create the plugins for importing OS-specific or third-party software specific performance counters into MSI Afterburner
Open source SDK, demonstrating hardware monitoring plugins development principles to third party programmers.
The SDK includes the following open source plugins:
SMART.dll – demonstrates HDD SMART attributes readback and HDD temperature monitoring
PerfCounter.dll – demonstrates the principles of importing native OS performance counters into 
MSI Afterburner. The list of imported performance counters includes but not limited to hard disk usage, hard disk read and write rates, free disk space on system partition, network download and upload rates. You may also add any other performance counter visible to OS (e.g. disk queue size or some specific process CPU usage) via editing the plugin configuration file
AIDA64.dll – demonstrates the principles of importing sensors from AIDA64 application via shared memory interface. The list of imported performance counters includes but not limited to motherboard temperature, CPU socket temperature, CPU fan speed, CPU voltage, CPU package power, +3.3V, +5V and +12V voltages. You may also add any other sensors available in AIDA64 via editing the plugin configuration file
HWInfo.dll -imports sensors from HWiNFO32/64 application via shared memory interface. The list of imported performance counters includes but not limited to motherboard temperature, CPU socket temperature, CPU fan speed, CPU voltage, CPU package power, +3.3V, +5V and +12V voltages. You may also add any other sensors available in HWiNFO32/64 via editing the plugin configuration file. Please take a not that the plugin is not open source per HWiNFO developer request
Improved profiles architecture. Now MSI Afterburner can store hardware monitoring module settings in the profile slots. This allows you to switch between different On-Screen Display configurations on the fly with hotkeys bound to profile slots. You may configure desired profile slot contents in new “Profile contents” settings group in “Profiles” tab 
o Added experimental interleaved hardware polling mode, aimed to reduce hardware polling time on the systems with multiple polled I2C devices. When interleaved polling is enabled, just a part of hardware monitoring data sources is being polled on each hardware polling period, so it takes multiple periods to refresh all monitoring data sources. Power users may enable interleaved hardware polling mode via the configuration file if necessary 
o Added ability to define a hotkey for hardware monitoring logging start and stop 
o Now the path to hardware monitoring logs supports macro names:
You may use new %ABDir% macro in the path to specify relative path to current MSI Afterburner installation directory. This macro allows you to use logging if you are using portal installation and start MSI Afterburner from removable drive
You may use new %Time% macro in the path to make hardware monitoring sessions to be stored in unique timestamp-named log files instead of single multi-session log file
Changed hardware monitoring properties layout, the controls have been reordered a bit to give more compact and convenient look to the properties
Changed default hardware monitoring graphs order. GPU related graphs have been reordered a bit in order to provide more convenient layout on multi-GPU systems. “Framerate” and “Frametime” graphs have been moved to the bottom of the list
Now you may right-click the list of active hardware monitoring graphs and select “Reset order” command from the context menu to restore default active hardware monitoring graphs order
The maximum limit for “Frametime” graph has been decreased to 50ms (20 FPS) by default 
Improved drag and drop implementation for the list of active hardware monitoring graphs. Now it is possible to drag and drop items below the bottom edge of the list to move the graphs to the end of the list
Improved multiple selection functionality:
Now you may hold <Shift> key when clicking a checkmark next to a graph name in the list of active hardware monitoring graphs to enable or disable all graphs at once
Now you may hold <Shift> or <Ctrl> keys to select multiple items in the list of active hardware monitoring  graphs. The following functionality is available for multiple selected hardware monitoring graphs: • Multiple selected graphs can be dragged and dropped when rearranging the graphs • When multiple hardware monitoring graphs are selected, you may hold <Ctrl> key when changing 
graph specific On-Screen Display, Logitech keyboard LCD and tray icon related properties (e.g. “Show in On-Screen Display” property) to change it synchronically for all selected graphs
When multiple hardware monitoring graphs are selected, you may hold <Ctrl> when clicking a checkmark next to a graph name in the list of active hardware monitoring graphs to enable or disable all selected graphs at once
When multiple graphs are selected you may press <Ctrl>+<M> inside group name edit field to apply group name changes synchronically to all selected graphs Now “Override graph name” and “Override group name” checkboxes are also affected by multiple selection functionality, so you may hold <Shift> when toggling those options to toggle it synchronically for all graphs or hold <Ctrl> when toggling those options to toggle it synchronically for all selected graphs.
Improved system information window. Now 3D API usage info, x64 and UWP application architecture attributes are displayed for each currently running process in the list of active 3D applications
Now the installer is preserving installation path
RivaTuner Statistics Server has been upgraded to v7.0.0 
 

ესეც გადმოსაწერი ლინკი: http://www.guru3d.com/files-get/msi-afterburner-beta-download,32.html

 

Link to comment
Share on other sites

  • 1 month later...

MSI Afterburner v4.4.2 გამოვიდა შემდეგი ჩეინჯლოგით (4.4.1 ჩეინჯლოგიც დავამატე):

MSI Afterburner v4.4.1:

· Fixed crash on application startup on the systems with more than 8 NVIDIA GPUs installed on recent NVIDIA display drivers
· Now the list of GPUs in "General" tab in the application properties is sorted properly on the systems with more than 10 GPUs installed
· Added voltage control for NVIDIA P104-100 and P106-100 mining cards
· Now MSI Afterburner is displaying notification message in monitoring window area when trying to overclock NVIDIA 10x0 series GPU with debug mode enabled in NVIDIA control panel
· Added "Frametate Min", "Frametate Avg", "Frametate Max", "Frametate 1% Low" and "Frametate 0.1% Low" graphs to hardware monitoring module. The graphs are duplicating benchmark statistics displayed in benchmark On-Screen Display, but give you more freedom in On-Screen Display customization
· Improved On-Screen Display layout editor. Now you can customize On-Screen Display graph styles independently for each graph instead of changing it globally
· RivaTuner Statistics Server has been upgraded to v7.0.1

RivaTuner Statistics Server v7.0.1:

· Improved built-in benchmarking engine:
o Added 1%/0.1% low framerate statistics calculation. Unlike traditional calculation approach, which is assuming post-processing of whole set of collected frametimes at the final stage of benchmarking, RivaTuner Statistics Server introduces new concepts of dynamic 1%/0.1% low framerate statistics calculation. The implementation is open source and demonstrated in RivaTuner Statistics Server SDK.
o 1%/0.1% low framerates are stored in the benchmark results file. 1%/0.1% low framerate are also displayed in benchmark On-Screen Display, so you may track 1%/0.1% low framerate dynamics in realtime.
· Updated SDK:
o Added new open source RTSSFrametimePipeSample sample. The sample is demonstrating implementation of custom benchmarking software, which is receiving per-frame frametime statistics in realtime via named pipe connection to RivaTuner Statistics Server. Post-processing text frametime log files after running the benchmark is no longer necessary! Now you may create your own benchmarking software and receive frametime data from RivaTuner Statistics Server in realtime directly while 3D application is running. Such approach was in use by some major hardware reviewers for a few years, now it is open source and available to everyone! The sample is also demonstrating the following techniques:
§ Realtime frametime graph rendering
§ Realtime current framerate averaging with sliding window algorithm, minimum and maximum framerates calculation and display
§ Dynamic 1%/0.1% low framerate statistics calculation and display
§ Logging per-frame frametime, current, minimum, average, maximum, 1% low and 0.1% low framerates to CSV text file
· Improved text formatting tags support:
o Now text position tags can use negative coordinates to move a text to a new position specified in character units instead of zoomed pixel units
o Improved text position tags handling for cases when the tag is used explicitly before the embedded object
o Added new visualization style support for embedded graph objects. Now it is possible to embed barchart styled graphs
· Slightly optimized On-Screen Display geometry batching for all 3D APIs in order to simplify the process of new functionality implementation in future versions

MSI Afterburner v4.4.2:

- Added core voltage control for reference design NVIDIA TITAN V series graphics cards
- Fixed one polling period delay for values displayed in On-Screen Display graph labels
- Fixed incorrect group names displayed for "Framerate Min", "Framerate Avg", "Framerate Max", "Framerate 1% Low" and "Framerate 0.1% Low" graphs in Logitech keyboard LCD in text mode
- Improved detection of active 3D application, which is supplying data to "Framerate" and "Frametime" graphs, in cases when running multiple 3D applications simultaneously
- RivaTuner Statistics Server has been upgraded to v7.0.2

RivaTuner Statistics Server v7.0.2:

- New unified geometry batching implementation for all supported 3D APIs provides more efficient On-Screen Display rendering and more easily extendable renderer architecture
- Due to new unified geometry batching implementation barchart graphs are now being rendered in a single pass with On-Screen Display text
- Added new formatting tags for displaying embedded bars
- Fixed multithreaded audio encoder uninitialization issue, which could cause temporary prerecord files not to be deleted when prerecording video to a file
- Updated profiles list

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/[Guru3D.com]-MSIAfterburnerSetup442.rar

ხო განახლებული RTSS მოყვება მაგ ახალს და ესეთი ფიშკები დაუმატებია ანვინდერს:

 

y7XYpSy.jpg

დავაყენე და ეხლა ისევ power მონიტორინგს ვტესტავ ღირს თუ არა ლონგ რანში ჩართული დატოვება და იწვევს თუ არა ისევ სტატერინგს

Link to comment
Share on other sites

ოფიციალური ფინალური ბილდიც გამოვიდა მაგ ბოლო ვერსიის: http://www.guru3d.com/files-get/msi-afterburner-beta-download,32.html

Link to comment
Share on other sites

  • 2 months later...

MSI AB Version 4.4.3 beta 2 გამოვიდა შემდეგი აბიომნი ჩეინჯლოგით (ბეტა 1 ჩეინჯლოგიც დავამატე):

MSI AB Version 4.4.3

· Minimum, average, maximum, 1% low and 0.1% low framerates are now displayed in On-Screen Display with special text formatting tags introduced by new RivaTuner Statistics Server. The tags are allowing On-Screen Display clients to display independent benchmark statistics simultaneously for multiple running 3D applications instead of displaying foreground 3D application statistics only
· Improved built-in performance profiler. Now you may hold <Ctrl>+<Shift> buttons pressed when “Show status” option is enabled in hardware monitoring window to see additional polling statistics displayed in hardware monitoring window status area. Polling statistics includes information about the slowest polled sensor with maximum polling time, so power users can easily identify problematic sensors eating most of CPU time on each polling period (e.g. abnormally slow GPU power sensor in some versions of NVIDIA drivers)
· Improved default MSI Cyborg White skin. Monochrome on / off states of fan speed auto button were hardly identifiable before, they are more contrast now 
· Improved monitoring plugins architecture:
o Added new SetupSource API function allowing you to configure the plugins. This function is allowing you to customize the plugins either globally from plugin selection window (e.g. configure whole list of data sources exported by each plugin) or customize desired data source only directly from corresponding graph properties window (e.g. change network download rate units from MB/s to KB/s). SetupSource function usage is demonstrated in SDK in updated AIDA64 and PerfCounter plugins
o Added new GetHostAppProperty API function allowing the plugins to retrieve various properties from the host application (i.e. MSI Afterburner), e.g. retrieve GUI color scheme specific to currently selected skin. GetHostAppProperty function usage is demonstrated in SDK in updated AIDA64 and PerfCounter plugins
· Improved monitoring plugins:
o Now the plugins store user customized and built-in default configurations in separate files, so your custom plugin settings won’t be lost on new version install
o Added configuration GUI for AIDA64, HwInfo and PerfCounter plugins. Each plugin’s user interface is allowing you to edit the list of sensors exported by each plugin, export full list of available sensors to a text file, customize each sensor’s properties or reset plugin settings to defaults
o Improved SMART plugin. Added airflow temperature SMART attribute support for Intel/Samsung SSDs.
· Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
· RivaTuner Statistics Server has been upgraded to v7.1.0

- New hardware monitoring performance profiler panel is now visualizing sorted per-sensor polling statistics diagram instead of displaying just a single sensor with maximum polling time. This allows you to identify multiple most CPU hungry sensor much easier than before. The panel is no longer triggered by <Ctrl>+<Shift> hotkeys and "Show status" context menu command, now it can be displayed with new separate "Show profiler panel" command in the context menu.
- Added double buffering style to list controls, displaying dynamically refreshable sensors in AIDA64/HwInfo/PerfCounter plugin's GUI. Double buffering is aimed to minimize flickering effect.
- Added new button for selecting instance name or index in performance counter data source setup dialog in PerfCounter plugin. It is no longer necessary (but still possible) to type it in manually.
- The list of root items (i.e. performance object names) is sorted alphabetically in "Add new source" window in PerfCounter plugin.
- Now you can hold <Ctrl> while clicking "Add new source" buttons in AIDA64/HwInfo/PerfCounter plugins to clone currently selected sources in AIDA64/HwInfo/PerfCounter plugins. This feature can be useful when populating the same sets of sensors for multiple instances of physical devices (e.g. clone HDD1 sensors and add the same for HDD2).
- Fixed bug in HwInfo plugin GUI, which could result in displaying duplicated sensor data in "Add new source" window in HwInfo plugin.
- Added ability to use performance counters with non-localized names in PerfCounter plugin (e.g. GPU Engine performance counters introduced in Windows 10 Fall Creators Update)

RTSS Version 7.1.0

· Added On-Screen Display locking mechanism for third party On-Screen Display client applications. The mechanism is aimed to eliminate unwanted On-Screen Display flickering effect when some client application is performing risky two-stage On-Screen Display refresh while On-Screen Display is being actively refreshed by another client. Please take a note that third party On-Screen Display clients must be also updated in order to use this mechanism and get rid of flickering
· Added new text formatting tags support for displaying minimum, average, maximum, 1% low and 0.1% low framerates in benchmark mode. The tags are allowing On-Screen Display clients to display independent benchmark statistics simultaneously for multiple running 3D applications instead of displaying foreground 3D application statistics only
· Now it is possible to adjust frametime history graph size via RivaTuner Statistics Server properties. Please take a note that you may use positive values to specify the size in pixels or negative values to specify it in symbols
· Now it is possible to toggle benchmark mode state from RivaTuner Statistics Server properties. However, third party benchmark client applications like MSI Afterburner are still required to toggle benchmark mode state with hotkeys during 3D application runtime and to save benchmark results to a text file
· Now it is possible to toggle between averaged or instantaneous calculation modes for peak (i.e. minimum and maximum) framerates for benchmark mode via RivaTuner Statistics Server properties
· Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
· Updated SDK:
o Now RTSSSharedMemorySample sample code is demonstrating the implementation of On-Screen Display locking and flickering filter
· Updated profiles list

ახალი პლაგინი დაუმატებია unwinder:

CfUDWlH.png

 

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/[Guru3D.com]-MSIAfterburnerSetup443Beta2.rar

მიყენია ეგ ვერსია და არანაირი ბაგი არ შემინიშნავს

Link to comment
Share on other sites

4.4.3 Beta 3 გამოვიდა შემდეგი ჩეინჯლოგით:

o Added experimental support for Intel i7 and i9 7XXXX LGA2066 CPUs
o Added CPU package power monitoring for Intel CPUs
o Fixed one more bug in HwInfo plugin GUI, which could cause duplicated sensor readings in “Add new data source” window
o Improved PerfCounter plugin. Added support for dynamic data sources. Dynamic data sources are not validated during creation, such sources are allowed to export no data until some condition is met (e.g. “CPU usage” performance counters specific to some target process export data only when the process is running)
o Added new open source CPU.DLL plugin. The plugin fully duplicates MSI Afterburner’s built-in CPU temperature monitoring implementation (with the only exception of AMD Ryzen codepath, which cannot be open sourced due to NDA) and shows third party plugin developers how to implement low-level CPU specific sensors in plugins using CPU MSR registers and PCI configuration space access API
o Now uninstaller is also removing user plugin configuration files when you’re performing full application uninstallation

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/[Guru3D.com]-MSIAfterburnerSetup443Beta3.rar

CPU package power monitoring for Intel CPU დაემატა მაგ ახალში და შეიძლება დატესტვა თამასში რამდენ ვატს მოიხმარს პროციკა პიკზე, აი power კი მგონი ისევ ახურებს და სტატერინგი აქვს ვიდოების ყურების დროს და გავუთიშე მაგის მონიტორინგი, რავი მაგის გარეშე მე უფრო გლატკათ მეჩვენება ახლო კადრები, ისე თითოქს ცოტათი ლაგავსო, თუმცა ეგრე ძალიან აღარ როგორც ადრე 388 სერიის ნვიდიას დრაივერები რომ გამოვიდა და მერე ფიქსი რომ გამოუშვეს

Link to comment
Share on other sites

  • 2 weeks later...

MSI AB Version 4.4.3 beta 4 გამოვიდა შემდეგი ჩეინჯლოგით:

- Added new keyboard modifiers to "Add new source" window in AIDA/HwInfo/PerfCounter plugins. Now you may hold <Ctrl>+<Shift> when clicking <Add> button to clone currently selected data sources and automatically increment instance indices (if specified) in data source properties. This way you can easily clone the same set of sensors for multiple similar devices, e.g. simply select the set of performance counters specific to HDD4 in PerfCounter plugin then easily create the same set of sensors for HDD5 with single click.
- Now new added data sources are automatically selected in the list of available data sources in AIDA/HwInfo/PerfCounter plugins. Combining with previously mentioned keyboard modifiers, this feature simplify the process of cloning the same sets of sensors for multiple similar devices
- Minimum sampling interval for CPU usage calculation has been reduced from 1000ms to 100ms
- Fixed incorrect tracking markers rendering on the graphs dynamically added to hardware monitoring module
- Fixed incorrect tracking markers rendering when monitoring ring data buffer is full

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/[Guru3D.com]-MSIAfterburnerSetup443Beta4.rar

Power-ზე მაინც აქვს მცირე ლაგები მონიტორინგში თუ მაგი გაქვს მონუშნული, ამიტომ გამორთული მაქვს ეგ პაკაზატელი

Link to comment
Share on other sites

  • 4 weeks later...

MSI AB Version v4.5.0 beta 5 beta 4 გამოვიდა შემდეგი ჩეინჯლოგით:

· Added power user oriented restore points system. Experienced users may use new /backup and /restore command line switches to create multiple named restore points containing full backups of MSI Afterburner's settings (including hardware profiles and custom hardware monitoring plugin configurations) and restore settings from any previously created restore point if necessary
· Original RivaTuner's monitoring history fragment selection and selected fragment processing functionality is back! Now you may hold <Shift> and press left mouse button on initial desired position in hardware monitoring window to begin fragment selection, then drag mouse cursor to desired final position and release left mouse button to select a fragment. The following functionality is available for selected fragments:
· When the fragment is selected, minimum and maximum displayed values are estimated within selected fragment only. This feature can be used if you don't need the global minimum and maximum values, estimated during whole monitoring session, and wish to see local minimum and maximum values estimated within some shorter period of time (e.g. during benchmark application runtime only)
· When the fragment is selected you may use the context menu of any graph to set tracking marker into the local minimum or maximum position within the selection. This feature can be used to automate the process of identifying and visualizing the moments of reaching peak values (e.g. peak GPU temperature) on desired fragments
· Added new open source GPU plugin. The plugin shows third party developers how to extend MSI Afterburner's GPU monitoring functionality and implement own GPU specific sensors in plugins using GPU enumeration and identification API. The plugin is demonstrating implementation of D3DKMT GPU performance counters providing unified vendor agnostic per-engine GPU usage, dedicated and shared memory usage monitoring
· RTSS has been upgraded to slightly newer build, which fixes the problem with screen capture feature in On-Screen Display preview window when RivaTuner Statistics Server is installed in UAC-protected folder

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/[Guru3D.com]-MSIAfterburnerSetup450Beta5.rar

 

This video is demonstrating:

- Fast OSD setup from scratch with keyboard shortcuts and multi-selection functionality. It is not actually new for 4.5.0 and it was available in the previous version, but too few users actually read the context help and use this functionality. And multi-selection functionality can actually speed up the process of configuring OSD.
- Process specific memory monitoring with PerfCounter plugin
- Monitoring history selection and local min/max values detection
- Monitoring performance profiler usage, helping you to identify and disable most performance hungry sensors
ანვინდერის ატვირთული ვიდეოა მაგ ახალი ფიშკების გასააქტიურებლათ

Link to comment
Share on other sites

  • 3 weeks later...

MSI AB 4.5.0 RC გამოვიდა შემდეგი ჩეინჯლოგით:

 Minimum, average, maximum, 1% low and 0.1% low framerates are now displayed in On-Screen Display with special text formatting tags introduced by new RivaTuner Statistics Server. The tags are allowing On-Screen Display clients to display independent benchmark statistics simultaneously for multiple running 3D applications instead of displaying foreground 3D application statistics only
· Improved default MSI Cyborg White skin. Monochrome on / off states of fan speed auto button were hardly identifiable before, they are more contrast now 
· Added power user oriented restore points system. Experienced users may use new /backup and /restore command line switches to create multiple named restore points containing full backups of MSI Afterburner’s settings (including hardware profiles and custom hardware monitoring plugin configurations) and restore settings from any previously created restore point if necessary
· Improved hardware monitoring module:
o Improved built-in performance profiler. Now you may enable “Show profiler panel” option is the context menu of hardware monitoring window to see additional panel with detailed per-sensor polling statistics in hardware monitoring window status area. Polling statistics visualizes information about the slowest polled sensors with maximum polling time, so power users can easily identify problematic sensors eating most of CPU time on each polling period (e.g. abnormally slow GPU power sensor in some versions of NVIDIA drivers)
o Improved correction formulas support. Now in addition to “x” variable representing current data source the formulas may also use sibling data sources. For example, you may use “x – “RAM Usage”” correction formula for “Pagefile usage” (commit charge) data source to subtract RAM usage from displayed value
o Fixed incorrect tracking markers rendering on the graphs dynamically added to hardware monitoring module
o Fixed incorrect tracking markers rendering when monitoring ring data buffer is full
o Added experimental support for Intel i7 and i9 7XXXX LGA2066 CPUs
o Added CPU package power monitoring for Intel CPUs
o Minimum sampling interval for CPU usage calculation has been reduced from 1000ms to 100ms
o Original RivaTuner’s monitoring history fragment selection and selected fragment processing functionality is back! Now you may hold <Shift> and press left mouse button on initial desired position in hardware monitoring window to begin fragment selection, then drag mouse cursor to desired final position and release left mouse button to select a fragment. The following functionality is available for selected fragments:
§ When the fragment is selected, minimum and maximum displayed values are estimated within selected fragment only. This feature can be used if you don’t need the global minimum and maximum values, estimated during whole monitoring session, and wish to see local minimum and maximum values estimated within some shorter period of time (e.g. during benchmark application runtime only)
§ When the fragment is selected you may use the context menu of any graph to set tracking marker into the local minimum or maximum position within the selection. This feature can be used to automate the process of identifying and visualizing the moments of reaching peak values (e.g. peak GPU temperature) on desired fragments
o Improved monitoring plugins architecture:
§ Added plugin descriptions to plugins selection window
§ Added new SetupSource API function allowing you to configure the plugins. This function is allowing you to customize the plugins either globally from plugin selection window (e.g. configure whole list of data sources exported by each plugin) or customize desired data source only directly from corresponding graph properties window (e.g. change network download rate units from MB/s to KB/s). SetupSource function usage is demonstrated in SDK in updated AIDA64 and PerfCounter plugins
§ Added new GetHostAppProperty API function allowing the plugins to retrieve various properties from the host application (i.e. MSI Afterburner), e.g. retrieve GUI color scheme specific to currently selected skin. GetHostAppProperty function usage is demonstrated in SDK in updated AIDA64 and PerfCounter plugins
o Improved monitoring plugins:
§ Now the plugins store user customized and built-in default configurations in separate files, so your custom plugin settings won’t be lost on new version install
§ Added configuration GUI for AIDA64, HwInfo and PerfCounter plugins. Each plugin’s user interface is allowing you to edit the list of sensors exported by each plugin, export full list of available sensors to a text file, customize each sensor’s properties or reset plugin settings to defaults
§ Improved PerfCounter plugin:
· Added support for performance counters with non-localized names (e.g. “GPU Engine” under Windows Fall Creators Update)
· Added support for dynamic data sources. Dynamic data sources are not validated during creation, such sources are allowed to export no data until some condition is met (e.g. “CPU usage” performance counters specific to some target process export data only when the process is running)
§ Improved SMART plugin:
· Added airflow temperature SMART attribute support for Intel/Samsung SSDs.
§ Added new CPU plugin:
· The plugin fully duplicates MSI Afterburner’s built-in CPU temperature monitoring implementation (with the only exception of AMD Ryzen codepath, which cannot be open sourced due to NDA) and shows third party plugin developers how to implement low-level CPU specific sensors in plugins using CPU MSR registers and PCI configuration space access API
§ Added new GPU plugin:
· The plugin shows third party developers how to extend MSI Afterburner’s GPU monitoring functionality and implement own GPU specific sensors in plugins using GPU enumeration and identification API. The plugin is demonstrating implementation of D3DKMT GPU performance counters providing unified vendor agnostic per-engine GPU usage, dedicated and shared memory usage monitoring 
· Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
· RivaTuner Statistics Server has been upgraded to v7.1.0

RTSS v7.1.0:

· Added On-Screen Display locking mechanism for third party On-Screen Display client applications. The mechanism is aimed to eliminate unwanted On-Screen Display flickering effect when some client application is performing risky two-stage On-Screen Display refresh while On-Screen Display is being actively refreshed by another client. Please take a note that third party On-Screen Display clients must be also updated in order to use this mechanism and get rid of flickering
· Added new text formatting tags support for displaying minimum, average, maximum, 1% low and 0.1% low framerates in benchmark mode. The tags are allowing On-Screen Display clients to display independent benchmark statistics simultaneously for multiple running 3D applications instead of displaying foreground 3D application statistics only
· Now it is possible to adjust frametime history graph size via RivaTuner Statistics Server properties. Please take a note that you may use positive values to specify the size in pixels or negative values to specify it in symbols
· Now it is possible to toggle benchmark mode state from RivaTuner Statistics Server properties. However, third party benchmark client applications like MSI Afterburner are still required to toggle benchmark mode state with hotkeys during 3D application runtime and to save benchmark results to a text file
· Now it is possible to toggle between averaged or instantaneous calculation modes for peak (i.e. minimum and maximum) framerates for benchmark mode via RivaTuner Statistics Server properties
· Fixed issue in context help system, which could cause the tooltip to flicker when it was displayed below mouse cursor
· Fixed screen capture feature in On-Screen Display preview window when RivaTuner Statistics Server is installed in UAC-protected folder
· Updated SDK:
o Now RTSSSharedMemorySample sample code is demonstrating the implementation of On-Screen Display locking and flickering filter 
· Updated profiles list
 

ესეც გადმოსაწერი ლინკი: http://download-eu2.guru3d.com/afterburner/MSIAfterburnerSetup450Build12819.rar

Link to comment
Share on other sites

ფინალურიც გამოვიდა http://www.guru3d.com/files-get/msi-afterburner-beta-download,33.html ჩეინჯოგი მგონი იგვე დარჩა, აქ შეიძლება ნახვა სრული ჩეინჯლოგის: 

http://www.guru3d.com/files-details/msi-afterburner-beta-download.html

Link to comment
Share on other sites

მაინინგისთვის ვერაფრით ვერ დავამახსოვრებინე 5 კარტისთვის სხვადასხვა რაზგონის ნასტროიკები, მერე ამ ფოლდერში C:\Program Files (x86)\MSI Afterburner\Profiles რა ფაილებიც იყო ამოვშალე და ხელახლე დავამახსოვრებინე 5 პროფილში ხუთი სხვადასხვა კარტის ნასტროიკა და აი აქედან დამატების შემდეგ ავტომატურათ ირთვება ეგ პროფილები ყოველი ვინდოუსის რესტარტის შემდეგ:

hzq6BJs.png

დეფოლტზე მაინინგი სისულელეა და ხელით ხელახლა ნასტროიკების შეყვანას ყოველი რესტარტის შემდეგ ბევრი დრო მიქონდა, იქნება ვინმეს გამოადგეს პირველ რიგში მაინინგისთვის, რახან 1-2 კარტაზე დასეივების პრობლემა მგონი არა აქვს

Link to comment
Share on other sites

  • 4 weeks later...

RTSS 7.2.0 beta 1 გამოვიდა უზარმაზარი ჩეინჯლოგით:

· Added On-Screen Display performance profiler. Power users may enable it to measure and visualize CPU and GPU performance overhead added by On-Screen Display rendering. Two performance profiling modes are available: 
o Compact mode provides basic and the most important CPU prepare (On-Screen Display hypertext formatting, parsing and tessellation), CPU rendering and total CPU times, as well as GPU rendering time (currently supported for Direct3D9+ and OpenGL applications only)
o Full mode provides additional and more detailed per-stage CPU times
· Improved built-in framerate limiter:
o Added power user oriented profile setting, allowing you to specify the limit directly as a target frametime with 1 microsecond precision
o Added power user oriented profile setting, allowing you to adjust throttle time. Throttle time adjustment is aimed to reduce input lag when framerate is below the target limit or without limiting the framerate
o Added power user oriented profile setting, allowing you to synchronize framerate to up to two independent scanline indices per refresh interval. Combining with user configurable scanline wait timeout, those settings provide experienced users low input lag adaptive VSync or double VSync functionality on any hardware
· Various On-Screen Display optimizations and improvements:
o Added adjustable minimum refresh period for On-Screen Display renderer. The period is set to 10 milliseconds by default, so now the On-Screen Display is not allowed to be refreshed more frequently than 100 times per second. Such implementation allows keeping smooth animation when On-Screen Display contents are being updated on each frame (e.g. when displaying realtime frametime graph) without wasting too much CPU time on it
o Added alternate GPU copy based Vector2D On-Screen Display rendering mode implementation for Direct3D1x applications. New mode provides up to 5x Vector2D performance improvement on NVIDIA graphics cards, however it is disabled on AMD hardware due to slow implementation of CopySubresourceRegion in AMD display drivers
o Vector2D rendering mode is now forcibly disabled in Vulkan applications on AMD graphics cards due to insanely slow implementation of vkCmdClearAttachments in AMD display drivers
o Revamped geometry batching and vertex buffer usage strategy in pure Direct3D12 On-Screen Display renderer (currently used in Halo Wars 2 only)
o Added Vector2D rendering mode support to pure Direct3D12 On-Screen Display renderer
o Optimized On-Screen Display hypertext parsing and tessellation implementation
o Optimized state changes in OpenGL On-Screen Display rendering implementation
o Optimized state changes in Direct3D1x On-Screen Display rendering implementation
o Solid rectangles and line primitives in Direct3D8 and Direct3D9 On-Screen Display rendering implementations are now rendered from vertex buffer instead of user memory 
o Improved OpenGL framebuffer dimensions detection when framebuffer coordinate space is selected
· Fixed On-Screen Display rendering in wrong colors when Vector2D mode is selected and Direct3D1x applications use 10-bit framebuffer
· Fixed Vulkan fence synchronization issue, which could cause GPU-limited Vulkan applications to hang due to attempt to reuse busy command buffer
· Active busy-wait loop in the framerate limiter module is now forcibly interrupted during unloading the hooks library to minimize the risk of deadlocking 3D application when dynamically closing RivaTuner Statistics Server during 3D application runtime
· Improved synchronization in 32-bit hook uninstallation routines 
· Updated profiles list

A few notes about new toys for power users:

New performance profiler

Performance profiler can be enabled by setting PerformanceProfiler field in [OSD] section to 1 (basic mode) or 2 (detailed mode). "Show own statistics" must be enabled in RTSS to see the profiler. The following performance counters are available for detailed mode:

CPU acquire – CPU time, spend on acquiring access to 3D API. This CPU time depends on 3D API used by application, in most cases it is zero, for D3D12 applications displaying OSD in D3D11on12 mode it is CPU time spend on acquiring D3D11on12 wrapper for rendering, in Vulkan applications asynchronically presenting frames from compute queue (e.g. DOOM or Wolfenstein II on AMD cards) it is CPU time spend on synchronizing graphics and compute queues. For OpenGL applications it can be nonzero if application is forcibly flushing the pipeline in the end of each frame rendering with glFlush. CPU acquire stage is executed on each frame.

CPU prepare – CPU time spend on preparing OSD contents for rendering. This CPU time doesn’t depend on 3D API used by application, it entirely depends on the amount of text/graphs you’re displaying in OSD. CPU prepare time is divided into the following substages: init, parse and tessellate. Init is CPU time spend on formatting own RTSS OSD contents (i.e. formatting own framerate counters, scanning hypertext and replacing framerate macro with real formatted framerate values, formatting performance counters, benchmark statistics etc). Parse is CPU time spend on parsing resulting OSD hypertext (including the hypertext supplied by OSD clients like MSI AB or HwInfo), processing hypertext formatting tags and preparing OSD contents as collection of text with attributes to be tessellated on the next stage. Tessellate is CPU time spend on converting parsed OSD text and attributes to renderable form (collection of vector rects for each symbol for vector 2D/3D OSD rendering modes or collection of textured quads for each symbol for raster 3D mode). CPU prepare stage is executed on the frames when OSD contents is refreshing, i.e. if you’re displaying OSD with framerate counter and default refresh rate in RTSS properties (500 ms), then OSD is refreshing and this stage is executed just twice per second.

CPU render – CPU time spend on rendering OSD. This CPU time depends on 3D API used by application and on OSD rendering mode selected in RTSS (Vector2D, Vector3D or Raster3D). CPU render time is divided into the following substages: save, submit and restore. Save is CPU time spend on saving 3D rendering pipeline state before rendering OSD. This substage entirely depends on 3D API used by application, for example state changes are most expensive for Direct3D9 applications (especially pure Direct3D9 ones). Low-level 3D APIs (pure Direct3D12 or Vulkan) do not require saving pipeline state, so this CPU time is zero. Vector2D OSD rendering mode also doesn’t require saving and restoring rendering pipeline state, so it is zero in this case too. Submit is CPU time spend on filling vertex buffers with previously tessellated OSD geometry and submitting it to 3D API. Restore is CPU time spend on restoring previously saved 3D rendering pipeline state after drawing OSD. CPU render stage is executed on each frame.

CPU capture – CPU time spend of capturing framebuffer contents. This stage is executed and this time is not equal to zero during videocapture only.

CPU flush – CPU time spend on the final stage of flushing OSD renderer and returning control to application’s 3D API. This time is D3D11on12 wrapper flushing time D3D12 applications displaying OSD in D3D11on12 mode. For applications using different 3D APIs it is zero. This stage is executed on each frame.

CPU total – total CPU time including all stages listed above.

GPU render – GPU time spend on rendering OSD. This performance counter is currently collected for Direct3D9, Direct3D10, Direct3D11, Direct3D12 applications displaying overlay in D3D11on12 mode and OpenGL applications only. GPU render time profiling is currently not supported for Vulkan and pure Direct3D12 applications.

New scanline sync based framerate limiter

Before you start experimenting with new sync mode, it is recommended to enable diagnostic scanline sync related info in OSD by setting SyncInfo field in [OSD] section to 1. "Show own statistics" must be also enabled in RTSS to see it. New scanline sync based framerate limiter is controlled by the following values:

SyncDisplay – name of logical display device to be synchronized with. Currently it is a primary display name.

SyncScanline0 – index of the first scanline for framerate synchronization. No synchronization is performed when it is set to zero, otherwise this is treated as scanline index starting from top of the frame. E.g. SyncScanline0=1 means that the frame will be synchronized with the top (or more precisely the second scanline, because indices are zero based) scanline and SyncScanline0=1000 means that the frame will be synchronized with scanline 1000 (which is located in the bottom part of screen if we use 1080p mode with 1125 scanlines total).

SyncScanline1 – index of the second scanline for framerate synchronization. Defining two independent sycnhronization points per refresh allows us to get functionality of double VSync, i.e. you get smooth 2xRefreshRate framerate). No synchronization is performed when it is set to zero, otherwise this is treated as index starting from middle of the frame. E.g. SyncScanline1=1 with total 1125 scanlines means that the frame will be synchronized with the scanline 562(1125/2)+1=563 and SyncScanline1=400 means that the frame will be synchronized with scanline 562(1125/2)+400=962 (which is located in the bottom part of screen if we use 1080p mode with 1125 scanlines total). 

SyncTimeout – allows adjusting timeout for scanline synchronization. The timeout provides functionality similar to NVIDIA’s Adaptive VSync, meaning that you may forcibly disable synchronization when framerate drops below the refresh rate. Timeout can be specified either explicitly in microseconds (e.g. SyncTimeout=16667 for 60Hz refresh rate) or you can let RTSS to benchmark and calibrate it automatically and set it to 1/N of refresh time when SyncTimeout=N is in [1,8] range). 

Summarizing, you may start experiments with scanline sync with the following presets:

For traditional VSync with low input lag:

Code:
SyncScanline0=1
SyncScanline1=0
SyncTimeout=0
In this case tearline position is fixed in the top of frame, so you can move it down via tuning and increasing SyncScanline0 value.

For adaptive VSync with low input lag on 60Hz refresh rate:

Code:
SyncScanline0=1
SyncScanline1=0
SyncTimeout=16667
or calibrate timeout automatically:

Code:
SyncScanline0=1
SyncScanline1=0
SyncTimeout=1
For double VSync (i.e. 2x refresh rate framerate, 120FPS for 60Hz refresh rate)

Code:
SyncScanline0=1
SyncScanline1=1
SyncTimeout=0
In this case tearlines will be in the top and in the middle of frame, you can move it down via synchronically increasing SyncScanline0 and SyncScanline1 values. To control timeout in such case use either explicit value:

Code:
SyncScanline0=1
SyncScanline1=1
SyncTimeout=8333
or calibrate timeout automatically:

Code:
SyncScanline0=1
SyncScanline1=1
SyncTimeout=2

საკმაოთ საინრერესო რაღაცეებია დამატებული ისე, აი გადმოსაწერი ლინკიც ვინმეს თუ დატესტვა მოუნდება:

http://www.guru3d.com/files-get/rtss-rivatuner-statistics-server-download,15.html

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...