# IEEE Floating-Point 128-bit: A32B32G32R32F support in PVRTexTool and PVRTexLib

**URL:** <https://forums.imgtec.com/t/ieee-floating-point-128-bit-a32b32g32r32f-support-in-pvrtextool-and-pvrtexlib/2596>\
**Category:** PowerVR Insider\
**Tags:** pvrtextool\
**Created:** [February 26, 2018, 8:33am UTC](https://forums.imgtec.com/t/ieee-floating-point-128-bit-a32b32g32r32f-support-in-pvrtextool-and-pvrtexlib/2596 "2018-02-26T08:33:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![saneesh](https://avatars.discourse-cdn.com/v4/letter/s/45deac/32.png) [@saneesh](https://forums.imgtec.com/u/saneesh)\
**Post date:** [February 26, 2018, 8:33am UTC](https://forums.imgtec.com/t/ieee-floating-point-128-bit-a32b32g32r32f-support-in-pvrtextool-and-pvrtexlib/2596/1 "2018-02-26T08:33:05Z")

</div>

Hi All,  
I have created a DDS file in IEEE Floating-Point 128-bit: A32B32G32R32F using DirectX Texture Tool. When viewed that DDS file in PVRTexTool the rendering result was totally different when compared with DirectX Texture Tool.

I have attached a simple DDS file(A32B32G32R32F.dds inside the A32B32G32R32F\_Issue.zip) which can reproduce the issue.

Similar test was performed using Floating-Point 64-bit: A16B16G16R16F. But the rendering result was exactly the same in both DirectX Texture Tool and PVRTexTool.

Side by side image comparison is added for both A16B16G16R16F(A16B16G16R16F\_Comparison.png) and A32B32G32R32F(A32B32G32R32F\_Comparison.png)

What is the reason for the issue?

Note  
The same issue is present in the PVRTexLib also. That is when a dds file in the A32B32G32R32F format is saved to dds file the image seems to be strange.