[DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Printable Version

+- All-Aircraft-Simulations (https://allaircraftsimulations.com)
+-- Forum: IL2 Skins, Textures, Patches, Utilities Missions & Campaigns (https://allaircraftsimulations.com/forumdisplay.php?fid=272)
+--- Forum: Il2 Missions & Campaigns Download (https://allaircraftsimulations.com/forumdisplay.php?fid=300)
+--- Thread: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION (/showthread.php?tid=70819)

---

[DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Triad773 - 11.07.2010

Cold_War_Intercept Single Mission
==================

Get it here

The Ruskies are restless and they've been sending survelence planes around recently. Because we have 'sensitive' work going on, we need them to refrain from being so inquisitive.

- Take Missions/Single/US/F86J file folder and put in corresponding IL-2 1946 root folder.

- Take skins for F-86J and B-25 and put into Paint Schemes as usual.
[Two skins included:
F-86J: "F-86 1st FDS 413th FDW (409).bmp" by Lefty, Template by HH_Blaze, US Grant
B-29: "$$ Tu-4 Highlander.bmp" by Highlander] [Thanks to these Gentlemen for such nice skins!]

- Review your load.ini in Mods/Mapmods/Maps/Aleutians/ (or AG_Aleutians I think) and review that it matches the below entry (for fuller effect)

===
[WORLDPOS]
CAMOUFLAGE = WINTER
MONTH=9
DECLIN = 10
PRESSURE = 745
TEMPERATURE = -10
=====

Your flight time is about an hour-twenty minutes. Time to target from lift off is about a half an hour. Good luck, and don't start World War Three unecessarilly!

Mods needed:
- UP 2.0 or higher
- Storbror's F 86 J with AIM 9 Sidewinders from AAS
- Agracier's Aleutian Islands map mod from AAS or SAS

It helps to be comfortable in blind flying conditions, but so much more to emulate 'what might have happened '



1.) Fly out of the Aleutian Island Chain (Kiska AFB) to check on unknown intruder(s) to the south


2.) Take off in dark, slushy weather to meet what awaits you


3.) It might be handy to be instrument-rated as you certainly cannot see much outside the canopy at 5AM


4.) Be aware of freindlies in the area; there is at least one Neptune out tonight looking for naval traffic


5.) Your target is high above the snow and misery looking for what ever it can sense as to what we are up to


6.) Your return base at Amchitka has had some electrical problems. They have improvised lighting so you don't have to end the mission on a sour note


Special thanks to Storebror, Deutschmark and Wolf & company, as well as Agracier and others who inspired this early Cold War mission by way of thier works.

Thanks also to the Modders in general who have extended the life of this great combat flight simulator by Oleg Maddox and crew, as well as All Aircraft Similations and Special Aircraft Service.

Enjoy

Triad

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Cracken - 12.07.2010

Very interesting subject, hope you will make more missions and put them into a campaign!

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Russ_Ace - 12.07.2010

I tryed it last night. works grate on HSFX and is so much fun, but maybe ad a russian fighter, or more missions and possibly ad this:
http://www.sas1946.com/main/index.php?topic=3323.0

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Triad773 - 12.07.2010

Cool! Thanks for the feedback Russ_Ace. I am glad it works on HSFX. I had to give up having multiple installs a while ago and with it the benefit of testing on that.

One of these days I want to get into campaign making when I have time.

This was fun to make and I wanted to feature pilotage as well as just 'shoot'n down' stuff.

Triad

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - sluggs - 13.07.2010

Ahh Triad, AWESOME mission.

And Russ_Ace beat me to it, I was going to say that the Kong Jiang-1 would be good for this mission

I did a couple of modifications though, I changed the weather to "Hazy" because my cpu was taking a bit of a hit and when you combine that with Freddys F-86 cockpit, it had some lag. Not much, but then combine that with the way the F-86 likes to "nose jump" on take off and I literally got off the ground 3 out of 6 or 7 tries, and I stalled and crashed on the 3 succesful ones :mrgreen:

The second thing I did was add a wingman just for the sake of atmosphere. He served absolutely no purpose, but it was cool to see him in formation with me (I gave him the same skin too).



Now, for the debriefing (humor me lol):
[I had everything set to full-real except for external views, so the map was useless]

