Difference between revisions of "GTNB Pharos"
m (→Name origin: oops) |
(→Statistics) |
||
(One intermediate revision by one other user not shown) | |||
Line 15: | Line 15: | ||
==Performance:== | ==Performance:== | ||
===Statistics=== | ===Statistics=== | ||
− | {{Ship Stats|Navigation Buoy|Unknown|N/A|N/A|N/A|N/A|100|N/A|}} | + | {{Ship Stats|Navigation Buoy|Unknown|N/A|N/A|N/A|N/A|N/A|100|N/A|}} |
===Armaments=== | ===Armaments=== | ||
Line 42: | Line 42: | ||
==Veteran Comments== | ==Veteran Comments== | ||
− | {{Comment|}} | + | {{Comment|Due to having the "no_collide" flag enabled, Pharos beacons cannot be interacted with in any meaningful way (shots pass through it; ships cannot collide with it) without mission-specific scripting.}} |
[[Category:Ship]] | [[Category:Ship]] |
Latest revision as of 01:17, 10 October 2012
| ||||||||
|
The GTNB Pharos is a Terran-designed navigation buoy. The Pharos serves as a distress beacon for ships that are stranded in remote locations. When used in conjunction with other navigation buoys in the vicinity, the Pharos can also serve as a waypoint for ships to fly to, or otherwise a marker to designate the boundary of a hazardous area.
Contents
Description:
The GTNB Pharos |
---|
FS2 Tech Room Description
None
Developer Notes
They mark things.
Name origin
Historically, the Pharos of Alexandria was a lighthouse that guided sailors into the harbor of Alexandria, Egypt. This is paralleled by its role in FreeSpace, in which it serves as a navigational aid.
Performance:
Statistics
Type | Navigation Buoy |
Manufacturer | Unknown |
Maneuverability | N/A |
Yaw, Pitch, Roll | N/A s |
Max Velocity | N/A ms-1 |
Max Afterburner Velocity | N/A ms-1 |
Armor | N/A |
Hitpoints | 100 |
Shields | N/A |
Length | m |
Armaments
None
Modding Resources
The GTNB Pharos in FS2_Open 3.6.10 |
---|
Retail:
- $POF File: ???
- Textures: ???
MediaVP 3.6.10:
- $POF File: ???
- Textures: ???
History
Proposed by: ??? on ???
First WIP Post: ??? on ???
First In-Game Model: ??? on ???
Completed In-Game Model: ??? on ???
Final Corrections: ??? on ???