CV32

It is possible to create a victory condition that uses enemy 'time on station' (i.e. time spent in the vicinity of an objective) and of course, also possible to create a victory condition that involves the destruction of a player controlled installation. Yep, this is possible. We created the ability to use 'suicide' weapons that destroy their launching platform in order to model kamikaze aircraft for WWII era scenarios. No reason why I could not do the same in the HCDB. Other non-warship options for you, already present in the database, are pirate dhow, pirate launch and the merchant that carries a 'suitcase nuke'. Yes, you can do this. You can add all sorts of 'traffic' (including neutrals and opposing forces that aren't overtly hostile, e.g. a Red Cessna) to complicate the plot. And throw your hostile in there to carry out its mission.

Well, don't get confused. The refueling process took about a minute. The 8.5 minutes was the interval between the receipt of the 'No Refuel' info and the prompt to split off the tanker.

There isn't a third message. Game time.

No. Because its not in the code/model. IIRC, its a wish list item. Again, because its not part of the code/model. Definitely a wish list item (at least for active sonobuoys).

The actual refueling process, or more particularly, the time interval between receiving a message that refueling has started and the appearance of the 'No Refuel' info, seems to run about 30 to 60 seconds. (Grossly simplified for the purposes of the game, obviously, as RL refueling would take considerably longer). It has been my experience that you can rely on the appearance of the 'No Refuel' info as being an indicator that refueling is completed. The actual prompt to split off the tanker may take considerably longer. In the quick test I just ran, with a group of 4x Hornets and 1x KA-6D, it took 8.5 minutes.

CV32: You've heard of the ice trucks, perhaps, but how about the ice bombers? From Flight Global [excerpt]

Some folks are more skittish than others. You're aware that the group info will show 'Mission: *** w/Refuel' when it still has fuel and then 'Mission: *** No Refuel' when it does not, right?

in progress Maybe we can flesh out the carrier battle groups if we build the skeleton first ... USS Constellation (CV-64) June to August 1964 May to December 1966 April to December 1967 May 1968 to January 1969 August 1969 (then to Defender Station in Sea of Japan) On Yankee Station from November 1969 to May 1970 October 1971 to July 1972 January to October 1973 USS Enterprise (CVN-65) Six six combat deployments to Southeast Asia from 1965-75 Return to Southeast Asia in Spring 1971 On Yankee Station from August–November 1971 On Yankee Station from October-December 1972 January 1973 - strikes on targets in Laos April 1975 - Operation Frequent Wind USS Hancock (CV-19) On Yankee Station, November 1964 to Spring 1965 December 1965 to August 1966 Early 1967 to July 1967 November 1970 to May 1971 March 1972 to ?? USS Oriskany (CV-34) May to December 1965 On Dixie Station 27 June 1966 On Yankee Station 8 July to October 1966 On Yankee Station July 1967 to January 1968 Return April 1969? USS Ranger (CV-61) Joined TF 77 in October 1964, till April 1965 January to August 1966 On Yankee Station, December 1967 to April 1968 Return to Yankee Station 11 April to 5 May 1968 October 1968 to May 1969 October 1969 to May 1970 October 1970 to March 1971 December 1972 to August 1973 USS Ticonderoga (CV-14) August 1964 On Dixie (later Yankee also) Station November 1964 to March/April 1965 November 1966 to April 1967 January to July 1968 March to April 1969 On Yankee Station May to August 1969

I tend to perform the split manually too, after refueling, usually because I'm looking to get the strike package (or whatever the recipient of the fuel was) back to its ordinary cruise speed and back on the job.

Can you provide more details of what exactly you hope to portray? There are civilian aircraft in the database, but nothing that would try and carry out an attack. How do you want them to attack? Gun fire? Missiles?

I am not surprised that '0 nm' actually means '0 nm', as far as the code is concerned. The question arises, then, whether it should be actually be zero, or some other number, say 1 nm. Or, if there should be any Vsmall aircraft. Personally, I find it useful to have Vsmall aircraft (like UAVs) in play. Keep in mind that there is no model for being able to 'hear' aircraft overhead or nearby. The MRH-90, btw, (and some others) has since been changed to Small, because as I said earlier in the thread, I intended to make some adjustments as to which aircraft were actually Vsmall.

Some pics of the Canadian contribution ...

Some pics from the Charles de Gaulle ... FS Forbin, as seen from the Charles de Gaulle And a pic of how nice Gadhafi was to line up his jets (looks like those Galebs) in a row at Misratah: And some bombing video starting to emerge ... Tornado GR.4's in action (Paveway IV?) ... F-15Es and GBU-12s ...

Was chatting about that very issue with Brains earlier. As I understand it, the 'gripstock' typically contains not just the launch mechanism, but the necessary electronics; sometimes an IFF; usually the coolant for the seeker; and sometimes the battery or a connector for the battery. With the truck mounted Strelets, all of this appears to be built into the launcher pedestal, as can be seen in these photos. Without all of this, the missile in a tube is really just a round of ammo.

They are, imho. It is, imho. Go to Settings / Staff Options / Surface SAM Fire Rate. Play with the options there. 'Light' should generally allocate one SAM per one attacking/incoming missile. 'Normal' should generally allocate two SAMs per one attacker. 'Heavy' should generally allocate three SAMs per one attacker. Also, under the same options, see 'Auto AAW Fire Range' Here, 'Optimum' refers to the full range of your SAM unless that value >60 nm, at which point it becomes 82% of range if the target is a missile or 88% of range if the target is an aircraft. The other choices are self-explanatory. You can't control point defense, but you can exercise some degree of control of whether to engage at all by playing with the Auto AAW Fire Range options above. Also, where SAMs are semi-active radar guided (and many are), you can keep them from firing by shutting down your radars. Whether it is wise to do that is, of course, your call. I would say very few (if any; we'd probably have to be very specific to be sure) of your observations are consistent with normally expected behavior by the vast majority of players around here. Are you going to try the logging?

