correct as is ME using PREVIOUS mission name when saving a NEW MISSION - possible overwrite accident!

[TEMPEST.114]

If you have a mission you're working on and saved and then select NEW from the top menu, choose a map and then click SAVE, despite the 'new' mission have a new name of 'New Mission.miz' the SAVE dialog has the PREVIOUS MISSION name in the save field. 

If a user just clicks save you're going to overwrite their old mission with the blank new one.

e.g.

 

 

 

 

[BIGNEWY]

this is intended, if you want to save it as something else you can edit the file name during the save. 

[TEMPEST.114]

48 minutes ago, BIGNEWY said:

this is intended, if you want to save it as something else you can edit the file name during the save. 

How can it be correct? You've created a new mission and it's given you a new default name - that the dialog shows the old mission name that you AREN'T even referencing or using... then this is a broken UX. 

Edited November 18, 2022 by Elphaba

[BIGNEWY]

the UI remembers your last file location, it is intended. But thank you for your feedback. 

[TEMPEST.114]

Just now, BIGNEWY said:

the UI remembers your last file location, it is intended. But thank you for your feedback. 

But it shouldn't. It should use the new default name you've given it. Not the last. Sure the last folder, but not last mission name. That breaks the mental model. 

[TEMPEST.114]

On 11/18/2022 at 1:15 PM, BIGNEWY said:

the UI remembers your last file location, it is intended. But thank you for your feedback. 

I sincerely think you have misunderstood this bug report. 
 

Remembering the last saved FILE LOCATION  - is correct.

Remembering the last saved FILE NAME - when the mission editor has given you a new name - IS INCORRECT. 
 

Please re-read or talk to me but I think marking this as ‘correct as-is’ is completely wrong. 

[Flappie]

Before the file gets overwritten, the ME gives a warning popup with a "Cancel" button:

[TEMPEST.114]

2 hours ago, Flappie said:

Before the file gets overwritten, the ME gives a warning popup with a "Cancel" button:

Yes. That's good. 

But my point is that 'mission1.miz' as the file name shouldn't be in the 'File name:' dialog box, because the mission editor gave you a new mission file name when you created the new mission. It's THAT NEW NAME that should be inside that box, not the name of the mission file you had PREVIOUSLY loaded before you created a new mission. 

I agree the location of the save dialog should be the same, but not putting in the wrong name in the File name: box. 

[79Au]

Having a default "new file" name in the save box is standard in any software, new projects appear as "new project" or "untitled" or whatever, exactly because of the problem OP described. People who aren't aware of this DCS problem are unlikely to double check the name in the save box. Sometimes depending on the names or naming conventions people use, file names look almost identical. ("2022-11-28 PG freeroam" and "2022-11-26 PG freeroam" for example). People simply don't expect to overwrite anything existing, when they save their freshly created "New Mission.miz" for the first time. And the "confirm overwrite" box appears every time we move the ME map, so most people got used to hitting Yes over and over again, it appears all the time.

If people get distracted while saving the new mission, they're going to think "oh I already entered a name" and hit "Yes overwrite" because they're used to it. Boom, previous mission is gone.

Or when they see the warning message they think there's just an old "New Mission" file somewhere they don't need anymore.

Putting an existing file name as the default name when saving recently created "New Mission.miz" is... sabotage!

 

[Durham]

I couldn't agree more with your post.

Having the filepath default to last is fine.

Having the filename default to "newmission" or "untitledmission" is fine.

Letting them save "newmission" or "untitledmission" or whatever the default is set at is stupid - just check for the default and throw an error box asking for a new filename.

Having the filename be equal to the last filename that you saved is moronic, and just begs for the user to overwrite a mission they have spent hours on with a new one they have spent minutes on!!  And I have been bitten by this dog before, so please remove the teeth from the dog.

 

 

[79Au]

And here we go! I wasn't paying attention and the "save" prompt got me, overwriting my last test mission with a completely empty mission when I briefly went into the ME and decided to go back into main menu settings.

What the eff man. There's no way that's correct. I didn't even open that test mission that got deleted. Upon leaving the empty mission editor, the damn save prompt came up and took the name out of nowhere and put it into the save box of a completely emtpy mission for no reason.

I thought I was editing said test mission after getting back to the pc but I was wrong. I was messing with the weather and didn't look whether units were there. I made a mistake but my old test mission would still exist if DCS assigned a "new" name by default and not an existing name of another mission.

Excuse me but it's SUPER frustrating to lose hours of work due to a simple problem like that.