comrpnt

I must be getting old, and my fuse is getting short, but I suddenly feel the need to sound-off and retort... [Rant On] Is it just me, or are some people never happy? I don't understand the difficulty in requesting permission from Capun to get access to the excellent models on his site. For the carrier missions I chose to use his models and that of the A-team. Yes, they used to be hosted here at CA, but now they're not. Big deal. They are still available and I've cleaned up the mission packs to make sure I only use models that are still posted on his site - rather than one or two that have now been withdrawn since I wrote the originals - so at least you have a current working solution with the reworked versions. I even rewrote the README using HTML links to each of the prerequisites, to make it as easy as possible to get the models to make it all work. If you really want to do this using the CA-hosted ships, then here's a list of possible candidates: USS Tarawa Carrier http://forum.combatace.com/index.php?autoc...p;showfile=2688 Coventry Destroyer http://forum.combatace.com/index.php?autoc...p;showfile=3351 Glamorgan Destroyer http://forum.combatace.com/index.php?autoc...p;showfile=3350 Cardiff Destroyer http://forum.combatace.com/index.php?autoc...p;showfile=3340 Yarmouth Frigate http://forum.combatace.com/index.php?autoc...p;showfile=1917 Plymouth Frigate http://forum.combatace.com/index.php?autoc...p;showfile=1915 Foch Battleship http://forum.combatace.com/index.php?autoc...p;showfile=2173 Cavour Battleship http://forum.combatace.com/index.php?autoc...p;showfile=2198 You'll need to encode each one as a type, and then add a new target definition which places them accordingly, to replace the one I used in the appropriate targets definition file. Oh, and you'll also need to rename the carrier that must be defined in each mission file, to coincide with the one defined in the targets file for the new fleet. To just use the CA-hosted ships to make up a wholly new fleet is one rework too far, when there are perfectly suitable ships available elsewhere. If you feel the need, then be my guest. [Rant off] Regards, comrpnt

Ok, SFP1/SFG (and WOE) version now also re-worked and uploaded. See here: http://forum.combatace.com/index.php?autoc...p;showfile=5989 Enjoy! Any problems, please let me know. All the best, comrpnt :-)

Ok folks, the re-write and clean-up has started. WOV version has been re-done: http://forum.combatace.com/index.php?autoc...p;showfile=5847 Tomorrow the SFP1/SFG version. Cheers, regards, comrpnt.

Anything else worth doing in Vancouver? I'm passing through there in late July and might have a couple of hours to kill. Cheers, comrpnt :-)

