MajorH TacOps Developer

Thanks for the link.

> But do you know how to make deployment boundaries? Time > delays on new formations and how do you set a formation for > player deployment? You can't do any of those things in TacOps4 when creating a scenario from scratch. They can be done in the TacOps5 military edition.

> I am trying to convince my boss to let our organization purchase > TacOps to run a CPX to familiarize civilians with military > operations and the MDMP. Who do you work for? The somewhat obsolete TacOpsCav v4.x is still available for free to active duty or reserve U.S. Army members. TacOpsMC v5 (not obsolete) is similarly available for free to active duty or reserve Marines. If you or the folks you work for qualify for either, send an email to majorh@satx.rr.com for more info.

> Is there a repository of OOBs in the correct Excel format so that > they can be directly imported into the game? I don't think so. However, several of the gents who like to run hobby CPXes have compiled such files to support their activities. I think that the TacOpsCav exercise honchos at the Command and General Staff College have also compiled some for their exercises. You should ask about them on the semi private TacOps mailing list. To subscribe to the TacOps mailing list go to the URL below and follow the screen instructions. http://nxport.com/mailman/listinfo/tacops Once subscribed you can also read list message archives via a button somewhere around the link above. The TacOps mailing list is a no flame zone. No politics, no insults, and members are expected to stay reasonably on topic - which means mainly posts related to the TacOps game and or related to tactical level warfare in general. It is OK to discuss the "how" of contemporary warfare on the list but is not generally OK to discuss the "why".

Drat! It looks like several ship related bugs got into the last update. Those ship types in TacOps4 should not be able to load anything. In fact the program should not even allow you to add them to a scenario. If you do add them, you will notice that they can not move/be given orders. For a while, TacOps4 and the military versions of TacOps5 shared the same data base but TacOps4 did not and will not have the code to actually use watercraft except for landing craft and inflatable boats.

Suppression from direct fire sometimes drifts over onto nearby units, but the distance is much less than 100 meters.

Yes.

You can also get file information by doing the following. Run TacOps. Load a scenario and map. Select the "About TacOps" menu item. The resultant window will show the game program version number, the name and version number of the currently loaded scenario, and the name and version number of the currently loaded map.

You are not doing anything wrong. Some maps are smaller than 1024 x 768 pixels and TacOps does not zoom such maps to fill a particular user's screen. I chose that approach so that the TacOps ground/map scale would appear consistant regardless of map size (in kilometers). However, I don't understand why you are unable to play scenarios that use the smaller maps. The map may be smaller than your screen space but the entire map should still be there to be played on. If after reading this note, you still think that something might be wrong with your game, please send a zipped screen capture of the problem to the following email address. majorh@satx.rr.com.

Reducing CPU usage is at the top of the Windows only wish list, however I have taken several quick looks at it over the last year and did not find an easy fix that did not kill the network play mode. I don't like to promise things that I may not be able to deliver in a timely fashion so if 100% CPU usage is a concern to you, then I recommend that you not buy TacOps4 until such time as that feature changes.

>I run windows at 1280x1024, my monitor's native resolution. This is good >because I can see a large portion of the map and the detail is sharp and >clear. But the type at the bottom is small. Is there a way to increase >font size? Not at present but it is on the wish list. I have taken a couple of quick passes over the years at making font size user variable but I couldn't correct the many unwanted ripples into other areas of the user interrace in the amount of time that I was willing to devote to it. >Is there a way to slow unit movement in the combat phase? (already found >the adjustment to slow combat) No. Most people compain that the portrayal of movement is too slow and want an option to speed it up. It is likely that after you have played a bit more that you will come to share that perception. >Is there a way to view the combat phase more than once? Only by restarting the game and then loading the most recent auto save file. >An idea for the next patch: Have tool tips for units. So if you simply put >the mouse on the unit it will show the same info at the bottom as if you >clicked on it. Good on the game map and setup box. I gave that a try some years ago and it slowed down the user interface and thus game play significantly. Constantly checking the current mouse position against the position of every enemy and friendly unit eats up a lot of CPU cycles.

