Jump to content

cbd80

Members
  • Posts

    1391
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by cbd80

  1. The title says it all. The buildings seems too high off the ground.

    How to fix,

    Thanks,

    Brad

    Hi. Do you have any 3rd party meshes installed like FS Global? I know with that product it has a specific mesh for Maderia that will conflict and you need to deactivate it (which can be done by renaming the file in the FS Global 'Local' folder).

    Chris

  2. I agree with Matt. Memory is a good thing if you require it. I can use around 8GB of RAM due to the addons I run with FSX.

    But the number of sticks of memory limits my overclock potential. I can't provide enough voltage to keep the memory stable with any higher an overclock than I currently have, not without putting the CPU at risk with high temps anyway.

    Chris

  3. Hi Felix. I worked on the original Airbus X beta (and currently the Extended version).

    It's been a while since I've used Autoland, but if I remember correctly:

    1) Ensure you are 7-10nm from the airport.

    2) Approach from a 45 degree angle and be below the glide slope.

    3) AP1 should be on. Press the LOC button before intercepting the localised.

    4) Once the GS indicator moves down to the centre position press APPR.

    5) Now Press AP2 and it should supply DUAL on the PFD.

    Note that AP2 will not engage with AP1 at the same time unless both the localiser and glide slope are established with the LOC and APPR on.

    I hope that helps.

    Chris

  4. I think it would confuse things as customers may regard the relabelled product as a new or updated version.

    Personally, I would use your new naming convention only on new products going forwards. What has passed has passed.

    Chris

  5. Hello Florian. Do you have 'User Account Control' in Win7 disabled? If not this can cause issues with files being installed correctly. Additionally did you right-click the installer and select 'Run as Administrator'?

    Trying the above may help to resolve your issues.

    Chris

  6. Henk. No, a faster CPU will not address the issues. You say you understand it's all about the VAS, but clearly not as unfortunately the CPU would not address this.

    Simply put, with a 32bit program like FSX you'll have a maximum of around 4GB VAS. You can't make it any more.

    FSX, your addon plans, your photoscenery, clouds etc. will all eat into this 4GB VAS limit. Once it gets consumed you get an OOM.

    So, as you've found removing the photoscenery prevents the OOM as you are staying with the VAS limit.

    With today's heavy addons you sometimes have to compromise. Reducing your slider settings can also help.

    Chris

  7. I only have the boxed version of this. Could well be one is FSX and the other is FS9. I would guess that the larger file is the FSX version. Perhaps download both and have a look at the content before installing.

    Chris

  8. Have you looked in your FSX folder for a uninstall.exe specific to Innsbruck?

    If you get really stuck you could use the crude method of deleting the Approaching Innsbruck entry from the Scenery Library and then deleting the Approaching Innsbruck folder under FSX/Aerosoft (or your equivalent directly). For a scenery product that should get rid of most if not all of the files.

    Chris

  9. As Shaun has said, you need to edit the aircraft.cfg of the aircraft you are flying.

    In the section for your airline you need to add:

    atc_parking_types = GATES

    atc_parking_codes = xyz

    Where xyz is the 3 letter code of the airline. You can find this by using google.

    It corresponds to the gate codes in the AFCAD.

    Chris

  10. Hi. I think that would be difficult to tie in, or rather some work involved as AES would have to be familiar with each addon aircraft and read the LUA variables, assuming they exist.

    It depends on your perspective. Ground crew saying to the captain 'Cleared to taxi' only means the push back truck has been removed to me. Taxi clearance is only given by the ground controller once the pilot has made the call. So engine start does not need to be completed by the time AES finishes.

    Chris

  11. Automation dll errors often occur when you try and access the FSX menu. Some have suggested a fix when using Win7 IIRC. Personally, I've always found the issue when being too eager to access the menu; take it slow yields better results.

    Also, referring to a previous post. Don't confuse system RAM and video RAM. Totally different. Often, with the OS video RAM is shared with the system RAM. This can apparently have an impact. But not that I've seen.

    Chris

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use