Please let me know if there is a more appropriate forum within which to ask
this question.
I am considering switching to squish (from nvDXT) if it will solve the
following issue(s):
What steps will reproduce the problem?
in nvDXT (a somewhat old version):
1. Debug seems to be changing the FP (x86) control word (I can tell because
it is not restoring it on return), where Release seems to not be changing
it (or maybe is, but then _is_ restoring it, not sure)
2. If I build Debug v Release, my compressed image will be different (even
if I call _controlfp(_PC_24, _MCW_PC);)
3. Comments online concerning the CUDA library (in software mode) indicate
that the output may be different based on the compile flags, compile target
(32bit/64bit), and (more troublesome) on the specific machine the
compression is run on.
4. I am concerned (though have not confirmed) that compressing the same
source data may result in different target data if they occur during the
same application instance (possibly due to "leftover" state of memory
within the nvDXT lib from a previous compression).
What is the expected output? What do you see instead?
Is there a way to configure squish such that I can get reliable results
regardless of the machine/compile target/build I am running? It seems that
nvDXT is not.
What version of the product are you using? On what operating system?
not using it yet. Windows
Please provide any additional information below.
I am using DXT1 compression on many machines within a team and am trying to
use CRC checks to confirm consistency. I understand that DXT1 compression
at large does not mandate identical results, but since all machines will be
running the same code I would like to be able to get identical results from
identical source data on all of the machines on my team.
Thank you for your consideration/help.
Original issue reported on code.google.com by kpatel...@gmail.com on 11 Jun 2009 at 9:12
Original issue reported on code.google.com by
kpatel...@gmail.comon 11 Jun 2009 at 9:12