Messages

1

Bugs / Re: Problem with 0.5 routes

« on: May 31, 2009, 10:38:15 am »

I noticed (while playing in world 506,) that there seems to be a problem with the game in the area of 0.5 routes:

- First, I noticed the game showed me the ^ carat symbol meaning "no one-way flights" for planes that had only one 0.5 route on them at the time.
- I was, however, able to make further 0.5 routes with those planes.
- Furthermore, the game, when I tested it to see if it would, allowed me to make a third 0.5 flight on an aircraft which would logically be unable to do this. (it happened to be plane id #8380) Of course, I then closed the route.

So there are several reports on this bug, and no news?

Did I miss something? It worked fine when I last played... of course, that was in World 3.

2

Bugs / Re: Typos - centralized thread

« on: May 31, 2009, 10:36:06 am »

Country name:
Viet Nam: Incorrect
It should be Vietnam not Viet Nam

Actually...it is correct both ways

Not in English, it's not.

Unless we start seeing "Espana" and "Deutschland" in the game.

BTW, I aggravates me to no end that airports aren't consistently listed as city served first, then name.  While the following are listed as expected:
- (YYZ) Toronto-Pearson
- (YUL) Montreal-...Trudeau
- (CLT) Charlotte-Douglas

... the following have (that I can think off hand), quite frankly, crappy listings in light of the fact that we have to select it from a pull-down menu:
- (SNA) John Wayne Airport - Should be listed either "Santa Ana-John Wayne" or "Orange County-John Wayne"
- (BWI) Glen Burnie - Should be "Baltimore/Washington"... I have no idea why it's listed as "Glen Burnie" but the airport's full name is "Baltimore/Washington-Thurgood Marshall Airport".  Who the hell is Glen Burnie?
- (PVD) Theodore Francis Green State - A big "WTF?" here.  We just know it as "Providence"
- (STL) Lambert-St. Louis - Should be "St. Louis-Lambert"
- (SJC) Normal Y Mineta-San Jose - Should be "San Jose-Mineta International"
- (OAK) Metropolitan Oakland Int'l - Just call it "Oakland"
- (MSY) Louis Armstrong-New Orleans - Flip it around.
- (CMH) Port Columbus - Just call it "Columbus"
- (BDL) Windsor Locks/Hartford - Yes, it's in Windsor Locks, but it should be listed as "Hartford-Bradley"
- (ANC) Ted Stevens - Should be listed as "Anchorage-Ted Stevens"
- (AUS)
- And the big one... why is ATL listed as "Hartsfield-Atlanta" and not "Atlanta" or "Atlanta-Hartsfield"?

And if the named airport should be the listing, then may I suggest the following edits:
- LHR - Change to "Heathrow"
- JFK - Change to "John F. Kennedy Airport"
- LGA - Change to "LaGuardia Airport"
- DCA - Change to "Ronald Reagan National Airport"
- CDG - change to "Roissy"
- ORD - Change to "O'Hare Int'l Airport"
.... just to make it a little more hard.

I'm sure there are more.  I imagine most of the issue above are because of local references... and to those locals, I say "Eff you, locals! The rest of the country doesn't care who the airport is named after!"

I feel better now.

3

Bugs / Re: multi-city trip bug

« on: May 16, 2009, 06:06:01 am »

Dammit... alright, forget my example.  Here's a real life one:

On a 767-200ER (GE CF6-80C2B7F), it's flying:
- HND-KUL, 0.5
- HND-LAX, 0.5

... and it has ~3 hours left (and a 460 speed rating, 1.16 turn).  So presumably I should be able to fly LAX-SAN with a 0.5 freq, even with the turn.  But I just tried to create that route and the aircraft doesn't show.

(FYI - This is in PW 577, aircraft no. 122)

4

Bugs / Re: multi-city trip bug

« on: May 15, 2009, 06:01:25 am »

The problem is, you already have that plane doing two 0.5s out of SFO - one to PDX and one to LAX (it doesn't matter than you launched it from LAX, it is still a 0.5 in/out of SFO).  It's a logic thing: the plane starts in SAN, flies to LAX, then flies to SFO, then to PDX...it now needs to go somewhere from there - it cannot just teleport back to SFO to launch another route.

If neither LAX or SAN are bases of yours then your best bet is probably to launch a short-sector 1-frequency out of LAX or SFO, or have it do either LAX-SAN or SFO-PDX as a 1-frequency to get better utilisation.

Thanks, I actually had my hypothetical example incorrect... I've edited to reflect a 1.0 freq LAX-SFO, so I still have to 0.5 freqs on that one aircraft.  I still won't be able to place a 3rd 0.5 freq (and the 2nd 0.5 from SFO) unless there's enough hours left for a complete 1.0.

5

Bugs / Re: multi-city trip bug

« on: May 14, 2009, 09:16:10 am »

Same problem in PW 577.... only (2) 0.5 freqs are allowed per aircraft even when routing through multiple hubs.  This happens IF the available hours left amounts only to 0.5.  If there are enough hours left to constitute at least 1.0, then the aircraft is made available for 0.5 freq (but with a "^" mark).

Example... Two aircraft have the following routings (with LAX and SFO as hubs):
- LAX-SAN 0.5
- LAX-SFO 1.0
- SFO-PDX 0.5
- plus other routes

I'd like to create a route SFO-SLC, so I should still be able to make one more 0.5 segment.  Let's assume SFO-SLC takes 1.4 hours... Aircraft A with 2 hours left will NOT show as available, but Aircraft B with 4 hours will be made available, with a 0.5 listed.

(As a result, in my game I have a lot of long-distance planes with 6+ hours left, because I can't utilize them on short domestic routes).

I hope that made sense.

EDIT: Fixed my example.