Quati

Once you see it, you can't unseen it.

It was just a mission that I made for myself to learn to use the direction finding radios. The idea was to find a crash/landing site with a beacon signal using the R-852 and before reaching the area the signal is gone. I would then have to find the moving truck with the stolen cargo "listening" (because you cannot hear and find the direction of the signal at the same time) the communication of the truck and it's hideout.

Not sure if this is the issue with you, but while trying to set a couple vehicles transmitting VHF AM for a "recover stolen cargo/spacecraft" mission for the Hind using the R-852 Radio Receiver + ARK-U2 Direction finder I notice that; if you are a RED Coalition Hind; if the vehicles transmitting are BLUE, you can get a signal on ARK-U2 (and the needle works) but no sound (even with the ARK-U2 switch on COMMS and the radio suite rotary knob on ARK). if the transmitting vehicles are also RED, you get the signal and the sound (with the ARK-U2 switch on COMMS and the radio suite rotary knob on ARK).

I played two times and didn't have this issue. I wish there was a F10 command to tell 27 that I'm ready to taxi also, so I could start my helicopter in my pace. Also think the cruise speed of 27 should be lower. I had to keep my engines above the cruise setting to try to catch 27 and only make it in formation with him near the FARP descend phase.

Like that

# -------------- 20230604-011240 -------------- DCS/2.8.5.40170 (x86_64; MT; Windows NT 10.0.19044) E:\Simuladores\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Mi-24P\bin\CockpitMi24.dll # C0000005 ACCESS_VIOLATION at 00007ffec732ef51 00:00000000 SymInit: Symbol-SearchPath: 'E:\Simuladores\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'Fernando' OS-Version: 10.0.19044 () 0x100-0x1 0x000000000012ef51 (CockpitMi24): cockpit::Mi24::ccMainPanel_Mi24::wheelBrakes + 0xD951 0x000000000013faee (CockpitMi24): cockpit::Mi24::ccMainPanel_Mi24::wheelBrakes + 0x1E4EE 0x000000000020d4ae (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E 0x0000000000003b53 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x4C3 0x000000000000405e (World): wSimCalendar::DoActionsUntil + 0x1FE 0x0000000000876858 (DCS): SW + 0x3E0128 0x0000000000876521 (DCS): SW + 0x3DFDF1 0x000000000089796a (DCS): SW + 0x40123A 0x0000000000855c74 (DCS): SW + 0x3BF544 0x0000000000856b45 (DCS): SW + 0x3C0415 0x000000000236ca60 (DCS): AmdPowerXpressRequestHighPerformance + 0xFBDA5C 0x0000000000c56962 (DCS): SW + 0x7C0232 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14 Just had the same on CTD on RotorHeads. When zooming all the way and asking for Petro to scan the area.

I had 3 times when on Rotorheads server. Just like you, on multithread and just after asking Petro to scan an area and Crash to Desktop instantly. Did not test on Single player yet. But played at ColdWar (Persian) and A4Y (South Atlantic) with no issues.

I think that's for the ground based launch system like Shturm-S MT-LS. https://www.armedconflicts.com/9K114-Shturm-S-t20165 https://www.army-technology.com/projects/shturm/

We have to see this as an opportunity to test our Dead Reckoning navigation skills using the ABU-11/A clock.

At least in Multiplayer when the Pilot jumps to the Door Gunner position (pressing 3) and return to Pilot seat (pressing 1) the Door Gunner AI does not turn on again (LCtrl+Win+3) and on the Gunner AI (LShift+H) it shows as if it has a player on the gunner (2x PLAYER under ROE). Mi-24_DoorGunnerAI_MP.trk

This never happened to me. Maybe you are on an enemy (different coalition then yours), or contested, (with enemies nearby) airfield. You also should not be able to repair nor rearm on those conditions. If that's the case you have more info on the DCS Manual. The same applies for FARPS.

I use it a lot when playing at the RotorHeads server. I use the F10 Map ruler to measure the distance and heading to troops, downed pilots or damaged vehicles for example, and set the values at DISS. I know I could just keep looking at the F10 Map or at the Online Map but I like to get on the region and start to search with my eyeballs. This works great, if you keep the helicopter attitude inside the parameters for DISS to work. On other servers, with F10 icons disabled, I usually keep a 000 HDG and read North/South East/West distances as AeriaGloria said when flying around.

