The Raven One campaign for the F/A-18C Hornet is based on the bestselling novel of the same title. This campaign was developed with the active participation of author Kevin Miller and Vincent “Jell-O” Aiello, host of the Fighter Pilot Podcast. Both are retired U.S. Navy Hornet pilots, each with over 3,000 career flight hours and numerous overseas deployments.

The campaign faithfully recreates sorties from the book, while adding additional ones related to the action, for a total of 15 immersive, fully voiced-over missions. Each script was carefully checked by Kevin and Vincent to ensure the most realistic experience available in DCS.
​
Finally, the campaign utilizes innovative solutions, making in-game AI more responsive and predictive. It will also have a limited save-game capability during the campaign gameplay, as some missions may take two or more hours to complete.

Features:
- 15 story – driven missions
- Over 2200 recorded lines performed by over 50 voice actors
- All main characters from the “Raven One” novel
- Mission briefings supplementing and extending the ones described in the - book, written in close cooperation with Kevin Miller
- Highly detailed and realistic maps, kneeboards and other documents based on real-life counterparts
- All major types of missions: CAP, CAS, SEAD, ground and surface strikes, Alert – 7 and Alert – 30 launches, Sea Surface Search Control, air interceptions and others

And again, you take over the seat of the commander of a Mi-8MTV2.

You are Dmitry Tarasov - a young pilot, who climbs the career ladder and is faced with professional difficulties that your crew helps to overcome. The adventure story of the Crew campaign consists of two parts.
In the first part, you have to perform the following tasks:
Transport of vip-passengers on the Mi-8MTV2 in the configuration "Salon".
Work at Gazprom-Yuzhneft sites in the Krasnodar Territory.
Perform tasks in VFR and IFR.
Work on Gazprom-Arctic sites on the territory of the Bolshevik island, the Severnaya Zemlya archipelago (implemented on the Caucasus map).
In combat missions, you have to complete combat training flights with firing at ground targets.
Day and night flights.

To pass the Crew campaign, you will need to know about how avionics, radio and navigation equipment work. The ability to conduct sustainable helicopter control in all stages of flight is required. Skills in handling engine and instrument failures will also be useful to you.

Main features:
- 14 story missions
- 163 pages of detailed briefings and kneeboard
- 1320 triggers
- 1680 voiceovers

Known issues affecting mission design.

The team have been working hard to find and fix issues that will affect mission design and gameplay, and whilst many have been resolved, some did not make it in time to be included in the release build. Below is a summary of the current known issues in this early access release. We encourage all Open Beta players to report any and all bugs and issues that you encounter to our forum, as you are an invaluable piece of the puzzle, to enable us to move forwards and bring this truly breath-taking terrain out of early access.

Al-Dumayr – AI Taxi route to parking spot 15 & 16 passes through runway leading to possible collision.

Jirah – AI taxi route to parking spots 4 & 5 is incorrect, leading to possible collision.

Beirut – Collison issue when large aircraft (C-17, IL-76 etc) pass over road tunnel under runway 24/16. Small aircraft unaffected.

Eyn Shemer – Possible collision when multiple aircraft land in succession.

Damascus – AI taxi route issue when using parking spots 110 & 302 can lead to traffic jam.
- Aircraft taxiing from southern apron blocks all other taxi activity until in passes northern apron.

Mezzeh – Some aircraft & Helicopter parking spots are missing.
- Incorrect AI taxi routing to parking spots 17,18 & 19 leads to traffic jam.

Taftanaz – Possible collision when helicopter AI is taxiing.

Khalkhalah – Incorrect AI taxi from parking spots 19 & 19 can lead to collision.
- Possible AI collision with hangar 25.

Megiddo – Possible collision on runway when large AI group lands.
- Runway collision when using parking spot 10.
- Taxiway hold point is displaced onto runway.

Ramat David – Possible AI aircraft collision with small building between parking spot 37 & 36.
- 2 parking spots numbered 24.
- Parking spots 37-41 only available for helicopters (correct), but not marked as such.

Haifa – Possible traffic jam when many AI land in succession.

