I'm curious, can you replicate this in stock, with stock assets?
I just got back to look at this and, yes, as a matter of fact I did finally discover the real origin of the problem. Throw all of that above out the window, it matters not.
The problem originates if you open a .mis file with the Torque World Editor and then save the .mis file from within the editor.
To replicate it:
- Launch stock Torque3D 3.7 (64 bit build)
- Launch the 'Empty Terrain' mission (any mission should work).
- Once in the mission, hit F11 to go into the World Editor.
- Alter or change anything in the mission, and then click File -> Save Level.
- Exit Torque.
- Setup a .bat file to launch the executable with the -dedicated parameter and for the -mission parameter use the 'Empty Terrain.mis' file you just saved in the World Editor.
- The cmd window should give the error about not supporting the GFX formats (tested in Windows 8.1 and 7 so far).
So now we know the 'why' of what's causing it, now just to find the 'how' to fix it
I can take the same .mis file, open it with a text editor, alter any fields and save the file without the dedicated launch problem. So it does certainly appear that something in the World Editor's save function is presenting a problem.
That all being said, is there perhaps a 'best practice' for building dedicated builds to avoid any issues that could arise from the Editor tools? I mean, after all, when it's all said and done the tools wouldn't be included with the dedicated build of course.