NineLine

Hey all I am gonna have the team review one of these tracks, it does seem like the gear might be a little soft when you leave prepared surfaces. That said, especially the Caucasus, nothing good comes from leaving the tarmac

From what I see in your new mission, you have the client set to position 2 in the flight, so in this case, you are the one breaking formation as you are not the flight lead. Changing the client to aircraft 1, the wingman happily follows you to the waypoint of your choosing. Let me know if I am missing something here, thanks.

Ok I will look again, but you did not have a route set up like this in your original mission, so I will need to re-analyze what you have now.

Just reviewing your mission vs Wag's video, he set the first waypoint to the recovery airfield, and the next 2 would be the divert airfields. This corresponds to the 3 buttons on then Nav panel, button 1 being the recovery airfield and the other 2 the diverts, this is when the switch is in AD (Aerodrome). Setting my own flight like this seems to work as expected based on Wag's video. The AI seems to follow along as expected. Let me know if I am missing the issue you are seeing.

Thanks I will run this by the team.

Checking with the team to make sure this isnt just top of the line Soviet braking systems

Reported, thanks!

Please include tracks of both issues. Thanks!

Make sure both the base NS430 is installed and the Addon for the MiG-29A Then make sure its selected in the Mission Editor

Yes, looks like it is not logging time, I will report, thanks!

Could you include a track of both issues?

Did you set Avionics to English as well? Can you include a track? Thanks

The mask would most likely be added if a new pilot were created.

The MiG-29A remains one of the most famous fighters in the world due to its outstanding performance characteristics, reliability, and simplicity of the weapons systems. It is capable of performing high-alpha maneuvers that make it deadly in close air combat. In addition to the R-73 and HMS, the MiG-29A is also armed with medium-range radar-guided missiles, a 30mm cannon, and unguided bombs and rockets. https://www.digitalcombatsimulator.com/en/shop/modules/fulcrum/

First week patch updates: The animations for the cannon trigger and the missile trigger to be swapped. Lock indication is not resetting after lock break. But logic is working correctly and radar stops locking. Air intake louvers animation corrections. Provide lower resolution textures cockpit option CHAFF/FLARE sequence corrections. When repairing after a wheels up landing, the repair completes, but the landing gear is not lowered, so after repair you are dropped back on your belly, negating the repair. IFF issues for clients connected to the mission hosted on a dedicated server. Single Player or Self-hosted servers do not have this issue. Controls Indicator overlay (RCTRL+ENTER) missing 3D model damage WIP (first iteration) Additional English HUD/HDD version (fictional for convenience) Known issues to be patched: Autopilot-induced oscillations, mostly visual on stick, no effect on flight path below 600 KpH Landing/taxi lights issues - the light from penetrates into the model. Brake chute is not visible for other clients in multiplayer, physics working correctly When using FCR, missile launch is not blocked in the absence of a LA signal on the HUD/HDD. Ejection sequence and animation improvements. Cannon muzzle flash improvement Ejected cartridge animation The logic of the CAJ (Compensation Active Jammer) switch is not implemented when working with jamming. Imperial units cockpit version IAS indicator animation issue with Mach number. 3D models enhancements in progress: Finalization of the main texture, wear and tear. Technical inscriptions and stencils. Main landing gear bay high detail. Detailing of the air brake and the drag chute container. Main technical hatches and equipment bays. Detailing of the IRST. Detailing of the Flare/Chaff dispenser. Ejection seat details. 3D model damage improvements Additional LODs for 3D model FLIR texture. Additional liveries of countries that were operating MiG-29A. Livery template. (planned for October) Improved weapons pylons. Dynamic reflections on the canopy. Improved pilot model.

The release of videos does not necessarily coincide with the release of the module and would not hold up the release; Wags often releases videos after the module is released. There should be a new video this week.

Or appreciate the options to make it easier for all to access at a level that is comfortable to them.

This is still planned to be done, sorry I dont have a timeline right now.

These are pretty redundant threads, so closing. It's not going anywhere helpful, sorry.