Marj Ruhayyil – AI uses taxiway for take-off and landing.
- Unable to place Flanker size aircraft on ramp parking spots 28-33.

Incirlik – Small chance of collisions during AI taxi.
- Aircraft at parking spots 100-109 are facing the wrong way.
- A-10C cannot be placed on parking 114-120 & 63-69.

Marj as Sulthan North & South and Qabr as Sitt – Helicopter AI touches down short of runway.
Fixed wing AI can be set to land at helicopter only bases.
Visual and collision issues with weapon impacts on bridges.
Some of the prepared SAM sites have uneven terrain, making unit placement difficult.
Fast mission creator is currently not functioning for Syria Terrain.

petsild napsal:

Zrcátka ukazují pohled na 6h, což je po tolika letech zázrak.

Hi all,

We have introduced some fixes and improvements to the Hornet's INS modeling in the 2.5.6.53756 Open Beta. Here's an overview:

1. Previously, in scenarios where GPS is not available, it was necessary to perform a fix (such as TACAN) to complete INS alignment. This is no longer the case - initial alignment position in GND alignment mode is provided by the position of waypoint 0 instead of GPS. Normally, waypoint 0 coincides with the aircraft's initial position at mission start, but it may be edited in the HSI/DATA subpage as necessary prior to alignment. In CV alignment mode, initial position is provided automatically via RF (CV SINS) or manually by the pilot (CV MAN).

2. Previously, INS alignment was not complete after 0.5 OK status was displayed in the HSI, and it was necessary to wait a little longer. This has been fixed: 0.5 OK status now indicates a complete and successful alignment.

3. Alignment times have been tweaked: GND and CV alignment take around 8 minutes now. Stored heading option has been introduced, which reduces alignment time to about 90 seconds. GPS alignment has been introduced which takes around 10 minutes and can be performed on the ground and in flight.

4. The stored heading alignment option can now be selected in the HSI when the INS switch is in the GND or CV position. As mentioned above, it reduces alignment time from about 8 minutes to about 90 seconds.

5. GPS alignment has been introduced. When GPS is available and INS quality is less than 0.5 OK, GPS alignment can be performed by placing in the INS switch in the IFA position and observing the HSI indicates IFA GPS and a countdown. This type of alignment takes about 10 minutes.

6. If the INS switch is moved to the NAV position without a complete alignment (ie status less than 0.5 OK), a crossed out ALGN advisory will be displayed in the left DDI.

7. POS/AINS (GPS aided INS) position keeping mode has been introduced. If GPS is available, once alignment is complete, the INS switch should be moved to and kept in the IFA position as per the normal startup checklist. This enables POS/AINS mode which can be verified in the top left corner in the HSI. In POS/AINS mode, GPS is used in conjunction with INS to provide the position of the aircraft. If GPS is not available, the INS switch should be moved to and kept in the NAV position.

8. If the INS switch is placed in the IFA position before INS alignment is complete, in-flight alignment mode will be entered. IFA GPS (with GPS available) or IFA RDR (with GPS not available) will be displayed in the HSI. In the first case, once alignment is complete, the IFA GPS legend will disappear and POS/AINS mode will be entered automatically. In the second case, once alignment is complete the INS switch should be moved back to the NAV position.

10. If GPS is available and the INS switch is in the NAV position, a P/INS advisory will be displayed. This notifies the pilot that GPS is available but it is not being used to augment the INS because the INS switch is in the NAV position, and that it should be moved to the IFA position to enable POS/AINS mode.

GPS is unavailable if the mission date is set before 1986 or the Hornet is in redfor. The second one can be bypassed with the "unrestricted satnav" option in the editor.

So for most cases, you'll have GPS. One quick way to check is to put the INS switch in NAV after your INS is aligned. If you get a P/INS advisory then GPS is available and you should move the switch to IFA.

AJaromir napsal:


Si je stačí jen správně natočit.

Baron napsal:Ako si natočím zrkadlo?

HMS Plymouth & HMS Invincible

Baron napsal:



Ako si natočím zrkadlo?