6/28/2019 – Beta version 0.9.4124.26691055 – Initial Release
 
Please contact NVIDIA with any issues or suggestions.
 
**Known Issues***
 
• AMD Power API reports unknown value; neither chip nor board power. Until AMD describes what their API is reporting, NVIDIA to AMD power comparisons are NOT apples-to-apples.
• Power is not correctly reported while in idle mode. Ensure that the GPU is under load for accurate power measurements with FrameView.
• FrameView default benchmark folder location path may not exist. Ensure that you selected a valid path before testing.
• The FrameView overlay is sometimes delayed when hooking into applications.
• Using FrameView to collect logs in gaming applications often leads to collection of separate log files for Chrome, DWM, or other open applications.
• Overlay section of GUI may flicker. 
• Overlay will not appear in DX9 and Vulkan titles. However, logging works with all APIs including DX9/10/11/12, OpenGL, and Vulkan.
• Running FrameView and Fraps simultaneously will cause the FrameView overlay to disappear. Please refer to the Troubleshooting section of the User Guide for instructions to overcome this.
• Rarely, power is displayed as 0 in the FrameView overlay. Run uninstall.cmd and then install.cmd again to resolve this issue.
• AMDPWR is shown only when both rendered and displayed FPS are selected in the FrameView GUI.
• Occasionally, Quake 2 RTX crashes when FrameView is active.
• Some games including Forza Horizon 4 crash when FrameView is active due to anti-cheat mechanism built into the game.
