I'm using 3D-Analyze to get past one of the annoying errors that prevents me from playing Supreme Commander, yet there is another one that is getting in my way.
I first have the error that says "Unable to create direct3d..." and I can get past this point by checking the "emulate HW TnL caps".
Great.
Now another one shows up after this. It says "Hardware instancing required". Almost got it working.
So I thought that I could fix this by using a batch file and typing in one of the commands built into supreme commander that uses a "/softwareinstancing" to bypass this problem. Here is the full command:
"C:\Documents and Settings\Owner\Desktop\3danalyzer-v236\3DAnalyze.exe" /EXE=C:\Program Files\THQ\Gas Powered Games\Supreme Commander - Forged Alliance\bin\ForgedAlliance.exe /softwareinstancing
Anyway, it didn't work and I tried replacing "/softwareinstancing" with "/log logfile.txt" in the command above.
This did not create a logfile in the forged alliance bin directory as expected. I tried doing typing "ForgedAlliance.exe /log logfile.txt" into a command line and it created the logfile as expected.
This leads me to believe that the "/softwareinstancing" at the end of the batch file is being ignored for some reason. I was hoping that someone would be kind enough to help me find a workaround for this issue, or that one of the programmers for 3D-Analyze could help fit this (hopefully) minor feature into the next release.
-Aterxerxes (Ater-zerk-sees)
I first have the error that says "Unable to create direct3d..." and I can get past this point by checking the "emulate HW TnL caps".
Great.
Now another one shows up after this. It says "Hardware instancing required". Almost got it working.
So I thought that I could fix this by using a batch file and typing in one of the commands built into supreme commander that uses a "/softwareinstancing" to bypass this problem. Here is the full command:
"C:\Documents and Settings\Owner\Desktop\3danalyzer-v236\3DAnalyze.exe" /EXE=C:\Program Files\THQ\Gas Powered Games\Supreme Commander - Forged Alliance\bin\ForgedAlliance.exe /softwareinstancing
Anyway, it didn't work and I tried replacing "/softwareinstancing" with "/log logfile.txt" in the command above.
This did not create a logfile in the forged alliance bin directory as expected. I tried doing typing "ForgedAlliance.exe /log logfile.txt" into a command line and it created the logfile as expected.
This leads me to believe that the "/softwareinstancing" at the end of the batch file is being ignored for some reason. I was hoping that someone would be kind enough to help me find a workaround for this issue, or that one of the programmers for 3D-Analyze could help fit this (hopefully) minor feature into the next release.
-Aterxerxes (Ater-zerk-sees)