SketchUp Ground Polygons - Revision history

BASys: Infobox-Applicable-FSVersion added.

2014-06-29T21:39:31Z

Infobox-Applicable-FSVersion added.

← Older revision		Revision as of 16:39, 29 June 2014
Line 1:		Line 1:
			{{Infobox-Applicable-FSVersion
			\| P3D2 = true
			\| P3D = true
			\| FSXI = true
			\| FSXA = true
			\| FSX = true
			\| FS2004 = true
			\| FS2002 = false
			\| FS2000 = false
			\| FS98 = false
			}}
	SketchUp is often overlooked as a legitimate design tool for Flight Simulator, largely because it lacks integration with the ACES toolset. While that inhibits some important functionality, namely in terms of material attributes, SketchUp (SU) offers some powerful features that are simply not found in other 3D modeling programs. The feature that this article will focus on involves SU's ability to integrate with Google Earth and include position data with exported models. Another very important feature is SU's ability to work with most relevant file formats, including Photoshop .psd files. Bear in mind that SU has no native capacity to manipulate .DDS files; if that is your intended format for completed textures, you will have to make allowances. I use FSXA, Photoshop CS 5.1 and SketchUpPro 2013. Many of these techniques will work with other versions and software, but it would be up to the user to make the required adjustments.		SketchUp is often overlooked as a legitimate design tool for Flight Simulator, largely because it lacks integration with the ACES toolset. While that inhibits some important functionality, namely in terms of material attributes, SketchUp (SU) offers some powerful features that are simply not found in other 3D modeling programs. The feature that this article will focus on involves SU's ability to integrate with Google Earth and include position data with exported models. Another very important feature is SU's ability to work with most relevant file formats, including Photoshop .psd files. Bear in mind that SU has no native capacity to manipulate .DDS files; if that is your intended format for completed textures, you will have to make allowances. I use FSXA, Photoshop CS 5.1 and SketchUpPro 2013. Many of these techniques will work with other versions and software, but it would be up to the user to make the required adjustments.

=rk= at 12:51, 18 March 2014

2014-03-18T12:51:18Z

← Older revision		Revision as of 07:51, 18 March 2014
Line 13:		Line 13:


	Now locate your .psd file and import it directly into the SU scene. Upon importing, you will have to stretch and rotate it to fit exactly over it's coverage area shown in the Google Earth snapshot:		Now locate your .psd file and import it directly into the SU scene. Upon importing, you will have to stretch and rotate it to fit exactly over it's coverage area shown in the Google Earth snapshot. I should make a note here that the crisp letters were derived by editing the .psd file before saving:

	[[File:Positioned.JPG]]		[[File:Positioned.JPG]]

=rk= at 21:22, 17 March 2014

2014-03-17T21:22:22Z

← Older revision		Revision as of 16:22, 17 March 2014
Line 18:		Line 18:


	After that you can unlock and delete the Google Earth snapshot. ~~previously~~ I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In that program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and using the check box will prevent flickering near the middle of the large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.		After that you can unlock and delete the Google Earth snapshot. Previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In that program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and using the check box will prevent flickering near the middle of the large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.
	Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your intended scenery library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.		Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your intended scenery library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.
	Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is somewhat off and the customs box looks exactly like what it is, added:		Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is somewhat off and the customs box looks exactly like what it is, added:

Rhumbaflappy at 21:07, 17 March 2014

2014-03-17T21:07:29Z

