Hard Light Productions Forums
Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: sparr on July 19, 2008, 05:09:05 pm
-
I have replayed this mission over a dozen times now. The very first time I got a scan of the Eva easily then died before my subspace drive came back up. Every time after that I can barely, if at all, find the "sweet spot" to scan the Eva, which is now moving at 85+m/s the entire time and virtually impossible to keep up with. Any advice?
-
Why is the Eva moving at 85 m/s?
-
Yeh, it should slow down after succesfully jumping in.
As a side note, hitting Alt-S (I think it was Alt) can be useful, since it disables the subsystem targeting. Which means that you can't be on the wrong side of the Eva, when trying to scan it.
-
You scan the Nav, IIRC. That's under the head. Stay a little ways away from the node and you'll be fine. I figured that out after the Eva jumped out on me the time before.
-
I still prefer the no-subsystems-targeted way, since that way the game isn't too nitpicking about where you are pointing at when scanning.
-
:bump:
Don't beam me now! :nervous:
I always run into a lot of problems when I play this mission. The Eva jumps in so fast that parking at the jump node is the stupidest thing to do.
What I usually do is to fly 4000 metres away from the jump node. When the Eva jumps in and slows down, it should have slowed down far enough about 4000 meters away from the jump node for you to get a nice long scan of it.
-
If you're near the node and it blows by you, you can always just, y'know, chase it. :p
-
It shoots out of the node at over 400 m/s. How can I chase it and expect myself to have sufficient time to scan it before it jumps out? :wtf:
-
As it has been said. Don't hang around isnide the node. Be at a proper distance from it. Disable subsystem targeting.
-
From what I remember, the thing jumps out of the area a good minute or two after it enters through the node, which should be more than enough time for you to catch up to it enough to scan it. Like Lobo said, if you disable subsystem targeting (which didn't automatically happen in FS1 to begin with), you should only have to be some distance off the ass-end of the ship in order to trigger the scan. I think I'd usually wind up completing some portion of the scan as the Eva jumped in, having the scan pause as it pulled away from me, and then finishing the rest once I got close enough to it.
-
Disable subsystem targeting, eh? Good tip; I shall bind that key when I reach that mission. :D
By the way, how do you scan the cargo surrounded by the sentries and fighters? Every time I play Playing Judas, I'm reduced to using ~ + K. :(
-
Just stay in that area between the sentry guns. I don't know why people would go to the node, when the sentries in front of it can detect you. I dunno, personally I've never had a problem scanning the Eva on Playing Judas. But I've never played it on the FSPort so maybe it's slightly different even though it shouldn't be. The problem is always staying alive once idiot Command tells you to fly into the fighter bay.
-
I hung away from the node the second time I played it, and the Eva was perfectly scannable :nod:
-
By the way, how do you scan the cargo surrounded by the sentries and fighters? Every time I play Playing Judas, I'm reduced to using ~ + K. :(
The idea of that mission, for me anyway is to enter that area.
Okay, the mission set-up is basically this. There's two sentries at the node. There's two sentries at a warpout point a way from the node. And between those sentries is basically a "road" if you will that the ships all warp into and follow. Also the cargo is on that road as well. The enemy fighters, don't really enter this area. They fly around it, sometimes they get close enough to detect you but in general, that area is safe. So all you have to really do, is get into that area, undetected and stay there. Get in, scan the freighters, scan the cargo, etcetera and so on. But you only have a small window to scan each ship, if you take too long they'll get too close to the warp-out sentries. Other than that you should be fine.
-
If my memory hasn't completely failed me, flying almost directly toward the general region in front of the node (though stopping some distance before actually entering the node space) always worked just fine for me, at least on Easy difficulty. Command would give me the occasional warning about one of the sentries getting a bit too close, but moving in the opposite direction for a few seconds solved that quickly enough; I don't think I ever had to bother with observing their flight paths. I'd sometimes receive a message about getting too close to the node sentries, but backing off a bit solved that just fine. From that position, I was able to nab each of the ships as they jumped in, and I usually managed to scan the cargo even before the freighters got around to docking with it. My only caveat is that parking yourself slightly above/below the plane of the node is advisable, lest you wind up windshield fodder for a Demon or Lucifer. :p
-
I see. I never looked at it as a road. I was thinking it was more of a storage depot set up beside a jump node.
-
I see. I never looked at it as a road. I was thinking it was more of a storage depot set up beside a jump node.
Well, whatever word you want to use. Road's kinda a dumb word to use but it illustrates the idea. It's like the "protected area" basically, where the fleet and cargo enters but doesn't really venture outside of. Just get in that area, and you'll be nice and protected too!
-
I've found that the best way to scan the Eva was to sit ahead of the node in the "safe zone", while facing away from the node. When the Eva jumps in, I hit the burners and let it pass over top of me. As it does, I use the "target nearest subsystem" feature and start scanning. Doing this ensures that I'm closer to it already when it reaches a low enough speed for me to sustain a scan. As for the Lucifer, for some reason its always non-collide just after it jumps in, so I kinda pass through it... coulda been a bug though.
-
You could always just skip this mission. S'not like you'll miss out on anything...
-
You miss out on Command being an idiot and telling you to fly into the Lucifer for some god forsaken reason.
Oh yeah, and what if it works and I get to land? I'm not getting out of the Dragon. The Shivans will kill me once I do.
-
Oh yeah, and what if it works and I get to land? I'm not getting out of the Dragon. The Shivans will kill me once I do.
"Have no fear pilot. You're Alpha 1! You won't die, just because. Now land in there now or be court martialled!"
-
You miss out on Command being an idiot and telling you to fly into the Lucifer for some god forsaken reason.
Oh yeah, and what if it works and I get to land? I'm not getting out of the Dragon. The Shivans will kill me once I do.
You could always upload a computer virus into their main computer!
Or fire your weapons into their exposed primary reactor which happens to be visible from the launch bay!
Or could you get out of your fighter, realize that you're a shivan too, then get back into your ship, head back to base and put two rounds into Command's chest!
-
Or we could rip off the War of the Worlds, have Alpha 1 land on the fighterbay, make him exit his Dragon and expose the "crew" of the Lucifer to some basic human illness that the Shivans do not have immunity for yet.
-
Gonorrhea?
-
Nope. Just a slight cough. :D
-
Or could you get out of your fighter, realize that you're a shivan too, then get back into your ship, head back to base and put two rounds into Command's chest!
And get shot in the belly by an ugly flight deck technician, just a few episodes later? no way! :P
Seriously, I have just finished today plating FSport main campaign and I spent about 2 hours straight trying to figure out how to complete Playing Judas... I had the very same problem with the Eva, sometimes with the 2 lilith-class cruisers too.
My best suggestion is to play it just the way I did it myself:
when the two Lilith-class cruisers jump in, scan no. 1 (I think they're both called Genma), then approach lilith no.2 from behind. You should be able to get a scan by pointing right at the cruiser's engines, if you do not, just fly above the cruiser and get a scan from that position. The important thing is that when the Eva makes her appearance, you are standing exactly above the second Lilith-class cruiser. From that position, then Eva should appear either right above or right beneath you (I can't really remember too well), but the thing is, you should already be in a perfect spot to get a nice scan of it.
*careful* this strategy worked perfectly for me at least 3 times, but there is ONE big issue you should know about: after you scan the Eva, if you followed my instructions correctly, you will most probably be very, very close so either one of the Arjuna Dragon fighters, or to one of the sentries. Just make sure that the moment you complete the scan of the Eva you start targeting fighters and sentries, and get as far as possible from the closest of them.
-
I really don't understand how this mission could be so impossible. I've played it numerous times and never, never have I failed to scan the Eva. Or any other ship, for that matter.
-
I really don't understand how this mission could be so impossible. I've played it numerous times and never, never have I failed to scan the Eva. Or any other ship, for that matter.
Uh, because you're U? :p
-
If you fail to destroy the Shakti in the previous mission, there are four Arjunas instead of three, making the mission substantially harder.
On the other hand, experience helps. The very first time I played through FreeSpace I thought that mission was nearly impossible. (And this was while playing on Easy.) The first few times I played through it, it took me several attempts each time, but now I can usually do it in one go. It probably has something to do with learning where to park your fighter.
-
to be honest, i've always had problems with this "behind enemy lines recon" missions, in all kind of games. There's one ****ed up mission in X-Wing, (can't recall if it was the original classic or X-Wing Alliance, but i think the former), where you get to pilot an A-Wing in the middle of a huge imperial fleet. Thing is, there's no such thing as a stealth A-Wing, so you basically have to fly like you got hell on your heels and get an ID of all crafts in the area... which, by the way, are not mere freighters like in Playing Judas, but are cruisers, Victory Star Destroyers, Imperial Star Destroyers and so on.
There's another similar mission in Starlancer, where you actually pilot an enemy bomber and must get in position behind a huge enemy destroyer to make a surgical strike with your payload. The mission itself is kinda simple but it really takes forever, and after dropping your load you have to get straight back to your carrier, jump into another ship and then take off again to join the dogfight :P
-
to be honest, i've always had problems with this "behind enemy lines recon" missions, in all kind of games.
Try playing the Procryon Insurgency. There's a really doozy in there.
-
Try playing the Procryon Insurgency. There's a really doozy in there.
What's a doozy?
Those missions give me the creeps. They should've been included in the actual FreeSpace 2 campaign.
-
Try playing the Procryon Insurgency. There's a really doozy in there.
What's a doozy?
"something extraordinary"
I'm getting old.
-
to be honest, i've always had problems with this "behind enemy lines recon" missions, in all kind of games. There's one ****ed up mission in X-Wing, (can't recall if it was the original classic or X-Wing Alliance, but i think the former), where you get to pilot an A-Wing in the middle of a huge imperial fleet. Thing is, there's no such thing as a stealth A-Wing, so you basically have to fly like you got hell on your heels and get an ID of all crafts in the area... which, by the way, are not mere freighters like in Playing Judas, but are cruisers, Victory Star Destroyers, Imperial Star Destroyers and so on.
It's in X-Wing Alliance. You just brought back memories! I dumped all my freaking power to my freaking engines in that mission :O
-
/me engages necro.
:necro:
-
Doesn't count, its less than one month.
-
I hate it when people say stuff like that. It's like those times when you say something reasonable and some guy kicks you in your balls and says "Well, TECHNICALLY..."
-
Kind of like losing a debate and then, 2 hours later saying "Yeah, and besides...".
-
O RLY?
CUT
CUT
(http://images2.wikia.nocookie.net/uncyclopedia/images/2/2f/Cowbell2.gif)
-
I don't get it ...
-
The post before the offending post was one month and thirteen days old.
-
The post before the offending post was one month and thirteen days old.
What's the point of posting nothing but a necro beam that's what I don't understand. He may have necroed it but it was less of a waste time reading his post than it was reading yours.
-
Posting a necrobeam and nothing else is as useless as posting a full stop and nothing else, don't do it again, is what I think the moral of the story is.
-
.