Cristofer

MBot: I have a problem when generating missions in a campaign I´m working with. It only happens about 1/10 of the times when generating a new mission with firstmission.bat I think it has something to do with Intercept, but I have no idea. See screens.

I have now reinstalled my DCS, and are now using the "normal" folder name DCS world (instead of DCS World OpenBeta), and uploaded a new version. So it should work if your game is installed to a folder named DCS World If it is installed to DCS World OpenBeta, the files mentioned above must be altered

Thanks. I don´t now why they don´t engage. I have also noticed that the SEAD flights doesn´t do much to help, but I have seen them fire missiles at SAMs, when the SAM itself is the main target. I have updated the campaign and now the SEAD also have laser guided missiles so they can engage non radar targets, like missile launchers. I have no idea if they will.

Exactly what I´m looking for, thanks alot :)

Where do I find airdromeId for the db_airbases.lua?

If put in other folders, some files has to be edited. FirstMission.bat The numbers of ..\ For example if the EN folder is missing, the campaign folder is "one step" closer to the main DCS folders, and one of the ..\ has to be removed. The same thing goes with the SkipMission.bat file. Nordic Battle.cmp This is the campaign file, and there are a path on four places in it. Open it with notepad++ and correct the paths. camp_init.lua in the init folder. Edit it with notepad++ There is a path to the campaign folder there. I think that´s all files that has to be edited

Campaign updated again, there were missing folders so the campaign didn´t progress. Sorry about that.

Hmm, I think I solved it. For some reason, when adding files to a zip archive, empty folders are not added, so two folders was missing in the nordic battle folder: Debriefing and debug. I have updated the zip file, and I hope it works now. I noticed that the same thing on my other campaign Red Bear, and have updated it as well. Sorry about that

Hmm, I have no idea:( What happens if you make a new start mission with the firstmission.bat file, than restart camapign within the game?

Look if the path is correct in the Nordic Battle.cmp file (on 4 places) Try to make a new mission with the firstmission.bat in CMD I am using the openbeta, so my filepath is Eagle Dynamic\DCS World OpenBeta\...and so on I have noticed that some have just "DCS World" as folder name. Perhaps that´s why. Change the path in the cmp-file, I believe it´s the only file that has to be changed, but I´m not sure. Then make a new start mission with the bat file, then restart campaign in the game.

Does this message appear every time? The campaign has beed updated, there was a missing image error.

Operation Red Bear is my first campaign I made, and it seems I missed to correct the readme, sorry about that. I don´t know if it works on stable. Maybe you need to correct the path in the Nordic Battle.cmp file. Open it with notepad++ Look for ["directory"] = "DCS World OpenBeta\\Mods\\aircraft\\AJS37\\Missions\\EN\\Campaigns" Change it to the correct path. Observe that there are on several places. Also: run the game as an admin. I have to do that to make it work.

Please try my Viggen Campaign. For more information, go here: https://forums.eagle.ru/showthread.php?t=188167

Nordic Battle, a campaign for the AJS37 Viggen. This is a dynamic campaign built with MBot´s Dynamic Campaign Engine, and it needs testing. I´m not a very good Viggen pilot, so I haven´t tested it myself more than a couple of missions, just to see if it works. There are probably alot of bugs, so please report them here if you encounter some. Download here: https://www.dropbox.com/s/b5fj0b9uibkix2g/Nordic%20Battle.zip?dl=0 Updates: ver 1.1 Corrected a missing image bug. Updated readme file.

Maybe it is damage on weapons? A message appears when ships fires at anti ship missiles.

A message appears when launching mavericks on a recently destroyed target, for example when firing several mavericks on the same target. It doesn´t seem to appear if firing on a destroyed target after some time. Se image. Nothing "bad" happens though, just press ok and everything works.

Yes, no problem there. Maybe increase the number of sorties/day in the loadouts file? Or add more targets.

Ah, ok

I can´t find all vehicles and units in the mission editor, for example the WW2 AAA units (Bofors 40 etc) and soldiers. WW2 Assets pack installed.

Campaign updated

Well, they seem dead :) They should be dead after a GBU10 hit. Something called "Small Crush" dies, according to the in game debriefing. The warehouses stay dead, but not the tanks. Well I guess I´ll will make it easy for now and just remove the fuel storages from the target list.

In my new campaign I´m working with, I have a problem with some of the map objects, they do not stay dead in the next mission, and they do not appear in the debriefing text-file either. And since the AI hit the targets the cordinates must be correct. I have only seen this with one type of targets, and it is fuel tanks (see image).

This is from the targetlist file, and it is on all OCA strikes: ["Vaziani OCA Strike"] = { task = "CAS", priority = 6, attributes = {"OCA","Parked Aircraft"}, firepower = { min = 40, max = 120, }, class = "airbase", name = "Vaziani", }, Shouldn´t it be a space between "OCA" and "Parked Aircraft"? Like this: "OCA", "Parked Aircraft". But it is the same in the loadouts file, so maybe it works anyway.

Viggen frequencies Right now I´m working on a Viggen campaign, and everything seems to working just fine, except for one thing. When loading the mission, an error occurs. If I open the mission in the mission editor, and try to save it, a message appears that says invalid frequency. I think it has something to do with the decimals, like the frequency is 154.85, and I´m not sure that you can have this in the Viggen, but I can have wrong. MBot: Any ideas? Is there a way to set the frequencies manually, or not using decimals? Edit: Nevermind, I think I´ve solved it. Changing frequency to min 100, max 149 seems to work.

Win + x open a menu so you can run the CMD window as an admin. Then goto the folder where the bat files are, within the CMD, then run them