>1- add an option to increase game speed, don't show each individual action >just show the results. Some turns last up to 10 minutes to complete >although the time step is only 1 minute. You can greatly speed up the portrayal of combat by placing a check mark in the "Options/Use Click Sound" menu item. This simply substitutes a short, quiet click for the normal battle sounds. >2- add an option to take bigger steps (2 and 5 minutes) That option is available when playing in multiplayer teams network mode. In that mode the exercise umpire can choose to have a movement/combat phase last for one to five minutes. >3- add the possibility to deploy large formations. I would like to have a >Bde deployed with Bn/Cie rather than a Bn with Pl/Sec. On the wish list. >Do more maps exist? Try the following sites. http://www.tacopshq.com/Maproom/index.html http://www.strategyzoneonline.com/forums/downloads.php?do=cat&id=18 >Would it be possible to use the weapons library so I can include it in >another program? I don't understand the question.

The unit type and weapon databases are not user editable. If they are hacked, then PBEM and network games will go out of sync fairly quickly so as to produce different turn outcomes on the different computers.

Ladder play never really took off for TacOps. Don't know why. Could be partly my fault as I have never personally pushed/encouraged it - mainly because I have no personal experience in ladder or tournament game play.

Once you have advanced past the initial setup turn you will need to select (i.e. place a check mark in) the "Options/Enable Umpire Tools" menu item in order to access such features. Some scenarios do not have optional unit groups, in which case the "Options/Add Optional Units" will not show anything even when umpire tools are enabled. However, the "Options/Add One Unit" menu item should still be available.

The following info is for TacOps Newbies. The TacOps game movie/replay feature is not adequately explained in the user guide so a detailed review follows. The game replay feature automatically links and displays a series of saved game files. The feature is controlled with an on-screen control panel containing play, pause, and skip buttons similar to a CD player. This feature is intended mainly for viewing a completed game. It is not intended for replaying turns merely to refresh the player's memory of recent game events. The latter usage is possible but it is intentionally inconvenient. If any force color is protected by a password, the replay feature will not work unless the viewer knows the password for that force color. In order for the automatic linking to work correctly, the saved game files must follow the following naming rules. The user does not normally have to worry about this because the program automatically and silently names and saves the files with the correct names without prompting the user. (1) Each filename must begin with a twelve character sequence that consists of "AutoSave" followed by four numeric characters (0 through 9) with padding zeros if needed to produce a four digit number. Examples: "AutoSave0000", "AutoSave0001", "AutoSave0100", "AutoSave9999", etc. (2) Each filename must end with an extension of ".tac". (3) It does not matter what if any characters appear in the filename between the first twelve characters and the ".tac" extension. (4) There can not be a numerical gap between consecutive files that is larger than five. If a gap greater than five is encountered then the replay will stop at the gap. Examples: OK -> AutoSave0002.tac, AutoSave0007.tac, AutoSave0010.tac, etc. NOT OK -> AutoSave0002.tac, AutoSave0008.tac Note that it is possible for a folder to contain several auto save files that begin with the same twelve characters. The replay feature will display the first file that it finds that begins with the twelve characters that the program is looking for. Example: A folder contains the following files. AutoSave0005 021115_1835.tac AutoSave0005 021115_1840.tac AutoSave0005 021115_1843.tac The program will display the file named AutoSave0005 021115_1835.tac and skip the other two.

The TacOps v406_AH update patch is available from the following support page. http://www.battlefront.com/downloads.html The Windows patch is titled "TacOps_406AHu.zip". The Macintosh patch is titled "TacOps_406AHu.sit". If you do not see those file names then hit the "Refresh" button on your web browser. A. Download and then Unzip or Unstuff the patch file for your OS. B. Then read and carefully follow the instructions contained in the file "Instructions & Copyright.txt". This is not an auto installer. You must manually copy/move each file from the patch folder to a precise location in your TacOps4 folder - so as to replace any files or folders of the same name. This patch is only for the retail editions of TacOps v403 through v406AF. Do not apply this patch package to TacOps v3.x or to any military version of TacOps - permanent damage will result. This patch is comprehensive for TacOps v403 through v406AG so there is no need to retain or install any previous patch. Below are the changes that have been made to the TacOps4 program since v406AG. - - - - v406AH Bug fix. The Unit Information window displayed incorrect values for the amount of ammunition remaining in a unit. - - - -

The v406AH patch is on the Battlefront download page. It is comprehensive for all previous versions of TacOps4. http://www.battlefront.com/downloads.html

>Now to learn TacOps ... Do the TacOps "Basic Training" tutorial first, even before looking at the user guide. See the file named “Tutorial.pdf” . The tutorial offers the fastest path to enjoyable play.

