Matt is PR person and he is not a software developer. And no, there are no AMD APIs supporting it for Fiji. Please stop pushing your desires that actively, I CANNOT help you with that.

Click to expand...

Hello and thankyou for the reply.

Have I offended you in any way because I asked as politely as possible on behalf of all Fiji owners? How is that I quote 'Pushing your desires'?

With the upmost respect your reply is quite hostile for someone only requesting information on this subject. I wasn't demanding anything I was only requesting for some of your valuable time to maybe dig deeper? No-one else in this world is capable so of coarse you will see me here requesting your expertise. I don't know what you have already back engineered and I guess you have already figured out the API. I apologize for wasting your time.

I need to ask one more question if I may? How is the AMD driver reverting even a modified bios? I believe the API is deliberately reverting any setting applied to the HBM. If this is true then the API can be altered. If you could point us in the right direction we can do the rest.

Have I offended you in any way because I asked as politely as possible on behalf of all Fiji owners? How is that I quote 'Pushing your desires'?

With the upmost respect your reply is quite hostile for someone only requesting information on this subject. I wasn't demanding anything I was only requesting for some of your valuable time to maybe dig deeper? No-one else in this world is capable so of coarse you will see me here requesting your expertise. I don't know what you have already back engineered and I guess you have already figured out the API. I apologize for wasting your time.

I need to ask one more question if I may? How is the AMD driver reverting even a modified bios? I believe the API is deliberately reverting any setting applied to the HBM. If this is true then the API can be altered. If you could point us in the right direction we can do the rest.

Click to expand...

I said that I cannot help with Fiji HBM clock control a few times, no need to discuss it over and over again. I cannot help you with that, take it as a fact please.

@Unwinder
I noticed ...Sometimes in games I just notice on the OSD, that ingame the memory clock is just running at 2 Ghz instead of 2.1 Ghz. Then I have to adjust the memory Overclock to +400, to get my 2.1 Ghz.

I can confirm that Rivatuner Statistics Server (RTSS) was causing the d3d9 0xc0000409 exception on my system when attempting to launch Handbrake. Closing RTSS before opening Handbrake mitigates this. Alternatively a profile can be created for Handbrake with the 'None' option selected under the 'Application detection level' entry. Doing so will allow both applications to run in harmony since its hook isn't taking place.

· 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

I would like if I could enable the 1% low and 0.1% low regulary in the OSD and not just in benchmarkmode.

Click to expand...

You can do it easily. Benchmark mode state is permanent, wchich means that you may press "Begin benchmark recording" hotkey just once and after that it will stay active for all subsequently started 3D applications, even after rebooting the system. But keep in mind that 1/0.1% low statistics calculation requires storing and processing full set of slowest frametimes since the beginning of benchmark, and the buffer for storing that data in realtime is not infinite. For RTSS I selected it to keep up to 1024 slowest frames, which is a good balance for memory usage/realtime sort performance and it provides statistically correct 1/0.1% low results for up to 30 minutes of testing on 60 FPS framerate. So keep it in mind while using longer benchmarking sessions.

Ah I understand! I didn`t think about the buffer because the statistics have to base on something. So it wouldn`t make sense when they are permanently active. My fault. But I understand what you mean. Thanks.

Ah I understand! I didn`t think about the buffer because the statistics have to base on something. So it wouldn`t make sense when they are permanently active. My fault. But I understand what you mean. Thanks.

Click to expand...

Also I have to add that statistics is reset for each new started 3D application, and you can also always press “Begin benchmark recording” hotkey one more time to reset the statistics if necessary. So it is safe to keep it always on.