Hi all,I'm trying to adapt David Cuvillier's FS2004 Paro (VQPR) scenery to FSX and Holger's excellent Himalayas mesh, but the flatten for the airport is not working well. There's definitely flattening going on, but the elevation it's actually flattening to is a good 200 feet higher than the elevation called for by the flatten (and the real airport height). What makes it even more frustrating is that the real altitude would clearly work pretty well with the mesh, if the flatten would actually flatten to that height! Instead I end up with a plateau (pictures below). Any ideas of what might be going wrong or how I can fix this? I don't know a whole lot about working with mesh, scenery, etc.--I'm basically learning by trial and error. Any help would be vastly appreciated.Thanks!Best,James

Could there be an "Area16N" style flatten in one of the bgls? Update: took a quick look at the scenery and I would guess you should get rid of (rename from .bgl to something else) paro_sol_A16N.bgl.scott s..

Hello:Looks like an interesting place to fly ! :( Here's the *.sca code for the legacy format Area16N SCASM 2,235.730 Meter (7,335.05 Feet) flatten... which FSX is not able to render:

; ----------------------------------------; paro_sol_A16N.bgl disassembled by BGLAnalyze (c) on Fri Feb 18 16:50:29 2011; ----------------------------------------Header( 1  N27:24:40.71 N27:23:41.46 E089:26:03.67 E089:24:56.93 )LatRange(  N27:23:41.46  N27:24:40.71 ); since SCASM does not support multiple latitude ranges; the range has been set to the minimum/maximum latitude.; LatRange information in the BGL file is given as comment.; If you want to use band separation, you must edit; the source file manually.; Insert the "Set( FSVers 0x800 )" instruction at the beginning; of the file, if you want to use the FS2002 instructions; for the facilities sectionmif( [$Version < 285] )   Error( You need at least SCASM version 2.85 to compile this code )mifend; ----------------------------------------; Miscellaneous section; ----------------------------------------; LatRange(  N27:23:39.75  N27:24:29.50 ); ----------------------------------------Area16N	Flatten( 2235.730		 N27:24:11.62  E089:25:21.29 ; vertex 1		 N27:24:12.06  E089:25:22.38 ; vertex 2		 N27:24:11.35  E089:25:22.64 ; vertex 3		 N27:24:10.86  E089:25:21.74 ; vertex 4	)End16Area16N	Flatten( 2235.730		 N27:24:07.83  E089:25:23.10 ; vertex 1		 N27:24:07.05  E089:25:23.50 ; vertex 2		 N27:24:07.32  E089:25:24.32 ; vertex 3		 N27:24:08.12  E089:25:23.87 ; vertex 4	)End16; ----------------------------------------; end of SCASM source

The real world airport elevation is reportedly 2,200 Meters according to this web site:http://en.wikipedia.org/wiki/Paro_Airport2,235 meters (7,332 feet) is the stated elevation according to this web site:http://worldaerodata.com/wad.cgi?id=BT71541&sch=VQPRI suggest making a replacement FSX SDK compliant CVX Vector "Airport Background" Flatten BGL which has the desired 'single' elevation, using either Airport Design Engine (ADE) or SBuilderX.If you do not plan to use AI traffic at your custom version of the airport, using Holger's terrain mesh, you can enter each of the above vertex coordinates into FS' Map view, and 'jump' around to get the elevation 'as rendered' in FS with Rhumbaflappy's TCalcX_003 to read ground altitude data.You could then make a "sloped flatten" instead (see the manual for the above scenery programs for details on how to do this).TCalcX_003:http://www.fsdeveloper.com/forum/downloads.php?do=file&id=79Hope this helps ! :( GaryGB

Gary, you have the best looking FS scenery that I have ever seen!Best regards.Luis

Hi Luis:Why thanks... but I really must give all credit to MS Game Studios for the fine job they are doing on the FS-11 beta; I especially like the way it is rendering photoreal textures, lighting, and 'running' inland water (still working on the crepuscular lighting "God-Rays+Clouds" SDK though) ! :(< Just kidding of course... credit wikipedia.org for that photo >But who knows what the future will make possible... "MS Flight!" is looking very promising, isn't it ? GaryGB

Scott and Gary,Thanks so much! You're exactly right, there was an Area16N flatten that was causing the trouble. I managed to make a quick-and-dirty replacement flatten without sloping and I'm reasonably satisfied with the results--it's at least flyable now. Thanks so much for your help. It's a great airport and it's so much better now.Best,James