World Editor doesn't add ".mis" extension to filenames - RESOLVED

#1 torque never has..

#2 It's still poor production value.

#3 ..if production value is a major concern for you, then you're in the wrongest of wrong places. ;)

#4 Yeah.


We cannot wait to be finished with the Torque3D project we are working. Thanks to Obama and his offshore drilling ban we will prolly be on it for almost another year now. :(

It is nice to have the steady stream of revenue but man we really wish we had gone with Unity. Really Looking forward to Unity 3.

#5 So if torque has 150K seats, and they all have done this once at a rate of 2 secs of typing, the total wasted time would be 83 hours.

Funny part is someone already did the two-line correction necessary for ".prefab."

#6 ::sings:: !Lowered Expectations!

//Edit: Peter, if you wonder why somethings do not make sense around here, you'll make yourself mad by the end of the day.

#7 When you type the name for the new mission, add the ".mis" to the name you are typing instead of relying on the dialog box to figure it out and add it for you, thus:

filename_for_my_new_mission.mis

and it will save correctly.

But watch out... the terrain file is still pointing to the terrain file from the old mission! This caused some havoc for me until I adopted the following habits...

In the levels directory, when I create a new mission, I actually do it in the file manager. I clone the mission file with copy and paste, then rename it.

Then I open the new mission file and look at the terrain file it is referencing by pathname. This is the old mission's terrain file, so I create a new directory specific to the mission, and clone the terrain file referenced in the mission file, again with copy and paste, into the new directory. Then I edit the mission file to point to the copy of the terrain file. (I put them in their own directories because I find them confusing in the base level directory.)

Saving a mission file as a new file does not create a new terrain file--it still references the old location and old file, so using the editor can... alter... your previous mission, if you had expected it to remain as is.

Please note this is entirely from my experience, and as more do not seem to note it, may be entirely owing to my own apparently incredibly high level of stupid. I'd still stop and check when the new "saved as" mission has its terrain pointing...

#8 Logged as TQA-852

#9 This was fixed in 1.1 Beta 2.