WinPixEventRuntime 2102.09: Minor fixes and optimizations

Matt Amert

Matt

It’s hard to believe it’s been over a year since our last update to WinPixEventRuntime! This update brings a couple of minor fixes and optimizations, which should hopefully lead to a slightly better quality of life when using the runtime 😊

You can download the new runtime here.

Release notes:

  • Fixed a bug where PIX could occasionally show an incorrect event hierarchy if the title called PixBeginEvent with format string arguments. This happened because PIX couldn’t successfully determine when the event ended.
  • Fixed C4100 warnings in PIXEvents.h header.
  • Optimization: Removed a branch when timing captures are not running.
  • Updated license and icon for new NuGet requirements.

Known Issue:

  • On ARM64 devices, the Debug Layer will emit a D3D12 debug error if you use PixBeginEvent. This is an issue in the Debug Layer and will be fixed shortly.
    • In the meantime, you can work around the issue using a few different methods (only one method is needed):
      • On devices running Windows 10 version 2004 or newer:
        • Run the command: d3dconfig message-mute --add-id-12 3
        • Don’t forget to remove it later with: d3dconfig message-mute --remove-id-12 3
      • In dxcpl, add “CORRUPTED_PARAMETER1 (D3D12)” to the Mute Message ID list.
      • In your code, call the function ID3D12InfoQueue::AddStorageFilterEntries with D3D12_MESSAGE_ID_CORRUPTED_PARAMETER1 included in the DenyList.
    • Keep in mind that these workarounds will prevent any other CORRUPTED_PARAMETER1 messages from showing, which may be legitimate issues.

As always, feel free to reach out to us with any questions or feedback on our Discord Server, or simply use the little feedback button in the top right corner of your PIX window.

0 comments

Leave a comment