R2D2
holo
 Latest News
News       Downloads       Media       Wiki       Stats       Team       Forums    
WolfServers.com
Shattered Planet
 First Strike Installation Guide
25 Sep 2010 - 09:09 by TALON FirstStrike News | comments (114)
INTRODUCTION

Welcome, this guide is intended to help you install and solve the most common problems reported with First Strike. First Strike is a total conversion mod for Battlefield 2142, placing the game in that galaxy far far away.

Some quick notes:

The path directories mentioned here are the default ones created when Battlefield 2142 is installed. If you install Battlefield 2142 to any other file path you must ensure that First Strike also extracts to that location.

The mod does not alter ANY BF2142 files, it creates it’s own directory folder in C:program files/electronic arts/battlefield 2142/mods.

The mod is built to run on a valid licensed version of Battlefield 2142 patched to 1.50. Cracked copies of the game are not supported and this mod will not help you bypass any of the games security checks.

The mod will install its own autopatcher and launcher program. This should be used to launch the game, do not attempt to launch the game through the First Strike.exe found in the Battlefield 2142 folder.



INSTALLATION

Ok, with those bits out of the way, it’s time to crack on. For users running Windows XP, installation is straightforward. Simply run the downloaded installer, ensuring that the program installs to your Battlefield 2142 directory. You must ensure you allow it to also install the First Strike autolauncher and updater.

Installation under Windows Vista and Windows 7 can be a little more involved. It certainly helps to turn off User Account Control, if you are not happy to turn off User Account Control, then you must ensure you have administrative rights in order to install.

Install BF2142 and update to 1.5
Install First Strike 1.5 (at time of writing this is the latest version)
Right click on both BF2142 and FS icons, then set to run as administrator.
Run First Strike and allow it to update.

*Note, when clicking on the installer for either game, you may need to right click and select run as admin.

When running First Strike for the first time you may get some firewall warning pop-ups, remember to allow First Strike through your firewall!

If still encountering problems on Vista or Windows 7, right click on First Strike and check if it is running under compatibility mode for earlier versions. If it is, disable compatibility, if not, try setting it to run under compatibility mode for Windows XP.


CRASH WHEN LAUNCHING

A common problem reported is a crash to desktop when first starting First Strike. This is most often reported by users running widescreen resolutions. In order to allow First Strike to run widescreen, and show widescreen resolution options in game, we have included the ability to enable it from the First Strike launcher.

Open the launcher but do not hit deploy.
Click on file then preferences.
In the small windows is a field titled Arguments, in this field you can enter ANY resolution you wish. To enable widescreen options simply enter: +widescreen 1
Click apply then ok.

You can also use this same field to enter any resolution not supported from the in game options. To do this, again find the arguments field as above. This time enter +szx **** +szy **** substituting the asterisks for your resolution, eg +szx 1920 +szy 1080.






CANNOT FIND SERVERS

Some users are unable to find servers when in game. To find servers running First Strike, first click on First Strike servers tab from the multiplayer menu. Ensure all buttons along the bottom are unchecked except for same version and same mod. Click update, the menu should now populate with all servers running First Strike.






ISSUES WITH PUNKBUSTER

If you find you are getting disconnected from servers with a punkbuster error you can try the following. Ensure punkbuster is installed on your system and running, you can do this by starting taskmanager and under processes look for pnkbstrA and pnkbstrB. You may need to tick the checkbox titled 'Show processes from all users'. If you cannot see those processes then you will need to reinstall Punkbuster. Go to the EvenBalance website (just Google it), and download punkbuster. It will ask you what games you have installed, direct it to look for Battlefield 2142. It should then correctly identify the game, instruct it to check for updates. Once updating has finished you should then be able to run the game with no further problems.


CRASH WHEN USING SOME VEHICLES

There have been reports of game lock ups when using some vehicles, particularly the AT-ST. The symptoms are game freezing, with a constant looping of recent sound. No game response, and user may have to alt tab or ctrl-alt-del to bring up task manager and halt the game. This seems to be a compatibility issue between some soundcard hardware. To fix this, in the game options menu disable audio hardware and set it to software, then disable EAX.


CRASH WHEN CLICKING DEPLOY

When a map loads and you click the deploy button it can be one of a number of reasons.

1) The server is running a different version of First Strike. Check you are running the latest version of First Strike (1.5 at time of writing). As First Strike has the ability to download incremental builds produced by the development team, you must ensure you allow these to install. You can check which 'build number' you have installed by clicking on File, Preferences in the launcher window, the build number is displayed in the field 'Version'.

2) A recent patch has not yet been applied to the server you attempted to join, try a different server.

3) You have attempted to join the Development server. This server is used to test new content by the First Strike team. Attempting to join it using the publically released files will result in a crash to desktop.

Other crashes and game freezes can often be solved by clearing your cache, this is found in My Documents, Battlefield 2142, Mods, FirstStrike. Just delete everything in the cache folder. The game will repopulate with contents but it will cause you to load shaders again when you first start loading.


UNABLE TO RUN FIRST STRIKE WITH DIGITAL COPY OF BF2142

Those who have a digital copy of BF2142 from the EA Store may have problems running First Strike, it may even ask you for the BF2142 disk. In order to get around this, you need to navigate to your BF2142 directory, usually this is program files/electronic arts/battlefield 2142. In this folder you need to find two items, BF2142.exe and FirstStrike.exe. Copy your BF2142.exe somewhere and then rename it to exactly match the FirstStrike.exe. Delete FirstStrike.exe from your BF2142 directory, then place your newly named .exe in the folder.


CAN'T SEE ANYTHING IN SPACE MAPS

In order to fully appreciate First Strike and play all maps you need to ensure that you have View Distance set to 100% in game options.


MAPS NOT LOADING, STOPPING AROUND 60%

1) Go to your BF2142 folder, eg C:Program FilesElectronic ArtsBattlefield 2142

2) Locate the file "radial.cdb"

If you do not see this file in the folder then you need to go to folder options tell Windows to show hidden files. You also (or instead) have to uncheck the box just a little bit below it, which is "Hide protected operating system files".
(For some reason this is a protected file and will not show if you ask to show normal hidden files.)

3) Rename the file to oldradial.cdb (or something similar so you know what it is) and start your game.

The game will create a new radial.cdb file on it's own.



FIRST STRIKE GAMEPLAY

This section will briefly cover some of the more common mistakes players may make when they first play First Strike.

Many maps in First Strike use a set sequence that flags must be captured in. The loading screen will always tell you if the map you are about to play has this, if you check the map once deployed you will often see lines or arrows connecting flags. These lines and arrows indicate which order flags must be captured in. Arrows also indicate the direction flags may be captured in, for example on the map Endor Strike Team, the arrows indicate the capture order, but also show that only Rebels may capture flags. In this case Imperials may only defend the areas. If in doubt, please ask in game by pressing the Talk key (default 'J' key) and typing your message.

Other maps have what it known as an objective mode, this means that items such as ships must be destroyed to achieve victory. In the map Battle of Yavin, the four deflector towers must be destroyed before Rebels will be able to attempt the famous Death Star Trench Run. Other maps require ships to be destroyed or to reach a certain location, again check the map loading screen for more details or ask in game.

First Strike is a very teamplay orientated mod. In order to emphasise this, certain kit items may only become available when in a squad with a set number of players.

The Officer kit found on infantry maps is only available to Squad Leaders, if you are not a Squad Leader and you select this kit you will end up with a spawn in count of 1000, so choose one of the other available kits.

First Strike does not have kit item descriptions, although some items such as guns and knives are self explanatory, other items may not be immediately obvious. You can often pick up some items such as droids or shields, but be careful when selecting something for the first time! Squad members may not take kindly to you throwing a frag nade in their midst while attempting to capture a point!

Although some vehicles may seem difficult to destroy, all weapons in First Strike will do some damage to them, but a pistol will obviously not be as powerful as a rocket launcher. By utilising good squad play, four or five people can quickly bring down an AT-ST or tank.

Some vehicles feature spawn points, such as the Lambda shuttle or APC Freerunner. Be careful when spawning in these vehicles, if you appear in the drivers seat do not be tempted to suddenly drive off, you could end up killing team mates, or remove a valuable asset from a strategic area.

On atmospheric maps, aircraft have a VTOL (vertical take off and landing) capability (default S key), remember to use this, it can be embarrassing to throttle up and suddenly crash your ship. When using the Lambda Shuttle or Sentinel Landing Craft this is doubly important. These craft have folding wings for landing, attempting to land with the wings down will topple your ship and result in a number of teamkills. Always remember to land using the repulsorlift hover (S key!) to fold the wings and set her down gently.

For further information on all things First Strike, including descriptions of weapons, gadgets, vehicles and maps check out the:

First Strike Wiki

Read More   |   Older News

 1.5 Release Review: Part Two
21 Sep 2010 - 19:09 by TALON FirstStrike News | comments (110)
Welcome to the 2nd part of our retrospective review of the release of 1.5. Below Twigs delves into the development of the hotfix patch and the new Singleplayer and Co-Op maps amongst other things, the article is also lavishly illustrated with shots from Strike at Parmel and several Co-Op maps showing the truly intense action to be had there.

Enjoy.



Well Troopers, now that FSDev Talon has written up his thoughts on 1.5, it’s time for me to add mine. Grab your favourite beverage and settle in as I talk you through some of the changes that were made for the 1.5 hotfix.

I’d like to think Strike at Parmel has it’s fans. It’s a quick, no holds barred space map, where you choose your fighter and seek out the enemy. There were some issues though, the largest complaint was to do with the number of seeking missiles from A-Wings and TIE-Defenders, though bizarrely one of those that complained then went on to ask if we could add homing torpedoes to the X-Wings!

My first task then was to settle this issue, but it wasn’t as simple as merely changing the projectile numbers for the ships. Any changes made to the ship directly would affect other maps, and copying the craft to have two different versions would have added more to the mod increasing it’s size, only by a little though. In the end I was able to use a different method that changed both the number of missiles and the characteristics to the missiles using a method to create an edit in the maps control files. The result was to limit the number of missiles to 2, so you really need to think about when to release them!




How do I feel about the map now it’s out there though? Well, being biased of course, I love it! It’s a great illustration of how those early X-Wing games can translate across to First Strike. Get a few people on and it quickly begins to look a lot like a scene from the movies. The layout of the map focuses the action in a much tighter area than some other space maps, and the result is a whirlwind of ships jockeying for position and a light show that really impresses.

The second part of the hotfix focused on that most troublesome of maps, battle of Yavin. This was a map that many had looked forward to, recreating the Death Star trench run as closely as possible, it’s a must do for any Star Wars fan. Nvidia users experienced problems from day one though, low frame rates, graphical glitches or crashes were the result for them if they tried to join. The problem, said the majority, was caused by the icons for the deflector towers, but nothing appeared wrong with them when looking through the code or at the icons themselves.

I decided it was time to tackle the problem once and for all, if the icon is the problem then lets get rid of it. I needed a volunteer to test out my ideas though, I had never suffered from this dreaded bug. New Dev team member Benu_Kenobi quickly volunteered to be my guinea pig. We started by removing the icon code from the deflector towers, Benu started the game and jumped in and within moments reported that the issue still existed. After sending me a screenshot and also mentioning some other issues I wasn’t convinced it was anything to do with the towers. Instructing him to remove the towers altogether, he once again jumped in game and confirmed that the issue still existed. Checking some other items on the map, we went through a number of trials, reducing view distance on objects to see if cards were being overlooked, removing the exhaust trench icon etc, but still couldn’t find the root cause. Eventually I decided I’d had enough, it was late and I needed to get to sleep.




Benu decided to keep going alone. He did suffer from the glitch, and now that it was confirmed that it was neither the deflector towers 3d icon, or even related to the towers themselves, he was now determined to discover what was keeping him from enjoying this map. He removed items one by one until eventually he was left (and I’m not kidding!) with a black map with only fighters and turbolasers. The issue was still there, and by now he was beginning to think it was perhaps an invisible terrain problem, or a heightmap or something else. Tired, annoyed and angry, he tried one last thing and removed the turbolasers.

The map ran without a problem, shocked, he began to add in everything except the turbolasers. His words to me when he told me about it were, “my God, Yavin is beautiful!” The cause then was a 3d icon, but not for the deflector towers, but the turbolasers. We simply removed those icons and now the map can be enjoyed by everyone. I must say, I did chuckle when Benu was playing the map with the updated turbolaser code and said to me, “Oh my God! The exhaust port DOES have an icon!” It was just one of those things, with everyone so focused on the towers he’d never been told the trench had one.




So, with all that said, the other hotfix things were fairly minor. My own brief thoughts on 1.5? I think it’s done pretty well. A lot of minor issues were resolved, some new maps and of course the addition of Singleplayer and Co-Op. I do get a chuckle though when I hear people say the bots are too hard! Personally, my real favourite change is the Rebel fighters on yavin now shooting down TIE’s, it was a real bugbear of mine that the X’s and Y’s couldn’t fire lasers.

Now, some people will tell you I’ve done a lot of work in 1.5, and yes it’s true to some extent, but on the whole my job has been one of refinement or implementation. Much of the real work has been done by others like FSDev Benu, who really stuck with finding the Yavin bug, FSDev Restnpit who helped a great deal with some of the AI especially the X-Wing laser fire, and of course FSDev Dnamro who supplied all the Co-Op and Singleplayer maps. My role was more that of an apprentice, taking the work these guys produced and learning from it before finding ways to try and tweak that further.




There’s plenty more to come yet though folks. I have more plans for SP and Co-Op implementation and continue to work with Dnamro on that. We still have other minor issues to fix, but in order to do that we need players! Get on the servers, enjoy the mod and come tell us what you think could be done to help improve it. Until next time!

Twigs
Read More   |   Older News

 1.5 Release Review: Part One
14 Sep 2010 - 08:09 by TALON FirstStrike News | comments (115)
Greetings Troopers!

With the Summer drawing to a close and the latest release of First Strike out there in people's hands for a few weeks now, it is time for us to take stock, and look back at how this release went. Of course there'll also be quite a bit of eye candy to be had in this article too, taken from heavily populated games post the release of First Strike 1.5, so enjoy.

So just how did things go? Well as seems to be something of a tradition these days with our releases, something went wrong with the parent game literally days before our release date. In this instance it was an issue with the EA Master Server. It seems that GameSpy decided to change the location of their server which deals with several Battlefield games including BF1942, BF2, and of course the one that concerns us the most, BF2142. Now it was thought that this server move would go smoothly causing no issues whatsoever to players of the games concerned. Famous last words, of course this turned out not to be the case and all these games suffered from intermittent connection to the EA Master Server meaning that you'd drop out of play every 5 minutes or so. There were also issues with stats not registering, but that is a minor issue when compared with not being able to enjoy a full round of a game without banging out half a dozen times. Obviously with our release occurring so close to this incident no doubt a lot of players new to First Strike have assumed that the issues they were experiencing with our mod and BF2142 were caused by First Strike, and I can state categorically here that that was not the case. Within a week the problem was fixed, and not long after that everything went pretty much back to normal. Any bugs, crashes and further issues after that point were all ours.




Overall despite these issues the release has been a success, people have stuck with us despite the initial EA Master server bug, and we have been releasing a steady stream of Hotfix updates with the First Strike Launcher through our Auto Updater system. This has allowed us to address several balance issues that came to light on release, and fix a long term problem with the space map Battle of Yavin, on which we shall go into more detail in a later update. In addition we have made a few server side updates that have also fixed a number of issues including getting our persistent stat tracking system operational again. I ask all First Strike server admins to restart their servers if they have not done so already, this will cause your server side version of First Strike to update, and as long as you're running Punkbuster, stats should then start to be recorded by your server.




What has been most pleasurable for me personally to witness on release, has been how theories on how the gameplay would flow on the new maps such as Jundland Wastes have proved to be true once we got large numbers of people playing the thing on servers. In testing there were many naysayers who felt that the Jawa Sandcrawler would be a useless asset due to it's slow speed, and that nobody would want to drive that thing across the map. You can clearly see from the screenshots in this article just how wrong they were. People just love fighting over that thing, and the fact that the mobile one can be captured makes it a dynamic asset that can really turn the tide of the battle. People also felt that the little tank that could, the MLC-3 would be useless in any situation where it saw real action, but that asset also proved its worth with a capable driver at the wheel. The Sentinel also turned out to be just as fun an asset to use and fight over as we expected it to be, so it is great to see lots of people playing these new maps and enjoying the fruits of our labour. Makes all the hard work worthwhile.




So we hope people stick around, enjoy the new maps, and the changes and balance tweaks that have been made to the old, including the inclusion of co-op and singleplayer functionality, again something we'll go into more detail about in a future news post. We'd like you to know that we'll be further tweaking the mod based on player feedback, and in a later update we'll also look at revealing our big plans for our next big release, finally the fabled release of the Battle of Hoth that you've all been waiting for.

Until then, see you out there on the Battlefield.


Read More   |   Older News

 New Hotfix Released
04 Sep 2010 - 09:09 by TALON FirstStrike News | comments (112)
A new hotfix is out!

This update will fix a few issues including making the Battle of Yavin map stable for players using Nvidia graphics cards at long last. There are also a number of tweaks based on player feedback to the release, and the return of the Mortar Freerunner, which we hope now will prove to be crash free.

Simply use your FirstStrike Launcher to update your mod. It might take a little while for servers to update, so if you are having problems connecting to them immediately after updating, wait a while.

This is just the first of a number of updates we have planned to improve your First Strike experience.

You'll find the full changelog below:

Strike at Parmel:
- ALL Spawn time of TIE/D and A-Wing increased
- ALL Changed behaviour of TIE/D and A-Wing missiles,
also now limited to 2

Battle of Yavin:
- ALL NVidia crash bug fixed
- ALL Turbolaser sensitivity fixed
- COOP 16p and 32p OOB area reduced
- SP 16p OOB area reduced

Vehicles
- Freerunner crash bug hopefully fixed, re-added to select maps
- ME Speeder rapid-fire bug fixed
- ATST rapid-fire bug fixed

Weapons
- Packered Mortar Gun zoom fire animation fixed
- Ironsights hit indicator added to select weapons
- Bots now re-supply E-Web generator

Read More   |   Older News

Screenshot of the Week
Divider

Screenshot of the Week #20 
Submitted by: Twigs 
View Past SSotW 


Top Ranked Players
Divider

 

    

© FirstStrike 2006-2025  -  Disclaimer

trapp Design