Hi Tobias,
Normal
0
false
false
false
EN-GB
X-NONE
X-NONE
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
Hi Joe,
This is still the case I'm afraid - for legal reasons we had to disallow this
as DXT compression/decompression should only be available on licensed
platforms.
The reason these tokens are not if def'd out is simply because they're in a
public header, and it's perfectly acceptable to handle the texture data on
MacOS, as long as no encoding/decoding is done. Information about the format
needs to be known to work out how big the texture data is for example.
Thanks,
Tobias
Just to be sure that I understand it right. DXT compression wil never be available on MacOSX ?
I was just about to post about the issue but I’m glad I did a quick lookup first.
What about libsquish ? It runs on MacOSX…
Hi Micha,
The issues are more complex than it seems on the face of it - and I can’t really go into the details about these reasons, I’m not a lawyer and can’t comment on legal issues on a public forum - sorry
However, I can say that for now, no we won’t support DXTC on MacOS or Linux. It’s something I’m attempting to see if we can support in future, but I can’t enable it unless we get a legal green light on the issue.
Regards,
Tobias