Jump to content

SimPilot23523

Frozen-Inactivity
  • Content Count

    17
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male
  • Location
    Perth

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No
  1. i generally advise people not to do this. for reasons why check outhttp://blogs.msdn.com/b/ptaylor/archive/2007/06/15/fsx-and-win32-process-address-space.aspxfor one thing, its not a free lunch. giving more memory to User Apps detriments memory that would be given to the System such as file caching.upgrading to say windows 7 64 bit is the safest way to access more than 2GB.happy simming
  2. perhaps but it depends on what games you play and the capabilities of your video card.though FSX is DirectX 10, more and more recent games are DirectX 11 which is not supported on XP x86/x64.http://en.wikipedia.org/wiki/DirectX#DirectX_11
  3. hi,you are right in that you must reinstall windows - you cannot upgrade from 32 bit (x86) to 64 bit (x64).now because you cant upgrade your OS, you generally have to reinstall everything. though backing up and restoring folders can help to a certain extent, most programs make use of the Windows Registry, AppData and System folders which is complex and dangerous to backup.i find its nicer to just reinstall.
  4. my ATI Eyefinity 3x1 works fine in virtual cockpit mode, but in 2D cockpit panels are missing. i read elsewhere this is a known issue with surround mode
  5. everything seems fine now!PMDG 747-400x/MD11 + Orbx FTX Australia SP3 + Navigraph AIRAC 0906 = OKconsidering there was a font corruption that was fixed with Add/REmove Programs-->Repair PMDG, i think my pmdg corruption was also interfering with navigation somehow.simming here i come!
  6. thanks dan, yes that clears things up for me. i turned off AFCAD et al - specifically REX and FTX SP3 since both are an unknown quantity at this stage, reapplied Navigraph AIRAC 0906 and voila - it works! ill try the 747-400x in FSX tonight on the same FP
  7. hmm ok. thanks.anyway after running the registry repair tool (again) and disabling Orbx FTX SP3 Australia enhancements, and re-installing 0906 i was able to AUTOLAND PMDG-11 in FSX at YSSY 16R. YAY!a puzzling thing happened tonight too. notice in the center display YSSY has funny magenta characters after it (upper-right hand corner of display) you can also see it in the altimiter. weird font characters. looks like something got corrupted or it was a one off.ill do another flight tonight for the PMDG 747-400x in FSX tonight to verify! there is a good chance of success now
  8. Hi,I ran the registry repair tool but did not fix it sadly.I loaded YSSY into an airport editor and noted what appears that ILS is off the runway for 16R/34L, i suspect the same thing has happened to YSCB which was odd since i definately have landed on YSCB ILS AUTOLAND on-target earlier in the year. What would have caused that?loading up all the airports into the editor and fixing them manually is not an option sadly. is it possible that applying: MD-11X v1.20.0055 Navigraph AIRAC 0906 ...has somehow conflicted?thanks in advance
  9. yes that was my mistake. in the beginning i said the problem occurred whilst flying the PMDG 737 and PMDG 747. I meant to say "PMDG MD-11 and PMDG 747". I dont own the 737. sorry about that.the above screen shots were in the 747-400x. (which used to work wonderfully)i first encountered the problem flying from YMML to YSCB in the MD-11. but then i tried the PMDG 747 and had the same issue both flying to YSCB and YSSY which was weird as both used to work earlier in the year.since the beginning of the year ive applied pmdg service packs, navigraph updates and installed other commercial scenery enhancers. perhaps one of these has corrupted something accidentally. ill reinstall everything tonight and let you know how i go later in the week.EDIT: ill try that magnetic fix first though thanks
  10. ok ill try that tool tomorrow, in the meantime here are some snap shots i prepared earlier.YSCB to YSSY. Runway is 16R using ILS. Everything worked fine, plane followed path, descended, captured ILS and auto-landed, though though-out the whole flight the magenta line never ligned-up and i was physically off course by about 10 degrees on touch down. odd. worked previously fine.0. Heading to BOREE, approach info displayedplane flew to BOREE fine except magenta line never lined-up. plane was NOT zig-zagging1. ILS intercepted, AUTO-LAND ON!i think im off course though2. YSSY 16R3. Offcourse4. Physically Offcoursethe plane still landed automatically, albeit on the grass. the gardener was not too happy. ;)
  11. hi richard,I too am experiencing issues with:PMDG 737 PMDG 747-400x FSX AIRAC Cycle 0906 from Navigraph Particularly: Plane heading is off by about 10 degrees from purple line (at the 20 or 40 scale) Plane follows 'approach path' to YSCB or YSSY ILS but it is off course physically by approximately 10 degrees from the runway. i end up landing on the grass! YSSY runways were 16L and 16R for 747 and 737 attempts respectively it does not seem to matter whether the FP was created in FlightSim Commander (like i normally do, also updated to the latest 0906) or if i create it inflight using the FMC Everything prior to Cycle 0906 from Navigraph worked fine. I am going to try an older version tonight. I posted on the navigraph forums where http://forum.navigraph.com/forum/default.a...osts&t=1196 similar issues have been reported. they asked that i post here too just in case.My System: FSX on Vista 64 bitthanks in advance guys
×
×
  • Create New...