The 25 meg 406AH patch at the Battlefront download page is comprehensive for all previous versions of TacOps4. However, if you already installed the G patch you can get just a G to H (2 meg) patch at the following URL. http://www.tacops.us/support/ The smaller Windows patch is titled "TacOps_406AHuShort.zip". The smaller Macintosh patch is titled "TacOps_406AHuShort.sit".

TacOps v406_AH update patches have been uploaded to the following support site. This is not a comprehensive update package. You must have already installed the v406_AG update. http://www.tacops.us/support/ The Windows patch is titled "TacOps_406AHuShort.zip". The Macintosh patch is titled "TacOps_406AHuShort.sit". If you do not see those file names then hit the "Refresh" button on your web browser. A. Download and then Unzip or Unstuff the patch file for your OS. B. Then read and carefully follow the instructions contained in the file "Instructions & Copyright.txt". This is not an auto installer. You must manually copy/move each file from the patch folder to a precise location in your TacOps4 folder - so as to replace any files or folders of the same name. This patch is only for the retail editions of TacOps v403 through v406AG. Do not apply this patch package to TacOps v3.x or to any military version of TacOps - permanent damage will result. This patch is comprehensive for TacOps v403 through v406AE so there is no need to retain or install any previous patch. Below are the changes that have been made to the TacOps4 program since v406AG (the last official release). v406AH Bug fix. The Unit Information window displayed incorrect values for the amount of ammunition remaining in a unit.

> How bout a v5 teaser list? Mac OSX. All else is frosting.

Sorry but no partial update this time. I expect to be able to return to providing a partial option the next time around.

TacOpsCav won't be upgraded again unless the Army provides some support funds - which the official Army sim community is not likely to do. I provided free updates for TacOpsCav for a couple of years as a good will gesture but after a while one gets tired of tilting at bureaucratic windmills. TacOps 4 has some upamored M113s in the Australian section of the data base. Send me a private email and I will add the M1114s and XM1117s to the list for TacOps 5. I am trying to make myself stop providing free updaes for v4.

