- February 5, 2012 at 11:21 am #30749
Just a quick question: does the PVRTextTool support the generation of a specified number of mipmap levels? The GUI version lets me choose none, 1-9 or all mipmap levels, but for the command line version it seems there’s only the -m switch that either turns on all or none of the mipmap levels.
In an older thread (https://www.imgtec.com/forum/forum_posts.asp?TID=1007), Gordon mentioned that this functionality was not available in the command line version, but a while later (https://www.imgtec.com/forum/forum_posts.asp?TID=1205) Tobias responded to a similar question about this and other issues that the issues would get taken care of – any update on this? This functionality would be really nice to have and save me from having to somehow automate the GUI version.
I’m actually quite puzzled as to why you wouldn’t just expose ALL the functionality of the GUI version on the command line – here (https://www.imgtec.com/forum/forum_posts.asp?TID=1958) is another post from someone who needs the dithering option from the GUI and hence can’t use the command line tool either and is also thinking about having to automate the GUI: it seems that the whole point of having a command line tool for automation purposes is defeated if that tool doesn’t expose all the necessary functionality. Is there any good reason as to why you would purposefully choose not to expose certain functions?February 6, 2012 at 7:52 am #35460
Unfortunately there is still a lack of functionality in the CL version compared to the GUI – I’ve been attempting to reconcile them (dithering is actually supported as seen from my reply for example) however the mip-mapping functionality is something that I appear to have missed, for which I apologise! Everything else in that post has been reconciled. Sadly at this point it’s too late to add new functionality to our next release, but the functionality will be making it into the release after that as I am planning to undertake an interface overhaul for the command line and GUI versions to make sure that everything possible is supported.
TobiasFebruary 6, 2012 at 8:31 am #35461
Just for your information, I’ve filed this as a bug in our internal bug tracker under BRN35896. Look out for this number in our release notes and it should let you know when it’s been fixed.
TobiasApril 3, 2013 at 8:11 am #35462
Hello. Are there any updates regarding this concern? Thank you! 🙂