This has come up many times before but I thought I would attempt to add to the knowledge base about it. I am working on recreating Pittsburgh Airport (KPIT) as of 1959. A couple of weeks ago I was adding some aprons and bglcomp threw this error. At the time I converted 10 aprons into part of my ground polygon model created with Sketchup 8 and brought the apron count down to 147. No error message now. Since I knew that I had only added two apron areas I decided to test if it was the number of aprons or the total number of apron vertex points that was causing the error. Before the buffer overflow error was thrown I was getting a good compile with 157 aprons. So I started adding triangle shaped aprons until I had added 15 onto my previous 147 for a total of 162 aprons. The compile was clean. So I took this to mean that apron vertex points were the culprit. To count them easily I used ADE's list function and exported my apron list as a csv file. I imported this into my spreadsheet program and used it to tell me how many total vertexes there were. I began adding vertexes until I got the buffer overflow message and then reduced them one by one to see if I could pinpoint a specific number of apron vertexes that were ok but one more would give you the error message. I never got to a point like that but I did discover that if you had 4,656 vertex points or less you should get a clean compile. I discovered that there is a sort of no man's land where the compile will not create an airport bgl that FS9 will read but also does not return the buffer overflow error message. This is in the area of 4.657 to about 4,660 vertex points. Above 4,660 vertex points you will probably get the error message. At one point in my experimenting I went from 4.657 points to 4.656 points and still got an unusable airport bgl. Recompiling that same file again with no changes got me a usable airport file. So in the future I plan on keeping an eye on my total vertex points to avoid this becoming a problem.
Ed
Ed
