I just tried the new GSA 1.57, and still its command-line usage is broken. On a freshly installed Win7 64-bit system I ran
GPUShaderAnalyzer.exe default_frag.glsl -A a.txt -C IL
which first returned to the prompt, and then printed the error message
Could Not Find D3DX
So it looks very weird on the prompt, like
[quote]C:\Program Files (x86)\GPU ShaderAnalyzer>GPUShaderAnalyzer.exe default_frag.glsl -A a.txt -C IL
C:\Program Files (x86)\GPU ShaderAnalyzer>Could Not Find D3DX
C:\Program Files (x86)\GPU ShaderAnalyzer>[/quote]
And then it wait for a key press.
After installing DirectX, the error message again changes to "No ASIC specified" (which is not true, as I've specified "IL").
Please fix the command line usage, it would be very nice to have.
Thank you for your feedback. IL is not currently supported as a compilation target through the command line option. We will add this feature request into our system. Meanwhile, you can select one of the valid output ASICs, such as Redwood, with the command line option -C.
Thanks! Could you please also enter a feature request to not wait for a key press when using the GSA command line interface? This is very inconvenient when calling GSA in scripts.