Okay. A little too generalized to be terribly useful, but you should probably take a closer look at some of the Soviet era surface ships and their emphasis on air defense. Then you should probably try them in the current version. That's the only way to move forward on these issues. Using the logging features already suggested to you on several occasions would help answer many of these questions.

From AFRICOM [excerpt]

From Aviation Week's Ares blog [excerpt]

I think I have to agree.

I'm curious as to what happens when (or if) you play the Soviet side. Not entirely true, as you can manipulate the range at which incomers are engaged, how many missiles you dedicate to your defense, and in some respects, whether you engage at all. (Now we digress ... )

From DefenseNews [excerpt]

A new version of the Harpoon Commander's Edition (HCE) 'Cold War' Database (HCCW-110328) is now available. Get it in the Downloads section of the HarpGamer website. New additions include: Aircraft: B-377M Anak - Israel C-130E Karnaf - Israel C-130H Karnaf - Israel F-4E Kurnass (69) - Israel F-4E Kurnass (70) - Israel F-4E Kurnass (71) - Israel F-4E Kurnass (73) - Israel F-4E Kurnass (75) - Israel F-5A/B - Iran F-5A/B - Jordan F-5A/B - Taiwan F-5A Freedom Fighter - Greece F-5C Skoshi Tiger - USA F-5E/F Tiger II - Jordan F-5E/F Tiger II - Taiwan F-104A Starfighter - Jordan Il-28 Beagle - Syria KC-97F Anak - Israel KC-97G Anak - Israel Kfir - Israel Mabat - Israel Mi-4 Hound A - Syria Mi-8TS Hip C - Syria MiG-15bis Fagot B - Syria MiG-17F Fresco C - Syria MiG-17PF Fresco D - Syria MiG-19S Farmer C - Syria MiG-21F-13 Fishbed C - Syria MiG-21M Fishbed J - Syria MiG-21MF Fishbed J - Syria MiG-21PF Fishbed D - Syria MiG-21R Fishbed H - Syria Mirage IIICJ (63) - Israel Mirage IIICJ (69) - Israel Mirage IIICJ (70) - Israel Mirage IIICJR - Israel Mirage IIIRJ - Israel Mystere IVA (56) - Israel Mystere IVA (57) - Israel Nesher S (69) - Israel Nesher S (73) - Israel Noratlas - Israel Ouragan - Israel P-51D Mustang - Israel PBY-5 Catalina - Israel RF-4C Phantom II - Israel RF-4E Oref - Israel RF-4ES Shablool - Israel RF-5A - Turkey S-55 Yona - Israel SA.321K Super Frelon - Israel Saar - Israel SF-5A/B - Spain Snunit - Israel Su-7BMK Fitter A - Syria Super Mystere B.2 - Israel Vautour IIA - Israel Vautour IIB (59) - Israel Vautour IIB (63) - Israel Vautour IIB (70) - Israel Vautour IIN (58) - Israel Vautour IIN (63) - Israel Installations: Afrikanda - USSR Al Ladhiqiyah - Syria Al Qusayr - Syria Bilbeis - Egypt Bir el Thamadah - Egypt Damascus - Syria DEW Line Site - USA Dumayr - Syria Hatzerim - Israel Hatzor - Israel Helwan - Egypt Kibrit - Egypt Kilpyavr - USSR Koshka Yavr - USSR Lod (Ben Gurion) - Israel Luxor - Egypt Mafraq (KHAB) - Jordan Olenya - USSR PGM-17 Thor Site - UK PGM-19 Jupiter Site - USA Prince Hassan (PHAB) - Jordan Ramat David - Israel S2 SSBS Site - France Sde Dov - Israel SS-3 Shyster Site - USSR SS-4 (R-12) Site - USSR SS-4 (R-12U) Site - USSR Tel Nof - Israel Ships: Iowa (1950) BB - USA Iowa (1956) BB - USA Iowa (1968) BB - USA Mobile Land Units: SAM Blowpipe Team - UK SAM Bomarc A Site - USA SAM Bomarc B Site - USA SAM Crotale Bty - France SAM Hawk Bty - USA SAM I-Hawk Bty - USA SAM Imp Nike Herc Bty - USA SAM Nike Ajax Bty - USA SAM Nike Hercules Bty - USA SAM Rapier FSA Bty - UK SAM Redeye Team - USA SAM Thunderbird 1 Bty - UK SAM Thunderbird 2 Bty - UK Telem Bty - Israel TEL Jericho 1 Bty - Israel TEL Pershing Bty - USA TEL Redstone Bty - USA TEL Scud Bty - USSR TEL Scud B Bty - USSR Enjoy.

I am not sure what you mean by the 'clock', but the 'randomizer' is not separate from the GE. Its built into the code, so if there were some problem with it, it should be repeatable in different computers.

Six UAE F-16 Desert Falcons now operating out Decimomannu AB in Sardinia. And six UAE Mirage 2000-9s operating out of Souda Bay AB, in Crete. Interesting that their contribution has been (geographically) split like that.

If they don't work for you, but they work for others, what conclusion should be drawn? It seems apparent that the problem is not with the game, but rather, over there where you are. This is not aimed at you personally, so please don't take it that way, because honestly I would like to see your issues resolved in a permanent way, but is there any other way of describing it? The 'computer experts' around here tell me that this is highly implausible. I mean some bug or flaw in the code. In most cases, these can be fairly easily rooted out - given enough material to work with (like the issue with the neutrals reporting player positions) - and squashed. Corruption, however, would likely prevent you from playing at all or else cause repeated error messages and crashes. I doubt it too, because the 'die rolls' are shown to go both ways, given enough tosses. Me too, because I rather dislike the suggestion that your own experiences are commonly found or are a characteristic of HCE, because they most certainly are not.