ataribaby

Of course you can access them. I am just using Total Commander to double click on miz file and you will open it as folder - miz is in reality ordinary zip file then you can extract, edit replace oob.lua Scipts are in l10n\DEFAULT\ folder inside miz file.

Second Quick Flight doesn't show up cos its filename is T45_Familiarization_Night.miz.miz istead T45_Familiarization_Night.miz

Glad you liked it! Try set DCS unit to metric in options. Also there is no AWACS in term of plane - for both sides it means ground EWR radars. Changing template is bit tricky and requires some inner knowledge how campaign works but I think can be deciphered from actual template mission and OOB lua script. BTW I released recently another version Operation Enable Sky Fulcrum Edition - Dynamic persistent campaign - Missions and Campaigns - ED Forums (eagle.ru)

Just tried it and it is great. Looking forward for next versions. Thanks for effort. As it is too early to report avionics and other system bugs just small cosmetic quirk - please remove pilot from static and parked-uncontrolled T-45s Just found there is Left MFD ADI bleed of symbols on right MFD

Hello, Skip Mission F10 option didn't give me any code to use in stage 2. What code should I use? It is even written in briefing I should get code after Skip Mission. I see now. It is not immediate. You need wait a while for code to pop-up.

Thank you for pointing on this! I proposed same some time ago. As you said this simple concept will allow truly dynamically generated campaigns. Same system is used in Operation Flashpoint / Arma series, It saves persistence into mission name space. You can do a lot with such small thing. Branching campaigns, keeps player score, dynamically change missions in campaign. Persist damage and so on. I can't understand why they are reluctant to add this simple feature. Meanwhile we are forced to hack MissionScripting.lua and take out sanitization to be able to persist. It works but not ideal. Also as addition to your global env storage I would implement mission relative calls as well that will store vars relative to each mission/campaign. But even your env. approach is big help - campaigns can reset "cookies" on first or last mission. Also it should be implemented as key, value pair to ease acess per mission/campaign env.saveData(string key, string data) env.loadData(string key) I made similar persistence code to save stuff for my own dynamic campaign.

Dynamic persistent campaign around fictional Abkhazia-Georgia border conflict Welcome into Operation Enable Sky Fulcrum Edition SP/MP PVP/PVE dynamic persistent DCS campaign. Mission can be played solo in SP or with other players in hosted MP/dedicated server MP. There is always PVE element as world is populated with fighting AI for both sides. Time passes and destroyed units will be carried over stages. Contains custom skins. Supported modules MiG-29A, M2000C See readme.txt for installation and usage. Enjoy and check six! What's new Operation Enable Sky Fulcrum Edition v1.1 * Added default RED/BLUE coords format and elevation units for targets report Operation Enable Sky Fulcrum Edition v1.0 * Initial reworked release DDC engine v2.3 * Added RED/BLUE coords format and elevation units for targets report DDC engine v2.2 * Fixed uncompletable ground groups that sometimes have all units destroyed and still reports as alive * Additional functionality for helicopter ops DDC engine v2.1 * Fixed CheckDispatcherSquadronConditions error in log when squadron is destroyed DDC engine v2.0 * Dynamic persistent weather * Numerous fixes and enhancements * Improved AI ground strike generation using Moose new auftrag * Possibility to display target coordinates and their position is marked on F10 map * Updated to latest Moose version DDC engine v1.0 * Initial release Download Operation Enable Sky Fulcrum Edition (digitalcombatsimulator.com)

Updated for DCS 2.7 weather.

I am getting various HUD glass rendering problems with 2.7. See YT videos.

Maybe you forgot set target waypoint to zero so it will be set to ground level. Your TGP probably looking at corrext coordination but at some 4000ft above that spot on terrain. You can set waypoint alt to zero in mission planner so it will auto snap to terrain level or in flight via WP edit and you can read terrain alt on the F10 map.

Coords you get at end of each mission are for campaign specific target for next mission, usually building. JTAC is for ground targets of opportunity, usually vehicles, that help with campaign progression. JTAC doesn't lase your mission target, you need use mission planner and set your editable waypoint over it via coords. Do not forget to set its alt to 0 so it will snaps to ground otherwise TGP will point into air over it. I think campaign docs and mission descriptions should be more descriptive how those things works. It will save a lot of confusion.

You will be with stage 2 for the rest of the campaign. Mission dynamically changes on progress code you enter. It is like stage 1 is predetermined intro mission and stage 2 is dynamic part of campaign If I am not mistaken.

Ahhh I am idiot. That bugging static F-4s are part of base_mission.miz scenery! All good with ramp allocations then. I will update fix for last time I hope. I hope final fix of fix of fix IRIAF_Tanker_War_tankers_fix_3.zip

Jutst got overlaping issue, It must be DCE code issue. Will check it out.

I think fixed tanker problem in IRIAF Tanker Wars. Scrapped fake airbase solution and turned Bandar Abas tanker sq into tanker reserves and reordered parking spots definitions for Shiraz squadrons and used tankers only from Shiraz. Seems work fine so far. BTW I noticed something odd with parking spots defintions in campaign, When I defined 4 parking spots for F-4 squadron there that has 4 aircrafts then parking and active planes was overleaping. When I set it only to two parking defintions all was fine. Strange. I will try investigate.

Here is better example from mission I just flew. Tasks was CAP CAP CAP SEAD http://prekladytextu.eu/DCS/Tacview2.zip See Phoenix 21, Phoenix 22, Phoenix 31 right after this moment: Hope it helps.

Seems there is distant LOD bug when light light is visible even lights are off on player/AI plane. See attached pic. Front plane is me and fine. back is my AI wingman with mysterious red light that pop-in at some distance. Simply do flyby view during night and you will see red light. It is not afterburner. Flying in VR.

http://prekladytextu.eu/DCS/Tacview1.zip See Tacview-20210302-161923-DCS-Operation Pontus Stage 2.1_Rain.zip.acmi and Phoenix 12 where is is flying. Tacview-20210305-180725-DCS-Operation Pontus Stage 2.3_Clear.zip.acmi see Phoenix 32 All remaining AIs lands on airfield instead boat. it is not best representatives as most of AI got regulary shot down by SAMs what was completely valid and ok. I will try collect better representatives. AI usually lands on land base if somehow do not crash in slow low level flight magically or simply eject over water when they fly to the edge of map. Never saw single AI returned to boat except my wingman. With all "ejecting..." radio calls. Maybe I am doing something wrong or I am completly worng on this...

I mostly setting first two as CAPs and last two usualy as SEADs.

Unfortunately AI package members are still bugged somewhat. AI still flying low and slow till they hit first small sloped hill or they fly to the edge of map and never return to carrier or land on airfield. It is very frustrating given how atmospheric and good whole campaign is. I will try collect more TacView recordings.

Just saw changelog for latest DCS Open Beta patch and it is there guys! Gonna fly it again today evening Thanks for update!

If you have Viggen you can try fomration flying missions here AJS-37 Viggen Quick Training Missions v1.1.0 (digitalcombatsimulator.com) You will get detailed info about your keeping formation with lead.

Red circle mark is there only after you land on carrier and you get debrief. Thats why you need note down coords as there is no target info at the begining of new mission.

It is bug tees, will be fixed in patch. Easy radio is set in first intro mission and one that I will not spoil out.

Don't forget to make same changes to MissionScripting.lua after every DCS update.