Bad CC Missions.

Post by **Jagged Fel** » Thu Mar 17, 2005 7:13 pm

I came across a XWA mission like that (EH) so I was lucky enough to have rudder. Each cap ship when trying to pivot towards you has a sweet spot, where if you're at just the right speed (I think matching is fine) and you follow one point on the ship's hull you'll circle each other unti lyou eventaully blow it up. You have to be careful though, as this requires being very close, and it suddenly switches direction you gotta get out of there fast.
I think I've done this is TIE, too, it was just easier in XWA.

Heh, Vort you're gonna have a fun time fixing stuff when you get my list

MCHuskie · Post by **MCHuskie** » Fri Mar 18, 2005 3:40 pm

Just about every TIE mission I remember ended up with me and a single cap ship (normally an escort frigate) in deep space, it following me around, me trying to blow it up.

Hey, about that OS mission I've just flown...

Syrtaras · Post by **Syrtaras** » Fri Mar 18, 2005 5:09 pm

Vort: Apparently, there's a bug in Tie 95: ISDs do not fire lasers.

Funny, eh? :P

Post by **Vortagh** » Fri Mar 18, 2005 5:59 pm

Then why do the other ISDs fire? :P

LC La Forge · Post by **LC La Forge** » Fri Mar 18, 2005 9:08 pm

Sick LA irony, perhaps?

Post by **Jagged Fel** » Fri Mar 18, 2005 10:51 pm

There's a patch for that.

drazhar · Post by **drazhar** » Thu Apr 21, 2005 9:49 am

ERS-71 is completly borked.

1: Mission One, no shields on the TIE's (dont give crap about challenges, stick to policy, Imperial Policy: TIE's get shields)

2: MIssion One: For me the TIE Bombers didnt fire any warheads

3: Mission Two: ISD Doesnt fire. This is a bug in the game. Make missions without ISD's or find a fully working patch. Dont provide missions that have ISD's that are supposed to fire, but dont

4: Mission Two: After destroying the CRS the ISD jumped to HS. The mission goals said that they were completed, but when i got to the debriefing screen it said i had failed. Tried this three times, and thats what happened.

5: CAPITAL SHIP ORDERS FOR CAPITAL SHIPS

I wont be reflying this mission, sorry, but ive spent nearly ten hours doing just two missions, it wont be happening again. Sort it out, release an XvT version, i dont care, BUT SORT IT OUT

Post by **Vortagh** » Thu Apr 21, 2005 9:53 am

drazhar wrote:ERS-71 is completly borked.

1: Mission One, no shields on the TIE's (dont give crap about challenges, stick to policy, Imperial Policy: TIE's get shields)

IIRC, Fel told me that Mission 1 of Battle 1 you cannot have shields on a normal TIE/F. Fel/Pol would have to explain though.

2: MIssion One: For me the TIE Bombers didnt fire any warheads

No idea why that happened, TIE/Bs are equipped with Torps.

3: Mission Two: ISD Doesnt fire. This is a bug in the game. Make missions without ISD's or find a fully working patch. Dont provide missions that have ISD's that are supposed to fire, but dont

I agree, but I think I have found a better TIE patch from the EH. Will test it.

4: Mission Two: After destroying the CRS the ISD jumped to HS. The mission goals said that they were completed, but when i got to the debriefing screen it said i had failed. Tried this three times, and thats what happened.

Checking the mission, I think I might have found the problem here: The orders. The ISD is sent to protect and allthough it has a "don't leave" setting in the orders, I think it jumps once you kill the last enemy (sort of like the "wait for craft" - once you kill all the enemy craft, the cap ship will jump). Seeing how many people said the ISD got angry at them, I guess the solution is to fire at the ISD before you kill the Mon Cal Cruiser - either that or get Pol to finally use the right orders. :P

5: CAPITAL SHIP ORDERS FOR CAPITAL SHIPS

I wont be relying this mission, sorry, but ive spent nearly ten hours doing just two missions, it wont be happening again. Sort it out, release an XvT version, i dont care, BUT SORT IT OUT

See last part of the last sentence for #4. :P

Post by **Vortagh** » Thu Apr 21, 2005 9:57 am

Two other things that would help:

1.) Stop making the OS missions at 3 AM, the night before they are released. Might help avoiding bugs due to stress and sleepyness.

2.) Let the guy who's in charge of mission testing test them.

:P

Post by **Fel** » Thu Apr 21, 2005 10:44 am

drazhar wrote:ERS-71 is completly borked.

1: Mission One, no shields on the TIE's (dont give crap about challenges, stick to policy, Imperial Policy: TIE's get shields)

2: MIssion One: For me the TIE Bombers didnt fire any warheads

3: Mission Two: ISD Doesnt fire. This is a bug in the game. Make missions without ISD's or find a fully working patch. Dont provide missions that have ISD's that are supposed to fire, but dont

4: Mission Two: After destroying the CRS the ISD jumped to HS. The mission goals said that they were completed, but when i got to the debriefing screen it said i had failed. Tried this three times, and thats what happened.

