Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
Unique features it can have/share with others:
Buddy lazing
HUD SOI
HMCS SOI
SPI (Sensor Point of Interest)
Expanded networking mechanics for the SPIs to be shareable between all networked allies
Expanded weapons delivery options: spread of cluster munitions
HARM pod, vastly enhancing Anti-radiation weaponry
Assuming it isn't already, off-bore HMCS targeting for the SIDEarm
Hell, how about a near cut and paste inclusion of a Falcon 3/4/BMS style truly dynamic campaign, and the Durandal introduced to see just what effect shutting an airbase down has on a militaries success rates
I could go on
Given how completely different the engines for VTOL VR and Falcon are - to the point where asking for features from one to be "brought over" is de facto meaningless. Implementing a dynamic campaign engine ala Falcon BMS would require developing, implementing, and debugging the following components in VTOL VR:
At that point it's better to make a flight sim myself, which I'm doing.