23-12-2008, 09:27 PM
I'm having the same exact problem as the people in this thread --
<< http://www.fspassengers.com/forum/showth...p?tid=7540 >>
I'm using XP64, not VISTA (I have NO idea what AERO is) and FSPax was working fine for over a year. I've done everything I can think of
and finally two days ago I just deleted FSPax from my hard drive (including a registry search and delete of all FSPassengers references)
and it still happens -- Drops right off the FS9 menu, too! Can somebody please help me with this -- it just doesn't seem worth flying
anymore with an empty plane.
I changed install drives a month or so ago from E: back to C: but I've done the clean install long since then. I first thought this was
happening because my airline had reached over a billion dollars and my rank was "Super God Pilot" or some such thing, but even
deleting the database and starting from scratch didn't help. After the reinstall I did get a couple of good flights out of FSpax, but then I had
to abort a flight while still on the ground, and then the very next flight this problem started all over again. Could that have something to do
with it?
<< http://www.fspassengers.com/forum/showth...p?tid=7540 >>
I'm using XP64, not VISTA (I have NO idea what AERO is) and FSPax was working fine for over a year. I've done everything I can think of
and finally two days ago I just deleted FSPax from my hard drive (including a registry search and delete of all FSPassengers references)
and it still happens -- Drops right off the FS9 menu, too! Can somebody please help me with this -- it just doesn't seem worth flying
anymore with an empty plane.
I changed install drives a month or so ago from E: back to C: but I've done the clean install long since then. I first thought this was
happening because my airline had reached over a billion dollars and my rank was "Super God Pilot" or some such thing, but even
deleting the database and starting from scratch didn't help. After the reinstall I did get a couple of good flights out of FSpax, but then I had
to abort a flight while still on the ground, and then the very next flight this problem started all over again. Could that have something to do
with it?