Mission editor dictkey errors

[Wright_GR1]

Hi there

 

Having issues in the latest version of the release version. Im the mission editor if I change anything all of my group names go to "Dictkey_groupname_X" where X = a number. The unit names go to Dictkey_unitname_X and the waypoints all change to Dictkey_wptname_X

 

I have never seen that before!

 

EDIT - PFA log

log.zip

Edited February 14, 2017 by Wright_GR1

[Grimes]

Attach DCS.log when it occurs, and if possible the mission it is doing it in. Could also try running a repair.

 

A little background on what is probably happening. So in the mission file itself all text is saved as "Dictkey_whatever" for the briefings, unit/group names, etc. There is another file located in the l01n folder within the .miz that actually contains what each value should be. Its setup this way for localization purposes so instead of having several copies of the same mission for each language all the localized information is saved directly into the mission. Everything displaying with a "dictkey" is caused by something screwing up. Whether it is a problem directly in the mission, a problem occurred when saving, or some other mission editor error.

[Wright_GR1]

Its a fresh install that was then updated to the latest version last friday (new laptop!) its doing it on lots of different missions, even a simple one where I only placed one unit, saved it ran the mission and then as soon as I came back to the editor and clicked the unit it came up with the dictkey thing. My friend is also seeing the same thing

 

Ill try and get the log to you asap

[SUNTSAG]

Hi Mate,

 

A friend of mine encountered the same issue when using the DAWS save mission Mod. It turned out to be linked to Windows 10 Firewall settings. Its a wild stab in the dark but perhaps that could be attributable to your issue? Just a thought and i hope it helps. Cheers. :thumbup:

[Wright_GR1]

Hi Mate,

 

A friend of mine encountered the same issue when using the DAWS save mission Mod. It turned out to be linked to Windows 10 Firewall settings. Its a wild stab in the dark but perhaps that could be attributable to your issue? Just a thought and i hope it helps. Cheers. :thumbup:

 

Had a look at my firewall settings, added dcs to not be effected by anything. It seems to happen after you save the mission then click a unit.

 

Grimes I have attached a log in thee OP for you.

 

Thanks

Edited February 14, 2017 by Wright_GR1

[Weta43]

Is it all missions or just old ones ? (if you make a new mission, save it and re-open it, does it still happen ?)

I think I remember having had that happen when opening very old missions in a newer version of the ME - I think it's that there are fields missing in the old files that get filled with auto-generated numbers as a file of the new format is generated (in this case the temp mission file you're editing in the ME before saving).

[Wright_GR1]

Hi mate. No its happenig in new missions im making and old (when I say old made in the last month) missions.

[Chump]

As Grimes noted, the string values in the actual mission file are referenced inside the .miz archive in the /l10n/DEFAULT/dictionary file. I have always figured this was for localization, and now it is confirmed!

 

For example, after saving a new mission designed with the latest release build (not sure when this was changed to this behavior, using the dictionary lookup), the mission file has a key/value of ["name"] = "DictKey_GroupName_5". If I look in the dictionary file, I see ["DictKey_GroupName_5"] = "MyGroupName" (or obviously whatever I set it to be in the mission editor).

 

I do not believe that there is anything wrong with your setup, Wright_GR1. The mission will behave fine. They groups are queried via LUA fine as well.

[Grimes]

Wright, can you verify that you are running the game as administrator? Go to your install location and the bin folder. Right click DCS_updater.exe and DCS.exe and go to properties>compatibility. There should be an option for "Run this program as administrator", make sure it is checked.

 

As Grimes noted, the string values in the actual mission file are referenced inside the .miz archive in the /l10n/DEFAULT/dictionary file. I have always figured this was for localization, and now it is confirmed!

 

Yeah if you look at something like the A-10C training missions you will notice there are 7 folders of localization within that l10n. Some even have localized audio files.

[Wright_GR1]

As Grimes noted, the string values in the actual mission file are referenced inside the .miz archive in the /l10n/DEFAULT/dictionary file. I have always figured this was for localization, and now it is confirmed!

 

For example, after saving a new mission designed with the latest release build (not sure when this was changed to this behavior, using the dictionary lookup), the mission file has a key/value of ["name"] = "DictKey_GroupName_5". If I look in the dictionary file, I see ["DictKey_GroupName_5"] = "MyGroupName" (or obviously whatever I set it to be in the mission editor).

 

I do not believe that there is anything wrong with your setup, Wright_GR1. The mission will behave fine. They groups are queried via LUA fine as well.

 

Hi Chump

 

No you can't run the mission when it has done this, it gives you an error box with a red X in it and some text (ill load a .Miz on here when it happens

 

Meanwhile I will make sure I am running as administrator Grimes, there is only one account on the machiine so I am assuming I already am but ill try that as well