-
Content count
419 -
Joined
-
Last visited
Content Type
Profiles
Forums
Calendar
Gallery
Downloads
Store
Everything posted by comrpnt
-
Not sure if anyone else has come across this but I thought that I'd spread the word. http://www.bbc.co.uk/mediaselector/check/p...ram=1&asb=1 Regards, comrpnt.
-
Bridge Busting
comrpnt replied to snakeman's topic in Thirdwire: Strike Fighters 1 Series - Mission/Campaign Building Discussion
Hi Snakeman, I do mine by hand - editing the GermanyCE_targets.ini to add a bridge to a new or exiting target area. Like so... [TargetAreaXXX] Name=Weser bridge, South of Bremen Position=383038,672975 Radius=2000 ActiveDate=08/12/1982 Location=1 Alignment=FRIENDLY Target[001].Type=vBridge1End Target[001].Offset=-100,0 Target[001].Heading=180 Target[001].InactiveDate=08/13/1982 Target[002].Type=vBridge1 Target[002].Offset=-50,0 Target[002].Heading=0 Target[002].InactiveDate=08/13/1982 Target[003].Type=vBridge1 Target[003].Offset=0,0 Target[003].Heading=0 Target[003].InactiveDate=08/13/1982 Target[004].Type=vBridge1 Target[004].Offset=50,0 Target[004].Heading=0 Target[004].InactiveDate=08/13/1982 Target[005].Type=vBridge1End Target[005].Offset=100,0 Target[005].Heading=0 Target[005].InactiveDate=08/13/1982 Then you can make your OBJECTIVE_POINT coords the x,y location of the bridge - remember to adjust the x,y location to allow for the offset values from the origin of the target area where the bridge resides. From the example above, as the offset of the centre of the bridge is 0,0, then your OP x,y is the same as the target area, as illustrated below in the mission file (.msn) extract... ... TargetArea=Weser bridge, South of Bremen ObjectiveID=3 ... // Approach RECON area Waypoint[04].Command=INITIAL_POINT Waypoint[04].Position=400000,672975,2000 Waypoint[04].Size=50 Waypoint[04].Speed=180 // RECON target area Waypoint[05].Command=OBJECTIVE_POINT Waypoint[05].Position=383038,672975,2000 Waypoint[05].Size=50 Waypoint[05].Speed=180 Waypoint[05].Objective=TRUE ... This WOE training mission pack contains a friendly bridge over the Weser to recon - so you can see how it's done in context. http://forum.combatace.com/index.php?autoc...p;showfile=5559 Hope this helps. Regards, comrpnt. -
WOE carrier campaign?
comrpnt replied to Stratos's topic in Thirdwire: Strike Fighters 1 Series - Mission/Campaign Building Discussion
Hi Stratos, no, but I do have a set of carrier missions in development for WOE that involve a mass strike against a heavily defended Warsaw Pact target, if that's of interest. When it's ready you'll be able to choose from one of Strike, SEAD or CAP missions for [A-6E, A-6B, EA-6A, FA-18A (carrier-based)], or [F-111F, F-4G, F-4M, Harrier GR-3 (land-based)]. Each aircraft choice gives you a different perspective of the day's events. Should be ready in a week or so. Regards, comrpnt. -
Anti-shipping mission problem
comrpnt replied to Sheriff__001's topic in Thirdwire: Strike Fighters 1 Series - General Discussion
Hi Sherrif, the ground objects in the latest patched versions of the TW games are in their own folders in the Objects/GroundObject folder. The object should have the same name (exactly) as the folder it's stored in, so, for example, the carrier that comes with Task Force 58 (see here: http://forum.combatace.com/index.php?autom...p;showfile=5438) will appear in folder named "CV-59" in the Objects/GroundObject folder. The ini file that defines the model within that folder will be named "CV-59.ini" and so on for each object. Aircraft are similarly named after their folder name. Reference to a ground object in a mission file (.msn) will reference the object exactly as named in the GroundObject folder - for example: [GroundMission001] GroundObjectType=CV-59 Name=USS Saratoga Texture=CV60 FormationType=Single ShipNumber=1 Size=1 StartTime=0 NavalObject=TRUE Carrier=TRUE Position=500000,800000,0 Heading=180 Speed=0 Loadout= ObjectiveID=1 Alignment=FRIENDLY Nation=USN Hope this helps, regards, comrpnt. :-) -
Carrier Missions Pack (SFP1/SFG/WOE) V2.10
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Incidentally, if you wait a couple of weeks I should have finished a WOE-specific set of missions with carrier support that uses only add-on carrier-based aircraft (as WOE doesn't come with any by default). So, the missions will therefore be set to use just those addon aircraft already. So far it looks like there will be the option of flying the A-6E, EA-6A and FA-18A from the carriers, then F-111F, Harrier GR3 (Stock), A-10A (Stock), F-4C Wild Weasel IV (and probably a few others) from the mainland. Read parts of 'Red Storm Rising' if you want an idea what's coming (http://en.wikipedia.org/wiki/Red_Storm_Rising). Like I said, if you're a WOE user then this should give you plenty to play with. The next mission Pack will be posted here as usual. Regards, comrpnt. -
Carrier Missions Pack (SFP1/SFG/WOE) V2.10
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi there Hide86, the missions show up for all those aircraft you have installed in your game, so for example, in SFP1/SFG you'll see just the one's you have in the objects/aircraft folder. In WOE you'll see a lot less as it doesn't come with any carrier-based aircraft. Go to here (http://www.column5.us/aircraft.shtml) or here (http://forum.combatace.com/index.php?autoc...&showcat=23) to add aircraft that match the other missions you want to try. In most cases I tended to use Stock carrier-based aircraft if they were available in the game already and their supplied skins. If you change the missions to use variants of the Stock aircraft I used (e.g add another variant of, say, the A-4E) then you'll need to edit the mission to use the new skins that come with that variant. As for mission briefings, the game does not support them in-game. Read them before-hand (or Alt-Tab to go back to the desktop to read them). I put my Mission Briefings folder in the main game's folder (i.e SFP1/Mission Briefings) to keep them close to the game to which they're associated. Hope this info helps. Let me know if you're still having problems. Kind regards, comrpnt. :-) -
Carrier Missions Pack (SFP1/SFG/WOE) V2.10
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi Typhoid, thanks for the feedback. You know, I never thought to try it out as an alternative terrain for WOE (doh!). Sometimes these things need another perspective in order to see their potential. Much appreciated :-) I've got a good write-up for Operation El Dorado Canyon so will put something together soon - everything I think I need is out there, just need to bring it all together for the 14th/15th April '86. Cheers, regards, comrpnt. -
Carrier Missions Pack (SFP1/SFG/WOE) V2.10
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi Canadair, yes, sure. I'll add it to my list - will take a while though I expect, my in-tray is filling up with mission requests ;-) I'll read up on it to get the story right. In fact I remember it well as I was working up near Lakenheath (UK) at the time when the F-111s went in from there. It was a pretty tense time around the base during that week in April '86. Cheers, regards, comrpnt. -
VMFA-531 Mission Pack I (13-17 April 1965) for WOV
comrpnt posted a topic in Thirdwire: Strike Fighters 1 Series - File Announcements
File Name: VMFA-531 Mission Pack I (13-17 April 1965) for WOV File Submitter: comrpnt File Submitted: 16 Dec 2007 File Updated: 13 Jul 2009 File Category: User Made Missions This is the first in a series of Mission Packs based on written accounts taken from the mission log of VMFA-531 'Ghost' Squadron for April 1965. This Pack replicates the missions undertaken by VMFA-531 for 13th April - 17th April 1965 inclusive. [Acknowledgements] I would like to thank 531_Ghost for the inspiration behind this project and Mike Wanamaker & Lee R. De Haven for writing the extracts from the original mission logs. Also, thanks go to all those contributors that have provided an environment whereby this mission pack could be produced with a degree of realism. Without your modifications to the original WOV platform the creation of this mission pack would not be possible. I am standing on the shoulders of giants - thank you. Update V1.10 This mod has been updated on request to remove direct links to any Capun and A-team prerequisite models. Instead please contact Capun for access - details enclosed. [Pre-requisites] This mission pack has a large number of pre-requisites due to the realism that I have tried to incorporate into the game. Please bear with me. This first Pack will require more pre-requisites than the subsequent Packs but you will get out what you put in, so the time invested in installing the pre-requisites will be worth it. The README details all necessary pre-requisites and installation instructions. [Contents] This Pack includes the following: 1. 11 x Missions taken from the historical accounts of VMFA-531 for the dates 13th April 1965 to 17th April 1965. 2. Detailed mission briefing pages for each mission. 3. The VMFA-531 mission log for April 1965. 4. New VMFA-531 pilot skins. 5. Static F-4B aircraft. 6. New loadout definitions for the F-4B. 7. Target definitions for each mission. If there are any problems with the missions then please contact me directly, not the authors of the pre-requisites. Thanks. During the course of 2008 I intend to post more mission packs that carry on where the last one left off, working through all of the missions identified in the original Mission Log write-up. That's about 60 missions in total! As usual, feedback and comments always greatly appreciated. Hope you like it. Regards, comrpnt. Click here to download this file -
VMFA-531 Mission Pack I (13-17 April 1965) for WOV
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi Canadair, thanks for your comments and feedback. In answer to your questions... 1. I used exclusively the mission log write-up to give me details about each mission and as, for example, AAA was not explicitly mentioned in the mission write up I didn't feel justified in adding into the original mission definitions I wrote. Adding it yourself is an ideal way to make these missions more fun and more difficult, if not historically correct. I shall leave it up to those who were there at the time that read these forums to respond with details of what it was really like w.r.t enemy defences in the South. (Anyone care to comment, please)? 2. As for the location of the target areas, the mission write-up was very detailed about the bearing and distance from key points, such as Da Nang or the Bien Hoa TACAN. To get these correct, given the inaccuracies of the WOV map/terrain for Vietnam I flew from each origin point, say Da Nang, on the bearing specified in the write-up for the distance specified. Then I looked around on the ground for somewhere decent to place my ground objects. In most cases these were placed within a reasonable distance from the specified target location. However, for the Bien Hoa TACAN, as I didn't have the exact location I had to guestimate its location and use that as my origin, then look for suitable target locations that were the correct heading and distance from that point. I hope these responses help answer your questions. More Mission packs will be coming out as the year rolls on, so hopefully you'll enjoy those too. Thanks again for the feedback. Regards, comrpnt. :-) -
Flying as Wingie
comrpnt replied to Rambler 1-1's topic in Thirdwire: Strike Fighters 1 Series - General Discussion
Hi Rambler, there are two ways to achieve this that I can think of. First, you can write a mission which contains a minimum of two aircraft - you as the wingman and the other (AI aircraft) as the lead. Examples of how to do this are here (SPF1) http://forum.combatace.com/index.php?autoc...p;showfile=4863 and here (WOV) http://forum.combatace.com/index.php?autoc...p;showfile=3911. Second, you can define a new formation type in FLIGHT/FORMATION.INI which places your AI wingman in formation in front of you. He still follows your moves but is physically located in front. (See details contained in this mission pack on how to do this: (WOV) http://forum.combatace.com/index.php?autoc...p;showfile=5847) Advantages of the first choice are that the lead is automonous and will carry out his mission regardless of what you do, so you can position yourself anywhere in relation to him. The downside is that you will have to work hard to keep up and close by in formation as he performs his mission. Advantages of the second choice are that the AI aircraft is 'attached' to you, in that he will re-position himself next to you after each manoeuvre and only detach on final approach or when you send him off to target one of your targets. A disadvantage is that the AI of a wingman (albeit one who sits out in front) restricts what he will do to what you do, so he's not automonous. Personally I prefer the first choice as I want my squadron buddies doing their own thing and reacting automatically to the enemy without me assigning targets for them. That way I know each man's mission in my wing prior to the flight and then all I have to do is keep up with them(!) Hope this helps, regards, comrpnt :-) -
I was so pleasantly surprised and encouraged by the positive feedback from my recent Carrier Training Mission Pack that I've decided to make another one to complement the first. Here are some screen shots of Carrier Training Mission Pack II. It supports all of the carrier-based Stock WOV aircraft and should be ready in a couple of days time. Here are details of what CTM Pack II contains: A little cooked, but still flying. Time to go home... BTW, You will need Pack I in order to use Pack II. Regards, comrpnt.
-
Carrier Training Mission Pack II screenies
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - Mission/Campaign Building Discussion
Hey thanks Mladuna, I tell you what I'll do - I'll port the carrier mission pack II to SFP1/SFG, probably using USAFMTL's Libya terrain. Would that be ok? Watch this space for news of an upload for them here at CA in a week or so. Cheers, regards, comrpnt. :-) -
For those of you who've tried VMFA-531 Mission Pack I, you may want to know that I've just posted screenies of Mission Pack II up at SimHQ... See here: http://www.simhq.com/forum/ubbthreads.php?...051#Post2425051 Pack II should be beta tested and released here at CA by the end of January. Pack I screenies here: http://www.simhq.com/forum/ubbthreads.php?...424#Post2397424 Pack I - get it here: http://forum.combatace.com/index.php?autom...p;showfile=5675 Regards, comrpnt.
-
VMFA-531 Mission Pack II (18-19 April 1965) for WOV
comrpnt posted a topic in Thirdwire: Strike Fighters 1 Series - File Announcements
File Name: VMFA-531 Mission Pack II (18-19 April 1965) for WOV File Submitter: comrpnt File Submitted: 25 Jan 2008 File Updated: 13 Jul 2009 File Category: User Made Missions This is the second in the series of Mission Packs based on written accounts taken from the mission log of VMFA-531 'Ghost' Squadron for April 1965. This Pack replicates the missions undertaken by VMFA-531 for 18th April - 19th April 1965 inclusive. [Acknowledgements] I would like to thank 531_Ghost for being the inspiration behind this project (and for the beta testing) and Mike Wanamaker & Lee R. De Haven for writing the extracts from the original mission logs. Also, thanks go to all those contributors that have provided the mods that I've used and referenced in this pack. Very much appreciated :-). Update V1.10 This mod has been updated on request to remove direct links to any Capun and A-team prerequisite models. Instead please contact Capun for access - details enclosed. [Pre-requisites] This mission pack requires some pre-requisites and these are documented in the readme. The readme also contains complete installation instructions. [Contents] This Pack includes the following: 1. 11 x Missions taken from the historical accounts of VMFA-531 for the dates 18th April 1965 to 19th April 1965. 2. Detailed mission briefing pages for each mission. 3. Static F-4B, O-1E, F-100D and A310 MRTT aircraft. 4. New loadout definitions for the F-4B, O-1E and F-100D. 5. Target definitions for each mission. If there are any problems with the missions then please contact me directly, not the authors of the pre-requisites. Thanks. Regards, comrpnt. Click here to download this file -
VMFA-531 Mission Pack II (18-19 April 1965) for WOV
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi Canadair, nope, you don't need to adjust the ServiceStartYear date - even though you could if you wanted to. It doesn't affect the inclusion of the ships in the game. Cheers, regards, comrpnt. -
VMFA-531 Mission Pack I (13-17 April 1965) for WOV
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi Storm, yes, simply drop the new ground objects (i.e. ships) in the GroundObjects folder and that's it. Let me know how you get on. Thanks. Regards, comrpnt. -
Version
770 downloads
This is the second in the series of Mission Packs based on written accounts taken from the mission log of VMFA-531 'Ghost' Squadron for April 1965. This Pack replicates the missions undertaken by VMFA-531 for 18th April - 19th April 1965 inclusive. [Acknowledgements] I would like to thank 531_Ghost for being the inspiration behind this project (and for the beta testing) and Mike Wanamaker & Lee R. De Haven for writing the extracts from the original mission logs. Also, thanks go to all those contributors that have provided the mods that I've used and referenced in this pack. Very much appreciated :-). Update V1.10 This mod has been updated on request to remove direct links to any Capun and A-team prerequisite models. Instead please contact Capun for access - details enclosed. [Pre-requisites] This mission pack requires some pre-requisites and these are documented in the readme. The readme also contains complete installation instructions. [Contents] This Pack includes the following: 1. 11 x Missions taken from the historical accounts of VMFA-531 for the dates 18th April 1965 to 19th April 1965. 2. Detailed mission briefing pages for each mission. 3. Static F-4B, O-1E, F-100D and A310 MRTT aircraft. 4. New loadout definitions for the F-4B, O-1E and F-100D. 5. Target definitions for each mission. If there are any problems with the missions then please contact me directly, not the authors of the pre-requisites. Thanks. Regards, comrpnt. -
Carrier Mission Pack (WOV) V2.10
comrpnt posted a topic in Thirdwire: Strike Fighters 1 Series - File Announcements
File Name: Carrier Mission Pack (WOV) V2.10 File Submitter: comrpnt File Submitted: 19 Jan 2008 File Updated: 13 Jul 2009 File Category: User Made Missions Carrier Missions and Training Pack for WOV Welcome to the 'Pack' for WOV, which provides basic carrier training and operations missions using (mostly) stock aircraft. Updated to V2.00 This mission pack has had a major update. 1. Merged Mission Pack I and II for WOV together into this single pack - training and operations missions are now all together in one place. 2. Re-vamped US fleet to be defined as types and also targets, to greatly simplify mission file contents and make it quicker to load missions. 3. Re-wrote ReadMe to point at currently available ships from the A-team - ReadMe is now also in HTML to make it easier to link to all pre-reqs. 4. Renamed mission files to make it easier to distinguish between carrier training (CT) and carrier operations (CO) missions. Updated to v2.10 This mod has been updated on request to remove direct links to any Capun and A-team prerequisite models. Instead, please contact Capun for access - details enclosed. Missions Included in this Pack The missions provided by this pack are named according to mission type, aircraft type, weather conditions and time of day. For example, using an A-4B, training missions are named as follows: CT A-4B denotes take off, circuit fleet and land back on carrier, in daylight, in clear weather CT A-4B(BW) denotes take off, circuit fleet and land back on carrier, in daylight, in bad weather CT A-4B(N) denotes take off, circuit fleet and land back on carrier, at night, in clear weather CT A-4B(BWN) denotes take off, circuit fleet and land back on carrier, at night, in bad weather CT A-4B(R ) denotes take off, RV with KA-6D tanker aircraft, circuit fleet and land back on carrier, in daylight, in clear weather CT A-4B(RBW) denotes take off, RV with KA-6D tanker aircraft, circuit fleet and land back on carrier, in daylight, in bad weather For operations missions, again using an A-4B, the following naming convention is used: CO A-4B(AS) denotes anti-ship mission. Intercept enemy patrol boats approaching from the South-West and North-West simultaneously, in daylight, in clear weather CO A-4B(ASBW) denotes anti-ship mission. Intercept enemy patrol boats approaching from the South-West and North-West simultaneously, in daylight, in bad weather CO A-4B(I) denotes aircraft intercept mission. Intercept enemy Migs approaching from the North-West at low level, in daylight, in clear weather CO A-4B(IBW) denotes aircraft intercept mission. Intercept enemy Migs approaching from the North-West at low level, in daylight, in bad weather Pre-requisites are listed in the README, together with installation instructions. comrpnt (April 2008). Click here to download this file -
Version
1,328 downloads
Carrier Missions and Training Pack for WOV Welcome to the 'Pack' for WOV, which provides basic carrier training and operations missions using (mostly) stock aircraft. Updated to V2.00 This mission pack has had a major update. 1. Merged Mission Pack I and II for WOV together into this single pack - training and operations missions are now all together in one place. 2. Re-vamped US fleet to be defined as types and also targets, to greatly simplify mission file contents and make it quicker to load missions. 3. Re-wrote ReadMe to point at currently available ships from the A-team - ReadMe is now also in HTML to make it easier to link to all pre-reqs. 4. Renamed mission files to make it easier to distinguish between carrier training (CT) and carrier operations (CO) missions. Updated to v2.10 This mod has been updated on request to remove direct links to any Capun and A-team prerequisite models. Instead, please contact Capun for access - details enclosed. Missions Included in this Pack The missions provided by this pack are named according to mission type, aircraft type, weather conditions and time of day. For example, using an A-4B, training missions are named as follows: CT A-4B denotes take off, circuit fleet and land back on carrier, in daylight, in clear weather CT A-4B(BW) denotes take off, circuit fleet and land back on carrier, in daylight, in bad weather CT A-4B(N) denotes take off, circuit fleet and land back on carrier, at night, in clear weather CT A-4B(BWN) denotes take off, circuit fleet and land back on carrier, at night, in bad weather CT A-4B(R ) denotes take off, RV with KA-6D tanker aircraft, circuit fleet and land back on carrier, in daylight, in clear weather CT A-4B(RBW) denotes take off, RV with KA-6D tanker aircraft, circuit fleet and land back on carrier, in daylight, in bad weather For operations missions, again using an A-4B, the following naming convention is used: CO A-4B(AS) denotes anti-ship mission. Intercept enemy patrol boats approaching from the South-West and North-West simultaneously, in daylight, in clear weather CO A-4B(ASBW) denotes anti-ship mission. Intercept enemy patrol boats approaching from the South-West and North-West simultaneously, in daylight, in bad weather CO A-4B(I) denotes aircraft intercept mission. Intercept enemy Migs approaching from the North-West at low level, in daylight, in clear weather CO A-4B(IBW) denotes aircraft intercept mission. Intercept enemy Migs approaching from the North-West at low level, in daylight, in bad weather Pre-requisites are listed in the README, together with installation instructions. comrpnt (April 2008). -
VMFA-531 Mission Pack I (13-17 April 1965) for WOV
comrpnt replied to comrpnt's topic in Thirdwire: Strike Fighters 1 Series - File Announcements
Hi Storm, mmm, your problem interests me. Certainly I will make the next Pack's installation instructions clearer. Thanks for the feedback. As for the Ground Objects, the ships in the fleet should be simply dropped into the Objects/Ground Objects folder - the game will then pick them up automatically when next run. You don't need to modify the GroundObject.ini file. An optional extra I supplied in the README allows you to immobilize the ships completely so that they don't drift while you are on your mission, making it simpler to find the fleet when you return and also for the AI to successfully land at the locations I specified in the mission files. This mod requires that you edit the _DATA.ini file for each affected ship in the fleet in their respective folders within the Ground Objects folder (tedious I know, but I couldn't find a simpler solution and I don't like wandering ships). Glad you're enjoying the brief moments you're able to run the missions - and the others who've replied to this thread. Many thanks for the feedback. Much appreciated. Please keep the highs, lows and bug reports coming. This is an evolving project so the feedback gets put into the next Pack. Latest news is that Pack II is now well underway and looks like it will ready by the end of January. From the mission log, read up on April 18th - 19th to see what will be included in it. There will be 10 missions, including Strike, FAC, Fast FAC (bonus mission - be a Misty for a day!), Patrol, Escort and Recon. Cheers, regards, comrpnt. -
Try here for some video...http://www.youtube.com/watch?v=Qy6q-_AEtQg Regards, comrpnt.
-
New pilots
comrpnt replied to triplethr3at's topic in Thirdwire: Strike Fighters 1 Series - General Discussion
You could always try these... http://forum.combatace.com/index.php?autom...p;showfile=3168 http://forum.combatace.com/index.php?autom...p;showfile=3344 Regards, comrpnt. -
The new mission set is here...
comrpnt replied to a topic in Thirdwire: Strike Fighters 1 Series - Mission/Campaign Building Discussion
Hi Topcat II, thanks for the feedback - that's good to hear - sort of like 'gamma' testing, if you like ;-) The next Pack will probably be out by the end of January '08 and should be a lot simpler to install as the number of pre-reqs looks like it will be minimal - mostly _targets.ini and simple loadout.ini additions. Cheers, regards, comrpnt. :-) -
Version
943 downloads
This is the first in a series of Mission Packs based on written accounts taken from the mission log of VMFA-531 'Ghost' Squadron for April 1965. This Pack replicates the missions undertaken by VMFA-531 for 13th April - 17th April 1965 inclusive. [Acknowledgements] I would like to thank 531_Ghost for the inspiration behind this project and Mike Wanamaker & Lee R. De Haven for writing the extracts from the original mission logs. Also, thanks go to all those contributors that have provided an environment whereby this mission pack could be produced with a degree of realism. Without your modifications to the original WOV platform the creation of this mission pack would not be possible. I am standing on the shoulders of giants - thank you. Update V1.10 This mod has been updated on request to remove direct links to any Capun and A-team prerequisite models. Instead please contact Capun for access - details enclosed. [Pre-requisites] This mission pack has a large number of pre-requisites due to the realism that I have tried to incorporate into the game. Please bear with me. This first Pack will require more pre-requisites than the subsequent Packs but you will get out what you put in, so the time invested in installing the pre-requisites will be worth it. The README details all necessary pre-requisites and installation instructions. [Contents] This Pack includes the following: 1. 11 x Missions taken from the historical accounts of VMFA-531 for the dates 13th April 1965 to 17th April 1965. 2. Detailed mission briefing pages for each mission. 3. The VMFA-531 mission log for April 1965. 4. New VMFA-531 pilot skins. 5. Static F-4B aircraft. 6. New loadout definitions for the F-4B. 7. Target definitions for each mission. If there are any problems with the missions then please contact me directly, not the authors of the pre-requisites. Thanks. During the course of 2008 I intend to post more mission packs that carry on where the last one left off, working through all of the missions identified in the original Mission Log write-up. That's about 60 missions in total! As usual, feedback and comments always greatly appreciated. Hope you like it. Regards, comrpnt.