SCASM Runway Overlays - Revision history

Thebeloved at 13:12, 21 June 2013

2013-06-21T13:12:32Z

← Older revision		Revision as of 08:12, 21 June 2013
Line 1:		Line 1:
	{{Infobox-Applicable-FSVersion		{{Infobox-Applicable-FSVersion
			\| P3D = true
	\| FSXI = unknown		\| FSXI = unknown
	\| FSXA = true		\| FSXA = true

Thebeloved: /* FSXA/P3D */

2012-10-25T13:38:14Z

FSXA/P3D

← Older revision		Revision as of 08:38, 25 October 2012
Line 63:		Line 63:
	The parameter '''Heading''' must be declared in range '''0.00''' to '''179.99''' and only non integer values are allowed (i.e. 120.00° must be at least 120.01° or 119.99°). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:		The parameter '''Heading''' must be declared in range '''0.00''' to '''179.99''' and only non integer values are allowed (i.e. 120.00° must be at least 120.01° or 119.99°). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:

	'''Heading 58.01~~'''~~ (i've added +2° degrees of magnetic declination, so 56° (Rwy True Heading) + 2° (MagDec) + 0.01°)		<pre>...
			Runway( 40.3425265999 14.6089375666
			Alt 99.974 ; in meters
			Heading 58.01 ;non integer value between 0.00° and 179.99°
			Length 5002 ; in feet
			Width 150 ; in feet
			...</pre>

			note the parameter:

			'''Heading''' 58.01 (i've added +2° degrees of magnetic declination, so 56° (Rwy True Heading) + 2° (MagDec) + 0.01°)

	Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.		Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.

Thebeloved: /* FSXA/P3D */

2012-10-25T13:34:09Z

FSXA/P3D

← Older revision		Revision as of 08:34, 25 October 2012
Line 61:		Line 61:
	== FSXA/P3D ==		== FSXA/P3D ==

	The parameter '''Heading''' must be declared in range 0 to 179 and only ~~decimal~~ values are allowed (i.e. ~~not integer values~~). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:		The parameter '''Heading''' must be declared in range '''0.00''' to '''179.99''' and only non integer values are allowed (i.e. 120.00° must be at least 120.01° or 119.99°). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:

	'''Heading 58.01''' (i've added +2° degrees of magnetic declination, so 56° (Rwy True Heading) + 2° (MagDec) + 0.01°)		'''Heading 58.01''' (i've added +2° degrees of magnetic declination, so 56° (Rwy True Heading) + 2° (MagDec) + 0.01°)

Thebeloved: /* FSXA/P3D */

2012-10-25T11:33:51Z

FSXA/P3D

← Older revision		Revision as of 06:33, 25 October 2012
Line 63:		Line 63:
	The parameter '''Heading''' must be declared in range 0 to 179 and only decimal values are allowed (i.e. not integer values). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:		The parameter '''Heading''' must be declared in range 0 to 179 and only decimal values are allowed (i.e. not integer values). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:

	'''Heading 58.01''' (~~we have~~ +2° degrees of magnetic declination)		'''Heading 58.01''' (i've added +2° degrees of magnetic declination, so 56° (Rwy True Heading) + 2° (MagDec) + 0.01°)

	Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.		Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.

Thebeloved: /* FSXA/P3D */

2012-10-25T11:32:30Z

FSXA/P3D

← Older revision		Revision as of 06:32, 25 October 2012
Line 63:		Line 63:
	The parameter '''Heading''' must be declared in range 0 to 179 and only decimal values are allowed (i.e. not integer values). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:		The parameter '''Heading''' must be declared in range 0 to 179 and only decimal values are allowed (i.e. not integer values). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:

	'''Heading 58.01''' (we have +2° degrees of ~~magnetical~~ declination)		'''Heading 58.01''' (we have +2° degrees of magnetic declination)

	Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.		Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.

Thebeloved at 09:40, 25 October 2012

2012-10-25T09:40:05Z

← Older revision		Revision as of 04:40, 25 October 2012
Line 9:		Line 9:
	Sometimes we need to create a flat runway that embeds certain lights elements that speed-up the design of a new airport.		Sometimes we need to create a flat runway that embeds certain lights elements that speed-up the design of a new airport.

	~~Intead~~ to create rwy lights and PAPI with custom techniques, we can use the old opcode 0xAA (NEW_BGL_RUNWAY) that is a legacy of FS8 opcodes to create a runway equipped with edge lights, PAPI and CALVERT, that lits automatically at night or in adverse weather conditions, and sits on top of our groundpolys or photoreal scenery. This runway has indeed layer number 24.		Instead to create rwy lights and PAPI with custom techniques, we can use the old opcode 0xAA (NEW_BGL_RUNWAY) that is a legacy of FS8 opcodes to create a runway equipped with edge lights, PAPI and CALVERT, that lits automatically at night or in adverse weather conditions, and sits on top of our groundpolys or photoreal scenery. This runway has indeed layer number 24.

	To do this we can use a SCASM command that helps to create a single bgl that contains all NEW_BGL_RUNWAY informations to create a runway that can overlay our photoreal or GMAX created runway.		To do this we can use a SCASM command that helps to create a single bgl that contains all NEW_BGL_RUNWAY informations to create a runway that can overlay our photoreal or GMAX created runway.

Thebeloved: /* Counter-effects */

2012-10-25T09:37:57Z

Counter-effects

← Older revision		Revision as of 04:37, 25 October 2012
Line 68:		Line 68:

	== Counter-effects ==		== Counter-effects ==
	SCASM created runways have the problem that FSX/P3D AI traffic disappear when the "Ground cast scenery shadows" is activated in the preferences. No workaround exists at the moment.		SCASM created runways have the problem that FSX/P3D AI traffic (with FS2004 native models) disappear when the "Ground cast scenery shadows" is activated in the preferences. No workaround exists at the moment.

			AI Traffic with FSX native model does not suffer of this problem.

	[[Category:Tweaking]]		[[Category:Tweaking]]
	[[Category:Scenery_Design]]		[[Category:Scenery_Design]]

Thebeloved at 09:13, 25 October 2012

2012-10-25T09:13:56Z

← Older revision		Revision as of 04:13, 25 October 2012
Line 1:		Line 1:
			{{Infobox-Applicable-FSVersion
			\| FSXI = unknown
			\| FSXA = true
			\| FSX = true
			\| FS2004 = true
			\| FS2002 = true
			}}

	Sometimes we need to create a flat runway that embeds certain lights elements that speed-up the design of a new airport.		Sometimes we need to create a flat runway that embeds certain lights elements that speed-up the design of a new airport.

Thebeloved at 09:02, 25 October 2012

2012-10-25T09:02:45Z

← Older revision		Revision as of 04:02, 25 October 2012
Line 1:		Line 1:
	Sometimes we need to create a flat~~, transparent,~~ runway that embeds certain elements that speed-up the design of a new airport.		Sometimes we need to create a flat runway that embeds certain lights elements that speed-up the design of a new airport.

	Intead to create rwy lights and PAPI with custom techniques, we can use the old opcode 0xAA (NEW_BGL_RUNWAY) that is a legacy of FS8 opcodes to create a runway equipped with edge lights, PAPI and CALVERT, that lits automatically at night or in adverse weather conditions, and sits on top of our groundpolys or photoreal scenery. This runway has indeed layer number 24.		Intead to create rwy lights and PAPI with custom techniques, we can use the old opcode 0xAA (NEW_BGL_RUNWAY) that is a legacy of FS8 opcodes to create a runway equipped with edge lights, PAPI and CALVERT, that lits automatically at night or in adverse weather conditions, and sits on top of our groundpolys or photoreal scenery. This runway has indeed layer number 24.

Thebeloved: SCASM Runway Overlays

2012-10-25T08:59:42Z

SCASM Runway Overlays

New page

Sometimes we need to create a flat, transparent, runway that embeds certain elements that speed-up the design of a new airport.

Intead to create rwy lights and PAPI with custom techniques, we can use the old opcode 0xAA (NEW_BGL_RUNWAY) that is a legacy of FS8 opcodes to create a runway equipped with edge lights, PAPI and CALVERT, that lits automatically at night or in adverse weather conditions, and sits on top of our groundpolys or photoreal scenery. This runway has indeed layer number 24.

To do this we can use a SCASM command that helps to create a single bgl that contains all NEW_BGL_RUNWAY informations to create a runway that can overlay our photoreal or GMAX created runway.

The basic code to do this is:

<pre>Header( 0 N40:54 N40:52 E014:16 E014:18 )
LatRange( N40:52 N40:54 )

Area( 5 40.3425265999 014.6089375666 12 )

Runway( 40.3425265999 14.6089375666
Alt 99.974 ; in meters
Heading 58.01
Length 5002 ; in feet
Width 150 ; in feet
Markers 00
Lights 03
Surface 1
Threshold 0
ThrOffN 0
ExtN 0
ExtF 0
ThrLightsN 1
AprLN 03
Strobes 5
VasiBarsN 8
VasiSpaceN 0
VasiDistN 1681
VasiSideN 125
VasiSlopeN 3.0
ThrLightsF 01
VasiBarsF 8
VasiSpaceF 0
VasiDistF 1681
VasiSideF 125
VasiSlopeF 3.0
)
EndA</pre>

Some caring must be payed to the parameter:

'''Heading'''

We need to take care of values of this parameter, because it can lead to frame rate drops and lights big-bulb effect in FSX-A and P3D.

== FS2002/FS2004/FSX+SP2(NOT ACCELERATION PACK) ==

The parameter '''Heading''' can be declared with any values from range 0 to 359, integer or decimal

== FSXA/P3D ==

The parameter '''Heading''' must be declared in range 0 to 179 and only decimal values are allowed (i.e. not integer values). For example, the Naples Capodichino runway has a 06/24 (056°/236° as per AIP Italy) orientation, so to declare it in the SCASM source file we need to do this trick:

'''Heading 58.01''' (we have +2° degrees of magnetical declination)

Note that i add a 0.01 degrees rotation to comply with the rule stated above. Declaring only 058.00 is not enough to prevent the "big-bulb" light effect that lead to dramatics drop in frame rates.

== Counter-effects ==
SCASM created runways have the problem that FSX/P3D AI traffic disappear when the "Ground cast scenery shadows" is activated in the preferences. No workaround exists at the moment.

[[Category:Tweaking]]
[[Category:Scenery_Design]]