Jump to content

pocketwatch50

Members
  • Content Count

    127
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

6 Neutral

About pocketwatch50

  • Rank
    Member
  • Birthday 01/03/1948

Profile Information

  • Gender
    Male
  • Location
    New Mexico

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. Offer of a refund. really? maybe on some secret site no one is aware of. Like this whole sordid affair this outfit really shines. I was an early payer and they have all our contact info. if they were sincere in a "refund" everyone should have been notified. I certainly wasn't. Maybe they mentioned it on their website? I never go there and shouldn't have to. Too many apologists for this outfit. This wasn't a crowd funding thing with a known possibility of it never happening. We aren't investors. Shame on this company.
  2. Sorry but I've run out of patience with this outfit. When you collect money up front from customers and tell them no time frame most normal folks consider what is reasonable. I mean, if you go to sites like indie and pay for or back a future item you expect 6 months a year maybe a year and a half. That is what it usually is. Three years and still no estimates =it ain't coming before the second coming of you know who. This outfit should admit they blew it and refund all their customers in full with an apology. And yes I am one of the advance payers for this software.
  3. There are many airports and runways in FSX where the runways are off. You just need to manually fly those.
  4. Thanks for all the advice. I solved the issue. Even though FSX was installed on my new drive the FSX.config file was installed on the system drive. Once located adding the highmem fix solved the issue. When I added the new drive and installed FSX it dumped all the files into the FSXdirectory I created. There was no users directory hidden or not. (The new drive is not the system drive) I then created the users directory myself with all the sub-directories and moved the FSX config from C to the new S drive but FSX didn't use it instead using the one it created on the C drive.
  5. I uninstalled FSX from my main drive and reinstalled on a new Drive I got specifically for that purpose. The install didn't go well and many of the files and directories were not installed where they should have gone. However I was able to move things around and FSX works without errors now and I got all the add-ons working too. So my problem is after loading up FSX and starting the program, at some point (usually pretty quickly) the video starts to go south and quickly the screen goes to black and orange and flashes and that's the end. I seem to recall from experience this can be caused by not having the highmemfix=1 notation in the config file. So my problem is where is the config file. When the program was installed there was no users directory and FSX didn't create one. A search of the drive only brings up config files I put there and have renamed to troubleshoot. At this point I've renamed all the FSX.Config files I found (all I placed there myself manually) so the program must have put it someplace. Of course unless it is using one off another drive if that is possible. So my options are 1-reinstall FSX again on my new drive after deleting it or 2- trying Steam or saying the heck with it and switching to P3D which I have but never used. Any suggestions Win 7 alienware aurora R4 I-7 extreme Nvidia GTX 1070
  6. I have the F1 King Air and the Turbo Duke and some others and that's not true. You hit the igniters with the condition levers at cutoff and at about 12% in the KA you put them in low idle and the engines start and run great. As a matter of fact if you start the KA with the condition lever at full you will get an engine fire and destroy your engines.
  7. I've been a long time sufferer of the clickspot issues. Right now all is well with the Duke. I have them with the Flight 1 King air. They are so sporadic finding a solution is a big challenge. Every time I think I've found the cause I'm proved wrong. often times I have no issue for days and then all of a sudden it happens. often times a reload of the aircraft solves the issue. Sometimes it doesn't. That issue is often accompanied by frozen PFDs and MFDs and view problems. Whatever the issue is it's common to at least 3 aircraft. The A2A 172 and the Duke and the King air.
  8. I have the same issue and also have it with the Flight 1 King air. Every time I think I've figured it out it proves me wrong. There is no rhyme or reason and no one really knows. I can go days with no issues and then all of a sudden it happens again. very erratic and sporadic with both planes. I also had it with the A2A cessna but haven't flown it much lately so I don't know if their fixes fixed it or not. it's something common to the newer high def planes coming out and some computers.
  9. yea, I had the same issue with landing and the plane going crazy. I guess I didn't think crash detection would cause that. I'll reset that. has anyone had problems with clickspots a la Flight 1 King air? I have it bad.
  10. I've found this is very common.Many airports are off varying amounts. Some very minor and some by quite a bit. I know of no fix for this.
×
×
  • Create New...