NOTE 1: When is it coming? We are still shooting for this month, but we cannot give an exact date until testing is complete. NOTE 2: In a later video, I'll discuss the ADF Panel. NOTE 3: I am not at liberty to discuss 3rd party products. Please keep comments on topic. NOTE 4: I'm still just learning this aircraft, so my skills (particularly in in-close IFR), need work. I know. In the previous two videos, we introduced you to our MiG-29A and how to start it up, taxi, and takeoff. In this video, we’ll learn navigation in the Fulcrum and how to land it. MiG-29A navigation is quite a bit different than navigating other 4th generation aircraft like the Viper and F/A-18C, but once you get your head around it, it’s rather easy system to use. For this video, we are parked in a hot Fulcrum at Herat airfield in western Afghanistan. I’m going to explain two methods of creating your navigation points: Using basic Mission Editor functions and using the Data Transfer Card, or DTC. When using basic Mission Editor functions, you can place up to six points; the first three are assigned to the three Navigation panel aerodrome buttons and the second three are assigned to the three waypoint buttons. You cannot assign the radio beacon buttons using this method; you’ll need to use the DTC for that. When using the DTC option, you can also assign the three radio beacon navigation buttons on the Navigation panel and a lot more control of aerodrome points and waypoints. Note that the real MiG-29A does not have an actual DTC card but is rather programmed into the aircraft prior to flight. For both methods, we’ll create a navigation plan from Herat to Shindand to the south. As the Fulcrum uses an Inertial Navigation System, INS, that can drift, we’ll also discuss how to tighten the alignment using a visual fix. In addition to creating navigation points, we’ll also touch on Return to Base, Landing, and Missed Approach modes.

When you end the mission, you can save a track file.

Can you attach an example mission where you are having trouble? I can take a look. Thanks!

Added to FAQ: Do I want this if I already own the Flaming Cliffs version? If you are a fan of simulation of complex real world systems, then yes, you very much want this. The Flaming Cliffs version for everything but FM is very simplified for ease of use, based on what Flaming Cliffs was meant to be. The MiG-29A Fulcrum will be like learning a new aircraft, from navigation to employing weapons and all the challenges expected for this complex Russian fighter.

