Jump to content

ehasanov

Members
  • Posts

    131
  • Joined

  • Last visited

Posts posted by ehasanov

  1. Hi

    I have a question regarding fs9 version of MAF .

    I installed all the updates and It works ok, but I notice strange texture in front of rwy25C.

    Could You please check?

    Same observation from another fs9 simmer.

    Image attached. Is this normal to see that grey texture in front of 25C

    Thanks

    post-449-0-90507000-1324325661_thumb.jpg

    post-449-0-03060400-1324325680_thumb.jpg

    Edin

  2. Hi

    I have boxed version of Mega Airport Frankfurt X v1.01 for Fs9.

    I think that update V2.0 was present before, but know when I logged to updates I see only version 2.01 and 2.02.

    Does it mean that I don't need version V2.0 or..?

    Could You please clarify this.

    Another question.

    I notice that after installation of update 2.02 I have got EDDF2008_LC directory which did not exist before last update.

    In that directory I have only one file A402-113hes_5.bgl. Should I activate in fs9 LC dir or not?

    I assume that previous updates checked for other scenery like scenery germany 4 and because of that did not create LC folder.

    Can somebody explain.

    Thanks

    Edin

  3. Hi

    I installed v1.03 and fps are much better.

    But I have problems with texture shimmering.

    I tried to convert textures with imagetool dxt3 with mips, but in that case I don't have a shimmering, but I have significant stuttering.

    Is it possible to convert only some most significant texture files to get rid off shimmering?

    And is it possible to download already converted textures from aerosoft.

    Thanks

    Edin

  4. Hi

    Any chance for similar patch for FS2004 version ;) ?

    Thanks

    Edin

    To give user with slower PC a chance to increase the performance of Antalya X, the developer has provide a small fix:

    You must have installed Version 1.01 (not 1.00) before you implement the fix! Make a backup of the file LTAI_objekt_place.BGL.

    Unpack the ZIP file you find here in the German Post into the <FSX>\Aerosoft\Antalya X\Scenery Subdirectory.

    Now you have 3 steps to optimize the performance by renameing the following file from *.BGL to *.OFF to disable this densitiy level:

    Start with LTAI_objekt_place_Dense.BGL, then LTAI_objekt_place_Medium.BGL and if that is still to slow also LTAI_objekt_place_Low.BGL.

    The file LTAI_objekt_place.BGL includes the mimimum objects you need, don't switch this off. Normally the rename of the Dense file should give you enough aditational frames to run the scenery.

  5. Edin,

    Have you tried loading your flight with a default aircraft then selecting your payware aircraft?

    .

    .

    .

    Chris

    Hi Chris.

    No I didn't try with selecting default a/c, and after loading scenery, switch to PMDG.

    But, at the moment I will not test it because I'm 99% sure that fault will re-appear. In my opinion selecting default a/c will not cure the problem.

    There is something else, but I cannot realize what.

    Thanks anyway.

    Edin

  6. Hi

    Just to add. I'm familiar with all the processes included in finding OOM and similar problems and I didn't find the reason of this error.

    I tried everything, no success.

    No memory leak, but error appears (i tested with payware MD11 nad B747 from PMDG).

    And the main question is why this error does not appear If I fly different route?

    If I fly from EBBR to approximate position of CTD 20nm from BUB VOR nothing happens (and I'm in holding for hours).

    So I gave up with testing and deactivate EBBR at the moment.

    There is a thread: http://www.forum.aerosoft.com/index.php?showtopic=32949

    Edin

  7. Hello Edin,

    Just search for the filenames that are associated with the airport and move them to a backup folder.

    If however the bgls have objects connected to both airports then you may not be able to remove them.

    Hi Shaun.

    Thanks for help.

    I made it ;)

    I rename all files beginning with rodeos*.

    Thanks again

    Edin

  8. When you disable EBBR you have a primitive scenery, which did not need any memory, so no CTD is normal in this case and says nothing.

    Hi , another question.

    Again with EBBR active, CTD around 30nm inbound BUB, heading 300DEG.

    Why crashed because I monitored mem usage and it was around normal values for PMDG B747 (900000K).

    g3d.dll!!

    Then I tried to TO from EBBR and fly to approximate position with same distance and heading from BUB and no CTD this time.

    Strange?!

    Thanks

×
×
  • 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