Sarix

Hi. As titled - when a target is designated on the RDR page, the TD box on the HUD may drift off target. This occurs in both SAM and STT. Please see the attached track for a demonstration of this issue. It is sped up to save time and keep the track short. Cheers. JF-17 TD.trk

Hi. Upon designating a target from RWS (and thus transitioning into SAM), target information is displayed in the upper part of the RDR page. The second entry (which I suspect to be target heading) is reversed - it increments target heading when the target turns counterclockwise. For example, a target heading west would show up as having "090" heading. Attached is the track demonstrating this issue. I accelerated the time in some places to speed up the process. Cheers. JF-17 target track rev.trk

As titled.nullnull

Hi. Does the Kiowa Warrior have any in-cockpit indications of crab angle and do the VSD/HSD indications compensate for crab for its heading indications/directions? Is there any other way other than regularly checking the VSD/HSD and correcting one's heading to keep the KW on a given track during long flights? Cheers.

Hi. As titled. When using the sight, the range arc displayed (normally in the first quadrant) has extra parts in the other quadrants if the weapon selector is kept in ВЫКЛ./УРС (OFF/MSL). Selecting other weapons and then returning to ВЫКЛ./УРС fixes this issue. Turning the sight off and back on has no impact on the issue. Steps to reproduce: 1. Take off. 2. Turn the sight on. 3. Observe that the range arc has extra sections starting from ~120 degrees clockwise where it is supposed to end, and extend all the way to "zero range" (see attached) 4. (If needed), manually set the range to observe that the extra sections rotate alongside the range arc. Overall only a ~120 degree section is not displayed. 4. Move the weapon selector out of ВЫКЛ./УРС. 5. Observe that the range arc is displayed normally. 6. Move the weapon selector back into ВЫКЛ./УРС. 7. Observe that the range arc is still displayed normally. Cheers.

Hi Kinkkujuustovoileipä, Thanks for the reply and understood. May I suggest adding a mention of this unreliability to the user manual? Cheers.

Hi. I've been enjoying the Kiowa so far, but one thing bugs me - the Heading Hold Mode. It's wonderful when I'm relatively slow (from hovering to 40 knots), but if I go to say 80 knots and engage HHM, it often would start oscillating in roll and swing the nose away from the initial heading. The user manual doesn't say anything about engaging the HHM at speed. Is it a me problem, or is it something with the helo? Cheers.

Much appreciate all the replies! Damn if actually "putting the bumper to use" would result in something like that...!

Hi. The modelviewer shows that the Mi-8 has a (hydraulically dampened?) tail bumper with a small piston-like structure near the tail end. This structure appears to be fixed in-place for the Mi-24P. If one tries to play all the animations for the 24P, the tail bumper does not move at all. Is the tail bumper on the real thing also fixed in-place, or is this an animation thing? Cheers.

I agree with the first, but the Hind's DISS does have the П light coming on when it goes into memory, unless it got shot up.

Hi. I came back from flying the Mi-24 (whose DISS deviation meter does reset to zero angle/no speed display after completing the self-test), and found that the Mi-8's DISS deviation meter doesn't reset itself to display zero deviation angle and no speed if I put the self-test switch to "work" (Р) from "test" (К). Is this intended or an issue? Cheers.

Hi. It appears that repeatedly spawning as a Viggen in MP will set the primary altimeter QFE to ~3040 hPa after one's fourth spawn. Leaving and rejoining the server resets the "counter" allowing three new spawns to occur without issue. Switching to other airframes in the same server play session will not help - the issue consistently occurs on the fourth Viggen spawn for a given player. Spawns are done through the Dynamic Slots system which may play a part too. EDIT: It appears that static slot spawning has the same issue. EDIT2: Single-player is also affected by this issue. EDIT3: Tested on Syria and Marianas, the issue doesn't appear on these maps. Cheers.

Hi. The internal gun appears to continue firing for approximately 0.4 seconds after letting go of the trigger, which the devs on Discord have stated is due to the gun spooling down. Attached is the trackfile in which I tapped the trigger multiple times. The wing-mounted gun pods stop firing almost immediately after trigger release, but the internal gun keeps firing for a short while. The internal gun always operates in auto-clear mode as the online manual have stated, however the external gun pods do not exhibit this "sticking" behavior with the auto-clear switch in auto-clear. 0.4 seconds for the internal gun is also inconsistent with the manual stating that it should fire 5-11 rounds after releasing the trigger (0.4 seconds correspond to ~25-40 rounds instead). Thus I suspect the spool-down behavior is incorrect either for the pod or the internal gun. If these are correct as-is please let me know as well! Cheers. Phantom gun spooldown.trk

Hi admiki, Interesting information. From memory - dry-cranking both engines sequentially takes roughly a minute and that's what I remember doing in the track. I also had a previous multiplayer session where no amount of dry-cranking saved me and I had to re-slot. But I'll check it out when I have time to launch DCS again. Cheers.