Please check out this DCS SPO-15 Manual as well: spo15manual.pdf We had some customer-submitted questions that we thought were important to answer; check them out below: Q - SPO-15 "A question popped into my comments: why does the SPO-15 auto-adapt to the mission, rather than leaving the choice to the mission designers? For instance, if you want to replicate something like Kosovo, the SPO-15 may not be able to react to the 120B. According to the books I read, the first MiG-29s were shot down without even realising they had incoming missiles. However, if you force it, this cannot be replicated. Couldn't a simple checkbox be set in the ME prior to the functions that recreate the threat list? (book example: ""Laslie, Brian D.. Operation Allied Force 1999: NATO's airpower victory in Kosovo."")" (K / YT) A - The SPO-15 will come with 2 options, selectable in special options tab for each aircraft in Mission Editor: stock and automatic. The stock setting is intended for former Warsaw Pact aircraft and includes a fixed program that matches the period when the MiG-29s were first delivered - this DB does not include most threats present in DCS, however that does NOT mean these threats will not be detected - the SPO-15 will detect any radar within its operational band and will always report a detection even if it doesn't recognize it. In other aircraft these unknown sources can be filtered out, but in the MiG-29 this option is not available. The automatic theat program is built on top of the stock program (overwriting PW/PRF bins of the stock program as needed) to match enemy threats within the mission. This however does NOT include missiles, for a simple reason: the SPO-15 doesn't have the resolving capability to distinguish ARH missiles from aircraft that carry them - therefore as long as the carrier aircraft is listed in the threat program (and it typically will be, as the entire HPRF range is filled in as type F by default as are some MPRF slots), the incoming ARH will be mis-identified as the carrier aircraft. As for the case described in the book: this will always be the case, because the transmitters in older ARH missiles are typically quite weak (as the seeker is used for terminal guidance), and the SPO-15 is not sensitive enough to give advanced warning - typically the missile will only be detected 2-4s before impact depending on angle of arrival. And even then, it will not trigger a launch warning (in fact there's no possible scenario in DCS that would trigger the launch warning in the MiG-29 currently), which means that in many scenarios it will be completely unnoticed, particularly if the aircraft is already locked on to by a higher priority threat than type F. As for manual database, it is something that we have considered and that might be considered later in EA if there's a demand for it - currently it doesn't fit any other workflow, as the threat programs are something that would be consistent per country, per theatre, and would not be customized on per-aircraft basis nor by the pilots, as they weren't possible to update in field - the theat program cartridge (which contained a hardware implementation of both the database and the threat recognition algorithm) had to be sent back to manufacturer to update. For that reason it does not fit into the new DTC functionality. Q - SPO-15 They mention side-lobe bleed causing threats to register in the wrong bearing sector (flank/sides/rear). are there cues that help pilots tell these apart from real emissions, like flickering, strength fluctuation, sector drift, etc? (Brody) A - Generally no. The indicator in the SPO-15 does not show raw signals, it shows fully processed (including recognition and priority check) detection events. It also does this separately for each sector, going through them in clockwise fashion one at a time and repeating the whole process for every sector separately. One cue that the pilot might get is if the threat is selected as priority - in that case the weaker signals from other sectors might be considered lower priority by the system due to their lower signal power, and thus they will not be marked as priority despite arriving at the same time from the same threat type. But even in that case there isn't really any way to discern that from an actual detection of another threat of the same type, but further away. As for signal strength indicator - it can provide clues as to whether the pilot is the intended target of the hostile system or not - if the strength is lower than expected, or if it goes up rapidly followed by a priority threat being dumped and returning with a lower signal power: all of that might indicate the hostile radar is actually locked onto another aircraft. Q - SPO-15 With their implementation, is it common for threats to briefly vanish or hop between bearing sectors? how should pilots interpret that behavior if so? (Brody) A - A few technical details need to be explained to address this question: First of all, each detection event is remembered for only 0.125-0.25s - that's how long the green light will flash for. The priority threat, as well as any detected type (type memory is separate from sector detection events memory with no association between a threat and the sector it was detected in) is remembered for 2-12s after that depending on emitter mode, scan rate, and which point in memory dump cycle it was picked up at. This threat memory is per sector, with again each sector treated as a separate "sub-RWR", even for the priority threat: the way a priority threat is tracked between sectors is by overwriting the priority threat memory if an equal or higher priority threat is detected and then extinguishing priority azimuth lights in sectors that do not have an ongoing detection event. Secondly, the azimuthal resolution of the SPO-15 is really poor - in best case scenario it's 10 degrees, but this is only within the +/-50 degree range, for higher AOA it will grow way above that. Thirdly, as this is likely the intent behind this question: no, the physical mechanisms behind fluctuation in measured AoA of western RWRs (a hot topic within the community) is not presently modelled for the SPO-15, as it is not a factor due to how poor the resolution is to begin with - such fluctuations are much lower in magnitude than the angular resolution of this device. The SPO-15 does not measure the AoA of the signal continuously like modern RWRs do, each sector is handled separately and will either detect the threat or not - with the result presented on the corresponding section of the indicator for that sector only. To answer the question: in the case of one receiver and one emitter with the receiving aircraft flying in a straight line, jumping between sectors will not be very common. Vanishing and reapperance will also not be common for incoming threats, but it might occur every scan cycle for outgoing threats (because their priority is decreasing) or for emitters that are powerful enough/have low enough scan rate to falsely trigger a lock on warning. For multiple threats, the primary threat might sometimes rapidly jump between sectors - in those cases, the pilot should assume they are dealing with mutliple threats of the same type, especially if they're separated in azimuth by more than 20 degrees. Q - SPO-15 They describe the SPO‑15 displays signal strength in 2 dB steps, but is this based on absolute ERP received at the antenna, or is it normalized relative to the strongest signal present at the time? can the same emitter show different power levels depending on what else is emitting nearby (Brody) A - It is based on absolute ERP, however the measurement range differs between CW and pulse signals by a factor of 18dB (the circuits for signal power measurement are separate for CW and pulse signals). The dynamic range of the device is only 30dB and the indicator spans that range. The indicated power will typically be consistent with range if the receiving aircraft stays close to boresight, otherwise it might vary considerably, as the radiation pattern of the emitter is taken into account. Q - SPO-15 Will the 90 light not only light up only with 50 light, but 90 light only light up at close range? Long range only 50 light turns on if radar is at 90 degrees. This is because the 90 light needs the less sensitive rear antenna to work Aerea Gloria A - Yes, the 90 degree "sector" is much weaker, not just because of lower sensitivity of rear hemisphere (AND sector 1 and 8 - in fact amplifier gain is adjusted so that these sectors are triggered at the same power density as rear sectors, about 3dB above the forward hemisphere threshold) but also because of how far off-boresight for both antennas the signal needs to be in order to be detected by both simultanously. In fact the 90 degree sector being triggered at all is going to be fairly uncommon. Q - SPO-15 Are PD fighters in Hawk category until around 15-20 km where they are then put in F category? (Aerea Gloria) A - Yes, however the range is much wider than 15-20km and will vary depending on emitter power, anywhere from merge range (F-16 at HPRF) to ~50km out (e.g F-14). A video version of these can be found here:

I will have to ask, but as I understand how it works with our FM, it cannot be turned on and off while you are flying.