Could someone out there take pity and do me a favor?

[Guest]

Archived from groups: alt.games.microsoft.flight-sim (More info?)

Some of y'all may remember my issue with Chicago Midway a while back,
where I'd get booted out of the program when attempting to fly out of
that airport. Someone said the mesh was faulty for that region and it
was causing the program to crash, and there was a similar fault at a
spot somewhere in Italy.

Well, last night I was trying to fly from Portland Oregon to KLAX and
the same thing happened, at about 5,000 feet after taking off. I ran it
three different times, to the same effect.

Was wondering if someone else could try taking off from Portland Int'l
and seeing if their flight ends the same way or if I have some other
issue to deal with. I have a third-party Portland Oregon airport
installed, but this happened with the third party airport, no third
party airport and a new third party airport I later installed, just
because I liked the new one better.

Thx.



John the Frustrated...No airport seems to like me

--


Von Herzen, moge es wieder zu Herzen gehen. --Beethoven

 

[Arthur]

Archived from groups: alt.games.microsoft.flight-sim (More info?)

I took pity and also took off from Portland Int'l to LAX in the default 737.
I flew until I reached cruising altitude of FL220 with no problems at all,
although the ATC did screw up my vectors a bit. I use the default airport
and enhanced scenery and did not have the problem you're experiencing.
Maybe one of the other sim pilots on here will crash at 5,000 and be able to
explain why. Sorry.

Arthur


"The Man Behind The Curtain" <johngrabowski@earthblink.net> wrote in message
news:42BB012F.80800@earthblink.net...
> Some of y'all may remember my issue with Chicago Midway a while back,
> where I'd get booted out of the program when attempting to fly out of that
> airport. Someone said the mesh was faulty for that region and it was
> causing the program to crash, and there was a similar fault at a spot
> somewhere in Italy.
>
> Well, last night I was trying to fly from Portland Oregon to KLAX and the
> same thing happened, at about 5,000 feet after taking off. I ran it three
> different times, to the same effect.
>
> Was wondering if someone else could try taking off from Portland Int'l and
> seeing if their flight ends the same way or if I have some other issue to
> deal with. I have a third-party Portland Oregon airport installed, but
> this happened with the third party airport, no third party airport and a
> new third party airport I later installed, just because I liked the new
> one better.
>
> Thx.
>
>
>
> John the Frustrated...No airport seems to like me
>
> --
>
>
> Von Herzen, moge es wieder zu Herzen gehen. --Beethoven
>

 

[Guest]

Archived from groups: alt.games.microsoft.flight-sim (More info?)

"The Man Behind The Curtain" <johngrabowski@earthblink.net> wrote in
message
>news:42BB012F.80800@earthblink.net...
>> Some of y'all may remember my issue with Chicago Midway a while back,
>> where I'd get booted out of the program when attempting to fly out of that
>> airport. Someone said the mesh was faulty for that region and it was
>> causing the program to crash, and there was a similar fault at a spot
>> somewhere in Italy.
>>
>> Well, last night I was trying to fly from Portland Oregon to KLAX and the
>> same thing happened, at about 5,000 feet after taking off. I ran it three
>> different times, to the same effect.
>>
>> Was wondering if someone else could try taking off from Portland Int'l and
>> seeing if their flight ends the same way or if I have some other issue to
>> deal with. I have a third-party Portland Oregon airport installed, but
>> this happened with the third party airport, no third party airport and a
>> new third party airport I later installed, just because I liked the new
>> one better.
>>
>> Thx.
>>
>>
>>
>> John the Frustrated...No airport seems to like me
John,

If your PC has more than 1 memory stick - try swapping them around.
Maybe you have a bad memory cell in one of them.

Just a thought - it cured some problems I had several years ago.

-=tom=-

 

[Guest]

Archived from groups: alt.games.microsoft.flight-sim (More info?)

ORRRRRRRRR

You might have an Afcad file for the local area. Double check your
scenery/scenery directory for a duplicate Afcad file and locate and delete
the oldest. Or better yet, delete them both and go get a new one.

Duplicate Afcad files are known to cause trouble.

Not4wood
Mark G

"Tom Orle" <xspam.torle@comcast.net> wrote in message
news:0elmb1pci8lf0gqefg1bal4ucb8ar6uofm@4ax.com...
> "The Man Behind The Curtain" <johngrabowski@earthblink.net> wrote in
> message
>>news:42BB012F.80800@earthblink.net...
>>> Some of y'all may remember my issue with Chicago Midway a while back,
>>> where I'd get booted out of the program when attempting to fly out of
>>> that
>>> airport. Someone said the mesh was faulty for that region and it was
>>> causing the program to crash, and there was a similar fault at a spot
>>> somewhere in Italy.
>>>
>>> Well, last night I was trying to fly from Portland Oregon to KLAX and
>>> the
>>> same thing happened, at about 5,000 feet after taking off. I ran it
>>> three
>>> different times, to the same effect.
>>>
>>> Was wondering if someone else could try taking off from Portland Int'l
>>> and
>>> seeing if their flight ends the same way or if I have some other issue
>>> to
>>> deal with. I have a third-party Portland Oregon airport installed, but
>>> this happened with the third party airport, no third party airport and a
>>> new third party airport I later installed, just because I liked the new
>>> one better.
>>>
>>> Thx.
>>>
>>>
>>>
>>> John the Frustrated...No airport seems to like me
> John,
>
> If your PC has more than 1 memory stick - try swapping them around.
> Maybe you have a bad memory cell in one of them.
>
> Just a thought - it cured some problems I had several years ago.
>
> -=tom=-

 

[Guest]

Archived from groups: alt.games.microsoft.flight-sim (More info?)

Not4wood wrote:
> ORRRRRRRRR
>
> You might have an Afcad file for the local area. Double check your
> scenery/scenery directory for a duplicate Afcad file and locate and delete
> the oldest. Or better yet, delete them both and go get a new one.
>
> Duplicate Afcad files are known to cause trouble.


No dup files. I checked.

Also tried removing the one that was there, just for the heck of it.
Same problem.

I wonder if a reinstall of the whole program might work.



John

--


Von Herzen, moge es wieder zu Herzen gehen. --Beethoven