Note 1: Sorry, but a smaller/minimal patch will not be available for this update. I want to be sure that all do the complete comprehensive update this time around. Note 2: Please take the time to actually read the change log (below) this time. Some good stuff made it into this update. - - - - - TacOps v406_AG update patches have been uploaded to the following support site. http://www.battlefront.com/downloads.html The Windows patch is titled "TacOps_406AGu.zip". The Macintosh patch is titled "TacOps_406AGu.sit". If you do not see those file names then hit the "Refresh" button on your web browser. A. Download and then Unzip or Unstuff the patch file for your OS. B. Then read and carefully follow the instructions contained in the file "Instructions & Copyright.txt". This is not an auto installer. You must manually copy/move each file from the patch folder to a precise location in your TacOps4 folder - so as to replace any files or folders of the same name. This patch is only for the retail editions of TacOps v403 through v406AF. Do not apply this patch package to TacOps v3.x or to any military version of TacOps - permanent damage will result. This patch is comprehensive for TacOps v403 through v406AF so there is no need to retain or install any previous patch. Below are the changes that have been made to the TacOps4 program since v406AE. - - - - v406AG User Request. The double click shortcut has been restored to the unit type selection list on the left side of the Add One Unit Window. Retained the "Add Unit" button for those who do not read instructions. User request. Added the following WW2 unit types: US Inf RL M1/M9 Team (Bazooka), UK Inf RL PIAT Team, and GM Inf Panzerschreck Tm. User request. Added the following generic WW2 unit types: AAA Portable Light, AAA SP Track Light, AAA SP Track Medium, AAA SP Track Heavy, AAA SP Wheel Light, AAA SP Wheel Medium, AAA SP Wheel Heavy, AAA Static Light, AAA Static Medium, AAA Static Heavy, AAA Towed Light, AAA Towed Medium, AAA Towed Heavy. User Request. Reworked the Unit Data Base Report Window, the Weapon Data Base Report Window, and the Add One Unit Window to more smoothly refresh their contents when a user scrolls through multiple unit/weapon types. Developer Initiative. A weapon's minimum range limitation, if any, is now included in the "Useful Range" column of the weapon list in the Unit Data Base Report Window and in the Add One Unit Window. Previously, only a weapon's maximum useful range was shown in these windows. User Request. When using the Unit Data Base Report Window or the Add One Unit Window, if there is no factory provided photo for a particular unit type the program now displays the text data base id number for that unit type. However, if a user adds a personally provided photo to the zPhotos folder whose filename starts with that id number and ends with ".bmp" then the program will now display that personal photo. User request. The unit data base record id number for a unit type is now included in the information list block in the Unit Data Base report window, the Unit Information window, and in the Add One Unit window next to the caption "DB ID:". This information has no practical game play use but is of interest to a few expert or professional users. User request. The attrition points value (AKA unit lethality value) for a unit type is now included in the information list block in the Unit Data Base Report window and in the Add One Unit window next to the caption "Attrition Points:". This information has no practical game play use but has been of interest to PBEM and CPX scenario builders who sometimes use this value as a "cost value" for balancing scenario OOBs. Developer Initiative. Added three arty fire mission plot symbols for WWII indirect fire units - light, medium, and heavy. Added three mortar fire mission plot symbols - light, medium, and heavy. User request. Increased the "cost" value of the US Inf LRASS Team P3 and US RECV HMMWV LRASS from 12 to 50 . User request. Deleted the .50 cal machine gun from the US RECV HMMWV LRASS vehicle and reduced its troop cargo capacity from 8 to 4. User request. Deleted the .50 cal (12.7mm) machine gun from the AU/NZ APC ASLAV-A Ambulance. Crash Bug fix. The program would occasionally hang, exit, or crash if the mouse was clicked in an empty, user selection choices list box in the following windows: Unit Database Report, Weapons Database Report, and Add One Unit Window. Bug Fix. AAA capable ground units without thermal or radar sights would sometimes fail to engage fixed wing airstrikes despite having achieved target acquisition. The bug did not effect ground units equipped with thermal or radar sights. Bug fix. The program failed to display a photo (#1212) for the Canadian Forces Taurus Armoured Recovery Vehicle. Bug fix. Changed the window title of the photo data base window from "Photo" to "Photo Database". Bug fix. When the user pressed the instant unload button in the Unit Orders Window, the program failed to instantly update the pending orders count box in the Unit Orders Window. Bug fix. When the user pressed the instant tow release button in the Unit Orders Window, the program failed to instantly update the pending orders count box in the Unit Orders Window. Bug fix. Changed name of weapon data base item #1227 to UK Gun 40mm Tk (2 Pdr). Changed name of weapon data base item #1262 to UK Gun 40mm AT (2 Pdr). Changed name of weapon data base item #1228 to UK Gun 57mm Tk (6 Pdr). Changed name of weapon data base item #1261 to UK Gun 57mm AT (6 Pdr). Bug fix. Weapon UK GL 40mm AG36 was displayed out of order in the Weapons Database Report window. Bug fix. When in NATO/wire box unit icon display mode, the program failed to draw a HQ icon on the US LAV C&C unit marker, and failed to draw a logistics/transport icon on the US LAV Logistics unit marker. Bug fix. The program failed to limit the display size of unit photos to not wider than 400 pixels and not taller than 350 pixels in the Unit Data Base Report Window and the Add One Unit Window. Bug fix. Mac Only. The program failed to draw a white background frame behind the black text accuracy number that is shown on the map to the right of an artillery target reference point marker. Bug fix. Mac Only. The program wrongly drew a white background frame behind certain text items on an artillery target marker, when unit marker text names were displayed on the map. Bug fix. The fire support target markers for some WWII on map artillery units displayed the wrong caliber for the owning unit. Such markers now display an L, M, or H (for light, medium, or heavy) instead of a numeric size. Bug fix. The US M1IP tank was wrongly defined as carrying 40 105mm rounds instead of 55 rounds. Bug fix. The program failed to correctly update the screen after a window drag operation when the "Setup On-Map Units" window and the "Change Units and Weapons" window were open at the same time. - - - - v406AF User request. Added the following unit types: JP Gun AT 47mm Type 1 JP Gun 37mm Model 94 JP Howitzer SP 150mm (Type 4 Ho Ro) JP Inf Team GL 50mm P3 (Grenade Launcher/Discharger/"Knee Mortar") JP Inf Squad w GL. JP Tank Amphibious T2 KaMi JP Tank Amphibious T3 KaChi. Bug fix. JP Howitzer 70mm Type92 was displayed out of order in the Unit Data Base Report and in other windows. Bug fix. Mac only. Found and corrected a minor memory leak. The program failed to dispose of bogus scroll bar pointers when closing certain support windows, alert windows, and dialog windows. Bug fix. The program was drawing UTM Northing lines one pixel too high. [ April 28, 2006, 05:58 PM: Message edited by: MajorH TacOps Developer ]