nickbabcock / Pfim

.NET Standard targa (.tga) and direct draw surface (.dds) image decoder
https://nickbabcock.github.io/Pfim/
MIT License
108 stars 18 forks source link

DDS: support for DXGI_FORMAT-like enumerations #22

Open Krakean opened 6 years ago

Krakean commented 6 years ago

@nickbabcock Hi! Can you please add support for parsing "dxgi" listed here - https://msdn.microsoft.com/en-us/library/windows/desktop/bb173059%28v=vs.85%29.aspx ? Actually, you have ImageFormat, which is in some way do same thing (but also specifies formats that library actually support or was able to detect), but constants listed in microsoft documentation are kinda standard, and thus a bit easier to understanding/perception.

nickbabcock commented 6 years ago

This is for DX10 dds images, correct? Yeah Pfim will need to have this enumeration in the dx10 parser. Then maybe some sort of conversion over to ImageFormat as well.

Krakean commented 6 years ago

@nickbabcock yes, it's for >=dx10 Dx9 have a bit different formats list, I gave you link on it in #21

Krakean commented 6 years ago

@nickbabcock Just curious, how is going on progress on dx10 dds support? :)

nickbabcock commented 6 years ago

Good! Now that Pfim will take a PfimConfig option to tweak compression and target format, there is a clear way forward for handling the uncommon formats like R16G16. Being able to decode any dds format into any target format is a tall order, so I'm unsure if the next version (0.6) will support all of them. Is there a dx10 dds format that is of particular interest to you (I keep using R16G16 as an example, but if there is one that you have need I can test with that first)

Krakean commented 6 years ago

Is there a dx10 dds format that is of particular interest to you

None, for now. As in previous time with tickets to dds/tga, will find out when will test new Pfim version :)

By the way, just one question out of curiosity - how is progress on bc6/7?

nickbabcock commented 6 years ago

how is progress on bc6/7

Ah, no progress as of yet!