An Eye for an Eye v0.9- Single player/2 player for F-15C

[feefifofum]

You rock, anirothan!

 

Thanks for finding the issue and letting me know! Rep inbound.

I will upload a 1.5 compatible version of the missions ASAP; with the ability to add afterburner restrictions I should finally be able to get that MiG-21 to settle down too; my interim solution was just to give him 10000 waypoints for each turn to keep him from jamming the throttle and making a 4G turn.

[Rivvern]

Currently on mission 4. Keep up the good work and thank you very much!

[feefifofum]

Thanks, Rivvern!

 

I've uploaded a DCS 1.5 compatible version to the first post of this thread.

 

Unfortunately, in doing so, I've inadvertently saved over some of the DCS 1.2 versions due to some weirdness with the new ME.

 

If you have all 14 of the missions of Eye for an Eye v1.9 for DCS 1.2, please shoot me a PM so I can get those back up on the front page!

[Rivvern]

Done! Check pm.

[anirothan]

DCS 1.5 issues with mission 5 - An Eye in the Storm

 

Glad to help!

 

I have played through up to mission 5 so far. I've experience a few additional issues with mission 5.

 

First, 1.5 appears to be adding fog, which as far as I can remember was not present in 1.2. I've checked the mission in the editor but the fog option is turned off! Enabling and disabling the fog, and then resaving makes the fog go away. However personally, I did like playing the mission with the fog enabled more. It looks amazing and makes the low level flying more exhilarating.

 

Second, the communications menu is getting stuck. I could not order my wingman to go trail formation for the low-level flying in the valleys because of that. When I tried to, the comms just got stuck. I have also noticed this when requesting permission to startup from ATC. The weird thing is, that even though you cannot ask ATC for permission to start-up, if you do it without asking permission, and then if you do not ask for taxi permission and just start taxiing, you can ask for permission to take off. However, at some point the comms just get stuck. Unfortunately, not matter how much I tried I could not figure out what was causing this. It may be a bug on ED's side, but I have not been able to re-create it outside of this mission.

 

Third, it seem's that in 1.5 the ATC is directing takeoffs the opposite direction than in 1.2 in the presence of wind. I noticed this because the AI was directing me to taxi to runway 32 (tail-wind) instead of 14 (nose-wind) as originally designed in this mission. The obvious way to fix this was to just re-adjust the wind to opposite directions.

[anirothan]

DCS 1.5 issues with mission 6 - A Kick in the Teeth

 

I've been playing mission 6 in DCS 1.5, and have encountered the following issues:

 

1). The GA SEAD Escort group of MiG-21s gets stuck while trying to taxi for takeoff. Basically, their hangars are too close and they both seem to be giving the right of way to each other. This is probably a bug in DCS 1.5 so I reported it here: http://forums.eagle.ru/showthread.php?t=148936. Placing one of the 2 MiGs in a different hangar seem's to be the solution for now.

 

2). The game consistently crashes once the GA SEAD group destroys all the SAM objectives. I've basically played the mission 4 times (plus the instant action versions twice), collecting tracks, logs and TacView recordings. On all occasions the crash occurs at the point the SEAD flight destroys its last SA target. I have also made a couple of runs with different graphics settings but the issue remained. This could be a bug in the tasking logic of DCS 1.5. I am going to try and recreate this issue in a minimum mission before submitting a bug report. It would be great if someone else can verify this is happening.

 

For now at least, this mission cannot be completed :cry:

[feefifofum]

Bleargh. This is all terrible news. :lol:

 

I gather the AI taxi/landing logic is still something of a work in progress, I've heard of and seen some other strange things going on with right-of-way. Looks like Mr. Grimes has let ED know, and hopefully this will be corrected in a future update!

 

I can't remember if fog, specifically, was on, but visibility has always been crap in mission 5...I loaded it up for a couple seconds to see how things looked in 1.5 and it looked normal to me. I also get a big kick out of the crazy foggy high-speed canyon run. :)

 

It's odd to me that there are so many issues with tasking/radio; especially in missions without custom commands (and there are only a few of those.) When I built these, I specifically avoided using anything outside of the basic in-engine functions so that they would hopefully keep working when DCS updated. Definitely a little frustrating that they're still screwed up.

 

When the SU-25Ts kill their final target, they report the specific group kill and a flag goes true; this triggers the radio message that the mission is complete a few seconds later, but nothing complicated happens. The SU-25Ts have a bunch of "attack" taskings at their waypoints near Zugdidi; when they run out of targets, they just fly back to Kobuleti to land.

 

There is another trigger zone in about a 10 mile radius around Vaziani; when the "mission complete" flag is true and the Su-25Ts enter this zone, it sets another flag true; the group of Russian Su-27s that had been pressing in from Sochi have "search then engage" taskings with the landed flag as their stop condition. I'm not sure if you're crashing at the -exact- same moment every time or just generally when they've completed their mission, but if it's just around that time it could have something to do with the Su-27s.

 

I should have some time tomorrow afternoon to run a few missions of the campaign and try to squash what bugs I can. Thanks for reporting these!

Edited October 5, 2015 by feefifofum

[anirothan]

It's odd to me that there are so many issues with tasking/radio; especially in missions without custom commands (and there are only a few of those.) When I built these, I specifically avoided using anything outside of the basic in-engine functions so that they would hopefully keep working when DCS updated. Definitely a little frustrating that they're still screwed up.

 

Yes, I did not notice anything special or suspicious used for radio in the mission file. It might be a backwards compatibility issue, a bug introduced by the new mission editor when the mission was re-saved, or just some bug in the new DCS engine.

 

When the SU-25Ts kill their final target, they report the specific group kill and a flag goes true; this triggers the radio message that the mission is complete a few seconds later, but nothing complicated happens. The SU-25Ts have a bunch of "attack" taskings at their waypoints near Zugdidi; when they run out of targets, they just fly back to Kobuleti to land.

 

There is another trigger zone in about a 10 mile radius around Vaziani; when the "mission complete" flag is true and the Su-25Ts enter this zone, it sets another flag true; the group of Russian Su-27s that had been pressing in from Sochi have "search then engage" taskings with the landed flag as their stop condition. I'm not sure if you're crashing at the -exact- same moment every time or just generally when they've completed their mission, but if it's just around that time it could have something to do with the Su-27s.

 

To clarify the crash occurs once the Su-25Ts destroy the SAM targets at waypoint 2, and start moving to attack the AAA targets at the next waypoint. Sometimes I get the message that all SAMs are destroyed ("SAMs killed message" trigger) before the crash, and sometimes I don't.

 

I am attaching one of the collected tracks and tacview files for reference.

E4E6CrashOnSA9Destroy3IA.trk

E4E6CrashOnSA9Destroy3IA.txt.acmi.zip

[feefifofum]

Thanks, that's a good place to start. I just got called in to work tomorrow morning (of course) but I'll start banging my head against this particular brick wall as soon as I'm able. :lol:

 

Hopefully I'll be able to start running tests later this evening or tomorrow afternoon when I get home from work.

 

I swear, those frogfoots in mission 6 have been the bane of my existence since that update to the SAMs a few months ago.

[REDEYE_CVW-66]

Keep up the good work. For me, the second to last mission also crashes/freesez after about 10 mins (twice) and I get horrible frames in 1.5. The one where you fly low with the A-10:)

[feefifofum]

Thanks, Zionid, I'm going to try to focus on playtesting 6 & 11 tomorrow to see if the crashes happen on my PC as well in SP and MP. I haven't forgotten about those hornets, either, just slipped my mind as I was trying to power through restoring corrupted briefing images and reset the initialization script on all 14 missions at once.

 

I'm not super hopeful this is stuff that I'm going to be able to fix on my end, but I should at least be able to restore any of the corrupted VOs as I find them and correct the taxi issue in mission 6.

 

With any luck the next beta update will take care of the crashes!

[baltic_dragon]

Good luck with fixes, feefifofum! Though I would advise to wait a bit on major ones until we go further down the beta, so that you don't have to fix what you have just fixed in case it is already fixed by ED (if that makes amy sense at all) :)) I've downloaded thw F-15 manual and I promise I will give it a try once things calm down at home (became a happy father this Sunday) :)

[feefifofum]

Congratulations! I hope we see Baltic Dragonlings occupying cockpits in years to come :)

 

Fortunately it's looking like most things are okay so far through mission 6.

Lots of little things that are easy to fix like corrupted VO files.