Hi. If the Mi-24P is cold-started from the ramp, and then shut down for repair without draining the remaining fuel from the engine, the engines will fail to start even after a dry-crank after repair. Attached is the track-file - I used acceleration in multiple places to speed up the process, otherwise it would be nearly 15 minutes long. Steps to reproduce: 1. Cold-start the Mi-24. 2. Break it by any means (I allowed the main rotor to hit the ground in the track). 3. Shut down the engines. Don't dry-crank them. 4. Request a repair from the ground crew and wait. 5. Dry-crank the engines. 6. Start the engines. 7. Profit - the engines won't start. Cheers. Mi-24P repair engines.trk

Hi BN, I am aware of the correct take-off procedure - I was told in the forum post linked above that trim reset logic happens when the gear handle is placed up, which is not the case here (trim reset happens when flaps are put from non-AUTO to AUTO after weight-off-wheels), hence the post. Seeing that it is marked correct as-is I'll take the team's word for it. Cheers.

Moved my extension on "weird stuff" to a separate thread. Cheers.

This could be tangentially related to https://forum.dcs.world/topic/345045-fcs-wow-mode-after-fm-update For the Hornet, when taking off, 22 degrees of ANU is commanded mid-takeoff roll, and after weight-off-wheels one can find the stabs being commanded to 19 degrees NU well into 30 degrees of AoA. I did not include further moments of the track, but after 19 degrees of NU STABs is seen, the STABs would be "eased off" to ~11 degrees NU, and is immediately fixed or at least alleviated by (via keybinds) cycling the flaps from AUTO to HALF/FULL and back into AUTO, with a different resulting STAB position. I have the FCS page on my right DDI - those of you watching the track should be able to see it as well. Hornet AUTO takeoff flaps cycled.trk One should find the stabilators returning to approximately 3 degs NU upon cycling the flaps in the track attached. Throughout the process the gear is not raised nor did the airspeed exceed 250 kts. To test the reset logic itself: I have attempted a normal takeoff, STABs are commanded to ~14-15 degs ANU. After WoW I put flaps to AUTO, gear handle up, and then put the gear handle down again. At ~180kts IAS, STAB is at 2-3 degs NU. Hornet normal takeoff 180kts.trk The same occurs without putting the gear handle up in the first place. Hornet normal takeoff no gear-up 180kts.trk Then - a second takeoff with flaps in AUTO. The aforementioned 22 degrees ANU STABs is observed with aggressive pitch-up tendencies. I used full stick forward to try to counter this tendency but there is not enough authority to counteract this. Cycled flaps from AUTO to FULL and back to AUTO. No gear up, ~180kts, STAB is also at 2-3 degs NU. Hornet AUTO takeoff 180kts.trk A third takeoff with flaps set to FULL would still have the STABs on 22 degrees ANU, but when flaps is put back into AUTO without gear up, STAB is observed at 2-3 degs NU at ~180kts. Hornet FULL takeoff 180kts.trk The gear handle appears to have no influence on the trim reset logic. Putting flaps from non-AUTO to AUTO does. Cheers.

Thanks for the investigation Ahmed! I'd like to extend on the "weird things" part, specifically taking off with AUTO flaps. The Hornet would aggressively command 22-degrees ANU for the stabilators starting at approximately 100kts and does not attempt to correct itself after weights are off wheels, leading to... amusing behaviors (continued pitch-up). However the FCS will correct itself and gradually revert stabs to 0 degrees if flaps are put to either HALF or FULL and then put back into AUTO. Tracks attached - hopefully it would be of use. Cheers. Hornet flapsup takeoff then flapsdown.trk Hornet flapsup takeoff.trk

Here's a track just in case. overlap.trk

As titled. When making a designation on the A/G RDR page for weapons delivery with the display frozen, when flying to the release with AGR as the ranging source the range number would show at the top of the display, overlapping the "FREEZE" text. Screenshot attached. Currently away from computer sadly so tracks will have to wait. Cheers

Reopening the thread. It appears that the HAS timer would reset itself after some seconds (in the tracks attached sometimes as long as 18 seconds sometimes as short as 4). Scanned targets appear to "jump around" the HAS page when scanning resets and there are multiple targets in seeker FoV. First track (HAS timer) shows the timer resetting itself. Second track (HAS jump) - I apologize for the length, it's a bit of a flight (~3 minutes?) - shows scanned targets jumping around the HAS page. Third track (HAS multiple) shows the HAS having issues scanning targets every reset - I had three or four SA-11 sites spread across 5nm firing at me and HAS could only detect the first two. Cheers. HAS timer.trk HAS jump.trk HAS multiple.trk

Much appreciate the insight. I did not "test" per se I just loaded the Mi-24 with some armaments (for weight) and tried to go full stick aft at ~200kph IAS and around 500m, at around 9-11 degs of rotor pitch to see if I could send myself into a deep stall. My impression prior to the patch was that if I go stick aft too quickly it sends the helo into a deep stall which is different from what I was seeing in this patch. Hence the confusion and the post. It seems that the helo is now much more "lenient" in the stall department.

It seems pretty hard now to push the Mi-24 into a deep stall. In my recent flights I can go full aft on the stick without much issue. How accurate is this compared to pre-update stall behaviors where you'd be "stuck" in a nose-up deep stall for a while? Cheers

Here is a track, hopefully it helps. It appears that when clicking on MSN XFER with XFER ALL, the jet would change to XFR WPN and transfer instead. XFER ALL.trk