BASys: Replaced Applicable-FSVersion for MSFS with MSFS2020, added MSFS2024

2024-05-25T17:20:27Z

Replaced Applicable-FSVersion for MSFS with MSFS2020, added MSFS2024

← Older revision		Revision as of 12:20, 25 May 2024
Line 4:		Line 4:

	{{Infobox-Applicable-FSVersion		{{Infobox-Applicable-FSVersion
	\| ~~MSFS~~ = true		\| MSFS2024 = unknown
			\| MSFS2020 = true
	\| FSXI = false		\| FSXI = false
	\| P3D5 = false		\| P3D5 = false

Mr LiamT: Created page on porting fsx missions to msfs

2021-11-14T14:01:24Z

Created page on porting fsx missions to msfs

New page

[[Category:Missions]]

{{:Ambox-Content-WIP}}

{{Infobox-Applicable-FSVersion
| MSFS = true
| FSXI = false
| P3D5 = false
| P3D4 = false
| P3D3 = false
| P3D2 = false
| P3D = false
| FSW = false
| FSXSE = false
| FSXA = false
| FSX = false
| FS2004 = false
| FS2002 = false
| XP11 = false
| XP10 = false
| XP9 = false
}}

You can open FSX mission scripts in MSFS.
You can find the .xml files in ''Mission Samples'' in the FSX SDK. Or you can use the fsx spb2xml tool to convert the .spb in the mission folder.

== Steps ==
Just make a mission project in msfs like normal. Copy the sounds folder if you want. Open the script editor. File>Open, open the fsx .xml. If it doesn't load, look in the console for a xml error.

[[File:MSFS_mission_script_fsx2msfs_1.png|400px]]<br>
[[File:MSFS_mission_script_fsx2msfs_2.png|400px]]

This will point to a specific part that isn't recognized. This means that part is not supported, so you have to delete it manually from the .xml . Keep in mind that you may have to replace this with a modern alternative later. When the script loads without error, you will see that all nodes are centered (because FSX had a different script editor):

[[File:MSFS_mission_script_fsx2msfs_3.png|400px]]

You will have to move the nodes to create a clear structure for yourself. I prefer to first seperate all unconnected parts:

[[File:MSFS_mission_script_fsx2msfs_4.png|800px]]

'''Remember to save frequently and make regular backups.'''

And then I sort them in roughly chronological order (you can use the numbers of the dialog and a video or your memory of the mission):

[[File:MSFS_mission_script_fsx2msfs_5.png|600px]]

Then I add comments to make the mission easier to understand:

[[File:MSFS_mission_script_fsx2msfs_6.png|600px]]

Now that we have a better idea of the mission, we can change some of the things that don't port over accurately.

== Updating [[MSFS_Mission_Script_-_Areas|Area rotation]] ==
In FSX, the rotation of areas was defined in the Area node itself, but now it has moved to the '''AttachedWorldPosition'''. So we need to move the rotation data. For every area and axis:
- Copy the rotation for the axis (e.g. '''Head''').
- Change it to 0 in the Area node.
- Go to AttachedWorldPosition and paste the rotation.

You may also have to change the position of areas at the airport, because the data may have changed.

== Updating [[Property Trigger|Property Triggers]] ==
PropertyTriggers used to have a child with the condition of the trigger. This has changed to a '''ReversePolishCondition''' in MSFS. Just click on the child condition. You will see the type like '''LessThan''' or '''Equal'''. If you click on it you will see LHS (left hand side) and RHS (right hand side). Remember the values. In the ReversePolishCondition, first fill in the LHS, then the RHS, and then the type.

You have to use C# operators like ''>'' and ''!=''.
Instead of, for example ''Simvar.AltitudeAGL'' you will have to use the new notation: ''(A:PLANE ALT ABOVE GROUND, feet)''.

Then remember remove the old child condition. Overall it will look like this:

[[File:MSFS_mission_script_fsx2msfs_7.png|300px]]

== [[MSFS_Mission_Script_-_Library_Objects|LibraryObject]] ==
The old references to FSX LibraryObjects won't work, because the objects are not included in msfs. You can add a modellib to your mission package, that contains the models you need. Then you can reference them with the GUID.

== [[MSFS_Mission_Script_-_Sim_Objects|SimObjects]] ==
AI planes will need to be updated with an MSFS airplane in the [[:Category:MSFS_Mission_Script|script (.xml)]] and [[Flight_file_(MSFS)|flight file (.FLT)]]. The AI may also need to be remade.

Flight file (.FLT):

'''FSX → MSFS'''

[[File:MSFS_mission_script_fsx2msfs_8.png|1000px]]

Script file (.xml):

'''FSX → MSFS'''

[[File:MSFS_mission_script_fsx2msfs_9.png|1000px]]

== Example ==
You can see an example by downloading the project files of [https://flightsim.to/file/19596/fsx-mission-caribbean-landing my Caribbean landing port].

{{Template:Navbox-Mission-Creation-MSFS}}

Porting FSX Missions to MSFS - Revision history

BASys: Replaced Applicable-FSVersion for MSFS with MSFS2020, added MSFS2024

Mr LiamT: Created page on porting fsx missions to msfs