Mifare-Windows-Tool VS PresentMon

Hi, my new beta release of Mifare windows tools can make conversion from/to Android (MCT) / Libnfc (MWT) / flipper Zero --> https://github.com/xavave/Mifare-Windows-Tool/releases/tag/beta1.5.8370.41492

nfc-mfclassic W b cardtocopy.dmp blank.dmp (after dumping both cards with mfoc). I use MWT (https://github.com/xavave/Mifare-Windows-Tool, which uses mfdread to read the dumps and display the next to each other) to read both cards and compare them, and as far as I can see they're identical.

Now that you have your card it’s time to write to it. Different operating systems does things a little bit differently. On windows theres some different tools that you can use but i recommend https://github.com/xavave/Mifare-Windows-Tool which has a simple setup process and nice buttons

Use PresentMon to figure out if it's a CPU or GPU issue. (GPUBusy)

EDIT - Intel's Presentmon has a "gpu busy" metric kinda designed to tell you if the gpu is waiting on the rest of the system and it's platform independent so should work with amd/nvidia stuff. https://game.intel.com/story/intel-presentmon/

You can also check the presentation latency with PresentMon

Borderless for DX12 and Vulkan games has no input delay. In fact those APIs don't have exclusive fullscreen support anymore. Why would the engineers who designed those get rid of "exclusive fullscreen" support if it wasn't useful? In fact most new games which offer a "fullscreen" option are faking it, you can use PresentMon to see which DXGI presentation mode is being used.

This behaviour can be monitored using PresentMon (best used on a second display) as well. This new DXGI layer would appear as Composed: Flip, Hardware: Independent Flip, or Hardware Composed: Independent Flip, while classic methods would appear as Hardware: Legacy Flip (if FSE was engaged) or Composed: Copy with GPU GDI.