Distance between NAV points

Sonntag

Spaceman
After I've played Wing 1-5, I am a bit confused about the distances between Nav points of the games. While Wing 1,2 and privateer measure the distance from one Nav Point to be from 50000-100000 klicks (that means it takes approx 5-10 mins to get there, which is reasonable), the distances are completely unrealistic in Wing3 and onwards! In WC 3, you are approx 1.000.000 klicks away from the nearest Nav point, which means you could need several hours to get there.

Does anybody have an explanation for this?
 
Originally posted by Napoleon
In the books the characters talk about putting auto pilot on then going to sleep for a number of hours

Really? And what if a Kilrathi Fighter says "Hello" while you sleep? THis does not make any sense, as I cannot see, why the Kilrathi should wait several hours at the next Nav Point, just so that you can kill them. I think it makes much more sense in WC1
 
Err, Hunter *joked* about going to sleep in Freedom Flight -- which mortified Knight <G>

(Grunt actually did go to sleep during a long patrol in WCA -- but he made sure Blair was watching his back first...)

The 'real' reason the distances changed is because people who are too stupid to read the manual end up complaining in WC1/2 when they have to wait all that time to get to a nav point... by making it virtually impossible not to autopilot, it forces them to figure it out <G>
 
Originally posted by Bandit LOAF
The 'real' reason the distances changed is because people who are too stupid to read the manual end up complaining in WC1/2 when they have to wait all that time to get to a nav point... by making it virtually impossible not to autopilot, it forces them to figure it out <G>

BTW, was there a bug in WC3 that the game crashes if you fly manually to the next WP? I've never tried it, but the manual states something about this issue.

From a "realistic" point of view, I'd imagine that the WC1/2 dates are more realistic, right? A distress call in WC3/5 would be useless if it took several hours to reach the ship.
 
I liked the increased distance between nav points in WCIII thru WCP/SO. It gave time to go get a refill, drain the tank, feed the cat, answer the phone, turn over the steak on the BBQ, and some other things with the wife I wont mention here! But the extended nav point distance should be any kind of factor in completing a mission or be a problem. Just think, it could be like FS where there are NO nav points, you get thrown into battle imediately with no time to adjust your power settings or even hit a few keys to send comms to your wing!

RFB
 
In the case of a rescue mission of some sort (as opposed to a patrol, where visible recon matters), a fighter can close its scoops and spend half the trip accelerated to incredibly high speeds...
 
I didnt autopilot one time when the distance between the nav points was well over 100,000km. Took some time even at full throttle (600kps black vamp) but that simulated real space flight, I mean the time it took to get from point A to point B without burning up afterburner fuel gave the trip a realistic feel. I for one am glad they did it that way, so you can prep for the next encounter at the next nav point. Unlike FS you get thrown into the battle zone without any chance of preparing your wing or ship settings. The defend carrier missions, although you get catapult right into a combat zone imediately, you could still do the quick command (ALT-B) and your wing went to work while you set your ship settings up as you head for the first boggie. FS did not give much chance to prep your settings. With all the keystrokes in FS, I began to think the game was more of a keyboard speed challenge than a space sim game.

RFB
 
Originally posted by Bandit LOAF
The 'real' reason the distances changed is because people who are too stupid to read the manual end up complaining in WC1/2 when they have to wait all that time to get to a nav point...
Hey, I afterburned to navpoints on my first WC run. :eek:

As for sleeping during autopilot, there'd be proximity alerts and what not to warn the pilot wouldn't there? Navpoint are really only for the ease of the mission designer, and all sorts of hazards occur between navpoints - asteriods, mines, as well as fighters.
 
The first time i played WC3 and i had to escort a transport i didnt know i had to actually get close to it so i ended up flying to all the jump points, killing the cats, coming back and finding out about it. The good news was the nav points were all cleared out:)
 
Eh eh... not a bad tactic Supdon... of course, not very realistic, but what the hell, is it *realistic* that friendly capships don't fire in WC I? Mmmmhhh? ;)
 
Problem was i got really bored on the long flight times and used up all of my afterburner fuel and it still took like an hour.
 
Read my previous post smart alec:) I didnt know about getting within range of the transports or else you CANT autopilot.
 
Mmmmhhh... doing the whole mission on AUTOPILOT... One mission for ONE hour...

I wonder who really is the "smart alec" here... :p
 
It was the first time i ever had to do that with a transport. Never happened in WC1/2/P so i think im granted a little leeway here.
 
Originally posted by Wedge009
Originally posted by Bandit LOAF
The 'real' reason the distances changed is because people who are too stupid to read the manual end up complaining in WC1/2 when they have to wait all that time to get to a nav point...
Hey, I afterburned to navpoints on my first WC run. :eek:

BTW, does anybody know what the "TAPE" signal lamp has for a purpose in WC1? This is a light that is situated next to the Autopilot light.
 
That's where the mission recorder button would have been, had the mission recorder been included in the game.
 
Originally posted by Bandit LOAF
That's where the mission recorder button would have been, had the mission recorder been included in the game.

Has that ever been planned, and if so, what would its purpose have been.
 
Back
Top