File Name: Operation Rubicon (WOE) - The BDA Missions File Submitter: comrpnt File Submitted: 07 Apr 2008 File Updated: 23 May 2010 File Category: User Made Missions Operation Rubicon (for WOE) – The Bomb Damage Assessment (BDA) Missions Welcome. These missions complement and extend the existing Operation Rubicon scenario (see here: http://forum.combata...p;showfile=6299) Disclaimer If there are any problems with these missions and my own mods, then please contact me directly, not the authors of any prerequisites that I have used. Thanks. Missions Provided in this Set USAFE F-111F (in stealth camo) departs Jever Airbase on Recon mission to carry out BDA for the Rostock Naval yard strikes RF-111G (experimental aircraft) departs Jever Airbase on Recon mission (as above) F-15A departs Jever Airbase on Escort mission to see F-111F/RF-111G safely into enemy airspace for their BDA mission RAFG Lightning F6 departs RAF Wunstorf on QRA mission to defend returning Laage strike force, and also assist Jaguar on BDA mission to Laage airbase Jaguar GR.1 departs RAF Gütersloh on Recon mission to assess Laage bomb damage Prerequisites The enclosed README is written in HTML so the few prerequisites that I've used are easy to find. Contents Combat & Training Missions for each aircraft listed above NATO briefings (for each type of mission, includes detailed planning map) Installation Guide (i.e README) Screenshots Available Here: http://forum.combata...rt=#entry149152 Any problems, please let me know. Thanks, regards, comrpnt. :-) Click here to download this file

Hi Cas, yes, I know. This is a bit of a problem as most of the ships have moved to Capun's site and some of them have become unavailable since I uploaded this pack. Give me a day or so and I'll rework the content and update the pack to point you towards alternative ships still hosted at CA. I have fixes for them all BTW, as Op. Rubicon was likewise affected and has since been patched, so it's just finding the time to do the updates. Regards, comrpnt.

Basher11, autopilot will not drop your own bombs - you're on your own on that one. Instead, define another aircraft for your mission and let the AI take over the first one you defined. Use PlayerMissionID=2 to tell the game you want to fly the 2nd one, then use F6 to view the AI-controlled aircraft. It should deploy its ordnance under AI control provided you have set up the Initial_Point and Objective_Point correctly. Regards, comrpnt.

Please send me a link to the specific model you mean. I don't see a RA-5C in the downloads section here or over at Column5. Then I'll have a go. For info, the version I got from Column5 a few months back lands fine on a carrier (here:http://www.column5.us/aircraft.shtml). Try this...in the _data.ini file... [Tailhook] SystemType=ARRESTER_HOOK MaxDeflection=60.0 AnimationID=1 Retractable=TRUE DeployTime=1.0 ModelNodeName=Tailhook HookArmLength=2.9 AttachmentPosition=-0.0000,-4.7687,-1.3335 ...and don't forget to add "SystemName[xxx]=TailHook" to the [Fuselage] section near the top of the _data.ini (replace the xxx's accordingly) Regards, comrpnt. :-)

Should have something up tomorrow - F-111F Stealth and RF-111G BDA Recon, and F-15A escort of Recon bird (for Op. Rubicon). Flys great BTW...although I need to practice my low-level approaches! See what I mean about needing the practice... Could sure have used ECM, like in the F-111F version - at least I came home after that mission. ;-) Regards, comrpnt.

The F-111F pit can be found here: http://www.schmidtwerner.de/products/f-111_pit.html Thanks for this model BTW - it sure looks mean! I'll knock up a BDA mission post-Operation Rubicon for you and send it along, so you can take it in low over Rostock after the F-111Fs and A-6Es have chewed it up. Cheers, regards, comrpnt. :-)

File Name: Operation Rubicon (WOE) File Submitter: comrpnt File Submitted: 27 Mar 2008 File Updated: 13 Jul 2009 File Category: User Made Missions Operation Rubicon (for WOE) Welcome to Operation Rubicon (for WOE) - where Rubicon has two meanings. First, it denotes R(ostock)uB(lockade)icon. Second, to "cross the Rubicon" is a popular idiom meaning to go past a point of no return and refers to Julius Caesar crossing the river of that name in 49 BC, deliberately as an act of war. The objective of this mission is to attack and destroy the Soviet Northern Naval fleet undergoing repairs and maintenance in Rostock Naval Yard, East Germany. Strategically, this will stop the Soviet fleet from responding to NATO air and ground strikes on Warsaw Pact forces massing in East Germany. By this very act the NATO forces have reached the point of no return. This mission was inspired from a Scenario in Tom Clancy's 1986 novel, Red Storm Rising (http://en.wikipedia.org/wiki/Red_Storm_Rising). Version 1.01 update Replaced broken links to CA-hosted A-Team models in README with links to Capun's skunkworks site. Version 1.02 update Removed reference to withdrawn A-Team model of Soviet Chapeav KrestaII-class cruiser. Alternative existing ship model used instead. Version 1.03 update Fixed minor typos in NATO and Warsaw Pact briefings. Version 1.04 update Removed reference to withdrawn A-Team model of CGN-9 cruiser. Alternative existing ship model used instead. Version v1.10 update Updated on request to remove direct links to any Capun and A-team prerequisite models. Instead, please contact Capun for access - details enclosed. Acknowledgements First, thank you to TK for providing an excellent platform and modding environment. Second, thanks go to all those modders that have provided the prerequisites I have used in my mission packs. Your hard work and dedication is very much appreciated. If there are any problems with these missions and my own mods, then please contact me directly, not the authors of the prerequisites. Thanks. Mission Overview This mission is complex (my most complex to-date) and involves a total of 65 NATO aircraft, drawn from USN, USMC, USAFE and RAFG, and 13 Warsaw Pact aircraft. You can take the part of each main player in the Operation and experience it from their perspective. The aircraft used on each side and their specific mission are detailed as follows: NATO Forces USN/USMC EA-6A, departs CV-62 USS Independence on SEAD mission to destroy EWR sites near Rostock naval yard A-6B, similar mission as above. A-6E, departs CV-62 on Strike mission to destroy the Soviet fleet at Rostock KA-6D Tanker (only used in air-to-air refuelling training missions) E-2C Hawkeye, departs CV-60 USS Saratoga on AEW mission close to East German (IG) border (AI mission only) FA-18A, departs CV-60 USS Saratoga on CAP mission North-East of Rostock USAFE F-111F, en route from RAF Lakenheath(UK) on Strike mission to destroy Soviet fleet at Rostock (returns to Jever Airbase, West Germany) F-4G, departs Diepholz Airbase on SEAD mission to penetrate border defences and destroy SAM sites prior to strike force arriving A-10A, departs Fassberg Airbase on Strike mission to disable enemy defences at Laage airbase RAFG Harrier GR3, departs RAF Wunstorf on Strike mission to disable enemy airbase at Laage F-4M, departs RAF Gütersloh on Strike mission to disable enemy airbase at Laage Warsaw Pact Forces Mi-24 Hind, departs Laage Airbase on Intercept mission to multiple radar threats approaching from the West MiG-29C, departs Laage Airbase on Intercept mission to radar threats from the North and also from the West SU-27 Flanker, departs Pütnitz Airbase on Intercept mission to multiple radar threats approaching from the North-West Prerequisites The prerequisites for this set of missions are extensive. However, this time I have written the README as a HTML file with links provided to each one, so they're easy to find. It's worth remembering that stock WOE does not contain enough of the correct types of NATO or Warsaw Pact aircraft or ground objects required to model such a complex scenario as portrayed by this Operation, especially for the era I have chosen (i.e. 1979). Contents Combat & Training Missions for each major player (i.e. aircraft) in the Operation Enhancements to the GermanyCE targets file (including enemy air defences, populated harbour targets and populated airbases) Enhancements to the Types file (to complement the targets additions) NATO briefings (for each type of mission, includes detailed planning map) Warsaw Pact briefings (for each type of mission) Comprehensive Installation Guide (i.e README) Screenshots Available Here: http://bbs.thirdwire.com/phpBB/viewtopic.php?t=5209 Any problems, please let me know. Thanks, regards, comrpnt. :-) Click here to download this file

Thanks for that article - brought back some good memories of the F-4s at a 74 Sqn reunion I went to at Wattisham in the summer of '91 with my Dad, who used to be stationed there at the end of his service and who had worked with 74's Lightnings at Tengah, Singapore. (See here: http://www.f4phantoms.co.uk/trevor.html). My tribute (in WOV): Happy days. Thanks again. Regards, comrpnt. :-)

Hi folks. Thanks for the kind words, and yes, Canadair, I did number the targets to coincide with the numbering I had used for the lighting mod that I did some while back - it was easier for me to do this as I always run WOE with that earlier mod :-) For those bases without QRA facilities I added the ground equipment but not the hangar buildings as these require changes to the lighting mod for those extra bases where QRA sheds were not originally present in my earlier lighting mod. Hopefully you're all up-and-running with the unexpected changes to the links to the A-team's models that I'd used. Please let me know if anyone is having trouble setting up their system with all these pre-reqs. Thanks. Regards, comrpnt.

Hi folks, thought I'd post a storyboard of my latest mission set, but I blew the limit on images in a single post...so I posted it here instead http://bbs.thirdwire.com/phpBB/viewtopic.php?t=5209. Should be ready in a week, as soon as I've written the mission briefings. Here's the banner page in the meantime: And the overall planning page: Regards, comrpnt. :-)

Mmm. Yes. That's annoying. They seem to have been pulled from CA since I wrote the README. I've now updated the README and fixed the broken links. Each one now points directly to Capun's skunkworks site, and I replaced one (i.e. Chapaev) that had been withdrawn. (I wish we had a notification mechanism that warns us when downloads are withdrawn or moved) Hopefully, as of version 1.02, that's all the links working again. Regards, comrpnt.

Out now! http://forum.combatace.com/index.php?autoc...p;showfile=6299

You will need lots of downloads. Nothing I can do to avoid it, but the readme I'm producing is in html this time so each pre-req is a link to the appropriate download. As for the GroundObjects limit...see here: http://bbs.thirdwire.com/phpBB/viewtopic.php?t=5173 Regards, comrpnt.

Hi Canadair, I'm with you on that - they are already targets and types! ;-) - but restricted to "ActiveDate=04/20/1979"..."InactiveDate=04/30/1979" (that's how I broke the limit on GroundObjects - but fixed now!). For you, and others, I can unrestrict them easily. But this may affect other situations you load into WOE. Not sure if a one-size-fits-all will be the way to go straight out of the box once I ship the mission pack. BUT, it's simply to unrestrict the _targets.ini entries just be removing the offending InactiveDate line for each one. For info, populated bases in the mission set are: [NATO] Jever, Fassberg, Gutersloh, Wunstorf, Diepholz, [Warsaw Pact] Laage and Putnitz. So, wherever you fly from and recover to, you'll see something on the base. Kind regards, comrpnt. :-)

