If you have setup FT Grenadines correctly with autogen and your default.xml is not corrupt it is still possible that Autogen is not working.
In my case, I have found the culprit to be the file: OLC_NA_REG.bgl located in the ORBX FTX_OLC Scenery folder.
I have switched it off and my autogen is 100% ok.
I am still testing and have not found any issues yet.
Will report back if I find some.
Autogen Issues after FTX_OLC install. A solution
Re: Autogen Issues after FTX_OLC install. A solution
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?If you have setup FT Grenadines correctly with autogen and your default.xml is not corrupt it is still possible that Autogen is not working.
In my case, I have found the culprit to be the file: OLC_NA_REG.bgl located in the ORBX FTX_OLC Scenery folder.
I have switched it off and my autogen is 100% ok.
I am still testing and have not found any issues yet.
Will report back if I find some.
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?
Warm regards,
Luís
Re: Autogen Issues after FTX_OLC install. A solution
Dear friends!
The ORBX changed the regional labelling of Lesser Antilles area!
Now it belongs to "H"-region. That's why it must to write the
completion of default.xml just below <CODE>H</CODE>.
With this, the autogen will appear perfectly.
Good luck!
The ORBX changed the regional labelling of Lesser Antilles area!
Now it belongs to "H"-region. That's why it must to write the
completion of default.xml just below <CODE>H</CODE>.
With this, the autogen will appear perfectly.
Good luck!
Re: Autogen Issues after FTX_OLC install. A solution
Update and final solution (I think)
Tks to nyfe for this info about code H.
1. If the flytampa autogen editor did its job, the proper entries would have been put in default.xml
2. The fly grenadines autogen puts its files startiing at <CODE>R</CODE>
3. In my case that is where they were (using P3Dv3.4)
4. With a proper xml editor changed the code R to code H just that single letter and save
5. Autogen is back and you don't have to turn off the ftx old na mentioned previously.
Cheers
Tks to nyfe for this info about code H.
1. If the flytampa autogen editor did its job, the proper entries would have been put in default.xml
2. The fly grenadines autogen puts its files startiing at <CODE>R</CODE>
3. In my case that is where they were (using P3Dv3.4)
4. With a proper xml editor changed the code R to code H just that single letter and save
5. Autogen is back and you don't have to turn off the ftx old na mentioned previously.
Cheers
- Sabretooth78
- Posts: 15
Re: Autogen Issues after FTX_OLC install. A solution
I was having some trouble with this particular method of fix, but got it all working a slightly different way:
Add the lines in the following post under the 'H' section (<CODE>H</CODE>), instead of the 'R' section.
http://www.flytampa.org/forum/viewtopic ... 069#p53069
For me this seems to actually be persistent. Before, something was resetting my default.xml even before P3D would boot. With this, Grenadines does indeed appear to be fully working and functional.
Just sort of makes me wonder what other autogen is missing elsewhere that I'm not even aware of...
Add the lines in the following post under the 'H' section (<CODE>H</CODE>), instead of the 'R' section.
http://www.flytampa.org/forum/viewtopic ... 069#p53069
For me this seems to actually be persistent. Before, something was resetting my default.xml even before P3D would boot. With this, Grenadines does indeed appear to be fully working and functional.
Just sort of makes me wonder what other autogen is missing elsewhere that I'm not even aware of...
- Sabretooth78
- Posts: 15
Re: Autogen Issues after FTX_OLC install. A solution
As a follow up, the autogen "fix" above was somehow undone last night when I ran ORBX FTX Central last night. Not sure if it was just the act of running it or that I also installed a couple new airports I had purchased. In any event, I repeated the fix and it again has seemed to work and hold. So it would seem you just need to perform periodic "maintenance" on it until a formal update is released.