Jump to content
The simFlight Network Forums

JonPatch

Members
  • Posts

    682
  • Joined

  • Last visited

Posts posted by JonPatch

  1. Hi Jerry,

    You can see for yourself the difference the mesh makes, you likely won't notice it in mountainous areas. Place the FSG mesh in it's own scenery folder, and place that at the highest priority in your library (with mesh in FS9 that gives it lower priority). See if you can tell the difference.

    In the cities there may be some little glitches with FSG mesh not lining up with scenery objects as well as the mesh that is supplied.

    Jon

  2. Are you running Version 1.1 of Vancouver+? I believe the version is indicated in the configurator. If not, please upgrade, Francois can provide details on how to do that.

    As Francois says, UT will crash if it's missing certain textures. Before trying to reinsall UT though, what other addons do you have active?

    Jon

  3. Guido, thanks for the kind words. And great work narrowing down the culprit files, thank you!

    Those files are all photoscenery. Without them you won't get realistic detail in those 4 areas: downtown Vancouver, Simon Fraser University, Metrotown and the Tsawwassen terminal area. So indeed, you can still enjoy most of Vancouver+ without impact.

    The most common cause of such an error is that the textures corresponding to those scenery files are missing. Those textures should have been installed into Flight Simulator 9\Scenery\World\Texture and have coded names like 000333102321222Su.bmp and 000333102321233Su.bmp. Check that folder for those files and many like them, there are something like 365 files there, including the corresponding autogen files, with a .agn extension.

    Do tell us a bit about your system as well (operating system, CPU type, video card, RAM, etc.) If you're using Vista there may be an adminstrative restriction preventing proper installation of these files.

    Let us know what you find ...

    Jon

  4. Oops, by "check out" vancouver+ I meant after uninstalling the mesh, try Vancouver+ in the sim. If you still see the issue, we can quit blaming WEL, or at least its prority.

    Abacus support is correct: the higher resolution mesh will have priority. However if the mesh resolution is the same (and I don't know what they provide for this area, Vancouver+ is 19m if your TERRAIN_MAX_VERTEX_LEVEL (“TMVL”) is set to 21 as you've done), the one that is LOWER in the scenery priority list overrides, unlike normal scenery. (This is true for FS9 only).

    So here's a question: what resolution is the WEL mesh? What else besides mesh does it provide? Landclass? Aircraft?

    Jon

  5. Thx for trying the suggestion, let us know how it goes. BUT I thought of something: after you've uninstall the mesh, and BEFORE you reinstall, check out Vancouver+.

    And that's useful to hear about your display issue, thanks for the note. It's not planned to update Vancouver+ for FS9.

    You can't fool the display by temporarily changing manually to another resolution?

    Jon

    P.S. Can you post some screenshots of the issue in case we're chasing a red herring?

  6. Thanks for the appreciation. I haven't heard of a compatibilty issue with that product.

    Have you set Terrain_Max_Vertex_Level=21 as suggested on Page 22 of the manual? If not, then try that first.

    If the problem persists, perhaps you can ask the Extreme Mesh folks in which folder their information goes? If it's in the default addon scenery folder perchance, you can temporarily deselect that one in the scenery library and see if that fixes it. Let us know. And perhaps, like FSGenesis mesh, there is an installation option that allows you to select a specific folder, so a reinstallation might help. Their support might be able to answer that as well.

    Let us know how it goes....

    Jon

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.