Microsoft StarLancer Readme File March 2000 © Microsoft Corporation, 2000. All rights reserved. Welcome to Microsoft® StarLancer™! Thank you for purchasing Microsoft StarLancer. This Readme file contains the most recent information concerning StarLancer. CONTENTS A. Online Answers to Your Questions B. Installation Issues C. Game Setup Issues D. Gameplay Issues E. Configuration Issues F. 3D Card Issues G. 3D Card Drivers and Manufacturers H. Multiplayer Scenarios A. ONLINE ANSWERS TO YOUR QUESTIONS You can find more information about StarLancer in the printed manual and on the StarLancer Web site: http://www.microsoft.com/games/da/starlancer. StarLancer MSN Gaming Zone Help If you have questions about StarLancer multiplayer games on the Zone, there are online resources that can help. Zone system operators (sysops) volunteer their time in a Zone Help chat room where you can ask questions about the Zone during the hours posted on the site. On the Zone home page (http://www.zone.com/), click the Help link at the top of the page. If you are unable to get into the Zone Help room, you can email zmaster@microsoft.com for an e-mail response. B. INSTALLATION ISSUES • Installing StarLancer from CD Check that you have inserted CD 1, not CD 2, into your CD-ROM drive. Setup is only on CD 1. If your computer does not automatically install StarLancer after CD 1 has been inserted into the CD-ROM drive: 1. Click Start and then click Run. 2. If your CD-ROM drive letter is D, type D:\setup and then click the Install button. 3. Follow the on-screen instructions for game setup. • Windows 2000 Compatibility If StarLancer will be run on Windows 2000, the user should first install the Windows 2000 compatibility update. 1. Click Start and then click Windows Update. 2. Select Products Update from the Microsoft Windows Update Web page. 3. Scroll down and select the Windows 2000 Compatibility Update. 4. Select Download and install. • Updated Video Drivers on Windows 2000 If you install StarLancer before the Windows 2000 compatibility update has been installed, and you have not updated your video drivers on nVidia based cards then StarLancer will default to software video acceleration mode. To run in D3D accelerated mode, uninstall StarLancer, install the Windows 2000 compatibility update, install the updated nVidia video drivers, and then reinstall StarLancer. • Installing and Running on Windows 2000 In order to install StarLancer on a computer running the Windows 2000 operating system, you must be logged in to Windows 2000 as an "Administrator." If you encounter graphics problems during a game, or are unable to enter a game, check with your video card manufacturer for updated drivers. Alternatively, you can run StarLancer in software mode, which can be enabled in the Video Configuration screen in Game Options. C. GAME SETUP ISSUES • Installation error while running NetMeeting Remote Desktop: StarLancer will crash during the hardware detection phase of installation if NetMeeting Remote Desktop is concurrently running. Close NetMeeting Remote Desktop before installing. • Cyrix 250 processor gives a below 233MHz warning upon installation: The Cyrix 250 processor may run at slower-than-anticipated clock speeds and cause unanticipated problems with StarLancer. D. GAMEPLAY ISSUES • Skip walkaround videos: Right-click the mouse or press the ESC key to bypass the walk-around videos on the capital ship. You can turn off the walk-around videos in the Video Configuration screen in Game Options. • Playing previously saved games after StarLancer is uninstalled: If you uninstall and then reinstall StarLancer, you must type in your old callsign when prompted in the single player game to access previously saved games. You can find your old callsigns in the C:\Program Files\Microsoft Games\Starlancer\Saves folder. All saved games are in the format CallsignGAMEXX.iff. • Enable grayscale: If StarLancer runs slowly or video quality is poor, switching to grayscale mode may improve your performance. Right-click the desktop shortcut to StarLancer. Select the Properties option. In the target field, go to the end of the command line and type “grayscale”. E. CONFIGURATION ISSUES Known hardware and operating system configuration issues (except 3D cards) are listed in this section. • Guillemot Maxi Sound 16 card plays game sound twice: This sound card and its accompanying drivers were never properly certified by Microsoft's Windows Hardware Compatibility Lab (WHQL). Contact the manufacturer for updated drivers. • Game control device does not function: If several game control devices (joysticks, gamepads, etc.) are attached to USB or gameports, they may not function properly. Disconnect all but the primary game control device and restart StarLancer. • Daisy-chained Sidewinder joystick has no throttle control: If your Sidewinder joystick is daisy-chained from a Sidewinder gamepad and the devices are switched in the middle of a game, then the throttle control may fail to work. If gamepad or joystick devices are reconfigured, restart StarLancer to recover full functionality. F. 3D CARD ISSUES StarLancer only fully supports DirectX 7–compliant video cards. If problems persist, run StarLancer in software mode, which can be enabled in the Video Configuration screen in Game Options. • #9 FX Reality 334: Some textures may be missing. Upgrade the latest drivers from the manufacturer (http://www.nine.com) to correct this issue. • #9 Revolution IV: Ship cockpit corrupts when pulling up. To resolve, upgrade video drivers for this card from the Number Nine Visual Technology site (http://www.nine.com). • 3DFx Voodoo 1 chipset: Cards may not be properly recognized and StarLancer will default to software mode. Other graphic and performance anomalies can also occur. Contact the manufacturer for DX7-compliant video drivers or install the latest reference drivers from http://www.3dfx.com. • 3DFx Voodoo, Voodoo 2–based 3D accelerator video cards: StarLancer hangs during the hardware detection phase of installation. Upgrade video drivers from the manufacturer to resolve this problem. • 3DFx Voodoo3 2000: StarLancer hangs at the “please wait while loading” screen when run at 1024768 resolution. Updating to the latest video drivers from the manufacturer (http://www.3dfx.com) solves this problem. • 3DFx Voodoo3 3000 and 2000 AGP: Loading certain missions causes StarLancer to hang. Upgrade video drivers for these cards from 3DFx (http://www.3dfx.com) to resolve this issue. • 3DFx Voodoo3: Changing resolution from 640480 to 1024768 will crash the game. Download and install the latest 3D/fx drivers (http://www.3dfx.com) to resolve this issue. • 3Dlabs Permedia 2: Nebula textures may be corrupted. Installing the latest drivers from 3Dlabs (http://www.3dlabs.com) will alleviate most of the texture problems. • Asus 3D Explorer: StarLancer will hang at the main menu after selecting an Instant Action game. Download the latest drivers to fix this problem (http://www.asus.com). • ATI All-in-Wonder PRO PCI: Game appears very dark. Download and install ATI’s Special Purpose 5.40 b2 driver, which will adjust the video card to a higher gamma value. • ATI Rage 128 GL AGP: Cannot change default video settings, and gameplay graphic textures appear unblended. Download the latest drivers from (http://www.atitech.com) to fix this problem. • ATI Rage 128: The orange glow from suns have black polygons cutting through them. Download latest drivers form ATI to resolve. • ATI Rage II/II+ PCI: StarLancer will hang if the ESC key is used to bring up the Options menu during a mission. Download and install the latest drivers for the ATI Rage II / II+ from www.atitech.com to resolve this issue. • ATI Rage/Rage II PCI (ati_m64) and Voodoo Graphics 3D Accelerators: May receive an error message that DX7.0a is required to run StarLancer. Install DirectX7.0a from the StarLancer CD 1. Right-click the CD-ROM drive and select Open. Double-click the Directx folder, and then double-click the Directxsetup application to install. • Canopus Pure3D PCI Video Multimedia Device: Textures are missing from capital ship. Contact the manufacturer for updated drivers (http://www.canopus.com) or download and install the latest 3DFx reference drivers (http://www.3dfx.com) to resolve this issue. • Creative Graphics Blaster Extreme: When StarLancer is run at 1024768 resolution, desktop images bleed onto the main menu. To resolve this problem, contact the hardware manufacturer for updated drivers or install the latest reference driver for this Permedia 2–based card from http://www.3dlabs.com. • Creative Graphics Blaster Savage 4: Changes made to brightness setting in Video/Options screen may be lost. Upgrade to the latest S3 Savage 4 reference drivers from http://www.s3.com, or contact the hardware manufacturer for updated drivers. • Creative Graphics Blaster Savage 4: Game shuts down during Mission 1 jump sequence. To resolve this issue, download the latest drivers from the manufacturer (http://www.creative.com). • Creative Graphics Blaster Savage 4: Textures may be improperly blended and game performance may be degraded depending on video driver version. Contact the manufacturer for updated drivers or download the latest S3 Savage 4 reference drivers from http://www.s3.com. • Dell Velocity 128: Dell OEM system owners should contact Dell (http://www.dell.com) for updated drivers. Installing third-party or reference drivers on Dell systems may cause graphics anomalies and system instability. • Diamond Stealth G460: StarLancer hangs during hardware detection. Download the latest drivers from the manufacturer (http://www.diamondmm.com) to resolve this issue. • Diamond Stealth III S540: Textures may be improperly rendered during gameplay depending on video driver version. Contact the manufacturer for updated drivers or download the latest S3 Savage 4 reference drivers from http://www.s3.com. • Hercules Power Drive Terminator Beast and Hercules Stingray 128: Older video drivers cause the title screen to hang. Download and install the latest drivers or run StarLancer in software mode. • Matrox MGA Mystique, Matrox Millennium II AGP PowerDesk, and ViRGE PC1 (325): Direct 3D acceleration is not supported. StarLancer will only run in software mode with these video cards. • Matrox Millennium G200 AGP: Background stars may disappear or flicker. Download and install the latest drivers from http://www.matrox.com to resolve this issue. • Matrox Millennium G400: StarLancer hangs at the “please wait while loading” screen when launching a mission. Update your display adapter with the latest video drivers from the manufacturer (http://www.matrox.com) to resolve this problem. • Matrox Productiva G100 AGP: Lighting effects may not be present in StarLancer. Upgrade drivers for this video card from http:\\www.matrox.com to resolve this issue. • NEC PCXR 2 chipset (Matrox M3D, Power VR 1): All textures are black. Contact the hardware manufacturer for updated drivers or run StarLancer in software mode to fix this problem. • Nvidia riva 128 chipset: StarLancer may hang at start/load game screen. Download the latest video drivers from your manufacturer to resolve this issue. • NVidia Riva TNT2 Ultra: When exiting StarLancer running on a Windows 2000 operating system an error message occurs. Install the Windows 2000 Application Update to resolve this problem (see Section B, “Installation Issues,” Windows 2000 Compatibility bullet). • Quantum Obsidian 2: Textures are missing from ships and planets. Upgrading the latest 3D accelerator drivers from the manufacturer (http://www.quantum3d.com) fixes the problem. • S3 Virge/Vx/Dx/Gx chipsets: StarLancer will not detect these video cards as D3D hardware compatible. Run StarLancer in software mode. • SiS 620: In some video memory configurations players see only their fighter, but not enemy ships or movies. Download and install the latest drivers from the manufacturer. If the problem persists, run StarLancer in software mode. • STB Nitro DVD Mpact chipset: HUD and radar maps do not render sharply. Run StarLancer in software mode. • STB nVidia ZX 8MB and NVidia RIVA 128/128ZX: StarLancer’s cinematic sequences may appear choppy when run at 1024768 resolution. Download the latest drivers for these video cards to alleviate this problem or run at a lower resolution. • STB Velocity 4400: Bottom of screen flickers during debriefing. Fix by upgrading video drivers for the STB Velocity 4400. • STB Velocity 4400: Changes made to brightness level in the video options has no effect. Download the latest video drivers from the manufacturer (http://www.stb.com) to fix this problem. G. 3D CARD DRIVERS AND MANUFACTURERS Make sure that you have the latest drivers from the manufacturer of your video card. Many video issues will be resolved if you install your video card's latest drivers. Some older video cards may not be detected properly by StarLancer because their video drivers are not DX7 compliant. Please contact your video card manufacturer for updated drivers or install the latest reference drivers for your video board. Note that many reference drivers are not supported by the chipset manufacturer. Listed below are some common video card manufacturers' Web sites. StarLancer may not support some or all of the cards produced by a particular manufacturer. 3D/fx Interactive -- http://www.3dfx.com/ 3Dlabs -- http://www.3dlabs.com/ AccelGraphics -- http://www.accelgraphics.com/ Asus -- http://www.asus.com/ ATI -- http://support.atitech.ca/ Canopus -- http://www.canopuscorp.com/ Creative Labs -- http://www.creativelabs.com/ Deltron Flash 3D -- http://www.deltrontech.com/ Deltron Technology -- http://www.deltrontech.com/ Diamond Multimedia -- http://www.diamondmm.com/ Elsa Technology -- http://www.elsa.de/ Gateway 2000 -- http://www.gw2k.com/ Guillemot -- http://www.guillemot.com/ Hercules -- http://www.hercules.com/ I/O Magic -- http://www.iomagic.com/ Intergraph -- http://www.intergraph.com/ Jaton -- http://www.jaton.com/ Leadtek -- http://www.leadtek.com/ Matrox -- http://www.matrox.com/ Metabyte -- http://www.metabyte.com/ Miro -- http://www.miro.de/ Number Nine -- http://www.nine.com/ NVIDIA -- http://www.nvidia.com/ Orchid -- http://www.orchid.com/ Quantum3D Obsidian -- http://www.quantum3d.com/ Real3D -- http://www.real3d.com/ S3 Incorporated -- http://www.s3.com/ Silicon Integrated Systems Corporation (SiS) – http://www.sis.com.tw/ Sierra On-Line -- http://www.sierra.com/ STB -- http://www.stb.com/ TechWorks -- http://www.techworks.com/ VideoLogic -- http://www.videologic.com/ H. MULTIPLAYER SCENARIOS Cooperative Play Two or more pilots can join forces and play through the StarLancer missions. • Loading Previously Saved Missions: Hosts can load previously saved co-op games. They can also load previously saved single-player games and start a co-op mission where that single-player mission ended. Death Match Multiplayer Games • AI turrets: Laser turrets embedded within asteroids. When this feature is enabled, turrets will shoot at all death match players. If a player, in turn, shoots and hits a turret, that turret will no longer fire upon that player. Death Match Scenarios • Asteroid Field: A death match set in a dense pocket of asteroids. Teamplay: Team with the most kills wins. • Nuclear Threat: Hidden in a field of asteroids are six beacons. The player who collects all six beacons and enters the beacon gate will trigger a nuclear strike, killing all other players. Destroying a player’s ship will drop any beacons they carry. Teamplay: None. • Dark Reign: This death match takes place around an active Dark Reign tower. The player who finds the Dark Reign Comms Relay cannot be targeted by the tower. All kills by the Dark Reign are added to the controlling player’s score. If the controlling player is killed, the core randomly re-spawns among the powerups. Teamplay: Team controlling the Dark Reign is immune to targeting. • Tag Bomb: Each player’s ship is fitted with a time bomb. When players are killed, they re spawn with the bomb timer ticking. If the player with an active bomb shoots and hits another player, his or her bomb will stop ticking and the other player’s starts. If a player is destroyed by his bomb, the person who tagged that player will get two kills instead of one. Teamplay: Team with the most kills wins. • Hunt the Shadow: The first player to kill an opponent becomes the shadow. The shadow is indefinitely cloaked, but has no shields and cannot pick up powerups. The player who kills the shadow becomes the next shadow and earns five additional kills. Teamplay: Team with the most kills wins. • Vampires: The first killed in this match becomes a vampire. Vampires can spread their disease by killing an uninfected player. The last human player remaining scores five kills, and then all players are cured and the process starts over. Vampires cannot pick up powerups. Teamplay: None.