I took off about 5 minutes after 5:00 AM in hazy weather, cloud bottoms at about 500 meters. I immediately turned to heading 180 and continued my climb at about 1500 to 2000 fpm at 70-80% throttle to allow my wingman to close the distance and form up, which he did on my starboard side and slightly aft.

At this point I asked Ground Control to give me a vector to the target,to which was responded with a heading of "175". We then turned to (approximately) heading 175 and continued our climb for the next 10-15 minutes.

We then maintained a heading of (approximately) 175 and an altitude that ranged between 23,000-26,000 feet for the next 10 minutes, periodically asking Ground Control for the nearest vector to target. After about 5-10 minutes of this, periodically asking for vectors, I was told to turn to (approximately) heading 327.

I was shocked, I hadn't seen a thing, but I followed through and turned to heading 327. I (we) followed this course for around 30-60 seconds when I asked Ground Control for another vector to target, which I was then told to turn to heading of which I do not exactly remember, although it was in almost the complete opposite direction of my current heading (327).

This cycle continued for nearly 10 minutes; me flying the designated heading, calling in for the next vector, then given a heading that was almost entirely opposite of the previous heading. I could not get a visual, although I had dropped in altitude from above 20,000 to somewhere near 10,000 feet.


{{Ok this is where I cheated lol. I couldnt see this guy at all, but I had a feeling he was close due to the designated vectors being almost completely opposite even though they were only a few seconds apart. So I Ctrl-F2'd to the B-29 while the game was paused and tried to match the cloud positions from his view with the cloud positions from my view. It helped a bit but the clouds that were just off of the horizon that I could only see the edge of made it difficult to determine positions, so I climbed back up to above 20,000 feet and continued the search visually.}}


After doing this for nearly another 10 minutes, I was in a wide right turn at somewhere near 20,000 feet, when at a heading of (approximately) 243 I looked North-North West and I made visual contact.

I (we) turned to follow the aircraft and closed on his starboard side, which I then identified as a TU-4 "Bull". I had to slow down considerably to maintain his speed (which was slightly below 200 Knots indicated). At this point I was having trouble with stability issues. I did not realize that my external tanks were empty though, which were the main cause of the low stability. My wingman, who I assume could not deccelerate in time, shot past and underneath me (he had jettisoned his externals at what I'm guesing was a few seconds before this).

I was moving further to the right of the aircraft and slightly ahead when I activated my Navigation Lights and also my Landing Lights. It was also at this time that my wingman (who was about 700-1000 meters ahead) went inverted and pulled into a steep dive and I did not see him again for the next few minutes. I continued ahead and about 200 meters above the "Bull", dropped my externals, and cut south across his flight path; he was heading almost dead west.

I circled around and pulled in behind the TU-4 and relatively maintained this position for a few minutes, moving back and forth (right to left, south to north) slightly aft and under his aircraft. Sometime during the next 30-60 seconds (approximately) my wingman had arrived back on my starboard side.I also noticed the belly gunner of the TU-4 traversing left and right, following my wingman, BUT HE DID NOT OPEN FIRE.

I then pulled to the TU-4's starboard side, pulled ahead, and crossed in front of his flight path to the left (north) then back to the right (south) one last time. All the while since I had made visual contact he had not responded to anything I had done. I did not want to shoot him down, he seemed to pose no threat, being nearly 100 kilometers south of Kiska AFB.

I then turned in the opposite direction (east) and then swung back around, gaining speed and closing in fast aft and starboard of the TU-4, changing my gunsight settings to "Gyro Only". I closed to within approximately 300 meters and opened fire with a 1-3 second burst, observing multiple hits on the tail gunners position, fuselage, and the right wing. I then shot another short burst, strafing a large section of the right wing. I saw the inner-most engine on the right wing seize and begin to pour black smoke.

I continued past him on his starboard side and climbed sharply, then descending into a wide sweeping turn and pulling up behind him at about 3000 to 3500 meters. I observed that he did not try to descend, or change course. At this point I fired a single AIM-9B from that range (3000-3500) meters. It struck him in the left elevetor and the entire aircraft exploded into multiple pieces.

I then turned north and asked Ground Control for a vector to the "nearest friendly airbase",to which I was given a heading of (exactly) 31. I continued on this course, descending to about 10,000 feet. shortly after I made visual contact with Amchitka Island and asked for permission to land, which was granted and I brought her down safely.

I had lost contact with my wingman just after the destruction of the TU-4, but after I had taxied to a stop off the south side of the runway near the Control Tower, he did a low level flyby over the runway. He then landed, taxied in, and parked about 30 meters from my aircraft.

Well thats kind of long, but I made it as realistic and accurately as I could (I saved the replay).

Once again, VERY GOOD JOB TRIAD!

~S~

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - KG64_Cnopicilin - 13.07.2010

Very nice, very nice.

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Triad773 - 13.07.2010

Thanks for the good review Sluggs. I had tried this with a wingman initially; but in testing my wingman would rush ahead of me and try shooting down the Soviet plane with missiles, often with disastrous results (collision) :OO

The target won't shoot back as it carries no ammo (just photographic eqt I guess :mrgreen: )

Yeah the J seems a bit of a surprise jumping off the runway for me too. It took a bit of getting used to but once I did, all was well

I also encourage use of minimap in the briefing; I don't trust those SAC air controllers

Cheers

Triad

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Bob_Drugstore_Arp - 13.07.2010

Thank you very much Triad773 for this mission! I had many happy minutes playing it! Full instrument control when zero-visibility is very interesting and dramatic action (I use full-real mode only). THAT WAS GREAT!!!
P.S. One little issue - I've got the airfield lights are much less brighter than they are on your screenshots. They are almost unvisible in my case. Maybe it is because I use HSFX... I dunno...
P.P.S. Thank you again Triad773!

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Triad773 - 13.07.2010

Yeah the lights- I use a Mod that I think I got here http://www.sas1946.com/main/index.php/topic,3718.0.html

I was not remembering how they would look without that mod, so I just went with it in hopes that the relative intensity was the same.

Thanks- glad you like

Triad

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Russ_Ace - 13.07.2010

sluggs Wrote:Ahh Triad, AWESOME mission.

And Russ_Ace beat me to it, I was going to say that the Kong Jiang-1 would be good for this mission

I did a couple of modifications though, I changed the weather to "Hazy" because my cpu was taking a bit of a hit and when you combine that with Freddys F-86 cockpit, it had some lag. Not much, but then combine that with the way the F-86 likes to "nose jump" on take off and I literally got off the ground 3 out of 6 or 7 tries, and I stalled and crashed on the 3 succesful ones :mrgreen:

The second thing I did was add a wingman just for the sake of atmosphere. He served absolutely no purpose, but it was cool to see him in formation with me (I gave him the same skin too).



Now, for the debriefing (humor me lol):
[I had everything set to full-real except for external views, so the map was useless]

I took off about 5 minutes after 5:00 AM in hazy weather, cloud bottoms at about 500 meters. I immediately turned to heading 180 and continued my climb at about 1500 to 2000 fpm at 70-80% throttle to allow my wingman to close the distance and form up, which he did on my starboard side and slightly aft.

At this point I asked Ground Control to give me a vector to the target,to which was responded with a heading of "175". We then turned to (approximately) heading 175 and continued our climb for the next 10-15 minutes.

We then maintained a heading of (approximately) 175 and an altitude that ranged between 23,000-26,000 feet for the next 10 minutes, periodically asking Ground Control for the nearest vector to target. After about 5-10 minutes of this, periodically asking for vectors, I was told to turn to (approximately) heading 327.

I was shocked, I hadn't seen a thing, but I followed through and turned to heading 327. I (we) followed this course for around 30-60 seconds when I asked Ground Control for another vector to target, which I was then told to turn to heading of which I do not exactly remember, although it was in almost the complete opposite direction of my current heading (327).

This cycle continued for nearly 10 minutes; me flying the designated heading, calling in for the next vector, then given a heading that was almost entirely opposite of the previous heading. I could not get a visual, although I had dropped in altitude from above 20,000 to somewhere near 10,000 feet.


{{Ok this is where I cheated lol. I couldnt see this guy at all, but I had a feeling he was close due to the designated vectors being almost completely opposite even though they were only a few seconds apart. So I Ctrl-F2'd to the B-29 while the game was paused and tried to match the cloud positions from his view with the cloud positions from my view. It helped a bit but the clouds that were just off of the horizon that I could only see the edge of made it difficult to determine positions, so I climbed back up to above 20,000 feet and continued the search visually.}}


After doing this for nearly another 10 minutes, I was in a wide right turn at somewhere near 20,000 feet, when at a heading of (approximately) 243 I looked North-North West and I made visual contact.

I (we) turned to follow the aircraft and closed on his starboard side, which I then identified as a TU-4 "Bull". I had to slow down considerably to maintain his speed (which was slightly below 200 Knots indicated). At this point I was having trouble with stability issues. I did not realize that my external tanks were empty though, which were the main cause of the low stability. My wingman, who I assume could not deccelerate in time, shot past and underneath me (he had jettisoned his externals at what I'm guesing was a few seconds before this).

I was moving further to the right of the aircraft and slightly ahead when I activated my Navigation Lights and also my Landing Lights. It was also at this time that my wingman (who was about 700-1000 meters ahead) went inverted and pulled into a steep dive and I did not see him again for the next few minutes. I continued ahead and about 200 meters above the "Bull", dropped my externals, and cut south across his flight path; he was heading almost dead west.

I circled around and pulled in behind the TU-4 and relatively maintained this position for a few minutes, moving back and forth (right to left, south to north) slightly aft and under his aircraft. Sometime during the next 30-60 seconds (approximately) my wingman had arrived back on my starboard side.I also noticed the belly gunner of the TU-4 traversing left and right, following my wingman, BUT HE DID NOT OPEN FIRE.

I then pulled to the TU-4's starboard side, pulled ahead, and crossed in front of his flight path to the left (north) then back to the right (south) one last time. All the while since I had made visual contact he had not responded to anything I had done. I did not want to shoot him down, he seemed to pose no threat, being nearly 100 kilometers south of Kiska AFB.

I then turned in the opposite direction (east) and then swung back around, gaining speed and closing in fast aft and starboard of the TU-4, changing my gunsight settings to "Gyro Only". I closed to within approximately 300 meters and opened fire with a 1-3 second burst, observing multiple hits on the tail gunners position, fuselage, and the right wing. I then shot another short burst, strafing a large section of the right wing. I saw the inner-most engine on the right wing seize and begin to pour black smoke.

I continued past him on his starboard side and climbed sharply, then descending into a wide sweeping turn and pulling up behind him at about 3000 to 3500 meters. I observed that he did not try to descend, or change course. At this point I fired a single AIM-9B from that range (3000-3500) meters. It struck him in the left elevetor and the entire aircraft exploded into multiple pieces.

I then turned north and asked Ground Control for a vector to the "nearest friendly airbase",to which I was given a heading of (exactly) 31. I continued on this course, descending to about 10,000 feet. shortly after I made visual contact with Amchitka Island and asked for permission to land, which was granted and I brought her down safely.

I had lost contact with my wingman just after the destruction of the TU-4, but after I had taxied to a stop off the south side of the runway near the Control Tower, he did a low level flyby over the runway. He then landed, taxied in, and parked about 30 meters from my aircraft.

Well thats kind of long, but I made it as realistic and accurately as I could (I saved the replay).

Once again, VERY GOOD JOB TRIAD!

~S~

I got lucky because he was above me in the moon light, i locked on and hit the cockpit, blew it in half.

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Bob_Drugstore_Arp - 13.07.2010

Triad773 Wrote:Yeah the lights- I use a Mod that I think I got here http://www.sas1946.com/main/index.php/topic,3718.0.html
I was not remembering how they would look without that mod, so I just went with it in hopes that the relative intensity was the same.
Thanks- glad you like
Triad

Yes Triad773! Now my world is like on your screenshots exactly! That is so beutiful! Super great lights from Santobr! Thank you for your link!
I'm gonna complete that great mission again!

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - sluggs - 13.07.2010

You know, benitomuso's radar mod woould be great for this mission.

The problem is, I cant get it to work with UP 2.01

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Triad773 - 13.07.2010

sluggs Wrote:You know, benitomuso's radar mod woould be great for this mission.

The problem is, I cant get it to work with UP 2.01

I have not tested it in 2.01, but the structure is not that much different I would imagine. As long as you have the F 86 J .4 version mod with the AIM 9b's and Agracier's Aleutians map it should work okay.

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - sluggs - 13.07.2010

No, no, your mission works perfectly.

It's the radar mod that I cant seem to figure out and Ive asked around but no one will help.

---

Re: [DOWNLOAD]Early Cold War Interception: SINGLE MISSION - Triad773 - 15.07.2010

sluggs Wrote:No, no, your mission works perfectly.

It's the radar mod that I cant seem to figure out and Ive asked around but no one will help.

Sry about delay; I would think if anyone had 2,1they should be able to add the missing elements but not having it, not sure :oops:

---