ATC and ground traffic seems a bit of a mess (I'll upload a shot of my tank invasion traffic jam for your amusement later ) but it hasn't been anything that's stopped me from completing missions so far.

 

Hoping I can get the reported issues with 6 & 11 (I think 11 is my personal favorite) squared away but yeah, I'm not going to go too crazy 1 week into the beta.

 

When you get to Eaglin, you can be my wingman any time ;)

[feefifofum]

Any of you other gents crashing on mission 7? I haven't pinned down the exact cause yet, but it appears that it may be when the first group of Abkhazian Su-25s goes down. It happened both times I ran it, once in SP and once in MP.

 

Here's a pretty amusing hiccup from mission 4...I like to imagine all these guys sticking their heads out of the hatches and yelling at each other with New York accents.

 

 

Edited October 7, 2015 by feefifofum

[feefifofum]

1.9.6 uploaded!

Getting closer to the source of the crashing, I think, but I'm out of time for the day. See first post for a list of fixes!

[Zibell]

I think todays changelog mentioned some russian air to ground weapon related crash is now fixed.

[feefifofum]

I saw there was a fix for crashes involving the BetAB 500, but unfortunately none of my guys are dropping bombs. My suspicion is it gas something to do with the S25L as that is the only ordnance present carried by both the 25As and 25Ts.

I should hopefully have some more time to test this week!

[feefifofum]

Unfortunately, I'm not having much luck getting the crash issues resolved; I've tried swapping out the S-25Ls, but the 25Ts still seem to be crashing the missions at the same points.

 

I have fixed wind directions again, and will upload a new version in a few hours whether or not I can get the crash issues resolved.

 

I've also tried just about everything I can think of in Mission 5 to help with the radio bug, and I'm not having much luck. Not a great week for me, unfortunately, but hopefully a future DCS update will squash whatever these bugs are.

[feefifofum]

The latest 1.5 hotfix has led me to make a few changes, as most crash problems have been resolved and the missions appear to be stable again.

 

Version 1.9.8 has been uploaded, and all missions appear to be functioning normally again!

 

Please leave a post if you encounter any bugs.

[Zarma]

Thx for the job ! Will you do a Mirage 2000C version once it is released ?

[feefifofum]

I anticipate coming up with lots of things for all of our upcoming full fidelity fighters to do!

Swapping in Mirages should be no issue; France is already blue (there are even some missions that already feature friendly M-2000Cs that could be converted for multiplayer)

[Hummersepp]

An Eye for an Eye - Mission 1 cannot be completed

 

Hi Folks,

 

I have a stupid question: I played Mission 1 many time but unfortunately without success. I shot down the plane as required and before it enters foreign airspace. I got the message that I finished my job, land at Kobeleti but only get 5 Mission Points. I thought for a successfull mission i get 100 points?

 

Hope somebody can help and I wish you all a good start in 2016!

 

Hummersepp (Germany)

[feefifofum]

Hey Hummer!

I haven't set things up with the campaign builder and mission scoring system yet, so right now the missions will not progress automatically.

 

If you see the "MISSION SUCCESS: YOU MAY EXIT AT ANY TIME" message that indicates you have completed the required tasking. Almost all of the time, this will also mark the end of any scripting for the mission.

 

There are a few exceptions where landing A/C may have a line or two after MISSION SUCCESS but it's nothing critical. Load up the next mission! Things are about to get interesting at Kobuleti. :)

Edited December 31, 2015 by feefifofum

[turbotommo]

Great missions, thanks for creating. On mission 2 (An Eye for an Eye - 02 - A Knock at the Door), my plane didn't seem to be equipped with the AIM-120Cs correctly. Wondered why I had 2 sidewinders only in battle, and in turn saw only 2 missiles fitted to the plane at the beginning of the mission... thought I'd let you know :) Easy to fix via mission editor, it's unusual that it showed up as black boxes under load out - I have some photos I can send you if you need me to.

[feefifofum]

Hey turbotommo, glad you're enjoying the campaign!

 

Thanks for the heads up. This is an issue caused when moving missions with custom loadouts between the 1.2 and the 1.5 open beta. Be sure you've downloaded version 1.9.8 for DCS 1.5.

 

This issue may have cropped up again with the conversion from the 1.5 open beta to the 1.5 stable (1.2 update) but I've run a couple of them since then without problems. Double check you're running the 1.9.8 version of Eye for an Eye; if problems persist I may need to upload another round of files.