Battlecruiser Millennium Full Freeware v1.09.03

ALL PATCHES ABSOLUTELY REQUIRE DIRECTX 8.1B OR HIGHER!! NEW VERSION INFO v1.09.03 - ??.??.?? No details available. v1.09.02 - 11.07.03 * FIXED: Cloned personnel were re-created without their default inventory v1.09.01 - 08.12.03 * The Quick Save option has been removed from the TLM/SYSTEMS menu. Also the ALT+CTRL+S command has been removed and ALT+S now does the Full Save. * Intruders and now prisoners are removed from the CC (and any support crafts) when docked at a station. Previously, intruders were captured and either converted into prisoners and placed in the detention hold, or removed. * When observing a planet with TACOPS, the view now zooms all the way to the player if the player is located on the planet. Previously the default zoom view is from the top level GBM. * Player can no longer drop the tractor beam during a hyperspace transition by lowering the shields * FIXED: The OC wasn't recharging when docked with the CC * FIXED: Prisoners can no longer be given orders from Tactical/Loadout/Team * FIXED: A very serious problem with loading saved games. In some instances the EOF marker was not being preserved and this would cause the game to either enter an infinite loop or crash. v1.09.00 - 06.02.03 * Added IA galaxy map galaxy_map_links_ia1.jpg to docsappendiximagesmaps. * If you go to MISCON and attempt to LOG OFF while running an IA or TA scenario, you will now return to the game instead of only being allowed to exit entirely. Previously, you could only return to the craft by first going to another sub system e.g. Logistix. * Navitron will no longer display the main galaxy map in IA/TA scenarios, since they take place in a different galaxy * Restricted the station's ability to have extremely high quantities of items * Revised orders menu so that access to all assets is now possible regardless of where the AE is located. Previously the Tacops shuttles menu could not be used to launch a shuttle if the AE is not aboard the CC. This was reported as a bug. Its not. Thats how it was originally designed to work. Also, a problem was reported in which if the AE was assigned to an OC in a launched shuttle, on quit/restore, the Tacops waypoint orders menu only listed orders for the OC regardless of the craft selected. This is not a bug. Basically the waypoint menu is showing options valid for the SC (for example it shows TOW which is not a valid OC option), however the AE is located in the OC and the startup code is using the asset (OC) that the AE is currently located in to create the menu and not his primary asset (CC). As the OC has no OC/FC/SC/DRN assets of its own, no orders that relate to these craft will be added to the orders menu. This occurs when the game is restored and the player is not located in his primary asset. The menu revision above should alleviate this confusion but it may cause other quirks elsewhere e.g. trying to order a unit that is invalid or in a completely different region. * Introduced special handling so that TER/MIL and TER/INS station captures work more reliably. Someone reported that EPs and medals were not awarded for capturing stations. This is false. As the manual indicates, EPs and medals are only awarded for the capture of hostile stations. In the case of TER/MIL and TER/INS, because the Insurgents are a special case caste, sometimes EPs would not be awarded in some cases. Also, as the EP.HTML file in the appendix indicates, medals for station captures are only awarded if you are playing as TER/MIL, TER/INS and TER/EAR. * The commander career now has access to the illegal items list in Tradcom * Updated appendix files airdefense2.html, cruisers.html, transports.html * FIXED: If you attempt to tow a unit when there is no power to launch control and cannot, when you turn power on to launch control and try again, the tow operation will fail. What was happening is that after the message "LAUNCH CONTROL NEEDS POWER" message is displayed a further message: "RECOVERY FAILED" is queued. This message had a zero display time, which is used when asking a question. But no question was issued with this message. The consequences of this situation are: 1) the message is never seen 2) the message remains locked in the message channel (waiting for a response) 3) the icon representing the person asking the message will remain on the display 4) further messages from the person are queued but never seen The deadlock is cleared when the message queue is flushed. * FIXED: If you accessed Logistix from Tacops, selected the SC icon and then select the CARGO icon (for the CC) without first selecting a craft, a crash may sometimes occur. * FIXED: The LBASES.INI file had some incorrect entries which affected the starting base locations for some careers. installed, thereby replacing the existing versions. * FIXED: In certain conditions an item can get into the "repair suspended" state but will be prevented from switching to "ready" status once it was 100% repaired. v1.08.00 - 04.01.03 * This version is compatible with saved games from the previous version. If upgrading from 1.08.27 or higher and you wish to keep your saved games, be sure to backup the SAVE game folder before patching. Then restore the contents after patching. * Minor maintenance * Scenarios are now sorted by filename instead of scenario type v1.08 RC36 - 03.04.03 * This version is compatible with saved games from the previous version. If upgrading from 1.08.27 or higher and you wish to keep your saved games, be sure to backup the SAVE game folder before patching. Then restore the contents after patching. * The obsolete multiplayer option has been removed from the main menu * Implemented new /cheat command line parameter which enables the following cheats. USE AT YOUR OWN RISK! + ALT+X : Destroy any target at will. To use, target the object in the TACSCAN, press V to view it in the CVD and press ALT+X to destroy it. Can also be done from F10 external camera view. If you use this command without a valid target, you will destroy yourself! + SHIFT+T : elapse 1 min of game time. Keep pressed for rapid time advancement. It is possible to activate the tractor beam (T) by accident when using this command. + CTRL+SHIFT+T: same as above but elapses 10 mins of game time. + Speed Boost : If you have a speed factor set e.g. 1-9, you can gain a very large speed boost by keeping the finger either on the afterburner (~) or retro-rockets (TAB) key. + Planetary Egress : O will allow you to leave the planet at any altitude. + Immediate asset switch : ESC while in fp mode will put you back in your primary asset regardless of where you are. + HSD artifact : The artifact allows you to jump from region to region without ever having to fly there. To use, look on the left side of the HUD for the LOC text and left-click on it. This will activate a menu showing the systems and regions. Select a desired destination and the ship will immediately be warped there. + Fleet C&C : This gives you command of any NPC asset in the game world, including stations. To use, simply go to TACOPS and either use the zoom-to menu or select an NPC on the map and you will see an orders menu for that NPC as if they were your assets. e.g. you could order a station to launch some carriers to escort or defend you. Then give those carriers their own orders later on. + Asset menu: The asset menu on the right side of the screen allows you to create any asset in front of you. Simply left-click on the text to activate the menu and go from there. * FIXED: Another hole which would sometimes allow negative inventory counts v1.08 RC35 - 02.15.03 * Maintenance only release v1.08 RC34 - 02.01.03 * Maintenance only release v1.08 RC33 - 01.27.03 * Adopted new revision number scheme for clarity. Also renamed bcmver.html to bcmvcf.html * Added a new file, bcm_manual_rev.html which lists all material game revisions and additions since the release of BCM. This saves having to troll this version control file looking for revisions and such. This file uses a different style sheet making printing easier. * Minor revision in station inventory update which removes support for negative inventory amounts * FIXED: a mzone naming problem which affected BCIA0024 and BCTA0003 scenarios. This caused you to start in the wrong place and usually in water. * FIXED: a problem with the alignment of explosions which came about as a result of the new camera system * FIXED: a serious problem related to an NPC targeting the location of another ship that is about to do a hyperjump but then ends up selecting an invalid region location to the target ship not having finished the transition. The result is that the ship ends up outside the region limits, is then destroyed, but that destruction itself occurs outside region limits and generates exceptions which essentially brings a single CPU system to grinding halt - until the condition clears. i.e. the exploding entities have been removed. What was happening is that ship A and B are autogenerated at the same time. Ship A decides to hyperjump to GHQ (for sake of argument, could be any target); it begins to orient itself to point in the direction of GHQ. Ship B decides to hyperjump to ship A, (maybe it wants to attack it). Ship B is smart and knows that Ship A is initiating a jump, so instead of jumping to towards the position of ship A, it finds out where the exit anomaly of ship A is and jumps there instead. The only problem is that until ship A has completed its turn maneuver and entered hyperspace the exit anomaly does not exist. Therefore ship B sets its egress position to an uninitialized location and tries to hyperjump to it; thereby causing the problem described above. Note that this only happens if ship B is ready to enter hyperspace before ship A is. This is more likely to occur if ship A is a transport and B is a fighter and therefore A turns more slowly than B. v1.0.08 RC32 - 01.06.03 * Implemented Tradcom support for OC so that you can now trade/repair while docked at a starbase with a vehicle (that has cargo space) * Minor revision in station inventory update which removes support for negative inventory amounts * Revised the playback of hostile gun sounds so that regardless of how many guns the unit has, only one sound is ever played when it fires. Previously a sound was played for each gun and this led to the system sometimes running out of sound channels in high threat areas (e.g. on planetary mzones) * If there's no free sound channel to play a sound, then it's just skipped instead of generating a FATAL error message and exiting the game. An error is still sent to the debug log file if debug is enabled. * FIXED: AE wasn't assigned to return to bridge if he was in OC in a SC which docks. This fixes a problem where if your AE is in an OC and docks with an SC and then docks the SC with the CC and you go to a FE module menus they still think your AE is in the SC even if your AE is on the bridge in the CC. * FIXED: minor issues in PTE2 terrain engine related to the terrain mesh allocation and vertext buffer locking (which would probably cause a crash in some rare instances) * FIXED: Tactical/Launch was always showing the reactor charge status of the FC, regardless of the currently selected craft/vehicle * FIXED: The Playmod GBS utility sometimes reported numeric values (AI, LF, FF etc) incorrectly v1.0.08 RC31 - 12.23.02 * TACOPS revisions: + Revised the global map mzone color coding further. In the previous version, if the mzone name contained SBASE, MBASE or NBASE, it would be color coded. This has now been revised to use the actual scene name itself for better handling. This means that the global map will now flag all mzones on that planet, not just the important ones with the aforementioned naming convention. The mzone color coding is now starbases (Red), military base (Cyan), naval bases (Cyan). If an mzone contains both a starbase and military base, the starbase color coding takes precedence. v1.0.08 RC30 - 12.16.02 * TACOPS revisions: + The SPACEBAR now toggles the region name labels when observing the planet/moon global map + The mission zone tab has been relocated to the top of the ZOOM-TO menu for easier access + If a scene or mzone contains the string SBASE or MBASE the final colors of the associated rectangles are now CYAN and RED respectively. This allows you to better identify starbases and military bases from the global map + Target menus relating to the surface no longer contain the space related items (planet/moon/navigation/hazard). + Mission Zone scene names are now upper case in menus. Also when the mouse passes over a scene or mission zone rectangle the name shown in the ZOOM-TO menu is upper case. + The sort order of items in mission zone and scene lists has been modified for items containing numbers. Any two items that share the same numeric prefix and contain digits are sorted according to the value indicated by the digits for example "earth3" is ordered before "earth20" (since 3 is numerically less than 20). Only the first set of digits encountered are considered significant. + The mission zone pullright in the ZOOM-TO menu now activates a region menu instead of a list of all the mission zones on the planet. The region menu lists all the different types of regions found on the planet (by race and caste) and each pullright then lists only mission zones matching that type. + At map and scene levels, the location displayed on the lower right of TACOPS indicates the region/mzone/scene at the current position. It previously only used to display the planet/moon name. * FIXED: When zooming back from SCENE level (in particular when using the numeric pad 5 key) the map display will now go back to the correct map and centre on the location at scene level. If the location at scene level was in a mission zone, the map centres on the mission zone origin. * FIXED: An obscure problem which had the potential to cause unexplained crashes in some high stress conditions. v1.0.08 RC29 - 12.12.02 * FIXED: When the AE orders menu was disabled in RC27, it also disabled the ability to deploy/evac the AE. The only method of evacuating the AE was manually by having the desired craft land and you enter it in fp mode. v1.0.08 RC28 - 11.27.02 * FIXED: Platforms on planets (bunker, barrack, starbase, launch pad etc) were not deploying marines when hostile marines are detected within their vicinity, due to an incorrect parameter in the AI script. This was previously fixed in RC3 but I accidentally restored the original values in a recent scripts DB merge in RC25. * FIXED: Your own craft was not listed in the support units menu list when Tascan was in SUL mode * FIXED: The shuttle was sinking into the terrain after deploying a vehicle * The mining drone is now deployed from behind the shuttle instead of in front. Note that if you manually deploy both units without waiting for the first unit to drive away, they will collide when the second unit is deployed. v1.0.08 RC27 - 11.25.02 * Added support for commandline /j which ignores the rudder axis and allows CTRL+J swap to work as if the stick didn't have a rudder axis. Of course you won't be able to use the twist axis on the stick. Serves you right, all of those who kept incessantly complaining about being unable to use the axis swap on sticks that had a rudder/twist axis. So, now you can render your twist axis useless if you want to. * The AE orders menu have now been disabled because the player is required to have direct control of his AE instead of attempting to give him/her orders (and wondering why most didn't work). * The enumerated TA/IA scenarios list is no longer displayed. This was causing too much confusion. Now only the actual name of the scenario file is used. e.g. IA01 [BCIA0015] [COMMANDER] [STATION DEFENSE] is now displayed as [BCIA0015] [COMMANDER] [STATION DEFENSE] * During waypoint interception that requires a landing, a craft will now begin decent to ground level if ETA to waypoint is less than 15 seconds. This places the craft much closer to the ground at final VTOL decent phase. * During a takeoff, the VTOL phase is extended so that the craft hovers for a short period before accelerating. * After performing a waypoint action that deploys player assets, the shuttle performs a resume waypoints action. Unfortunately this cancels a prior RTB order if there are no more waypoints. This has been revised so that resume waypoints is not performed if the orders are RTB. * FIXED: The shuttle can no longer deploy assets while still airborne. As a result, mining drones can no longer mine during their descent after being deployed while the shuttle is still in the air. In fact, the shuttle should no longer even deploy any crew/asset without first landing on the terrain. * FIXED: When the shuttle deploys a vehicle using waypoint orders, the vehicle is now forced to the ground rather than letting it fall under gravity (if the shuttle is allowed to deploy without first landing properly on the terrain). * FIXED: Engaging the A/P after CALS has landed (SHIFT+E) the craft will no longer cause a pitch up/down of the craft, which usually caused the craft to intersect the terrain. CALS now exclusively uses VTOL earlier in the final approach phase of the landing sequence. * FIXED: A craft performing a takeoff was forced to the surface because the auto-level VTOL procedure shares a routine that used to force objects to align with the terrain. The latter was recently modified to reposition the object on the surface without taking into account the fact that an object may be attempting a takeoff. This is what was causing the craft to fly along the terrain during takeoff and taking damage as a result. v1.0.08 RC26 - 11.19.02 * FIXED: The DRIVE TO order for the OC now works reliably. Note that this command will not cause the vehicle to halt on its own when it gets to the target. Instead, it will navigate around the general vicinity in much the same way a craft does. * FIXED: Mining drones will no longer collect minerals unless they are firmly on the terrain * FIXED: Some attributes were being displayed for careers that didn't support them e.g. BA/DF/CM/CK attributes are for pilots only - and are no longer displayed in the HUD stats or COMMLINK stats displays for non-pilot careers. * FIXED: EPs will now be displayed in the COMMLINK stats display when an IA/TA scenario ends * FIXED: a flickering in the shield indicator when it was fully depleted * FIXED: Tacops mzone list sorting implemented in RC22 was off by one. This resulted in loading of a different mzone from the one selected from the list. * FIXED: the incorrect cmdr model was being used if you exited the CC on the planet, then exited in space. This happened as a result of a revision in RC20 related to preserving your inventory when you exit/enter crafts. In fact, if you exit as a space marine and then resumed or restored a saved game, a crash will occur due to the incorrect model in use. v1.0.08 RC25 - 11.13.02 * The crew stats color coding in Perscan should now match the crew stats color coding in Tactical/Crew in all cases. * Revised the max amount of an item that a station can carry. This used to be a big number. Now its a huge number. Also did some revisions to ensure that the max amount remains clamped to its allowable maximum. * Increased the probe's max speed from 15000 m/s to 75000 m/s * You will now be awarded EPs for kills by your marine support units (merged from BCG) v1.0.08 RC24 - 11.03.02 - Revised the detail texturing to use the same vertex primitives as the site texture in order to solve a problem on ATI Radeon 9000/9700 cards which caused texturing artifacts on the terrain when both of these used different primitives. This problem seemed to automagically disappear in the latest 613.6193 (WIN2K/WINXP) and 413.9068 (WIN9X) drivers - but better be safe than sorry. Knowing ATI's penchant for screwing up drivers on a regular basis, even if they go and break it again, at least this fix will be there to ensure that problem doesn't return. This fix seems to have no adverse effects on previous drivers which exhibit this problem (not found on any other graphics card). - Added particle fx to shots (for a tracer type effect) fired by vehicles. Not that you'd even see them - considering the size of the shot which measures 0.16m (H) x 0.16m (W) x 0.48m (L). - The HSD artifact no longer gives access to the IA/TA galaxy (Garidian) when playing a game in the normal galaxy (and vice versa) - FIXED: Invisible entities were visible in release build (bug introduced in RC20 code merge). - FIXED: In 1.0.08 RC23 stray contrail particles are left in external camera views in some instances, due to the new camera implementation in 1.0.08 RC20. - FIXED: On some planetary locations, destroying certain types of units which can rebuild, would cause them to be duplicated at the center of the planet and also being rebuilt at the correct location. This was refered to as the Sygan Triangle issue. - FIXED: The position of the contrail tag on jetpacks has been revised to work with the new camera. These revised models are available as a separate download for RC23. Simply copy the zip file to your BCM install folder and unzip it there (after installing RC23!!) with folders intact. v1.0.08 RC23 - 11.01.02 * If you now dock at a station with intruders on board your CC, they will now be nabbed by the station marines. Previously, only prisoners (scripted or intruders taken into custody by marines) in the detention hold were transfered. Intruders were left alone and sent to the detention hold (which is why there were no longer intruders when you launch from the station). However, now, for each intruder the station nabs and removes from your ship, you will lose -250 EPs and -5000 galcreds. If you don't have the necessary galcreds, then you will lose an additional -250 EPs per intruder for a total of -500 EPs per intruder. Rule of thumb: You have marines, use them. When in doubt, fire Resnig. * Completed specialfx particles revisions to conform to new camera model. Note that because the transporter is used from Tacops, unless you are zoomed close enough to the surface when deploying troops, you won't see the fx. Also, particle fx are not played in the Tacops video camera for the same reason they are not played in the CVD/VID camera either. * Enabled particle contrails in Tacops. Previously these were disabled but the new camera system now makes it possible. * Config now opens to the SYSTEM tab by default. Also fixed a minor display glitch. * FIXED: Minor display glitch in Tactical/Crew/Marines assignment tab when assigning marines to a location * FIXED: Artifacts were appearing immediately on game start. They should only start appearing after three days of game time v1.0.08 RC22 - 10.28.02 * The mzone lists in Tacops menus are now sorted * It is now possible to destroy units without certain systems (e.g. reactor) with single hit missiles. e.g. previously, a missile with a damage factor of 300, could not destroy a unit (e.g. SAM) with 250 armor due to how the damage energy was distributed. * FIXED: The new planetary object sorting (see RC20) was putting them in the wrong position initially, when a game was restored. v1.0.08 RC21 - 10.20.02 * The descriptions for scenarios which take place on planets now includes the planet/mzone/scene info. It previously only included the planet name. e.g. in BCIA0005, you will see TRION,TRION01,BASE_SBASE04 * FIXED: Restoring a saved game would sometimes cause a crash when attempting to write the current date/time into the log file. This crept up as a result of new date/time functions introduced in RC16, which is why RC15 save/restore works OK. * FIXED: The last line of the BCCONFIG.INI file was being truncated when restoring a saved game. v1.0.08 RC20 - 10.16.02 * Patches will now update the game revision number in the BCSETUP.INI file as well as in the registry. Will also obtain the install path from this file and add to the registry. This is required for hosting/joining games from battlecruiser.net lobby. * The planetary Time Of Day (TOD) lighting has been revised so that it gets a lot darker at night. Ambient light is dominant at night, while specular and diffuse lighting at night are disabled. The transition period at dawn/dusk is now three hours. * The sorting of planetary bodies has been revised for better accuracy e.g. Jupiter space region * Several camera revisions have been made, in order to alleviate some anomalies related to viewing matrices * To prevent discontinuity and delay in multi-player, the /, ALT+E, ALT+D commands will no longer prompt for a Y/N answer when entering/existing vehicles in fp mode. * Mother will now play the acquired and hostile launch detected warning messages regardless of the craft you are in. Previously, these were only played if you were in the CC * Added a new softer grenade soundfx, more suited for outside environment. Also added a 3D shockwave effect to the detonation sequence. * The DIE mode switch time has been reduced from 1.0 to 0.2 seconds. The order of the modes has also been changed for combat efficienty : 1: TVM, 2: EVM, 3: IVM * The TACSCAN targeting commands, B and N, will no longer select the closest hostile if there is no closest hostile attacker in the vicinity. * The TACSCAN ground radar beep sound has been disabled as some people found it annoying and intrusive. * The TACSCAN air radar mode now displays the target's altitude (feet AGL) in the lower-right corner. The display is graduated in decimal point format if altitude is higher than 1000 feet. * The NID/NIR mode now displays a lot more info when on the planet. This includes planet/region/mzone/scene info * The NID/MAP mode now displays the mzone (Yellow box) and scene (White box) symbology, similar to the PTEstudio display. * Several mzone scenes (.3DG files) have been modified in order to reduce the number of EAD units present. This reduces the difficulty of attacking ground mission zones as well as the AI processing requirement of those units. Also, all NPC vehicular units (CAV, CAB etc) have been removed from the scenes. Don't worry, they appear in the multiplayer game. * Made speed improvement revisions to various specialfx settings in BCSFX.INI. Also changed a few of them (e.g. LR12 rocket) visually. * The ATV unit now has a mix of APM-RADIX and APR-RALAR rockets and fires the new Armor Piercing Round (APR) shells. Don't expect to see any visual cue of shots fired. They're too small to see. To see what they look like, load up SHOT_APR_T1.3D in BCS. * The close air support units (PAS1, PAS2, LAG, HAG) now only have APM-RADIX and APM-RALAR rockets and no ATA capability. They also now only have the newer APR (Armor Piercing Round) shots instead of lasers. * The speed rating of the close air support units have been severely reduced so that they are not as fast as fighters, but rather like gunships e.g. the HAG unit went from a high speed of 1000 m/s to 300 m/s. In multi-player, these should be used for local area defense and short range attacks. Thats what they were designed for and not fighter combat. Considering that planetary bases are sometimes close to 4000 km apart, anyone wanting to take a HAG this distance at the rate of 1080 kph (300 m/s), is welcome to try. I hope you like spawning a lot. NOTE that The US military's Apache gunship's max speed is rated at around 82 m/s (160 knots). While an F16 can reach 681 m/s (Mach 2 at sea level). If you don't have a clue about these values, there is an excellent units converter called Versaverter which has served me well, over the years. NOTE that In BC games, we only use ft for measuring altitude because you can't go higher than 35-50K feet without bleeding energy and the altitude tape can display these limits in a graduated ASL scale. All other measurements are in the metric system. e.g. in the TACSCAN display, its easier to display 250km distance to target, as 250.0 than 820209.9738 which would overflow the display! Truncating it to significant numbers is also less attractive and would cause more problems in Tacops and elsewhere. * SAM units will now launch missiles at stationary or slow moving targets. Previously, in order to conserve missiles, they wouldn't launch if the target wasn't moving (e.g. in VTOL mode), leaving it up to the SALs to take out the target. This presents an unacceptable cheat loophole in multi-player. * The SAL units now have beam weapons instead of regular shots. This helps tremendously with processing; especially in mp * EAD units (e.g. ADT) with turrets will no longer attack ground units e.g. vehicles * Ground vehicles (ATV,APC,HAV,LAV,CAB,CAV) no longer fire laser shots. They use armor piercing bullet rounds instead * The ADT, ZX10 and ZX15 rocket units now have their own rocketa and no longer fire APM-Ralix or APR-Ralar missiles * The minimum radar range for several units, including EAD units, have been revised due to inconsistencies. e.g. some EAD units capable of launching missiles had different launch parameters which caused them to detect and acquire targets outside of their spec range because the range of the missile's radar seeker, exceeded that of the unit itself that the missile is being launched from. NOTE also that manual page 25 was inconsistent. Here is the corrected text from the BCM Gold manual revision. For example, a SAM unit with a min/max radar distance range of 1km/100km and a radar min/max altitude range of 1km/10km, cannot see a target that is more than 100km away and at an altitude below 1km or above 10km. So, if you are flying towards it at an altitude below 1km or above 10km, at a distance of 25km, it won't see you at all; even though you are within its 100km radar distance range. However, if you pop above 1km and within 10km altitude, you'll get pinged. At that point, if it maintains an active ping for a period of time (e.g. 10 seconds), it will launch a missile. Note that all air, space and ground units have different radar detection characteristics. When in doubt, check the appendix data files. You can use the Track Warning Indicator, TWI, to determine whether or not a selected ground threat can see you on radar or not. * The Surface To Orbit, STO, units now have their own class. Previously used to use the Enemy Air Defense (EAD) class which caused them to attack air units within the planet. * Structures can no longer be destroyed by small arms fire e.g. you can no longer take out a building with a pistol. Also the armor for some of them has been reduced, making them easier to destroy using fewer rockets and missiles. * The probe had two extra zeros in its max speed rating. These have been removed, making its max speed 15000 m/s * The range of all rockets (LR12, APM-RADIX, APR-RALAR etc) have been reduced. This is due to the fact that rockets are less effective than missiles and are designed for short range attacks only. * The acquisition time of the ODS missiles has been reduced from 15 secs to 5 secs; and the range increased from 125km to 250km, in order to make them more effective. * FIXED: A bug which caused targets with zero armor to not be destroyed if hit with a high impact missile * FIXED: Mode 2 of the pistol is no longer loaded with ammo at a supply station. Note that Mode 2 is only a faster firing mode and uses the same ammo pool as Mode 1. * FIXED: In the marine/pilot careers, if you enter a vehicle with a weapon equiped and then exit, you will no longer lose ammo clips. Also, when you switch between two weapons which use the same ammo, if you had a partial clip when you switch from one weapon to the other, you will no longer lose the entire clip. Normally, you should only lose the contents of a partial clip if you reloaded the weapon while it contained a partial clip. * FIXED: When you turn off shield power in Logistix, the bridge shield display will now bleed off correctly. Also, when you turn off the reactor or shield, the shield system will turn off immediately, instead of gradually bleeding off power. * FIXED: An invalid terrain height sometimes being passed for scene objects. This caused a major shift in scene positions. v1.0.08 RC19 - 09.19.02 * External planet texture maps for up to four (was two) planetary bodies are now loaded simultaneously. This will reduce texture thrashing in regions (e.g. Jupiter) where there are more than two planetary bodies within viewing proximity. * Some appendix files were updated. Also, an entry about The Thirteenth Race is now in the NPC section * FIXED: The ZX15 threat unit didn't have parameters for a mobile vehicle. So, it didn't move. This has been corrected. v1.0.08 RC18 - 09.06.02 * The Tactical/Medibay screen is now refreshed every 12 secs. Note that an AI tick occurs every 60 seconds Note that p43 of the manual does not mention that the manual treat option in Medibay is not instantaneous (like in previous BC titles). Each Medpak can treat someone up to 25 units. When you use the manual treat, the person is healed at the rate of 5 units per minute. So e.g. someone with a LF of 25 will take 15 mins to get up to 100 LF * The MD5 encryption check in ASSETS.INI has been disabled in order to allow modifications by GBS scripters v1.0.08 RC17 - 08.14.02 * The selectable resolutions in CONFIG are now hardcoded in order to prevent users from selecting unsupported modes and then wondering why the screen looks funny. * FIXED: On some planets/moons which are far from the center of the region, a GPF would occur when a craft entered the planet or when you attempted to zoom-to it from Tacops. * FIXED: In the RC12 update a revision to prevent close air crafts and shuttles from performing a pitch over maneuver was preventing shuttles from being able to leave the planet. This is now ignored if the shuttle is attempting to egress. v1.0.08 RC16 - 08.03.02 * GBS parser/interpreter updates: + FIXED: Attempting to RELOCATE an object that was RECOVERed (vanished) would cause a GPF. Now, it just won't do it. So, create your scripts properly and ensure that the logic flow is correct. + FIXED: The RELOCATE script command was activating an object (it shouldn't). NOTE: When you relocate an object that has not previously been activated, you have to explicitly ACTIVATE it or it will remain out of scope. v1.0.08 RC15 - 07.17.02 * Added IA00024, an EFM based Ter/Ins script * GBS parser/interpreter updates: + FIXED: Units using the !reach event to detect a navigate waypoint identifier were unable to trigger this event reliably. This invalidates all prior saved games. Scripted objects that are placed using on_planet have an implicit halt order (displayed as HOLD). If a scripted unit is ordered to NAVIGATE to a fixed position, the orders are now set to "NAVIGATE" which is equivalent to FLY TO. Since "FLY TO" is inappropriate for vehicles that can't fly, the displayed text has been changed from to "FLYTO" to "NAVIGATE". Note that when the unit is navigating, the orders will be either SAD, PURSUE or COLLIDE, depending on circumstances and the nature of the target object. * Supply stations and DJP objects can no longer be destroyed * Minor revisions to explosion templates v1.0.08 RC14 - 07.14.02 * The planet/moon object LOD rendering has been revised so that instead of a circle (at great distances) it is now another LOD textured mesh. Looks better. (Merged in from BCG) * All ground units (SAM, SALs etc) now have revised friendly fire avoidance in order to minimize damage to their own assets during heavy combat. * FIXED: turning on Flight Path Trails in CONFIG would cause a crash due to another fix addressing explosion playback v1.0.08 RC13 - 07.13.02 * Disabled the shot (the colorful ones) based fragments played when an object explodes. Looked too cartoonish I think * The /I invincible cheat (now works in non-debug mode and without the /d flags) will no longer work in an mp game * The supply station and DJPs are now misc class units so they can be toggled in the CVD/RTM without having to toggle off tactical (previous class setting) units v1.0.08 RC12 - 07.07.02 * The radar emitter bleep in air/ground vehicles has been replaced by a softer less intrusive sound (beep05.wav) * The sensitivity of the ground collision warning cue (see manual p53) has been increased * The aircraft '>' ceiling parameter is now based on AGL instead of MSL. This allows close air craft to be flown at high ground elevation. This may also help reduce aircraft "stalls" during pitchover * Close air craft and shuttles now avoid pitch-over maneuvers (which are usually performed when their objective is behind them). This reduces the risk of NPC pilots inadvertently stalling the craft and crashing into the ground when at low altitudes. * Aircraft are now committed to a BREAK state for at least 3/4 of a second, this prevents "twitching" where an aircraft enters BREAK and PURSUE states on alternate cycles. v1.0.08 RC11 - 06.28.02 * Adjusted the EFM's right hand on the ZS10 rifle. Was slightly off the trigger * On planet, the object lighting direction is now constant for a given time of day irrespective of the camera direction * On planet, the daily visual track of the sun is now more accurate in an East to West pattern. Note: no attempt is made to model latitude/planet axial tilt; so at noon (local time) the sun is directly overhead. The orbital period of the sun now also matches the planet/moon length of day. * NPC units are now more aware of the cmdr AE (some folks complained about not being attacked often, when they beamed down with their marines into hostile territory) * FIXED: Marines without jetpacks were able to fly * FIXED: character models were sometimes incorrectly aligned with some terrain topology * FIXED: found workaround for terrain detail texture flickering on ATI boards * FIXED: ejecting cargo from Logistix would sometimes cause a GPF (must've crept in somehow, because it worked fine before) v1.0.08 RC10 - 06.24.02 * Increased the SA for personnel so that they can detect where an extracting shuttle has landed * Revised the shuttle's landing profile in order to guarantee a successful evac/deploy op regardless of location * Revised the firing rate of some weapons e.g. the ZS10 firing modes are now faster * Added reload sound for ZS10 mode4 * FIXED: some fp weapon sounds were too low (due to the recent directional fire revision) to be audible v1.0.08 RC9 - 06.04.02 * Several speed optimizations and memory management revisions. Game should load, restore and run slightly faster now than before. However, if you're still running a system with 64MB of RAM, now would be a good time to increase it to 128MB for more of a significant boost in performance. v1.0.08 RC8 - 05.24.02 * The CC can no longer leave a planet if at least 5 units of power isn't allocated to the engines in Logistix. This prevents instances where you can breach the planet's escape velocity regardless of engine state. * Added bounce (B) object script AI param. This effects the elasticity of the bounce. Range is 0 (no bounce, default) to 1.0 (rubber ball). For cargo pods, this is set to 0.25 and 0.2 in order to prevent them from being destroyed when dropped from high altitudes. An value of 0 causes an object to be destroyed immediately on impact with the surface from a high altitude drop. * When breaching the surface while swimming vertically up, you now revert to a horizontal attitude so you no longer appear to be swimming vertically out of the water. * Jetpack revisions/tweaks: + It is no longer possible to climb above 2000 ft when using a jetpack on the planet + FF is increased when flying. The effort value has been changed to 35 (swimming is currently the highest at 70). The altitude has no effect on FF. + Oxygen use is dependent on altitude above ground and starts to be required at 500 feet and increases linearly to a maximum at 2000 feet. At maximum altitude the rate of oxygen consumption is 100 percent (as if you were under water). The consumption at 500 feet is very low. + The rebreather SFX are played when oxygen is used. When oxygen runs out player chokes and then dies. + Forward velocity has no lift effect (as it does for craft) + The minimum speed during first person ground collision that causes damage is 2 m/s (vertical) and 4 m/s (horizontal). Previously was 50 and 100 respectively. This now increases chances of injury and discourages rampant use of jetpacks on mp servers. + WARNING: If you drop from a high altitude while flying with a jetpack, you stand a very good chance of dying * FIXED: When you hit the water while flying with a jetpack, you will no longer be repositioned to the seabed * FIXED: GPF during save game restore after deploying a team using shuttle deploy team waypoint. v1.0.08 RC7 - 05.14.02 * You can now deploy/extract personnel (SF marines only) to/from space regions using waypoints or the shuttle HUD menu. If you deploy your AE from the shuttle, you will be switched to fp mode in space. No other personnel types can be deployed to space, even if they happen to be in the shuttle and explicitly marked for space deployment. * If you manage to tow the CC out of the water before the self-destruct timer runs out, after five minutes of being out of the water, the state (beached) will be cleared. This allows you to tractor it from the sea to land or to a station and be able to resume playing. * The FLY-TO order now cancels a pending RTB order (see next item which made this change necessary) * FIXED: If you ordered a shuttle to dock at a station, then ordered it to RTB and then to dock at the same station, it will no longer appear as docked in the CC instead of at the station. v1.0.08 RC6 - 05.06.02 * Items placed into cargo pods are no longer compressed and occupy 1 unit of storage. They will now occupy their actual storage space. e.g. you now only place two OTS missiles (250 units of storage space each) into a cargo pod, instead of 500 of them. * FIXED: Attempting to transfer items from the cargo pod to the ship's bays would cause them to be ejected if the target bay has insufficient space to hold the items. * FIXED: The tooltip for fighters was active even when the CC didn't have support crafts v1.0.08 RC5 - 05.02.02 * A cloaked ship will now briefly decloak during weapons and launch operations. This feature wasn't carried over from the previous BC title due to revisions in the cloak rendering. * If a towed ship ever touches the planet surface, the tractor lock is now disengaged. This prevents the towed craft from breaching the terrain. * Shuttles are now given an increased takeoff velocity to prevent them sliding across terrain. During takeoff for player assets, the auto-level timer has been increased from 2 to 3 seconds (which simulates a perfect VTOL ascent). * Craft deployment/extraction ops have been completely revised. (Merged in from BCG) + Shuttles can no longer extract units clean, clear across the planet, irrespective of distance from the extract waypoint + At a deployment/extraction waypoint, the shuttle first engages CALS. + For deployment, when the shuttle reaches the surface it waits 10 seconds for the units to disperse from the shuttle before taking off and proceeding to the next waypoint. + For extraction, when the shuttle reaches the surface it waits for up to 5 minutes for units (flagged for evac) to return to the shuttle position. During this period, units to be extracted (drones/vehicle/personnel) are forced to navigate to the shuttle location. If the shuttle is destroyed, the units revert to prior orders. During the delay period the shuttle sends a commlink message at intervals of 5,4,3,2 minutes and 60,50,40,30, 20, 10, 5,4,3,2,1 seconds indicating when it will leave and resume waypoints. + If under attack while waiting to deploy/extract, the shuttle will dustoff if damaged below 40% integrity + If the shuttle orders are to extract a drone or vehicle and that craft is disabled/beached etc, the shuttle will fly to the craft location and extract it using tractor beam. For the beached/sinking craft the sinking state will be reset after a period of time. * The Computer Assisted Landing System (CALS) has been revised. The descent attitude has been corrected and level out is now performed at 300 feet. Terrain alignment is now performed just prior to touchdown. At touchdown the craft no longer continues to move across terrain due to the implementation of a new friction model. At high altitudes some crafts needed a steeper decent rate so it doesn't take several minutes to land. This is done by fine control of pitch during descent depending on altitude. The craft will circle the landing point during descent in case the landing point is a deployment/extraction waypoint, otherwise the craft can land several km from the waypoint. The CC engine will now switch OFF after the craft lands when using CALS. NOTE: Don't forget that SHIFT+E turns off the engine while in space; but on a planet, it activates CALS which then lands the craft and turns off the engine (CC only). For gameplay and design reasons, the FC and SC engines are not turned off when CALS lands the craft. * GBS parser/interpreter updates: + The new general purpose NAVIGATE command is now complete and final. This works in the START/STOP or EVENTS blocks for any unit type. The CRUISE and INTERCEPT commands are obsolete. Any scripts using these, should be updated. Naturally, all previous saved games which use the older form, are invalid and cannot be used in this version. NAVIGATE 'object' 'planet' 'mzone' 'x' 'y' 'z altitude' ['waypoint identifier'] NAVIGATE 'object' 'target' The first form is for objects on planets only. The second form can be used in space or on planets When used in the START/STOP block, 'object' is implicit and the syntax is: NAVIGATE 'planet' 'mzone' 'x' 'y' 'z altitude' [waypoint identifier] NAVIGATE 'target' NAVIGATE cannot be used as a start specification, i.e. the following is illegal start inactive NAVIGATE farstar farstar01 23.0 3.0 150 WP1 The ON_PLANET script command should be used instead i.e. start inactive ON_PLANET farstar farstar01 23.0 3.0 150 0 As with ON_PLANET, the x and y values are in km relative to the mzone origin (see PTEstudio) and the z altitude is in AGL feet. The waypoint identifiers are not local to an object but global and it is illegal to re-define an existing waypoint with NAVIGATE. The global nature of the waypoint allows any object to check if any other object has reached its waypoint using !REACH. The waypoint identifiers are not case sensitive, and forward references are also allowed The !REACH event can now accept a waypoint identifier IF preceded by a caret (^) i.e. !reach ^WP1 Multiple NAVIGATE actions are allowed to follow one after another, provided they are the positional ('planet') form. This generates a route that the object can follow. The first NAVIGATE in an action block will clear a previously defined route. Subsequent NAVIGATE actions are added in sequence and IF blocks can be used to fine tune the route. e.g usage .f1,100,100,100,100,100,100,0 start inactive on_planet farstar farstar01 22.847 4.666 0 0 navigate farstar farstar01 23.000 10.000 0 waypoint1 stop events !setupl1 activate this FLAG1 ON this !reach ^waypoint1 FLAG1 OFF this broadcast "Reached waypoint objective" signal proceed_to_next,2 !proceed_to_next broadcast "Proceeding to hostile target" navigate this hostile_target !level1tick IF FLAG1 OFF this RETURN ELSE broadcast "Still travelling...." ENDIF !reach hostile_target broadcast "Reached hostile target. Engaging..." attack hostile_target endevents v1.0.08 RC4 - 04.16.02 * The RE will no longer attempt to analyze the RANDOM weapon if the RANDOM DECODER is not in inventory. Also, the decoder is no longer analyzed by itself. * Cargo pods deployed in the air will now fall to the ground under gravity and bounce. They will also be destroyed depending on altitude of drop. So, if you air drop supplies at high altitudes in multi-player, the pod can be destroyed. The safe altitude for air drops is about 1000 feet. * FIXED: Naval carriers will no longer attempt to RTB when damaged or low on supplies * FIXED: Some city start locations in the SNG were defined incorrectly * FIXED: At low resolutions, the assignment display width in PerScan is now truncated to avoid overflow into the next pane. * FIXED: The effects of tractor drag are now active when the A/P has flight control * FIXED: The Combat Officer would sometimes cause incorrect missiles to be auto-loaded when weapons pods are empty * FIXED: A bug which caused the repair time to be reduced by half, each time the repair button was pressed * FIXED: The RE would sometimes confuse the analysis of one artifact with another, regardless of AI * FIXED: The vehicle/drone extract waypoint menu did not have entries for units #5 and higher e.g. the Firestorm was affected by this v1.0.08 RC3 - 03.30.02 * When an object which can rebuild is destroyed, it is now set to a DISABLED state so that the TTD will appear grey while rebuilding. When the rebuild is complete, the state is now cleared to fully reactivate it. This prevents the race/caste alliance from being set to neutral, causing the TTD to be displayed as Blue and thereby causing confusion. * The CVD/VID camera now displays the object rebuild time (H:M:S) at debug level 2 or higher (/d2) * The NID/WIR now displays your position relative to the equator so that it matches TacOps. The location format has also been changed by removing leading zeros and shortening NORTH/SOUTH/EAST/WEST to N/S/E/W. * Radine usage is now scaled according to Logistix engine power setting. If the setting is 5, Radine usage is the same as before. If the power setting is 10, Radine usage is doubled. The afterburner max speed is scaled according to the engine power setting and at 10 is twice the normal value. * If the engine power level in Logistix is less than 5, then: + The engine is disabled, is turned off and cannot be turned back on + Speed setting is disabled + Afterburner and retros are disabled + The Hyperdrive cannot be used + The CC will drift at its previous speed * Appendix revisions: + Added the tech/class/security levels to the launch bases appendix file + Added turret shot ratings to units that use turrets e.g. stations, capital ships, Orbital Defense Systems etc + Added system upgrade paths for capital ships to the upgrades section * FIXED: If the AE is on a shuttle that is towing a ship with RTB orders and he flies to a station, the request to deliver the tractored ship will no longer loop. * FIXED: If the AE is on a shuttle and uses the T key to tow a ship (as opposed to using the menu or other method to tow it), and the tow succeeds, the tow action on capture will now be "HALT, Wait for instructions". * FIXED: Platforms on planets (bunker, barrack, starbase, launch pad etc) were not deploying marines when hostile marines are detected within their vicinity, due to a incorrect parameter in the AI script. This has been fixed and a temporary 1.0.07 script update has been released for those who want it now, rather than wait for the next patch which includes this fix. Just unzip this file into your BCM install folder with folders intact. v1.0.08 RC2 - 03.18.02 * FIXED: The inflation rates in some regions was updated in too large increments (e.g. at Aleri) * FIXED: The manual weapons reload key (R) only worked in debug mode v1.0.08 RC1 - 03.11.02 * The mission zones listed in the Tacops global map are no longer enumerated, in order to avoid confusion with the zoom-to/mission zones list. e.g. instead of Mission Zone 200 earth00[sbase] where 200 is the derived from the number of mzones detected on the entire planet, it will now show the actual mzone name i.e. MZONE: earth00[sbase] * Revised the texture blending method so that destroyed objects in a rebuild state (e.g. stations), are rendered correctly on all cards under DX8, as seen here. * An OC will no longer be auto-armed with missiles if it can't use them. e.g. APC/HAV/LAV/CAB/CAV. These all use the same object class as the ATV base class (which can launch missiles), hence the default missiles loadout. v1.0.07 - 03.06.02 - The Hunger Factor (HF) value is now displayed in PerScan and in Tactical/Crew. Note that the HF value can go higher than 100% (480) but is usually clamped in the HUD in order to keep that tape readout consistent with the others. So, if you see a value of, e.g. 141% in Tactical/Crew but 100% in the HUD, thats why. Also note that at lower resolutions, some crew assignment names in PerScan will flow from the left to the right pane. - FIXED: problem with confirmation box in save/restore screen v1.0.07 RC2 - 03.05.02 - FIXED: Sometimes dead prisoners were not transfered to the station when you docked v1.0.07 RC1 - 03.01.02 - You can no longer assign prisoners. This prevents you from doing silly things such as beaming them down to a planet or ordering them about the ship as personnel - FIXED: One of the Satini starbase models was at the wrong location within the planetary mzone scene - FIXED: The inUse flag which determines when you can fire, was disabled when a grenade launching cheat was closed in 1.006 RC3. This resulted in rapid fp weapon firing rates. v1.0.06 RC7 - 02.21.02 - Implemented new general purpose NAVIGATE commands which works in the START/STOP or EVENTS blocks for any unit type NAVIGATE 'object' 'planet' 'mzone' 'x' 'y' 'z' ['waypoint'] NAVIGATE 'object' 'target' The first form is for objects on planets only. The second form can be used in space or on planets When used in the START/STOP block, 'this' is implicit, therefore 'object' is not permissible The optional 'waypoint' id can be used in a !reach event test e.g usage .f1,100,100,100,100,100,100,0 start inactive on_planet farstar farstar01 22.847 4.666 0 0 navigate farstar farstar01 23.000 10.000 0 waypoint1 stop events !setupl1 activate this !reach waypoint1 FLAG1 ON this broadcast "Reached waypoint objective" signal proceed_to_next,2 !proceed_to_next broadcast "Proceeding to f2 hostile" navigate this f2 !level1tick IF FLAG1 ON this RETURN ELSE broadcast "Still travelling...." ENDIF endevents - FIXED: Sometimes during an AI tick with intruders onboard, a fatal error (sometimes a CTD) would cause the game to shutdown. Note: an interim 1.005 SP1 fix for this problem has been released to the public, until the final 1.0.06 patch is released. Check the discussion forum for more info on this. This fix is included in the final 1.0.06 patch release and will be deleted once that patch is available. v1.0.06 RC6 - 02.15.02 - FIXED: Giving a vehicle an RTB order if its platform (e.g. CC) was not in the same region (e.g. planet) would cause it to vanish as if it were a normal NPC (for which this is valid) - FIXED: Accessing TradCom while docked at a naval base would cause a CTD (due to a minor revision in a previous patch) v1.0.06 RC5 - 02.14.02 - The Police caste now has access to MIM and EFM career. The Raider caste now has access to the EFM career - GBS-II Revisions: . Several docs updated. Basic tutorials added . BCStudio and PTEstudio now use BCSTUDIO.INI and PTESTUDIO.INI files instead of BCMSETUP.INI . CRUISE and INTERCEPT commands have been removed. Use NAVIGATE or JUMP instead - FIXED: Some starbase models were at the wrong location within the planetary mzone scene (e.g. Midae, Eori, Varan etc) v1.0.06 RC4 - 02.10.02 - Previously, if you selected a target from the Priority List for your crafts and the target was beyond their radar range, they would clear the order (e.g. fly-to, attack etc). This is perfectly normal. Just because you can see the target (Tacops and menus have no radar range restrictions), doesn't mean that they can. Now however, they will no longer clear the objective from their list, but instead will store it and attempt to intercept the target and perform the order. - Plugged an exploit in quick save which allowed the elapsing of time with each press - Revised the Perscan pane listings so that if all in a group fit on the left side pane, there is no longer an empty continuation listing on the right side pane. Also in the case of a partial listing, the same icon will now appear in both panes and both panes can now be scrolled. - Implemented several saved game restore integrity checks. Now when loading a saved game any error is considered fatal. Additional checks are performed to validate memory allocation sizes and ensure that object counts are not negative due to loss of syncronization and corruption. v1.0.06 RC3 - 02.05.02 - FIXED: Plugged an exploit in the hand launched grenade logic v1.0.06 RC2 - 02.02.02 - Added PERSONNEL filter to the CVD/RTM. This filters all personnel types, including marines. - A towing shuttle will now ignore its primary target unless it is the current objective. This resolves an issue whereby a shuttle that is delivering something to an object, will cancel its orders and enter "resume waypoints" profile if it's "primary objective" ended up being towed. This AI rule prevents multiple shuttles and other craft attempting to rescue the same object. It also allows craft with STRIKE orders to fall back to SAD if the target is captured. - When a player shuttle is ordered to tow a craft it, will now assume HALT orders and request further instructions when the tow is established. This resolves an issue whereby the shuttle will do an RTB to the CC, even though you may have wanted it to deliver the towed entity to another target e.g. a station. As such, you no longer have to intercept the shuttle and cancel its RTB orders. - The HALT order is now honored during FLY-TO orders. Previously the HALT order was ignored by the A/P or AI if a craft was navigating to a target in another space or planet region. - FIXED: The SFMs weapon will no longer go into an incorrect positional state during re-arming. This seems to be caused by the fact that the SFMs do not pitch the weapon in hand; instead they adjust their pitch orientation. And in some cases, the weapon pos offset is not updated. v1.0.06 RC1 - 01.30.02 - You can no longer dock while cloaked - FIXED: Docking at a starbase with a vehicle will no longer cause a CTD when you login and select the cargo option - FIXED: Attempting to delete a saved game and then opting to cancel the action, will no longer result in an infinite loop as the prompt waits for an invalid confirmation. - FIXED: Increased the separation conflict distance to prevent some ships from breaching a planet's 3D sphere. This feature was introduced in 1.0.05 RC1 but the distance was not large enough for some ship types. v1.0.05 - 01.25.02 * THIS PATCH WILL DELETE ALL SAVED GAMES. IF NOT, LOOK IN THE SAVE FOLDER AND MANUALLY DELETE THEM. - If you launch a craft from Tacops with the AE inside, the view will now auto-switch to the cockpit of the craft, the same way it does on the bridge. You no longer need to press F1 to switch to the cockpit. - FIXED: a station's DISABLED flag wasn't being cleared after it was fully rebuilt and operational v1.0.05 RC4 - 01.23.02 - In Tacops, popping the zoom from scene to map level will reset the view origin to the previous MAP position (not the previous SCENE position). - In TACOPS the grid extent has been doubled. This means that for e.g. in Earth space region, you can now see both Earth and it's moon, without having to adjust the zoom factor. - The maximum CC shield charge is now derated if the CC shield system is damaged. Previously the CC shield system integrity only effected the rate at which the shields recharged. i.e if the shield system was damaged it would take longer for the shields to recharge to the set capacity. - The shield indicator icon on the BridgeViewer now takes into account the shield system integrity. - The HSD hotspot on the BridgeViewer is now enabled on the LOC text if you have the HSD installed and working. - FIXED: In Perscan the text for Medic #10 was always active, as if the mouse was hovering over it v1.0.05 RC3 - 01.22.02 - You can now downgrade to an upgradeable system that is of lesser quality than your current. e.g. previously, upgrading to the TA shield artifact, would prevent you from downgrading to a Spectrum/A shield if the former was damaged. - FIXED: The shield integrity level displayed in the TTD for the CC was inconsistent with it's actual integrity level. e.g. if your shield max level was 1500 and it was destroyed (or being upgraded), instead of the TTD showing 0, it would still show 1500 v1.0.05 RC2 - 01.21.02 - Increased the master sound volume for the bridge comms chatter. Some audio cards (e.g. Santa Cruz) seem to have a different master volume level than others (e.g. SB Live!). As such, the default 0.7 volume level for the comms chatter wasn't even audible. Has now been increased to 0.855. - Added bcmFatalError.log file which contains fatal error messages which occur in fullscreen mode since you won't be able to see the error window in this mode. - FIXED: Towing the CC with an SC while the CC has the same jump target in the CVD as the one the SC is going to jump to would cause a lockup - FIXED: Sometimes when you deployed your AE to a planet (using the transporter) his tactical state remained in BEAM (though the 3D model is properly rendered after he materializes) which cancels all collision detect with the character, allowing him to breach models. v1.0.05 RC1 - 01.19.02 - New saved game digital signature check now compatible and compliant with the upcoming multiplayer Beta release file format. - Resuming/Saving/Restoring a game will now send a message to the debug log files as well as Commlink. This can be used for troubleshooting purposes. - The reactor and engine power are now calculated as full (maximum) based on the previous upgrade level + integrity value of current one being upgraded. - This attempts to solve the problem with you having immediate access to the improvements even though the upgrade is still in progress. - The shield power now linearly depends on the integrity of the shield system. This attempts to solve the problem with you having immediate access to the improvements even though the upgrade is still in progress. - Revised trading scheme to include price depreciation. Pointing to an item in Tradcom displays a status text at the bottom of the screen. The base buys/sells for A/B line indicates you buy (from base) at price A and the base buys (from you) at price B - The check for illegal items when docking at a base will now check the contents of the cargo pod less frequently. This means that you may get away with stashing illegal items in the cargo pod (Logistix/Cargo) prior to docking at a legal base. There is a good chance that they'll miss it. Note that will still always find illegal items in the normal cargo bays. - FIXED: NPCs not intending to actually establish planetfall (i.e. dogfighting close to or just navigating in real space) will now employ different flight dynamics logic in order to prevent them from intersecting the planetary sphere. They will still enter the planet as normal if it is their jump target. - FIXED: In some cases, the item description in Tradcom showed the default starting price of the item instead of the current price at the base. - FIXED: Changing the caste/race via a GBS-II script now properly changes the asset name prefix (e.g. ICV- instead of UCV-) - FIXED: an issue which may cause a problem when assigning System Engineers on some CC assets if there weren't any on-board. This has also been linked to an issue related to long save game load times after extended play. v1.0.04 - 01.05.02 This patch WILL delete ALL saved games. If not, look in the SAVE folder and manually delete them. - Added a digital signature check in saved games to prevent tampering by user or OS - You can now exit your craft in fp mode if it becomes stranded in water. In multi-player this will allow you to ditch the craft, swim to safety and then either use a DJP to get back to your base or have someone pick you up. - The collect order has now been added to the FC&C menu. Remember that the stores manifest for hostile and neutral

Please enter your age:
I am Age 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 years old.

Share this file:

URL: