Reviews for XWA-CAB 2
|
|
| | Not good. Half the missions left me guessing what I was supposed to do next, not a clue in sight. I'm pretty sure the 'Millenium Falcon' wasn't meant to be used arbitrarily, and how on earth does the player find himself stuck in a TIE Guardian, when he's not in Omega? Not to mention the bit where some n00b tactical guy decides to send an SSD into a warzone with NO SHIELDS??? In general: if you need to add invincibility to anything in order to ensure its survival for whatever reason, the battle usually sucks. In this, friendly MUTRs and T/D are invincible. Why are Imperials dogfighting in a MUTR?
|
| |
|
| | Pretty sure this is a joke battle. Such unreasonable difficulty deserves less than a 0, so.. I do not advise you play this battle unless you are a) Deimos or Bruc or b) High on drugs
|
| |
|
| | listing of why it is the worst battle ever: 3 sec AI lock, unclear mission objectives,unclear goals, mission 4 VERY unclear *tip* fly as fast as you possibly can and get to the CN/K sensor(close to name) as soon as freakin possible, then flay as fast as you can to the other container andif your lucky you can beat it, razer's with 3 sec lock with Adv. missiles(though good dodgeing missiles exercise), mission 7 overall,i would nitpick everything but i would need a whole page...unrealistic(SSD destroyed by T/G), too many enemy capital ships and spacestation stuff to destroy with little fighter support on your side, not to mention dealing with the "3 sec wonder" fighters at the same time you need to destroy capships and SSD. i can't give negative numbers so its 0. but if i could...I would.
|
| |
|
| | In mission 4 (or was it 5) it is extremely annoying that when oyu fly a Firespray, a few minutes in the mission Razor Fighters hyper in practically next to your CORT you are supposed to protect and annhilati it ina matter of maybe 10 seconds... THis takes out all the funn of the entire battle...
|
| |
|
| | The battle was originally created on a PII 200. What I'm seeing is a wide range of problems across various CPU speeds. I flew the battle myself again on a 2.1 gig machine, and ran into all sorts of timing problems because of the faster processor. All I can say is that it runs perfectly on a PII. What I can say is this. My biggest mistake was having events based on time instead of having them based on what the pilot does. As you can imagine, on faster PCs, the timing gets really screwed up which caused these problems. Well. I see this as a very valuable lesson and learning process. I went for an epic story and tried to make it unusual and interesting, but I see now, I needed to have constructed the battle in a different way than I did. Also it was specifically designed to use custom pilot ships, which would have mitigated some of the difficulty levels some pilots expressed to having. The ships were still pending being patched, but I should have waited until they were and I could add them in. My apologies to those of you who had a terrible time with it...
|
| |
|
| | Well i liked the story on this and some of the mission work was good but there are a few things that really ruin it. The mission objectives are unclear at best, especially in mission 4. I agree with Bros on the issue of the MUTR, its pointless as it is. Overall in most missions there are too many fighters with too many warheads. Needs a bit of work to be considered really good, but still a good start
|
| |
|
| | This battle still had some faults and was very annoying in some cases. Basically it's a "Superhero vs the world" scenario where you fly outnumbered 1 to 20 or something. What annoyed me the most is that the enemy fighters usually hypered in extremely close to you, so you ended up under fire from 12 fighters almost immediately. Oftentimes the new fighters kept crashing into me, simply because we were all in the same spot at the same time. Missions were still a little buggy in all kinds of aspects. The animated mission briefing in mission #1 for example showed 2 different sentences, while the 'review yor briefing' screen showed three. I also would remove the Adv torps the MUTR carries. It shoots them like they were laser blasts and the torps don't hit anything this way. That's what you get giving warheads to an AI craft that isn't supposed to be able to carry them. Once I completed mission #6, there was no place for me to return to. I had to use the 'Quit' mission command.
|
| |
|
| | Still a bit buggy, but after reinstalling XWA entirely, as well as reinstalling the XWA 2.02 upgrade, the S-foils patch and the TIE Guardian patch everything seemed to flow along pretty smoothly. Still a few quirks in the battle, but overall a great storyline and a very impressive design.
|
| |
|
| | I liked it. There is no bug to this mission (from what I can tell). If a hyperbouy doesn't show up, shoot at stuff. The destruction of a capital ship will bring about the hyperbouy. Your giving a MIS for a reason. In the gunboat mission, just use your jamming beam right and you will do fine.
|
| |
|
| | ok i gave it before 0 , but after consideration i change it to 2 , sorry i just had very much difficulty with that battle more people also , AI crafts even on easy insane , on 5th mission cant hyper out cos sometimes hyperboy doeasnt appear , many more but i forgoten them , i didnt finish that battle it happened first time in xwa , so play it and judge yourself
|
| |