For the E-2C, the planning map above shows you the routes - in light Blue. One to cover the Northern route USN/USMC inbound traffic and one further to the South for everyone else coming in from the West. Obviously this is all just simulated. The E-2C is just eye candy air traffic in this mission pack as it has a basic 'there and back again' mission defined. I didn't think anyone would want to take that role on the day of the mission as the E-2Cs don't engage with the enemy, so I left it as AI. As you can see, they mostly fly overland to their assigned GIB area, then recover back to CV-60, approaching from the North. comrpnt.

Many thanks Erik, much appreciated. :-)

Is there an architectural limit imposed on the number of targets allowed to be defined in the _targets.ini file in the terrain folder? Specifically, I noticed that after adding a bunch of ground object targets to an existing target area in WOE (to GermanyCE_targets.ini) that my missions failed to load - they get to 100% and then I get CDT. After working through the problem I noted that by removing a certain number of the new targets I was able to re-load the mission and carry on as normal. Adding the targets back in caused a CTD again. So, this got me thinking. Is there an upper limit to the size of the _targets.ini file (my WOE version is 1mb in size)? or perhaps more likely, Is there an upper limit to the number of objects that can be defined within the _targets.ini file? I looked in FlightEngine.ini in the Flight folder and increased the values in the [GraphicsSettings] section, which seemed a possible candidate to my troubles, but this does not appear to have worked. I still get CTD. Anyone else seen this behaviour? Kind regards, comrpnt.

