Editing – Operation Flashpoint: Elite Category
Jump to navigation
Jump to search
Lou Montana (talk | contribs) m (Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 ") |
m (formatting) |
||
| Line 1: | Line 1: | ||
Operation Flashpoint: Elite has a built-in mission editor much like the original {{ofp}} PC version. You can build decent, relatively complex missions using only the in-game editor and the mission templates provided. The editor does have limitations when compared to the {{ofp}} PC version. | |||
Operation Flashpoint: Elite has a built-in mission editor much like the original | |||
=== Editing Limitations === | === Editing Limitations === | ||
The follow items are not supported by the in-game editor: | The follow items are not supported by the in-game editor: | ||
*Triggers | * Triggers | ||
*Synchronizing triggers/waypoints | * Synchronizing triggers/waypoints | ||
*Scripts | * Scripts | ||
*Customized user text, addons, or sounds | * Customized user text, addons, or sounds | ||
Recently | Recently {{ofp}} fans have imported missions created in the PC version to Operation Flashpoint: Elite. These missions are generally tweaked using the editor in the PC version and then can be hashed together to work on the XBox version. While this makes it a lot easier to construct the mission and add user text and scripts there are still some limitations. Most of these limitations concern the multiplayer missions. | ||
=== Limitations on converting | === Limitations on converting {{ofp}} PC missions to Operation Flashpoint: Elite === | ||
* Sounds are not supported (MP only) | |||
* .JPG and .GIFs are not supported, only .PAA and .PAC image file types are supported | |||
* Briefing files, scripts, and files residing on the host will not be transfered to clients. (think server-side scripting) | |||
* Fonts are limited and have changed to support TV format. | |||
* Building names have changed. | |||
* There is a problem with cutscenes created with triggers in that the trigger now has x,y,z coordinates and z seems to be set to 0 (height), thus most cutscenes are viewed from ground level. | |||
{{GameCategory|ofpe}} | |||
Revision as of 15:38, 26 April 2021
Operation Flashpoint: Elite has a built-in mission editor much like the original Operation Flashpoint PC version. You can build decent, relatively complex missions using only the in-game editor and the mission templates provided. The editor does have limitations when compared to the Operation Flashpoint PC version.
Editing Limitations
The follow items are not supported by the in-game editor:
- Triggers
- Synchronizing triggers/waypoints
- Scripts
- Customized user text, addons, or sounds
Recently Operation Flashpoint fans have imported missions created in the PC version to Operation Flashpoint: Elite. These missions are generally tweaked using the editor in the PC version and then can be hashed together to work on the XBox version. While this makes it a lot easier to construct the mission and add user text and scripts there are still some limitations. Most of these limitations concern the multiplayer missions.
Limitations on converting Operation Flashpoint PC missions to Operation Flashpoint: Elite
- Sounds are not supported (MP only)
- .JPG and .GIFs are not supported, only .PAA and .PAC image file types are supported
- Briefing files, scripts, and files residing on the host will not be transfered to clients. (think server-side scripting)
- Fonts are limited and have changed to support TV format.
- Building names have changed.
- There is a problem with cutscenes created with triggers in that the trigger now has x,y,z coordinates and z seems to be set to 0 (height), thus most cutscenes are viewed from ground level.
Subcategories
This category has the following 5 subcategories, out of 5 total.
Pages in category "Operation Flashpoint: Elite: Editing"
The following 4 pages are in this category, out of 4 total.