Jump to content

Nightowl

Frozen-Inactivity
  • Content Count

    8
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Nightowl

  • Birthday 08/31/1976

Profile Information

  • Gender
    Male
  • Location
    North Las Vegas

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No
  1. I see. I am using the latest build of both RC and FSUIPC. I do use Active Sky Evolution but I am using FS9 so Im not sure if any of the info above applies relating to weather applies. I have added several missing callsigns by recordind bits and pieces of each controllers WAV. files but it is a very tedious process. The stock ATC and edit voicepack definetly have RC beat on that one. One thing that also irritates me is when there are AI aircraft waiting to take off on both sides of the runway. It seems to allow takeoff from alternating sides of the runway untill I get up to the hold short bar and then it allows all the aircraft from the other side to takeoff before clearing me onto the runway. Even if I have been sitting there waiting and another one taxis up as the last ac is taking off it lets that one go before me also. Is that a glitch? But I will check for the latest version of Makerwys. Thanks
  2. Why am I being instructed to change my transponder code so many times every flight? I had a flight that was barely 800 miles long and was instructed to change it 7 times. Twice while climbing out. It probably would have been more if I hadnt turned it off and finshed the flight in silence. And thats after being instructed to taxi to the farest possible runway for takeoff even though AI aircraft were taking off on it and the closest runway to me. And then there are all the missing callsigns without any apparent update coming, no "heavy" for any AI, being vectored into head on traffic on the runway, planes crossing in front of me while rolling out after landing, it not seeing you crossing waypionts and then it sayin YOU had navigation issues, warning me about traffic 14 miles away but saying nothing about the plane crossing a mile in front of me at the same altitude, its really starting to make me regret buying this. Im certnaly not expecting perfect but for something I paid money for I would at least expect it to be better in all respects than the stock ATC. Just my opinion and I think we still have a right to that in the USA.
  3. Hi all. So I was flying the PSS 757 and while on approach I received an error message saying the computer was out of available memory and FS will now shut down. I have never seen this message before. Bringing up the task manager it showed FS using just shy of 2Gb of RAM. It normally uses between 1/2 to 3/4 of a Gb. Anyone know whats going on here? I am running Win XP SP3, Intel P4 @ 3GHz, 3 GB of RAM, Nvidea GE Force 6200 with 256Mb of RAM and the FS9 Update. I purchased the 757 3 months ago so I assume it has all the updates. Any help would be appreciated. Thanks
  4. I have inserted that line as instructed and will let you know what the results are. Thanks
  5. Well I had another crash, this time with a different sector. However I had saved the flight about a minute before instructed to contact center and it crashed. I reloaded the flight and started the debug but could not replicate the crash. Instructed to contact Albuquerque center and tuned in without a problem the second time around. But I did notice something that may not be anything but I noticed that the enroute center frequency I am instructed to contact and get a crash is the same frequency as the wx briefing frequency at the departure airport. When it crashed on Clevland center the freq was 132.4. My departure airport was KLAS and the ATIS freq was also 132.4. This time my departure airport, KCLE, had a ATIS freq of 127.85. The Albuquerque Center freq it was tuning to when it crashed was also 127.85. Could these be related?
  6. Im sorry I should have posted that in the original post. I am running the FS9.1 update. I also am running RC V 4.3.3845 and makerunwys 4.6.7.4. FSUIPC is 3.9.9.9.
  7. Hi all. So I am nearing the end of a long flight from LAS to EWR at FL370. The controller instructs me to contact Cleveland Center on 132.4. I acknowledge the controller and as soon as the radio changes the sim goes to a black screen and the encounterd a problem box appears. The culprit: atc.dll. It has happened on 3 seperate occasions now, only with this sector. Anyone know what is happening? It occurs with different aircraft. Thnks
×
×
  • Create New...