F-5E-3 and Mission Editor problem

peachpossum · March 18, 2019

For quite a few months now I've had problems with the F-5E-3 in the mission editor.

Most often the problem is I cannot save a mission when I add an F-5E-3.

Steps to re-create the problem:

Open the mission editor, create a new mission, add aircraft -> F-5E-3 and place on an airfield.

Attempting to save the mission results in the following error.

What's worse is I cannot select the F-5E-3 once it is placed. I can select the F-5E-3 using the Unit List, but that is not working if F-5E-3s are the only units in that list.

Some work-arounds can be to add another A/C type and then select the F-5E-3 from the unit list, but this is a pain if you need to move the F-5E-3.

I'm all up to date with the most current Open Beta and a fresh repair. Any ideas?

Frag · March 19, 2019

I am using the F5 90% of the time and I am a mission editor freak. Never seen such an issue, but I am playing on the stable branch.

For sure you have some corruption of some sort. Sorry cant help here.

VZ_342 · March 19, 2019

I’ve set the F5e3 many times (DCS 2.5xxx, stable version), no problem.

peachpossum · March 19, 2019

I've tried running repairs and this has never resolved my problem. I'll try uninstalling the module and reinstalling. Is there a recommended way to uninstall and reinstall a module, use the module manager?

peachpossum · March 19, 2019

After disabling and trashing the module from the module manager, then reinstalling and reactivation, things are better but not completely fixed.

I still cannot directly select the F-5E in the ME by clicking on its icon, I must use the unit list which requires some other non-F-5E unit to be listed. From the unit list I can select the F-5E and then change things, and even click on its icon and move it to another location.

I no longer get the cannot save mission error, so things are mostly OK now. It's just odd that this is the only module with this strange behavior.

Thanks for your help.

MadDog-IC · March 19, 2019

After disabling and trashing the module from the module manager, then reinstalling and reactivation, things are better but not completely fixed.

I still cannot directly select the F-5E in the ME by clicking on its icon.

Thanks for your help.

Try renaming / backing up your SAVED GAMES Folder temparily and have DCS create a new default one and see if that helps with you issues, if it does,then rebuild the directory with you old configs, logbook, etc.

Also run CMD line: "dcs_updater.exe cleanup" to check for 3d party mod files that might be installed or left ov

Post a "Dcs.log" so we can see if there is any clues to issue.

Regards, Ian.

Edited March 21, 2019 by MadDog-IC
corrected CMD line string

609_Relentov · March 20, 2019

I was able to replicate the error just now in the mission editor:

- Added F-5E-3, SKILL=Client

- Changed the COMM value (MHz AM) just under the PILOT text box in the upper right of the properties pane to "124", where the numbers turned red

- Clicked Save and I got the error dialog as you did: "Invalid frequency 124 MHz"

- After changing that value from 124 to something valid (for the F-5E-3 UHF radio AN/ARC-164) between 225 and 399.999, I was able to save the mission.

So it seems that when you add an F-5E-3, it's somehow defaulting the COMM value to 124, which does not allow you to save the mission. Can you check what value you have, and if it's 124 change it to a valid value.

peachpossum · March 21, 2019

S:\DCS World\bin>dcs_updater.exe clean

S:\DCS World\bin>dcs_updater.exe -clean

S:\DCS World\bin>dcs_updater.exe clean @openbeta

S:\DCS World\bin>DCS_updater.exe clean

S:\DCS World\bin>DCS_updater.exe -clean @openbeta

None of these commands worked, they all popped up a window "unknown command: clean"

( I am running DCS World open beta from a dedicated M.2 SSD, hence the S:\ )

I'll try your other suggestion of temporarily removing my Saved Games folder and letting DCS create a new one.

MadDog-IC · March 21, 2019

None of these commands worked, they all popped up a window "unknown command: clean"

I'll try your other suggestion of temporarily removing my Saved Games folder and letting DCS create a new one.

My error, the command is "Dcs_updater.exe cleanup" from a command line box with admin priv.

peachpossum · March 21, 2019

Rebuilding the DCS folder in Saved Games seems to have fixed the problem. If I find a smoking gun as I move files back in I'll post an update. Thanks for all the help.

(Thanks for the correction on cleanup, that also worked)

Edited March 21, 2019 by peachpossum
added cleanup acknowledgement

peachpossum · March 21, 2019

I think I found the file causing problems;

~Saved Games\DCS\MissionEditor\UnitPayloads\F-5E-3.lua