Maybe it should be on the mission briefing page the same way that is displayed the wind and barometric pressure. That way it should be available for everyone independently of the module used.

Check this and also Part 2. More info here https://www.pro-flight-trainer.com/pages/accuracy-flight-tests

Use F4. With the numpad keys (not sure if I changed that for me or if is the default keys) you can move the camera and with the mouse you rotate and it will be locked with your plane (like a fixed action camera). There's also Alt+F4 (really not a joke, look at the controls options) you have a more "dynamic" chase view.

Thank you for that post and track. I was planning to do that since they told it was fixed on the last patch. The DC Voltmeter also has its values mixed up but the rotary switch and labels are OK, for instance, the DC voltage of the buses should appear after turning on the Power from Batt switch but it shows the voltage at the Rectifier position if I recall correctly (not in game right now).

I didn't use the sight yet, but noticed that Petro "search cone" is wider now. To the point that is making harder to get him to lock a target where I'm aiming when there's a lot of targets in the area. I didn't measured yet but looks like is almost 60° now. Would be great to add a way to choose the angle of the search cone like 15°, 30°, 60° and even a keep scanning for targets mode.

I'm not sure yet, but I think it's happening to me too on MP. I ordered Petrovich with Down-Short command, I saw the sight moving as if he was resetting the sight and going Observe Off but after turning around I notice that the sight was still trying to be somewhere else and with the Red Caution Light Sight Limit on, so I had to tell Petro to shut off again with Down-short. Now I usually keep pressing Down-short a couple times after using the sight with Petro just to be sure for not get the gyros jammed. I'll try to check in SP, when able, if can see the what is going on with the Observe switch and Petro.

I think IRL it should always have 2-way comms with the Tower (except if the tower/comms itself got destroyed/jammed) even when Scrambling. It wouldn't be helpful to lose the precious alert-ready aircraft on ground collisions, or during takeoff, when they are most needed. Don't even know where to look for actual doctrine for this, but found this for now. 9-2-7. INTERCEPTOR OPERATIONS Provide maximum assistance to expedite the movement of interceptor aircraft on active air defense (scrambles) missions until the unknown aircraft is identified in accordance with the policies and procedures published in FAA Order JO 7610.4, Special Operations. NOTE- The FAA and the military have mutually agreed to the implementation of policies and procedures for control of air defense interceptor operations. Effective coordination and cooperation between FAA and the military at all levels are essential if policy objectives are to be met. The ADCF initiating the SCRAMBLE must identify the mission as an active air defense mission. ATC services must be used for active air defense missions insofar as the circumstances and situation permits. Upon request, the ATC facility must expedite transfer of the control jurisdiction of the interceptors to the requesting ADCF.

On RotorHeads I noticed that Petro is identifying target that are very, very far now. Too far away for my taste. I had to scroll the target list a lot cause he prioritize AA and I was trying to get the armor that was close to me (and there are a lot of AA on the server now). Maybe on more realistic missions (a rotor craft shouldn't charge on an area with 10+ known SA-8, SA-13, SA-7), this is not an issue. As for identifying targets at night, even with full Moon, I feel like cheating as I feel when using the NVG. Anyways is up to us and the mission makers to decide the use of NVGs or using ATGMs at night with a full the Moon and clear skies.

Was searching for Ikarus and found that, so someone has used with the F-5E.

I'm happy that they did something about the mirror, but was expecting to be able to flip it. Before was like On/Off mirror-like display, now is like a vanish magic trick.

At first I though "no way you can stow this gun, but now I think it may be possible. If it's possible to unlock the "clamp" (red arrow) and swivel (blue arrow) . And the gun would be stowed parallel and close to the fuselage in the cargo bay!!! https://rg.ru/2019/06/25/reg-ufo/vertolet-mi-35m-poluchit-bortovoj-pulemet-kord-i-rakety-s-13.html Anyways I think we should move this conversation to a new post.

It has been reported already.

Here's the F10 Map indication of 1.06MHz on the eastern (same issue with the western one) Locator/Inner Marker Beacon. null Here's what we have on the Caucasus Beacons.lua file. frequency = 1065000.000000; It should have a third decimal place as 1.065 MHz or shown as 1065 kHz.