for part of why it is lower than expected. However, it does seem that Kingston (if they are really Kingston) is skimping on their capacity. A card with 64,000,000,000 usable bytes should be closer to 59.6 GB (64,000,000,000/2^30)
The camera require the cards to be in FAT32 format. If you take the card out of the camera after formatting with the camera, put the card in your pc, and look at the format, it will be formatted as FAT32, and no longer exFAT.
I just tried this with a MicroCenter 64GB card. Originally formatted with label and in NTFS format. Put it in the v2 camera, and it did not recognize the card, no ding-ding sound. Took it back out, put in USB adapter and formatted on Win 10 as exFAT (Win 10 GUI format program doesn’t give the option to format cards larger than 32 as FAT32). Put the card back in the v2 camera, and got the ding-ding. Then went to advanced setting, local storage, format. The after formatting, the card displayed 58.2 GB available. Then removed the card, put back in PC and rich clicked and looked at properties. FAT32 format, label erased, capacity 62,530,895,872 bytes (58.2 GB which agrees with camera). Note that this MicroCenter card was 2.3% below what it claimed (64 billion bytes), but still more than the “Kingston” card. The formatting data used (windows reports 1.2 MB used) is down in the noise level, it reports both available and capacity as 58.2 GB. The camera also creates a folder time_lapse when it formats the card.
For others reading: NTFS formatted cards are not even seen by the camera. If your card isn’t seen, format to exFAT first, then format with camera to FAT32. And before deploying, a run of h2testw is worthwhile to verify that the card actually has the capacity it reports it has.