local unitPayloads = {
["name"] = "F-5E-3",
["payloads"] = {
	[1] = {
		["name"] = "AIM-9B*2, Fuel 150",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 7,
			},
			[2] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 1,
			},
			[3] = {
				["CLSID"] = "{0395076D-2F77-4420-9D33-087A4398130B}",
				["num"] = 4,
			},
			[4] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 3,
			},
			[5] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 5,
			},
		},
		["tasks"] = {
			[1] = 10,
			[2] = 19,
		},
	},
	[2] = {
		["name"] = "AIM-9B*2, Fuel 150*3",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 7,
			},
			[2] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 4,
			},
			[3] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 1,
			},
		},
		["tasks"] = {
			[1] = 11,
			[2] = 18,
			[3] = 19,
		},
	},
	[3] = {
		["name"] = "New Payload2",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 1,
			},
			[2] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 3,
			},
			[3] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 4,
			},
			[4] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 5,
			},
			[5] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 7,
			},
		},
		["tasks"] = {
			[1] = 11,
		},
	},
	[4] = {
		["name"] = "New Payloadg",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 1,
			},
			[2] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 4,
			},
			[3] = {
				["CLSID"] = "{AIM-9B}",
				["num"] = 7,
			},
		},
		["tasks"] = {
			[1] = 32,
		},
	},
	[5] = {
		["name"] = "mk-82s",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 2,
			},
			[2] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 3,
			},
			[3] = {
				["CLSID"] = "{MER-5E_MK82x5}",
				["num"] = 4,
			},
			[4] = {
				["CLSID"] = "{6CEB49FC-DED8-4DED-B053-E1F033FF72D3}",
				["num"] = 11,
			},
			[5] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 5,
			},
			[6] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 6,
			},
		},
		["tasks"] = {
			[1] = 11,
		},
	},
	[6] = {
		["name"] = "New Payload",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 1,
			},
			[2] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 3,
			},
			[3] = {
				["CLSID"] = "{0395076D-2F77-4420-9D33-087A4398130B}",
				["num"] = 4,
			},
			[4] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 5,
			},
			[5] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 7,
			},
		},
		["tasks"] = {
			[1] = 11,
		},
	},
	[7] = {
		["name"] = "nnnnnn",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 2,
			},
			[2] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 3,
			},
			[3] = {
				["CLSID"] = "{MER-5E_MK82x5}",
				["num"] = 4,
			},
			[4] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 5,
			},
			[5] = {
				["CLSID"] = "{BCE4E030-38E9-423E-98ED-24BE3DA87C32}",
				["num"] = 6,
			},
			[6] = {
				["CLSID"] = "{6CEB49FC-DED8-4DED-B053-E1F033FF72D3}",
				["num"] = 11,
			},
		},
		["tasks"] = {
			[1] = 31,
		},
	},
	[8] = {
		["name"] = "Anti-Sochi",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 7,
			},
			[2] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 1,
			},
			[3] = {
				["CLSID"] = "{AB8B8299-F1CC-4359-89B5-2172E0CF4A5A}",
				["num"] = 4,
			},
			[4] = {
				["CLSID"] = "{7A44FF09-527C-4B7E-B42B-3F111CFE50FB}",
				["num"] = 3,
			},
			[5] = {
				["CLSID"] = "{7A44FF09-527C-4B7E-B42B-3F111CFE50FB}",
				["num"] = 5,
			},
			[6] = {
				["CLSID"] = "LAU3_HE5",
				["num"] = 2,
			},
			[7] = {
				["CLSID"] = "LAU3_HE5",
				["num"] = 6,
			},
		},
		["tasks"] = {
			[1] = 32,
		},
	},
	[9] = {
		["name"] = "radar practice",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 7,
			},
			[2] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 1,
			},
			[3] = {
				["CLSID"] = "{0395076D-2F77-4420-9D33-087A4398130B}",
				["num"] = 4,
			},
		},
		["tasks"] = {
			[1] = 31,
		},
	},
	[10] = {
		["name"] = "SW04 Payload",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{0395076D-2F77-4420-9D33-087A4398130B}",
				["num"] = 4,
			},
			[2] = {
				["CLSID"] = "{9BFD8C90-F7AE-4e90-833B-BFD0CED0E536}",
				["num"] = 1,
			},
			[3] = {
				["CLSID"] = "{9BFD8C90-F7AE-4e90-833B-BFD0CED0E536}",
				["num"] = 7,
			},
			[4] = {
				["CLSID"] = "LAU3_HE5",
				["num"] = 5,
			},
			[5] = {
				["CLSID"] = "LAU3_HE5",
				["num"] = 3,
			},
		},
		["tasks"] = {
			[1] = 11,
		},
	},
	[11] = {
		["name"] = "A2A training",
		["pylons"] = {
			[1] = {
				["CLSID"] = "{PTB-150GAL}",
				["num"] = 4,
			},
			[2] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 1,
			},
			[3] = {
				["CLSID"] = "{AIM-9P5}",
				["num"] = 7,
			},
		},
		["tasks"] = {
			[1] = 11,
		},
	},
},
["unitType"] = "F-5E-3",
}
return unitPayloads

MadDog-IC · March 21, 2019

I think I found the file causing problems;

~Saved Games\DCS\MissionEditor\UnitPayloads\F-5E-3.lua

Thanks for letting us know.

Cheers, Ian.

Sign In

F-5E-3 and Mission Editor problem

Recommended Posts

peachpossum

Frag

VZ_342

peachpossum

peachpossum

MadDog-IC

609_Relentov

peachpossum

MadDog-IC

peachpossum

peachpossum

MadDog-IC

Recently Browsing 0 members