iamlmc

I tried a different method (https://github.com/jet2code/arpc-injector) and ended breaking my MSFS 2020 .exe. Long story short, after modifying the .exe I got a compatibility error when starting the Sim (not recognized as being a 64 bit file). The odd thing was that the problem persisted even after changing the modified .exe with the unmodified .exe backup file. I also want to point out that my MSFS 2020 install (MS Store) had the .exe encrypted... so it would never work.

Stop using radioactive terminal buildings and airplanes! Don't have the finest idea of what is going on with your sim... Sorry. PS: ... Alternatively stop feeding Prepar3D with LSD. LoL

I posted over their forums but unfortunately got no response... http://www.flytampa.org/forum/viewtopic.php?f=16&t=10105

At least it's not a problem on my setup! Have you tried FlyTampa's support?

How about runway lights regarding Grenadines airports? I am experiencing some issues. TVSB and TVSC only half the runway lights are visible. If you do a runway flyby as soon as your plane is about to pass the turned off lights they will become on. TVSM PAPI lights show 4 lights at a distance. As soon you close in it will change to 2 lights as it should. TVSU and TGPZ no issues as they do not have illuminated runways. Anyone experiencing this? Any tips or solutions?

I am glad you did just that. It is an extremely tedious task for sure...

Change file extension of OLC_NA_REG.bgl to OLC_NA_REG.off The file is located in ...Prepar3D v3 (main folder)\ORBX\FTX_OLC\OLC_AA\Scenery

Tested on my system and vegetation and autogen are working as they should (don't forget to max all scenery related slides). How did you managed to find the culprit file? I have been using customer support (email) and Martin was unable to help to the point he stopped responding my emails. What's the "reverse coin" of having to disable OLC_NA_REG.bgl?

I have the exact same problem as you (https://www.avsim.com/forums/topic/504106-island-scenery/?page=2). Meanwhile you might want to try this (http://www.flytampa.org/forum/viewtopic.php?f=16&t=10165). I haven't tried it yet so no feedback on my behalf. Regards, Luís

I am having the no Autogen problem with the FlyTampa - Grenadines = No vegetation and no autogen. Anyone else experiencing this??? I am using Prepar3D v3.4.22.19868 on a Windows 10 x 64 machine and installed the latest Grenadines installer provided by Simmarket (FlyTampa_Grenadines_FSX_P3D_12.exe). Tried: Grenadines AutogenEditor and it did not fixed the issue. Used the backup autogen file and added the extra code from the "Manual Default.XML Autogen" with no avail. http://www.flytampa.org/forum/viewtopic.php?f=16&t=9477 Contacted support (25/03/17) with no solution till the present day... Grenadines does show up in FlyTampa Configurator along with my other FlyTampa sceneries.

+1

It will work although with some severe limitations. A new LPMA is being made, but at this point I don't know details about the level of detail of the airport and island. I also presume tha LPPS (minor inhabited island and airport of the archipelago) is not going to be included/made. Please check the following links: http://forum.aerosoft.com/index.php?/topic/107197-madeira-x-troubleshooting/ http://simmershome.de/madeira-fuer-p3d-v2-fix/

I don't know if we share the same cause. But regarding the end result, I can tell you that back on the days, when I had my Sim running (v3.2), I had the exact same bug with Latin VFR San Diego (KSAN) and Aerosoft A3xx tubes. Never understood why and never found a cure for it.

Was wondering the same...

I do understand what you're saying, I myself suffer from some type of "OCD issues" regarding this problem. But I have found, regarding Prepar3D, that it is more a matter of smoothness than to achieve a fixed FPS minimum. Although with all the bells and whistles and the various addons it's more easy to say than done! PS: Thanks for the inputs Afterburner.