5: CAPITAL SHIP ORDERS FOR CAPITAL SHIPS

I wont be reflying this mission, sorry, but ive spent nearly ten hours doing just two missions, it wont be happening again. Sort it out, release an XvT version, i dont care, BUT SORT IT OUT

1) We had a lot of issues with adding shields to T/F -- crashed the game every time. I don't actually know why.

2) They fired fine when I tested the mission.

3) I have discovered what's happened here. I have the DOS version of TIE. I should have gotten a picture (with a camera or something) of my screen. The Chimaera trashed the DREADs without problem. I didn't actually know when I was working on it that this was a big problem in TIE95.

4) Hmmm, I never had this problem either.

5) I didn't notice it when I was flying the first time but the only ship that misbehaved was the CRS, and it wasn't a problem so long as I stayed far enough away that it didn't ram me. This I found on my flythrough yesterday; when I tested it originally it acquired the Chimaera as its target so it looked to me like all Capships were well-behaved.

Point with no number) Would XWA work for everyone? We can import via AlliED that way and fix it up there...

Vort's points:

1) We're getting better: This time they were made by midnight and tested at 3 AM.

I'm going to avoid the catch-22 of making 3 missions and testing a 4-mission battle all in one day. This time I was a little stuck because I couldn't do anything until I got home from uni, and that was Saturday. That said, I did badger Pol every day last week...

2) Or volunteers.

Post by **Jagged Fel** » Thu Apr 21, 2005 12:14 pm

Here's another point I've got a problem with in 71-2 (I know we're not using ImpSquads, but everyone else is complaining here...) besides the fact the ISD's don't fire, and the patch makes about 4 of the guns work, sort of, that doesn't stop the DREADs from ramming the Chimaera, and sometimes the Strike Cruiser joins in too. So three cap ships are down by suicide, leaving the MonCal chasing you around, and now you have to watch all stray fire since the Chimmy is at 2% hull.

Zwibble · Post by **Zwibble** » Thu Apr 21, 2005 12:56 pm

Fel wrote:We had a lot of issues with adding shields to T/F -- crashed the game every time. I don't actually know why.

I just added shields and started the game up 5 times, each without a hitch. Did this happen for Pol as well? Does he have TIE95 or TIECD?

drazhar wrote:2: MIssion One: For me the TIE Bombers didnt fire any warheads

Are you sure they didn't fire, Draz? They're set to, and they have every time I have flown the mission. They usually don't manage to get much damage done before they're destroyed, but they do fire the torps.

drazhar wrote:3: Mission Two: ISD Doesnt fire. This is a bug in the game. Make missions without ISD's or find a fully working patch. Dont provide missions that have ISD's that are supposed to fire, but dont

I actually like this bug, since it makes getting higher scores easier, but I can certainly understand how it can be a pain. I'm testing the patch now.

drazhar wrote:4: Mission Two: After destroying the CRS the ISD jumped to HS. The mission goals said that they were completed, but when i got to the debriefing screen it said i had failed. Tried this three times, and thats what happened.

I'm trying to test this problem but I can't, because all of the capital ships trying to move like fighters keep smashing into each other, and the Chimmy invariably gets destroyed. After the 10th try, I've said forget it -- the orders need to be modified before I can see what the problem is here. I should be able to get that sorted out by the end of the day.

Vortagh wrote:Let the guy who's in charge of mission testing test them.

It seems to me that the version most people have of TIE is TIE95. Therefore, testing missions with this platform is probably a better idea than testing it with TIE CD. Even better would of course be to test them with all versions -- unless nobody uses the DOS one anymore. Vort and I have it here and a computer capable of running it, but it's painful to fly and so we use TIE95 instead. Does anyone know of anyone besides Fel who uses TIECD?

Fel wrote:Or volunteers.

I volunteer. As a matter of fact, I am working right now on getting the missions flyable. I'll try to hook up with Fel asap to get them approved and uploaded.

AD Polanski · Post by **AD Polanski** » Thu Apr 21, 2005 1:27 pm

In TIE Fighter Workshop, there is no listing of orders such as "SS Patrol and attack", just "Patrol and attack". In XvtED or AlliED, of course I'd set the matching SS orders - so if you are all complaining about the cap's orders, what would you have chosen? :

:

AD Polanski · Post by **AD Polanski** » Thu Apr 21, 2005 1:30 pm

Btw, sending any bug reports to me for the OS missions might not be such a bad idea too eh?

(oh, and post on the Tactical Forum, that's what they are for).

Zwibble · Post by **Zwibble** » Thu Apr 21, 2005 1:42 pm

FA Polanski wrote:In TIE Fighter Workshop, there is no listing of orders such as "SS Patrol and attack", just "Patrol and attack". In XvtED or AlliED, of course I'd set the matching SS orders - so if you are all complaining about the cap's orders, what would you have chosen? ::

"Patrol and Attack." They were set to simply "Attack," which was the problem.