Closed GoogleCodeExporter closed 9 years ago
Original comment by cast...@gmail.com
on 28 Nov 2007 at 3:15
Original comment by cast...@gmail.com
on 28 Nov 2007 at 3:23
I really miss the "-rescale nearest" feature that the older texture tool had.
Any
news on the progress of implementing some of the features the old version had?
Where
can I find a full pdf with a user guide for nvcompress.exe like we had for
nvdxt.exe?
Original comment by eri...@gmail.com
on 28 Jan 2008 at 1:58
This is almost implemented now. The only reason why the bug is not closed is
because
it has not been tested extensively, and I'm not fully satisfied with the
complexity
of the resulting code.
The main problem is that the input takes a mipmap pyramid, and when you want the
output to be rescaled, the provided mipmaps can either be ignored and
regenerated, or
you could try to find the closes mipmap for every rescaled output mipmap. I'm
implementing the latter, and it's a bit of a mess.
I'd like to revisit the code, try to clean it up, and possibly implement a
simpler
approach.
Regarding the documentation, there's extensive documentation of the API on the
wiki at:
http://code.google.com/p/nvidia-texture-tools/wiki/ApiDocumentation
and I'm planning to document the command line tools at:
http://code.google.com/p/nvidia-texture-tools/wiki/CommandLineTools
You can track the progress of the documentation with Issue 20:
http://code.google.com/p/nvidia-texture-tools/issues/detail?id=20
Original comment by cast...@gmail.com
on 28 Jan 2008 at 8:48
Support for scaling is now fully implemented, and reasonably tested. You can
find the
documentation of the available rescaling options at:
http://code.google.com/p/nvidia-texture-tools/wiki/ApiDocumentation#Image_Resizi
ng
Original comment by cast...@gmail.com
on 3 Feb 2008 at 8:21
Original issue reported on code.google.com by
Michael....@gmail.com
on 26 Sep 2007 at 4:46