medx421

Yep, purely optional. Referencing the author of FreeMeshX, I just choose to do it to avoid any conflict. I do it the other way around though as the coverage boxes of FreeMeshX do not line up with my ORBX/FTX boxes. FTX compatibility: The FTX regions with the USA come with their own mesh and they are also rendered at LOD12. We have not tested compatibility extensively, and we would like to see reports from the beta users on how the FTX meshes and FreeMeshX USA mesh conflict. Since they are both the same level of detail, there may be some conflict. If there is, the likely suggestion would be to uncheck FMX - USA from your Scenery Library when flying in the FTX regions. We highly encourage the use of FTX Vectors. Any good mesh needs a good vector replacement package.

In your scenery library you'll find the ORBX mesh entries. Just uncheck them.

FreemeshX is a wonderful product, and I would speculate to say is very widely used. To answer the OP questions; yes USA only has 55 files. I would verify that it is layered correctly in your scenery library. Should be below all of your add on sceneries, but higher than the defaults. There is a great deal of documentation on this. Also verify that your mesh resolution is set to at least 10m if not 5m. I think you may have been given some misinformation otherwise in this thread. Quality mesh is quite essential for lower altitude flying. It actually becomes less essential at high altitudes. Orbx, as suggested, while containing it's own mesh, also contains land class and vector information (regions, or global purchases). PNW was not freeware, although a small section of it is or was at one time. I actually have my ORBX mesh disabled as I choose to run FreemeshX instead.

I believe Shez's BUR version was for FS9, therefore I haven't tested compatibility with P3Dv4, as those usually don't work out too well. The LGB scenery is FSX and works well with minor issues as noted above.

This is true Bert, the database is in the trainer. The problem lies within the difference between RXP and F1. RXP allows for use of Garmin Trainer v6.41.1 where as F1's version only allows for use of v6.21.0. If you install 6.41.1 with F1, it will not work. There were file changes between the two trainer versions. If someone tries to update 6.21.0 with current data it won't work. Well, there is a way to make it work, but it is a bit drawn out.

May or may not be the case. If it is the case, people have found a way around it.

F1 uses an older version of Garmin Trainer than RXP does. The file structure changed a bit in the different versions of the trainer which, providing one has the data, makes RXP easily updatable, where the F1 version is left behind. F1 has rejected updating their product to function with the current version of the trainer.

Change your output device to your headset

Jim Young's suggestions (3rd comment down) worked well for me in curbing most of my shimmering.

I gave this a go just to see what it would do for my shimmers, particularly in the night environment. It made a profoundly positive difference. Not eliminated, as you already acknowledged, but certainly much better. Thank you.

I think STS has had some real world changes since release. The others you mention I believe are fine.

I can say it looks fine and blends well. There are special instructions for installing with Orbx. I am away from my computer for several days however and unable to provide screenshots.

ORBX builds night lighting into the trees. Hence the autogen reference. Reducing the distance may or may not alleviate flickering, but it will certainly reduce your view of distant night lighting. This is why ORBX night lighting doesnt carry very far in the distance. If you look during the day, odds are the trees shimmer too. I have not found a solution to this myself.

Hey Rancid, I unfortunately, really don't have the answer. I do have the A2A aircraft, but personally use the Flight1 GTN 650/750 in those. I believe the default GPS is the Garmin 295 or something to that effect. I do not own Carenado/Alabeo aircraft except what is default in P3Dv4. For starters, perhaps try the default A36 Bonanza as it is a Alabeo aircraft with a 430 in it. There is a few threads in the A2A forum. Here is from my search results. Perhaps it may lead you in a direction. https://a2asimulations.com/forum/search.php?keywords=fsaerodata&terms=all&author=&sc=1&sf=all&sk=t&sd=d&sr=posts&st=0&ch=300&t=0&submit=Search

They're essentially just default units in those particular add on's. The products do however allow for relatively easy upgrades through third party products (Flight1, RXP) or within those units through fsaerodata.