← Older revision		Revision as of 16:07, 17 March 2014
Line 4:		Line 4:

	In our example, we have a customs box with a dubious looking Dash-8 awaiting inspection. The photo ground .bgl depicts the dashed outline of the box well enough, but only hints at the contained text:		In our example, we have a customs box with a dubious looking Dash-8 awaiting inspection. The photo ground .bgl depicts the dashed outline of the box well enough, but only hints at the contained text:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/e/e6/~~Customs.JPG]
			[[File:Customs.JPG]]


	Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you have an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:		Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you have an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/6/62/~~Position.JPG]
			[[File:Position.JPG]]


	Now locate your .psd file and import it directly into the SU scene. Upon importing, you will have to stretch and rotate it to fit exactly over it's coverage area shown in the Google Earth snapshot:		Now locate your .psd file and import it directly into the SU scene. Upon importing, you will have to stretch and rotate it to fit exactly over it's coverage area shown in the Google Earth snapshot:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/3/37/~~Positioned.JPG]
			[[File:Positioned.JPG]]


	After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In that program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and using the check box will prevent flickering near the middle of the large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.		After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In that program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and using the check box will prevent flickering near the middle of the large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.
	Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your intended scenery library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.		Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your intended scenery library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.
	Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is somewhat off and the customs box looks exactly like what it is, added:		Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is somewhat off and the customs box looks exactly like what it is, added:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/c/c7/~~Placed.JPG]
			[[File:Placed.JPG]]


	No problem - and this is one of the neat things about working with these three programs. Go back to the original .psd and open it in Photoshop. Here I have taken the "Hue/Saturation" adjustment of Photoshop and moved one value to the extreme. Now export this to .dae; import to the Ground Polygon Wizard, convert, then copy the compiled texture to the working texture folder. Since the texture mapping is unchanged, the ground polygon will have the new textures next time you open Flight Simulator. This version seems to make a nice representation, close enough, and one could spend the effort to get a virtually seamless match:		No problem - and this is one of the neat things about working with these three programs. Go back to the original .psd and open it in Photoshop. Here I have taken the "Hue/Saturation" adjustment of Photoshop and moved one value to the extreme. Now export this to .dae; import to the Ground Polygon Wizard, convert, then copy the compiled texture to the working texture folder. Since the texture mapping is unchanged, the ground polygon will have the new textures next time you open Flight Simulator. This version seems to make a nice representation, close enough, and one could spend the effort to get a virtually seamless match:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/8/8b/~~Edited.JPG]
			[[File:Edited.JPG]]


	Now we can again examine our ground polygon in sim:		Now we can again examine our ground polygon in sim:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/6/6b/~~New.JPG]
			[[File:New.JPG]]


	Looking closer, we see that the letters are perfectly legible:		Looking closer, we see that the letters are perfectly legible:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/c/c3/~~Ground.JPG]
			[[File:Ground.JPG]]


	Even closer, we see that the Dash-8's tires are fully exposed. If they we partially obscured, we could slightly adjust the polygon elevation to compensate:		Even closer, we see that the Dash-8's tires are fully exposed. If they we partially obscured, we could slightly adjust the polygon elevation to compensate:
	[~~http~~:~~//www.fsdeveloper.com/wiki/images/e/ea/~~Cockpit.JPG]
			[[File:Cockpit.JPG]]


	This substitution technique is not limited to edited textures. Say, as an example, you selected an area of your model to apply a night texture, or for another reason, the texture mapping on your edited model no longer matched the model that has already been placed in scenery. Using the LOD tool of Model Converter X, one can delete the physical model and retain the GUID and placement data. Then by importing the edited model at the same LOD, then exporting as a scenery .bgl, you will see your new model in place of the old one within sim, so long as you remembered to export the new textures to the active texture folder.		This substitution technique is not limited to edited textures. Say, as an example, you selected an area of your model to apply a night texture, or for another reason, the texture mapping on your edited model no longer matched the model that has already been placed in scenery. Using the LOD tool of Model Converter X, one can delete the physical model and retain the GUID and placement data. Then by importing the edited model at the same LOD, then exporting as a scenery .bgl, you will see your new model in place of the old one within sim, so long as you remembered to export the new textures to the active texture folder.

	[[category:Scenery Design]]		[[category:Scenery Design]]

=rk= at 17:52, 17 March 2014

2014-03-17T17:52:39Z

← Older revision		Revision as of 12:52, 17 March 2014
Line 29:		Line 29:
	[http://www.fsdeveloper.com/wiki/images/e/ea/Cockpit.JPG]		[http://www.fsdeveloper.com/wiki/images/e/ea/Cockpit.JPG]

	This substitution technique is not limited to edited textures. Say, as an example, you selected an area of your model to apply a night texture, or for another reason, the texture mapping on your edited model no longer matched the model that has already been placed in scenery. Using the LOD tool of Model Converter X, one can delete the physical model and retain the GUID and placement data. Then by importing the edited model at the same LOD, then exporting as a scenery .bgl, you will see your new model in place of the old one within sim, so long as you remembered to export the textures to the active texture folder.		This substitution technique is not limited to edited textures. Say, as an example, you selected an area of your model to apply a night texture, or for another reason, the texture mapping on your edited model no longer matched the model that has already been placed in scenery. Using the LOD tool of Model Converter X, one can delete the physical model and retain the GUID and placement data. Then by importing the edited model at the same LOD, then exporting as a scenery .bgl, you will see your new model in place of the old one within sim, so long as you remembered to export the new textures to the active texture folder.

	[[category:Scenery Design]]		[[category:Scenery Design]]

=rk= at 17:49, 17 March 2014

2014-03-17T17:49:54Z

← Older revision		Revision as of 12:49, 17 March 2014
Line 12:		Line 12:
	[http://www.fsdeveloper.com/wiki/images/3/37/Positioned.JPG]		[http://www.fsdeveloper.com/wiki/images/3/37/Positioned.JPG]

	After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In ~~htat~~ program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and will prevent flickering near the middle of a large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.		After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In that program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and using the check box will prevent flickering near the middle of the large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.
	Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your ~~destination~~ library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.		Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your intended scenery library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.
	Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is ~~clearly~~ off and the customs box looks exactly like what it is, ~~something~~ added:		Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is somewhat off and the customs box looks exactly like what it is, added:
	[http://www.fsdeveloper.com/wiki/images/c/c7/Placed.JPG]		[http://www.fsdeveloper.com/wiki/images/c/c7/Placed.JPG]

	No problem - and this is one of the neat things about working with these three programs. Go back to the original .psd and open it in Photoshop. Here I have taken the "Hue/Saturation" adjustment of Photoshop and moved one value to the extreme. It seems to make a nice representation, close enough, and one could spend the effort to get a virtually seamless match:		No problem - and this is one of the neat things about working with these three programs. Go back to the original .psd and open it in Photoshop. Here I have taken the "Hue/Saturation" adjustment of Photoshop and moved one value to the extreme. Now export this to .dae; import to the Ground Polygon Wizard, convert, then copy the compiled texture to the working texture folder. Since the texture mapping is unchanged, the ground polygon will have the new textures next time you open Flight Simulator. This version seems to make a nice representation, close enough, and one could spend the effort to get a virtually seamless match:
	[http://www.fsdeveloper.com/wiki/images/8/8b/Edited.JPG]		[http://www.fsdeveloper.com/wiki/images/8/8b/Edited.JPG]

=rk= at 17:43, 17 March 2014

2014-03-17T17:43:21Z

← Older revision		Revision as of 12:43, 17 March 2014
Line 6:		Line 6:
	[http://www.fsdeveloper.com/wiki/images/e/e6/Customs.JPG]		[http://www.fsdeveloper.com/wiki/images/e/e6/Customs.JPG]

	Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you ~~hae~~ an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:		Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you have an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:
	[http://www.fsdeveloper.com/wiki/images/6/62/Position.JPG]		[http://www.fsdeveloper.com/wiki/images/6/62/Position.JPG]

=rk= at 17:41, 17 March 2014

2014-03-17T17:41:28Z

← Older revision		Revision as of 12:41, 17 March 2014
Line 1:		Line 1:
	SketchUp is often overlooked as a legitimate design tool for Flight Simulator, largely because it lacks integration with the ACES toolset. While that inhibits some important functionality, namely in terms of material attributes, SketchUp (SU) offers some powerful features that are simply not found in other 3D modeling programs. The feature that this article will focus on involves SU's ability to integrate with Google Earth and include position data with exported models. Another very important feature is SU's ability to work with most relevant file formats, including Photoshop .psd files. Bear in mind that SU has no native capacity to manipulate .DDS files; if that is your intended format for completed textures, you will have to make allowances. I use FSXA, Photoshop CS 5.1 and SketchUpPro 2013. Many of these techniques will work with other versions and software, but it would be up to the user to make the required adjustments.		SketchUp is often overlooked as a legitimate design tool for Flight Simulator, largely because it lacks integration with the ACES toolset. While that inhibits some important functionality, namely in terms of material attributes, SketchUp (SU) offers some powerful features that are simply not found in other 3D modeling programs. The feature that this article will focus on involves SU's ability to integrate with Google Earth and include position data with exported models. Another very important feature is SU's ability to work with most relevant file formats, including Photoshop .psd files. Bear in mind that SU has no native capacity to manipulate .DDS files; if that is your intended format for completed textures, you will have to make allowances. I use FSXA, Photoshop CS 5.1 and SketchUpPro 2013. Many of these techniques will work with other versions and software, but it would be up to the user to make the required adjustments.

	Arno published ~~and~~ excellent tutorial about using SketchUp to model your house in Flight Simulator. It is assumed that you are familiar with that process and we will start by expanding upon the ability to geographically locate your model. In this article we are going to again invoke the geographic placement tool of SU and this time we will use it to create and place a ground polygon. For this particular demonstration, we have access to high quality ground images of the area we want to improve. You may ask why we don't simply compile the images into a photo derived scenery .bgl; we could, except the quality is so high, it would take days to compile and the photo ground .bgl would be too immense to be practical. Another very good way to create high quality ground polygons would be to use the tool found in Airport Design Editor, the difference being that these ground .bgl's are able to be manipulated using a scenery placement program. I use Instant Scenery 3 and within the Flight Simulator interface, I am able to precisely place, observe and adjust these ground polygons. I can use the "line of objects" function to make a hold short line from a single "element" and I am able to minutely adjust elevation to both expose tires and conceal lower layers.		Arno published an excellent tutorial about using SketchUp to model your house in Flight Simulator. It is assumed that you are familiar with that process and we will start by expanding upon the ability to geographically locate your model. In this article we are going to again invoke the geographic placement tool of SU and this time we will use it to create and place a ground polygon. For this particular demonstration, we have access to high quality ground images of the area we want to improve. You may ask why we don't simply compile the images into a photo derived scenery .bgl; we could, except the quality is so high, it would take days to compile and the photo ground .bgl would be too immense to be practical. Another very good way to create high quality ground polygons would be to use the tool found in Airport Design Editor, the difference being that these ground .bgl's are able to be manipulated using a scenery placement program. I use Instant Scenery 3 and within the Flight Simulator interface, I am able to precisely place, observe and adjust these ground polygons. I can use the "line of objects" function to make a hold short line from a single "element" and I am able to minutely adjust elevation to both expose tires and conceal lower layers.

	In our example, we have a customs box with a dubious looking Dash-8 awaiting inspection. The photo ground .bgl depicts the dashed outline of the box well enough, but only hints at the contained text:		In our example, we have a customs box with a dubious looking Dash-8 awaiting inspection. The photo ground .bgl depicts the dashed outline of the box well enough, but only hints at the contained text:

=rk= at 17:40, 17 March 2014

2014-03-17T17:40:23Z

← Older revision		Revision as of 12:40, 17 March 2014
Line 7:		Line 7:

	Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you hae an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:		Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you hae an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:
	[~~[File~~:Position.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/6/62/Position.JPG]

	Now locate your .psd file and import it directly into the SU scene. Upon importing, you will have to stretch and rotate it to fit exactly over it's coverage area shown in the Google Earth snapshot:		Now locate your .psd file and import it directly into the SU scene. Upon importing, you will have to stretch and rotate it to fit exactly over it's coverage area shown in the Google Earth snapshot:
	[~~[File~~:Positioned.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/3/37/Positioned.JPG]

	After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In htat program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and will prevent flickering near the middle of a large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.		After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In htat program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and will prevent flickering near the middle of a large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.
	Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your destination library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.		Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your destination library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.
	Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is clearly off and the customs box looks exactly like what it is, something added:		Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is clearly off and the customs box looks exactly like what it is, something added:
	[~~[File~~:Placed.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/c/c7/Placed.JPG]

	No problem - and this is one of the neat things about working with these three programs. Go back to the original .psd and open it in Photoshop. Here I have taken the "Hue/Saturation" adjustment of Photoshop and moved one value to the extreme. It seems to make a nice representation, close enough, and one could spend the effort to get a virtually seamless match:		No problem - and this is one of the neat things about working with these three programs. Go back to the original .psd and open it in Photoshop. Here I have taken the "Hue/Saturation" adjustment of Photoshop and moved one value to the extreme. It seems to make a nice representation, close enough, and one could spend the effort to get a virtually seamless match:
	[~~[File~~:Edited.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/8/8b/Edited.JPG]

	Now we can again examine our ground polygon in sim:		Now we can again examine our ground polygon in sim:
	[~~[File~~:New.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/6/6b/New.JPG]

	Looking closer, we see that the letters are perfectly legible:		Looking closer, we see that the letters are perfectly legible:
	[~~[File~~:Ground.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/c/c3/Ground.JPG]

	Even closer, we see that the Dash-8's tires are fully exposed. If they we partially obscured, we could slightly adjust the polygon elevation to compensate:		Even closer, we see that the Dash-8's tires are fully exposed. If they we partially obscured, we could slightly adjust the polygon elevation to compensate:
	[~~[File~~:Cockpit.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/e/ea/Cockpit.JPG]

	This substitution technique is not limited to edited textures. Say, as an example, you selected an area of your model to apply a night texture, or for another reason, the texture mapping on your edited model no longer matched the model that has already been placed in scenery. Using the LOD tool of Model Converter X, one can delete the physical model and retain the GUID and placement data. Then by importing the edited model at the same LOD, then exporting as a scenery .bgl, you will see your new model in place of the old one within sim, so long as you remembered to export the textures to the active texture folder.		This substitution technique is not limited to edited textures. Say, as an example, you selected an area of your model to apply a night texture, or for another reason, the texture mapping on your edited model no longer matched the model that has already been placed in scenery. Using the LOD tool of Model Converter X, one can delete the physical model and retain the GUID and placement data. Then by importing the edited model at the same LOD, then exporting as a scenery .bgl, you will see your new model in place of the old one within sim, so long as you remembered to export the textures to the active texture folder.

	[[category:Scenery Design]]		[[category:Scenery Design]]

=rk= at 17:35, 17 March 2014

2014-03-17T17:35:57Z

← Older revision		Revision as of 12:35, 17 March 2014
Line 4:		Line 4:

	In our example, we have a customs box with a dubious looking Dash-8 awaiting inspection. The photo ground .bgl depicts the dashed outline of the box well enough, but only hints at the contained text:		In our example, we have a customs box with a dubious looking Dash-8 awaiting inspection. The photo ground .bgl depicts the dashed outline of the box well enough, but only hints at the contained text:
	[~~[File~~:Customs.~~jpg]~~]		[http://www.fsdeveloper.com/wiki/images/e/e6/Customs.JPG]

	Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you hae an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:		Our first step is to create the image to cover and effectively replace the customs box. I tried to cut the border right through the dashed lines to use the contrast to obscure the transition between my ground polygon and the underlying photo .bgl. Once you hae an acceptable image, save it in .psd format. Next open SU and use the Add Location function to get a Google Earth snapshot of the area you intend to modify:
Line 13:		Line 13:

	After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In htat program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and will prevent flickering near the middle of a large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.		After that you can unlock and delete the Google Earth snapshot. previously I wrote that you must highlight your imported .psd and select "use as texture," however this is not required. Now you can export your "model" in Collada .dae format to convert it using Model Converter X. In htat program, open the Ground Polygon Wizard and import the .dae. Un-check the slice and group polygons boxes, unless your polygon is exceptionally large. The slice polygons check box is useful if your polygon is a runway or something large that may be subject to Earth curvature and will prevent flickering near the middle of a large polygon. Bear in mind that the consequence is the polygon will have many shards that have to be aligned manually using this technique.
	Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your destination library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.		Remember to also select the convert textures check box and define a saved location. After clicking convert, use Model Converter X to import the compiled .bgl, then use the scenery objects editor to export all the contained models in .mdl format. Now use Model Converter X to open your destination library .bgl, or import one of the exported models; then use the scenery objects editor to add any remaining models. Now export this as a scenery .bgl and you are ready to place within the Flight Simulator interface.
	Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is clearly off and the customs box looks exactly like what it is, something added:		Here we see the ground polygon in place under the Dash-8. The words are clearly legible, even from this zoom level, but the color is clearly off and the customs box looks exactly like what it is, something added:
	[[File:Placed.jpg]]		[[File:Placed.jpg]]