PB0_CEF Posted August 21, 2017 Posted August 21, 2017 It seems that in 2.1 EWR is not working anymore so intercept enemy flights are never alerted and so never take off :( [/url]All known Dynamic Campaign Engine Campaigns Last DCE news : Crisis in PG - Iran-Iraq War - TF-71 - TF80s - War over Beirut ...
caponi Posted August 22, 2017 Posted August 22, 2017 feels like that .... in F2 view i could see some Mig-21 and in ME i could see 3 groups with 5 Migs, but no Mig will attack our package :( i will switch to the converted Mirage campagne in Caucasus and will give them a try ... hope that the problem will fixed soon ... :pilotfly::joystick::pilotfly: too much ...
PB0_CEF Posted August 22, 2017 Posted August 22, 2017 I hope so :( If you prefer F-15C you can try the "Eagle over Caucasus" campaign :thumbup: [/url]All known Dynamic Campaign Engine Campaigns Last DCE news : Crisis in PG - Iran-Iraq War - TF-71 - TF80s - War over Beirut ...
71st_AH Rob Posted August 22, 2017 Posted August 22, 2017 It seems that in 2.1 EWR is not working anymore so intercept enemy flights are never alerted and so never take off :( It's only the one EWR that is not working, just change it in the basement file in the initial folder and run the first_mission .bat file and it should work.
71st_AH Rob Posted August 22, 2017 Posted August 22, 2017 no idea what u mean:cry: Open the mission editor and go into this folder: C:\Program Files\Eagle Dynamics\DCS World 2 OpenAlpha\Mods\aircraft\Flaming Cliffs\Missions\EN\Campaigns\Screaming Eagle\Init Open the base_mission.miz and edit the EWR units At Tenopah you will see a unit that is called Tonopah AFB EWR the unit type is a EWR 1L13, change this to a EWR 55G6. Do this for all the EWR 1L13 that you find in the mission. Then save the mission and run the first_mission.bat file. run the first mission and it should work.
Stonehouse Posted August 23, 2017 Posted August 23, 2017 Updating the EWR units to 556Gs seems to cause the error: "Scripts/ATO_ThreatEvaluation.lua:461: attempt to index field 'ERW' (a nil value)" updating line 461 in the above lua from: GCI.ERW[side][unit.name] = true to be: GCI.EWR[side][unit.name] = true fixes the error. Looks like a simple typo error. Cheers, Stonehouse
caponi Posted August 23, 2017 Posted August 23, 2017 (edited) yes ... execute both hints and it works ... but i have no time for flying the mission ... i will give feedback later :smartass: Edited August 24, 2017 by caponi too much ...
71st_AH Rob Posted August 23, 2017 Posted August 23, 2017 Updating the EWR units to 556Gs seems to cause the error: "Scripts/ATO_ThreatEvaluation.lua:461: attempt to index field 'ERW' (a nil value)" updating line 461 in the above lua from: GCI.ERW[side][unit.name] = true to be: GCI.EWR[side][unit.name] = true fixes the error. Looks like a simple typo error. Cheers, Stonehouse Good catch. I have not seen that error strangely but I have been flying Desert Tiger lately.
MBot Posted August 24, 2017 Author Posted August 24, 2017 Good catch. As you can see, I usually do not use the 55G6 EWR, so that typo went unnoticed until I discovered the problem with 1L13 last week.
Riverseeker Posted September 1, 2017 Posted September 1, 2017 Is this issue fixed by DCS 2.1.1 Update 3 ? :) 200m butterflier inside :harhar: MERLO forever
MBot Posted September 1, 2017 Author Posted September 1, 2017 I am currently traveling and won't be back until in 2 weeks. Can somebody check?
Anonymous User Posted October 31, 2017 Posted October 31, 2017 Bug I have tried both of these corrections (with latest update) and still can not get enemy aircraft to takeoff. The EWRs are active but even when flying over the enemy bases, the MIGs don't do a thing..
MBot Posted October 31, 2017 Author Posted October 31, 2017 As modifications are involved, difficult to tell the problem remotely. I would advise to ignore any DCE campaign until ED fixes EWR and the SAMs. At least that is what I do.
Anonymous User Posted October 31, 2017 Posted October 31, 2017 Thanks Mbot. Something I did notice is that even though I changed all EWR 1L13's to EWR 55G6's in the base_mission.miz, they do not change in the actual mission itself. This is after exiting DCS and running first_mission.bat, then restarting the campaign. But no worries I will wait it out!
PB0_CEF Posted October 31, 2017 Posted October 31, 2017 Thanks Mbot. Something I did notice is that even though I changed all EWR 1L13's to EWR 55G6's in the base_mission.miz, they do not change in the actual mission itself. This is after exiting DCS and running first_mission.bat, then restarting the campaign. But no worries I will wait it out! You have to change EWR type in the oob_ground.lua file in the "STATUS" folder too. Then you run "first_mission.bat" again and you should have 55G6 EWR in missions ;) [/url]All known Dynamic Campaign Engine Campaigns Last DCE news : Crisis in PG - Iran-Iraq War - TF-71 - TF80s - War over Beirut ...
Lostcat Posted December 18, 2017 Posted December 18, 2017 (edited) Hi, thanks for the campaign, it's very good and the sense of immersion in a real war going on is very very strong !!! The only problem i have is that AG flights never drop their bombs... the escort clears the sky of enemies, the sead engages sams as well... but bombers (f-16, b-52, f-117) just fly overhead, maybe circle around a couple of times, and than push rtb with all the bombs under the wings. L.C. -edit- i just had to let the phantoms do their job with the sams... it took a couple of missions. This campaign is fantastic !!!! Edited December 20, 2017 by Lostcat
MBot Posted December 22, 2017 Author Posted December 22, 2017 First post updated with version 1.01. No changes specific to this campaign, just a maintenance update to bring it up to the latest standard of the Dynamic Campaign Engine. I didn't run any gameplay tests, fingers crossed that everything is still in order.
BigMillerTime Posted December 27, 2017 Posted December 27, 2017 Thanks a bunch, MBot! Appreciate it brother.
LC34 Posted January 20, 2018 Posted January 20, 2018 Only trouble I'm having is landing after the first mission I get the black box asking if I want to continue campaign etc.. I click "y" and enter, it waits a moment, generates a new mission it says but after I click continue it says I won the campaign. I mean, I got one kill, but I don't think that made the Iraqi Air Force and Army surrender. :) What have I done wrong? PS I love the first mission and if the next missions are half as good I'm in for a treat once I get it working correctly. Great job! AMD Ryzen 7 7800X#D 64 GB Ram MSI RTX 4090 Thrustmaster Warthog HOTAS
MBot Posted January 22, 2018 Author Posted January 22, 2018 This is a problem with an incorrect scoring of the mission, which determines progression within DCS's own campaign system. Why this happens I don't know. The triggers that are set up to apply the mission score are very simple and always the same. So it should either work for everyone all the time, or not work at all for anybody. I assume this is a bug within DCS, as I have observed the triggering of scores to be buggy on several occasions.
LC34 Posted January 27, 2018 Posted January 27, 2018 Thanks MBot. I have noticed that for whatever reason, it seems to work for me now. Now if I could only get better at engaging with the Aim-7. I have become too dependent on the 120 for all these years. AMD Ryzen 7 7800X#D 64 GB Ram MSI RTX 4090 Thrustmaster Warthog HOTAS
Shein Posted February 19, 2018 Posted February 19, 2018 Seem to be having an issue in 2.5 beta with strike packages not doing their job. First time it was buffs, straight up not dropping bombs. second time we had 8 (EIGHT!!!) F-16's circling over groom air force base, tasked with damaging the fuel depot. They didn't drop a damn thing, just circled overhead, sustaining heavy losses after a period of time.
Recommended Posts