• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

Solution for 'mmmm' and poor performance after installing

Scheduled Pinned Locked Moved Real Taxiways
3 Posts 3 Posters 1.1k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toby23T Offline
    toby23T Offline
    toby23
    wrote on last edited by toby23
    #1

    -- This is advice for anyone suffering poor performance or crashes since installing either of these products AND THE OPTIONAL TEXTURES into the latest version of MSFS 2020 --


    BACKGROUND

    I installed both EU and US Real Taxiways products AND THE OPTIONAL TEXTURES (for the black back on sign boxes, the taxiway and runway markings) without having any other texture mods installed e.g. REX Real Global Airport Textures and this happened:

    1. The signs were not displayed correctly e.g. 'MMMM' and the correct textures were not used.
    2. The back of the sign boxes was still yellow.
    3. My FPS was cut almost in half (at KSEA) from 48 to 25 fps!
    4. Good news, the optional taxiway and runway markings displayed correctly!

    ISSUE

    There is a problem with SU9 and the optional sign textures.

    There is a partial solution posted here BUT what they haven't mentioned is that you have to delete the bksq-optional-textures\scenery folder after overwriting the original textures or you could still have issues.

    This scenery folder contains the textures that are causing the conflict in the sim and, when I tested this, keeping the textures in this folder made my fps to drop from 48 to 25fps.

    Remember that whenever Asobo release an update for the sim, you will need to overwrite the original textures with Black Square's textures again - until Just Flight/ Black Square find a solution.


    REX Real Global Airport Textures COMPATIBILITY
    If you want to use REX Real Global Airport Textures for their runways and apron textures, in combination with Black Square's signs, taxiway and runway markings, you can. (See last image below)

    You will need to overwrite the files shown below in \LocalCache\Packages\Community\rex-real-global-airport-textures\MaterialLibs\Base_MaterialLib\Textures with those from the \LocalCache\Packages\Community\bksq-optional-textures\MaterialLibs\bksq_MaterialLib\TEXTURES

    replace.png


    REFERENCE
    Fresh Install (taxiway markings ok but signs not working)
    wrong.png

    Black Square signs correctly installed (without taxi and runway markings)
    right1.png

    Black Square signs correctly installed (with taxi and runway markings)
    12.png

    Black Square signs correctly installed (with taxi and runway markings)
    okk.png

    Black Square signs, taxiway and runway textures AND REX Real Global Airport Textures
    all.png

    Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11

    1 Reply Last reply
    1
  • M Offline
    M Offline
    mysticfm
    wrote on last edited by
    #2

    Since no one else has responded to this, and since this and other threads here briefly led me down a path of despair until I filed a support request, allow me to add to this thread that a fix installer can now be obtained from JustFlight Support which fully addresses this problem for me without the file overwriting that the linked post describes, and hence with presumably no need to delete any files from bksq-optional-textures as is described above (based upon the fact that I’m not seeing a significant effect upon my frame rates after applying their fix).

    1 Reply Last reply
    1
  • Nicotine70N Offline
    Nicotine70N Offline
    Nicotine70
    wrote on last edited by Nicotine70
    #3

    make me think I did the editing (replacing) texture mentionned in the workaround with the fs-base folder, in order to remove the MMMM and get black back sign, and forgot to actualise the layout.json I don't know if having inconsistency in size file or number may impact performance, but I guess it's worth it doing it, perhaps this should be added to those steps... (maybe this have 0 impact and I may be wrong, if having *.bak file listed in the json could lead to issue, btw kept a save of the initial layout.json)

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users