Hi folks, thanks for the replies so far. I've got a fix for this now - documented here: http://bbs.thirdwire.com/phpBB/viewtopic.php?p=31411#31411 Thanks to TK again for confirming my suspicions. Might want to be aware of this one, in case you're adding loads of ground objects to the _targets. ini file. It was a real pain to debug. Cheers, regards, comrpnt.

You may want to try adding the following to the C-130 _data.ini file...it worked for the A-3B I used in VMFA-531 Mission Pack 1 :-) // In the Fuselage section add a new SystemName reference...where XXX is the next number is sequence... [Fuselage]... SystemName[XXX]=Tailhook // And also add the following Tailhook section, usually near the end of the _DATA.INI file. [Tailhook] SystemType=ARRESTER_HOOK MaxDeflection=60.0 Retractable=TRUE DeployTime=2.0 ModelNodeName=tailhook HookArmLength=2.16 AttachmentPosition=0.0,-5.59,-0.79 Regards, comrpnt.

Yes, I agree. Please feel free to use my mods without the need to request explicit permission from myself, with the following provisos: (i) include my original ReadMe (for relevant credits and acknowledgements), (ii) excludes any of my work published as part of a team effort (you will need the team's permission), (iii) do not include my work in any payware, (iv) please credit me in your ReadMe (to allow users to contact me if necessary). Otherwise, I'm fine with this. Thanks. :-) Regards, comrpnt.