Rami or Xavier

B

B757

Members +
Hi all!
Have some airfield elevation issues, DEI samarinda II and DEI singkawang.
They are little bit higher from sorrounding groundelevation.
I`m missing something or someone have update.flatten?!
Using Rhumbas lod5,7,8 without watermasking
Thanks for nice campaign Dei 3,5 and scenery.

B757:wavey:
 
Reply...

B757,

That's a byproduct of the LOD mesh that Rhumbaflappy created. Due to the immense improvement that his mesh is over the original files, it was something I can live with.

I kinda figured someone would pick up on this...:redf:

However, if anyone can come up with a flatten for it, it would be an added bonus.
 
B757,

Your sim installation created a Readme.rtf file in the main directory. Open it and read the section called Backward Compatible Scenery. This section includes instructions on how to create an artificial flatten switch for any location in your sim world. It may take a few readings to fully understand the details, but that's all i had to work with too when i got started modifying the elevations of addon airfields that looked this way. Works like a charm....
 
Bearcat,

Thanks, flattenswitch works ok, except for the runways they will not flatten,still in the air. maybe need some rework?!

B757:wavey:
 
B757 said:
... except for the runways they will not flatten,still in the air. maybe need some rework?!
Click to expand...

Yeah, i see....hmmm....can't remember that ever happening. You may need to find an editor for the airfield's AFD file that will allow you to modify the elevation of the strips to flush with the surrounding terrain. There is the possibility of modifying the strip elevation yourself with a program called MkAFD2 : http://www.btinternet.com/~mnwright/

You seem to be pretty handy with this flattening thingy, so you might find the handle on this tool fairly easy.

Or... we may need a major rework of the campaign's airfields by the designer to meet the terrain mesh.
 
Well, I made that scenery for a different terrain elevation mesh, as specified in the readme file, long time before Rhumba's was available. No project to rebuild the airfields once again in agenda, sorry.
 
Correct me if i'm wrong, but isn't it the **A16N.bgl that alone controls the runway elevation while the **AFD.bgl and **.bgl control location, infrastructure placement and airfield elevation? If so, you can safely remove the A16N.bgl of any airstrip causing problems to correct this without affecting the entire scenery location. Its a little fuzzy now, but i remember doing something like this in the early days when i had an elevation problem with a new addon base which was conflicting with an older addon nearby. By removing the older addon's A16N i was able to correct the terrain conflicting and the two lived happily ever after. If memory serves it was two different installations of Le Havre which were close but separated enough to allow them to coexist. I wanted the location to keep that "overdeveloped" look when the two were present together.
 
Bear,

I am afraid it is not that easy.
The **A16N.bgl flattens the area where the airfield is build on.

Header( 1 N55:53:15.8871 N55:47:51.9129 E032:59:22.2404 E032:49:45.2257 )
LatRange( N55:47:51.9129 N55:53:15.8871 )
Area16N
Elevation( 204.57
N55:49:46.1341 E032:51:51.7866
N55:49:41.5984 E032:56:07.7051
N55:51:32.0210 E032:56:28.0573
N55:51:30.7494 E032:51:57.9591
)
End16

The **.bgl has among others the information of the runway elevation

:lblLayer
Runway( N55:50:40.3885 E032:54:00.4246
Altitude 204.57
 Heading 288.0
Length 3802
Width 171
ID 29
Surface -1
Markers 0
Threshold 0
Lights 1
)
Return
The altitude is the same as in the **A16N.bgl

And the **AFD.bgl has the information of the runway location, elevation and the respective headings

LatRange( N55:47:51.9129 N55:53:15.8871 )
Container( APT 13 )
APLocation( N55:50:33.9001 E032:54:33.9001 204.57 )
ICAO_ID( "ANY" )
RwyLoc( N55:50:40.2654 E032:54:00.3552 204.57 108.0 -7.2 3802 171 N 11 100 )

SetupLoc( N55:50:34.6639 E032:54:31.0600 204.57 288.0 1 N 29 )
SetupLoc( N55:50:45.8668 E032:53:29.6494 204.57 108.0 1 N 11 )

EndC

BTW the elevation (FSSC) is in meters.

In his tutorial MaskRider strongly recommends to have all visible parts of the airfield inside the flattend area. But I have never tried otherwise. My educated guess is that apart from the runway (if you delete the **A16N.bgl) taxiways and other will not show (because partly under the mesh or above it).

I am going to test it tomorrow.

Cheers

Achim
 
Yes, it is true: elevation is controlled by the **A16N.bgl file for each airfield. Remove the file and the original elevation will be gone. But there is at least one point: the infrastructure objects will look somewhat sunken. On the other hand, I do not use MaskRider system to create scenery.
 
Finally

Hi all!

At last i found out how to do it. Using BGL Analyze 3.1 to dissambling bgl to files (sca) and open with notepad to adjusted the altitude and drag the files to scasm.exec one at time to make new bgls.

Exempel shows DEI Samarinda II bgl files changed in red.(meters)
Runway Surface 64. I think its "runway64.bmp" not shure?!
Airbase dat. base_alt in feet!
Works fine for me!!

:jump:B757

; ----------------------------------------
; xbp_asia_borneo_v1_samarinda2_A16N.bgl disassembled by BGLAnalyze (c) on Tue Jan 26 20:37:08 2010

; ----------------------------------------
Header( 1 S00:21:20.13 S00:23:29.70 E116:18:37.50 E116:16:27.90 )
LatRange( S00:23:29.70 S00:21:20.13 )
; 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 section
mif( [$Version < 285] )
Error( You need at least SCASM version 2.85 to compile this code )
mifend

; ----------------------------------------
; Miscellaneous section
; ----------------------------------------


; LatRange( S00:23:29.80 S00:21:33.70 )
; ----------------------------------------
Area16N
Flatten( 12.000
S00:23:01.27 E116:16:56.54 ; vertex 1
S00:21:49.12 E116:16:55.77 ; vertex 2
S00:21:49.03 E116:18:08.34 ; vertex 3
S00:23:00.56 E116:18:08.08 ; vertex 4
)
End16

; ----------------------------------------
; end of SCASM source

; ----------------------------------------


; xbp_asia_borneo_v1_samarinda2_AFD.bgl disassembled by BGLAnalyze (c) on Tue Jan 26 20:56:40 2010

; ----------------------------------------
Header( 1 S00:21:20.13 S00:23:29.70 E116:18:37.50 E116:16:27.90 )
LatRange( S00:23:29.70 S00:21:20.13 )
; 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 section
mif( [$Version < 285] )
Error( You need at least SCASM version 2.85 to compile this code )
mifend

; ----------------------------------------
; AFD Section
; ----------------------------------------
; ----------------------------------------
; Object # 1, offset: 0000C8, size: 240 bytes
; ----------------------------------------
Container( APT 1 )
APLocation( S00:22:24.90 E116:17:32.70 12 )
ICAO_ID( ANY )
RwyLoc( S00:22:25.29 E116:17:33.82 12
90 -1.00 ; true heading, mag.var.
4346 279 ; length, width
N 9 64 ) ; rwy type, number and surface
SetupLoc( S00:22:25.29 E116:17:13.00 12
90 1 ; heading, type
N 9 ) ; runway type, number
SetupLoc( S00:22:25.29 E116:17:54.63 12
270 1 ; heading, type
N 27 ) ; runway type, number
EndC

; Namelists
Namelist( 0409 ) ; language
NameEntry( REGION 0 "Asia" )
NameEntry( COUNTRY 0 "Dutch East Indies" )
NameEntry( CITY 0 "Samarinda" )
NameEntry( AIRPORT 1 "DEI Samarinda II" )
EndNL
; ----------------------------------------
; end of SCASM source

; ----------------------------------------


; xbp_asia_borneo_v1_samarinda2.bgl disassembled by BGLAnalyze (c) on Tue Jan 26 20:41:01 2010

; ----------------------------------------
Header( 1 S00:21:20.13 S00:23:29.70 E116:18:37.50 E116:16:27.90 )
LatRange( S00:23:29.70 S00:21:20.13 )
; 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 section
mif( [$Version < 285] )
Error( You need at least SCASM version 2.85 to compile this code )
mifend

; ----------------------------------------
; Procedural scenery
; ----------------------------------------


; LatRange( S00:23:29.80 S00:21:33.70 )
; ----------------------------------------
; ----------------------------------------
; Object # 1, offset: 0x000A size: 160 bytes (0x00A0)
;; Lat: 0FFFF5DCFh Lon: 052B25E64h
; ----------------------------------------
Area( B S00:22:25.05 E116:17:32.31 40 )
RefPoint( rel :L0000A8 1.00 S00:22:25.03 E116:17:32.31
V1= 0 V2= 0 )
RotatedCall( :L000042 0 0 90 )
Return
:L000042
Points( 0
-1120 0 1120 ; 0
1120 0 1120 ; 1
1120 0 -1120 ; 2
-1120 0 -1120 ; 3
)
LoadBitmap( 0 5 00 1 1 1
back_0033.bmp )
Smoothing( 1 )
TexPoly( m 0 32767 0 0
0 0 255 ; 0
1 255 255 ; 1
2 255 0 ; 2
3 0 0 ; 3
)
Smoothing( 0 )
:L0000A8
Return
EndA

; ----------------------------------------
; Object # 2, offset: 0x00AA size: 102 bytes (0x0066)
;; Lat: 0FFFF5DC7h Lon: 052B271E4h
; ----------------------------------------
Area( 5 S00:22:25.30 E116:17:33.82 12 )
LayerCall( :L0000C0 24 )
Jump( : )
:L0000C0
Runway( S00:22:25.29 E116:17:33.82
Alt 12.0
Heading 90.0
Length 4346 ; in feet
Width 279 ; in feet
Markers 00
Id 9
Lights 0
Surface 64
Threshold 0
ThrOffN 0
ThrOffF 0
ExtN 0
ExtF 0
)
Return
EndA

; sorted list of objects
; S00:22:25.30 E116:17:33.82 Object # 2
; S00:22:25.05 E116:17:32.31 Object # 1
; ----------------------------------------
; end of SCASM source
; ----------------------------------------
; xbp_asia_borneo_v1_samarinda2.bgl disassembled by BGLAnalyze (c) on Tue Jan 26 20:41:01 2010

; ----------------------------------------
Header( 1 S00:21:20.13 S00:23:29.70 E116:18:37.50 E116:16:27.90 )
LatRange( S00:23:29.70 S00:21:20.13 )
; 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 section
mif( [$Version < 285] )
Error( You need at least SCASM version 2.85 to compile this code )
mifend

; ----------------------------------------
; Procedural scenery
; ----------------------------------------


; LatRange( S00:23:29.80 S00:21:33.70 )
; ----------------------------------------
; ----------------------------------------
; Object # 1, offset: 0x000A size: 160 bytes (0x00A0)
;; Lat: 0FFFF5DCFh Lon: 052B25E64h
; ----------------------------------------
Area( B S00:22:25.05 E116:17:32.31 40 )
RefPoint( rel :L0000A8 1.00 S00:22:25.03 E116:17:32.31
V1= 0 V2= 0 )
RotatedCall( :L000042 0 0 90 )
Return
:L000042
Points( 0
-1120 0 1120 ; 0
1120 0 1120 ; 1
1120 0 -1120 ; 2
-1120 0 -1120 ; 3
)
LoadBitmap( 0 5 00 1 1 1
back_0033.bmp )
Smoothing( 1 )
TexPoly( m 0 32767 0 0
0 0 255 ; 0
1 255 255 ; 1
2 255 0 ; 2
3 0 0 ; 3
)
Smoothing( 0 )
:L0000A8
Return
EndA

; ----------------------------------------
; Object # 2, offset: 0x00AA size: 102 bytes (0x0066)
;; Lat: 0FFFF5DC7h Lon: 052B271E4h
; ----------------------------------------
Area( 5 S00:22:25.30 E116:17:33.82 12 )
LayerCall( :L0000C0 24 )
Jump( : )
:L0000C0
Runway( S00:22:25.29 E116:17:33.82
Alt 12.0
Heading 90.0
Length 4346 ; in feet
Width 279 ; in feet
Markers 00
Id 9
Lights 0
Surface 64
Threshold 0
ThrOffN 0
ThrOffF 0
ExtN 0
ExtF 0
)
Return
EndA

; sorted list of objects
; S00:22:25.30 E116:17:33.82 Object # 2
; S00:22:25.05 E116:17:32.31 Object # 1
; ----------------------------------------
; end of SCASM source

[runway.XXX]
id=XXXX
name=Samarinda II
base_lat=S00 22.42
base_lon=E116 17.20
base_alt=36
heading=90
allegiance=0
units_across=2
takeoff_start_pos=-050,0
takeoff_stop_pos=1325,200
landing_start_pos=5000,350
landing_touchdown_pos=550,0
landing_stop_pos=-250,0
 
Hi B757,

I notice a couple of things with the coding. In the line that reads

Area( B S00:22:25.05 E116:17:32.31 40 )

Should read Area( A S00:22:25.05 E116:17:32.31 40 )

and in the line

Area( 5 S00:22:25.30 E116:17:33.82 12 )

should read

Area( A S00:22:25.30 E116:17:33.82 12 )

CFS uses Area A for ground poly's and runways.. There's a couple of other places in the code you'll need to change it too.


Cheers :ernae:
Lindsay
 
Hi B757,

One other thing you might encounter when adjusting airfield elevations is this:

When you recompile the sca file containing the runway data back to bgl format using scasm you sometimes get the runway surface changed to an old FS98 type surface. I think this is the fault of BGL Analyze, so if you know what the original runway surface code is, you can edit it before recompiling.

Kevin
 
Hi All,

For reference

CFS2 runway numbers:

64 = dirt square end
65 = dirt round end
66 = steel mat
67 = coral square end
68 = coral round end
-1 = invisible runway (good for float bases, carrier decks, and other things)


Cheers :ernae:
Lindsay
 
:wavey:Hi leroy10,kdriver!

Thanks for your comments and advices!
Yes, I have to change to surface 64, figure out that cfs2 runway numbers are in cfs2 root folder "TEXTURE" for "runway64.bmp" and so on.

Cheers :ernae:
B757
 
B757 said:
......
......Airbase dat. base_alt in feet!
Works fine for me!!

:jump:B757
.......
[runway.XXX]
id=XXXX
name=Samarinda II
base_lat=S00 22.42
base_lon=E116 17.20
base_alt=36
heading=90
allegiance=0
units_across=2
takeoff_start_pos=-050,0
takeoff_stop_pos=1325,200
landing_start_pos=5000,350
landing_touchdown_pos=550,0
landing_stop_pos=-250,0
Click to expand...

Hi B757 !
The altitude in airbase.dat is in meter .
icon23.gif


JP
 
You must log in or register to reply here.
Back
Top