xxJohnxx

In my opinion the yaw spins are not caused by the autopilot but rather by being overloaded. If you have a full weapons load and full fuel you are overweight and the helicopter still flies, but the tail rotor has too little authority to overcome the yaw produced by the main rotor at high blade angles required for hover. During forward flight both the lower blade angle and the aerodynamic stability of the tail cause reduced tail rotor load, and therefore it can fly even when overweight. However, as soon as speed is reduced, yaw becomes uncontrollable.

Hi Rabies, Thanks for letting me know. I was wondering about that as well while I was watching the finished video. Seems I skipped that step! I added a comment to the video. Best regards, Jonathan

Maybe this video can help:

Hi, I'd like to share my tutorials for the Mi-24P Hind. Part 1 - Introduction Part 2 - Cockpit-Tour and Startup Part 3 - Firing Shturm ATGM using Petrovitch AI Part 4 - Firing Shturm ATGM without using Petrovitch AI More videos to come! Best regards, John

I kinda expect that to be possible in DCS as well. I mean we already have the Garmin NS430 in the sim.

I agree. First time lookin at the DCS 430, I was a bit confused on what that symbol was actually showing. On first glance it just looks like a weird blob. Especially with the map "north-up" it is very hard to tell which direction you are actually facing... This is one of the pictures from the ED Shop page for the GNS 430 (https://www.digitalcombatsimulator.com/upload/iblock/ffc/Screen_170216_164755.jpg) and you can hardly make out the plane-symbol as such. If you compare that to the picture from sdflyer, that is taken from even further away, the diffrence becomes easily noticable.

This problem also extends to the map display. When selecting "Track UP" the map is infact "Heading UP", which is incorrect.

After entering a waypoint identifier and pressing ENT once, the "Activate?" prompt shows up. Correct behaviour for the GNS 430 would be, that the "Activate?" text starts blinking until ENT is pressed. However, in the DCS: NS 430, the "Activate?" text is not blinking, but instead the waypoint identifier entry line is blinking. See the attached picture with the "Activate?" text visible and the blinking "cursor" in the first line. Small bug, but would be nice to see that fixed too!

The "Direct-To button" seems to be missing two of the key functionalities: 1) Whenever a Airport Identifier, Waypoint or Navigation Aid (from now on called waypoint) is highlited (blinking), like for example in the NRST Page, pressign the "Direct-To button" should bring up the "Direct-To Page" with the previously highlited waypoint allready selected. However, with the DCS: NS 430, pressing the "Direct-To button" while having any waypoint selected does bring up the "Direct-To page", however, there is no waypoint preselected. This makes the NRST page quite useless, as you still have to enter the waypoint identifiers manually. 2) After setting a Direct-To route, bringing up the "Direct-To page" (without having any waypoint identifier selected (see point 1)) should show the current Direct-To waypoint, allowing the operator to quickly re-activate the same waypoint, plotting a new Direct-To route. This however, is not the case in the DCS: NS 430. Bringing up the "Direct-To page" while allready flying directly to a waypoint, shows an empty Direct-To waypoint, forcing you to re-enter the same waypoint you are allready heading too. This functionality is immensely useful while flying VFR and only using the NS as a loose direction reference and is desinged like that in every Garmin navigation system.

The "NRST Airport" page should list 9 airports, showing 3 at a time in a scrollable list. However, while the scrollbar is visible, it is not possible to scroll down to entries 4-9. The other NRST pages (NDBs, WPTs, VORs) scroll just fine.

Found a small issue with the NS 430: On the NAV Page 1, the TRK indicator actually shows heading instead of track. The NS 430 can not know the current heading of the helicopter because it lacks a compass. Track however is calculated by GPS position and is independed of helicopter orientation. Easily reproducable by flying forward and adding some rudder. Or by flying the helicopter in reverse.

Haha, nice! Thanks for sharing! I heard about "Runway 34", but I didn't know about the Heligrill. Will check it out once I move to Zurich! Best regards, John

Welcome to DCS and the forums and thanks for the kind words! Indeed, to make this mission a bit more challenging (so that one has actually use the radar :smilewink:) I have hidden the units in the mission editor. As Rudel mentioned, you can turn them back visible if you want to. If your radar screen is illumiated, do you actually see the sweep going across? If not make sure that you are in the proper A1 radar mode. In mode A0, the radar will be off and in mode A2 the radar will show a magnified B-Scope (zommed square representation instead of the arc) that is positioned arround the current target point. Best regards, John

As a followup to the previous video, in todays tutorial we are taking a look on how QNH, QFE and the radar altimeter work for targeting in the Viggen. Using QNH, QFE and the radar altimeter: Mission:Download Enjoy! :thumbup:

I would assume that this is not intended behaviour. It makes sense for doing a navigation update (on a B waypoint) where the new position is close to the waypoint. However, as you have experienced, this is quit annyoing when trying to desingate a target (especially BX waypoints that have not been set yet). Often the cursor appears somewhere off-screen and you have to guess in which direction to slew it so that it re-appears on the radar screen. I have seen this mentioned multiple times (also mentioned it here and there myselfe), however so far I am not sure if this is intended or indeed a bug. Maybe someone able to read the Swedish manuals (@renhanxue or someone else?) is able to shed some light on the real behaviour.

Thank you for the information. Could you provide a link?

Yes. If you have a 3 position switch it is a bit easier. You can have it set up that in the forward position it is in T0, in the middle it is in T1 and pulled back it is in TV. This is the closest that you will get to the functionality without using an actual 3 position trigger.

I think he is refering to a bug that caused a 90° at Bx7. This was/is happening when you use code 800002 for example. Has been happening since release.

While this is true in the real world in standard conditions (1 hPa = 8.3m) I found that there seems to be a diffrent pressure per meter change in DCS. Some testing I did showed that for a point at 2000m above sea level, the ratio seems to be more like: 1hPa =9.3m. Wondering why that is the case. Maybe a DCS quirk?

Thank you all for your kind words! Very appriciated! :thumbup: Just got arround to finish another video I was wanting to do for some time now: Ingame Flight Planning This video shows on how to use the ingame F-10 map for planning a flight without the use of the mission editor. Enjoy! :pilotfly:

The basics: More advanced stuff:

I wanted to videos about the bombing stuff, however, I caught the flu and spent majority of the last couple days in bed. Once fully recovered I will get back to the tutorials:pilotfly:

Looks great!

Will apparently ship during February!