All Activity

In addition to what AdrianL just said, there's a pretty awesome log file analyzer on ED's Discord that'll give some fairly specific feedback; you can find it here: https://discord.gg/PSGpNvBM3Z With your log file it reads: And then it also gives the following advice: And while mods shouldn't cause GFX crashes, it can not be overstated that you should really remove them before continuing; SRS should be fine, but just to be on the safe side, the Blackhawk and Herc mods should go until you can be sure they have nothing to do with these issues.

its on all of the maps we all own if you get the chance could you pls go to GAKK Shack server, and have a look. I am just an old vet form the army. lol not very good with pc things thank you so much

Yes. The first and second rules of George are never trust George. The third rule is that George doesn't suck, he blows. When you complete the startup in the backseat, turn on the CMWS, then calmly get out of the back seat, go to the front seat, pull George out, stuff him into the back seat, and chain his hands to his ankles. You may follow up with a rubber ball gag in his mouth. Close the back door, get into the front seat, and run all operations up front. He may occasionally mumble something about being unable to go down because "water is under", but that's because he's a wuss and probably related to the wicked witch of the west (ie he melts when exposed to water). It used to be that George would automatically start certain things up from the front seat without being told to do so, but even that was too dangerous for him, so now he's relegated to being a meat sandbag for weight and balance purposes. Set the front seat up with a mode switch for your essential TADS controls, adjust yourself to using the FLT page on the left MPD (the symbology select depress will become your best friend for this), and enjoy the freedom of slaving TADS to your own helmet for 240 degrees of awareness. Works great with the FCR, too!

So, just wondering how things progress with trailers. Not the little movie kind, the towed vehicle kind. Quite a while ago ED added a few vehicles that were specifically tractor units. The other day I noticed that quite a few units that are technically trailers, like several AA guns, now appear in the limbered configuration in the encyclopedia at least (even though I believe the QF 3.7" has a few bits the wrong way around, but I might be mistaken). That all leads me to the question: how is the progress on the system and can we expect to have usable trailers anytime soon? How is it going to work in the ME?

this still working with latest version? saw somewhere someone said it wasn't

bummer this mod seems dead, but going to try out @Kurdes mod

Would be totally acceptable if we only got conventionally armed missiles.

77th “BLACK CATS” TRAINING SQUADRON “TAKE TO THE SKIES OF WORLD WAR II” **77th “Black Cats” Training Squadron Naval Air Station Alameda, California World War II Military Simulation Flight Program** **WHO WE ARE** The 77th “Black Cats” Training Squadron is a historically-inspired, professional-grade virtual flight training unit. Based out of NAS Alameda, we specialize in World War II aviation simulation using DCS. Our mission is to rigorously train pilots—regardless of prior experience—in the procedures, skills, and tactics employed by real WWII aviators across both the Pacific and European theaters. **WHAT WE DO** Our structured block training program covers the full spectrum of WWII military flight operations, including: • Basic flight fundamentals and handling • Takeoff, landing, and formation flying • Full-spectrum ATC communications • Instrument flight, navigation, and dead reckoning • Air-to-air combat and dogfighting techniques • Real-world WWII combat tactics tailored to each airframe Every student is trained in accordance with historically accurate doctrine and procedures, ensuring tactical proficiency and operational realism. **TRAINING ELIGIBILITY** To apply, candidates must meet the following criteria: • Minimum age: 18 years • VR headset or head-tracking system • HOTAS setup • WWII aircraft modules for DCS • Pacific Theater modules if training on the F4U Corsair **PROGRAM DIFFICULTY** The 77th Black Cats uphold high standards rooted in historical realism. Training is intense, structured, and demands commitment. • Dropout Rate: ~65% • Why? You’ll be challenged to master the unique strengths—and quirks—of your selected WWII aircraft in realistic combat environments. **AFTER GRADUATION** Upon successful completion of the program, graduates will be assigned to one of our military simulation combat squadrons (Pacific or European) https://discord.gg/9QqUHh3mqG

DCS: MiG-29A Fulcrum | Defensive Systems Hey everyone, Wags here from Eagle Dynamics. In this DCS: MiG-29A Fulcrum video, we’ll discuss the defensive systems of the Fulcrum, the SPO-15LM Radar Warning Receiver, or RWR, and Countermeasure Defensive System, or CMDS. We’ll also discuss some of the Mission Editor options and Data Transfer Cartridge, or DTC, settings. The SPO-15, LM version, is an older RWR that detects radar signals in the centimeter band that provides the pilot notification of hostile radar signals in search and track modes. It does not provide launch indications, minus a single SAM type not currently in DCS. It provides indications of threat azimuth, radar mode (search or track), threat type, highest priority, threat closure, estimated weapon employment zone of some SAMs, and relative elevation to your aircraft. This RWR can detect radar emitters operating between 4.45 to 10.354 GHz in over-lapping sectors and + and – 30-degrees in elevation. Note that the RWR has blind spots directly above and below the aircraft, at very long ranges, and it is less sensitive and accurate to emissions abeam of the aircraft. As such, it cannot be relied upon for accurate notching maneuvers. Please also note that this version of the Fulcrum did not support full synchronization between the radar and the RWR, thus, the RWR cannot detect and process threats in its forward hemisphere when the radar is radiating. Let’s get started. I’m here over Groom Lake in the Nevada desert, as part of the Foreign Materials Exploitation, or FME, of the MiG-29. Let’s first talk about the RWR. I’ll be going over the basic, practical applications. If you really want to get into the weeds of its operation, I’ve linked a white paper on this topic. As discussed in previous Fulcrum videos, the SPO-15LM is in the bottom, right corner of the instrument panel. Forward of the Navigation panel though is the SPO-15 power switch and the switch to filter out radars operating in search mode. To the left is the SPO-15 volume knob. From some of the player videos I’ve seen, some of you may really want to start using this knob. In the bottom, right portion of the SPO-15 panel is the brightness knob, then the manual and automatic test switch in the center, and the audio warnings disabled lights that is lit when the SPO-15 volume knob is set to zero. We discussed the automatic and manual tests in the Fulcrum Start up, Taxi, and Takeoff video, but I’ll include a card and a link in the video description. Above the Test, Brightness, and Audio Status Light is a listing of the six radar types that are indicated as green letters. Moving from left to right: • Low Pulse Repetition Frequency, LPRF, radars that are equipped with a continuous wave illuminator. Such an indication is indicative of a missile launch with CW illumination like an F-4E, or a ship equipped with an Aegis system and SM-1 missiles. This appears as an П type indication. When such radars are in search mode, they will appear as a C type indication that we’ll discuss in a bit. • The next symbol is for short-range triple-A and SAMs systems like the Vulcan, Gepard, and Shilka tracking radars (not search) and some naval air defense radars. Note that the tracking radar would need to be in the frequency band covered by the SPO-15 and this does not include the search radar for such units. Further, the tracking radars are quite short-ranged, and they can easily be within the blind zone below the aircraft if the aircraft altitude is too high. This appears as a 3 type indication. • To the right is the type for the Hawk SAM using continuous wave. This type can also appear when other HPRF and MPRF radars are detected at low power levels, like many 4th generation fighter aircraft radars. This appears as an X type indication. If the X type symbol is flashing, it indicates low power mode, search, or a scan period that does not match the Hawk SAM. • Next is the type for a tracking Nike-Hercules SAM system, which is not at least currently in DCS. When in Automatic mode, this can indicate other long-range SAMs. This appears as an H type indication. However, for SAMs like the Patriot and S-300, it will also indicate a flashing X type when in search mode. • The F type symbol will be a common one, and it generally indicates 4th generation fighter aircraft in HPRF and MPRF and closer ranges. This includes aircraft like the F-14, F-16, F/A-18, F-15 and others. At longer ranges, they may first appear as a flashing X type symbol. • Last is the symbol type for LPRF radars equipped with continuous wave illuminator but operating in search mode. This can also indicate a radar track with no continuous wave illumination. This appears as a C type symbol. Note that these types are not specific to a particular radar and platform, but rather the radar form that can cover several types of radars. The SPO-15 does not magically detect radars, but rather the radar frequency must occupy the frequency spread between of 4.45 and 10.354 GHz, with a few exceptions. Also keep in mind that friendly radars can also potentially be detected as threats, despite not being in the threat library. This is particularly true with HPRF radar detections. Further, radar signals can overlap along similar azimuths and threat prioritization may suffer. Above the radar type symbols are a series of amber lights. The type that is highest threat will have its light illuminated above it. The priority threat is saved for 8 to 12 seconds if the radar is in search mode and 2 to 4 seconds if the radar is in track mode. The order of threat priority from highest to lowest is: Radar in track mode, threat within altitude and azimuth (like nose on being a higher threat), threat is outside altitude and azimuth, PRF is above 800 Hz, and the highest signal power. The azimuth of the priority threat is indicated by one of the 10 lamps around the aircraft. Eight in the forward hemisphere and two in the rear quarters. Inside this arc of priority lights is a similar arc of smaller, green lights that indicate threat azimuth indications . The system can distinguish between a radar in search or track mode, and a radar in track mode will take priority. A tracking detection triggers the red light in the center of the panel and a steady, high-pitch tone. As mentioned earlier, this version of the SPO-15 cannot alert to missile launches, outside of the Nike Hercules SAM, which is currently not in DCS. The inner ring around the aircraft symbol indicates the estimated signal strength of the priority threat emitter. The more 2 dB elements illuminated in the ring equates to higher peak power out from the priority threat radar. A flashing ring element that corresponds to the weapon employment zone indicates when you are roughly within the estimated range of the threat. As such, based on the signal strength of the lock, and if its signal strength is flashing, you should consider defensive measures. In the center of the aircraft symbol are two hemispheres. The upper B hemisphere, when lit, indicates the priority threat is above you, and the lower, H hemisphere indicates that the priority threat is below you. They are mutually exclusive and general estimates. Let’s now jump to the Mission Editor and discuss some of the programming options. The real SPO-15LM for this version of the Fulcrum is modular, and its threat library can be changed using a cartridge by the ground crew. Of the four Threat Types, four of the six can be edited but not Pi and X Types. In practice, changing the Threat library was rare. As such, changing the Threat Type Library is not freely available to the pilot. Instead, there are two options to choose the Threat Types. The Stock program library of threats is based on the Warsaw Pact setting for their MiG-29s. This corresponds to the default Types we’ve reviewed. Threats not in this program library can still be detected, but they may not be classified correctly. The Automatic Program library, which is the default, has its threat library generated automatically based on the threat radars in the mission. These radars are then assigned to the appropriate Threat Types we’ve discussed. Radars that operate in a frequency outside the SPO-15LM’s detection capability are not included in the program library. If two or more threats overlap in Azimuth, the higher threat will be set as the priority. If a threat is detected like an active-radar homing missile operating in the X-band, it will be an F type classification. Such a missile in active guidance would appear as F type threat with a rapid increase in signal strength as it closes. The program method is selected from the Airplane Group window, Aircraft Additional Properties tab, and then select the desired setting from the SPO-15LM Threat Program drown down. It can also be selected from the MiG-29A DTC by selecting the CMDS tab and then the SPO-15LM Threat Program. The threat program is also listed on the kneeboard that lists each threat radar and the Types it is assigned to. Some of the biggest limitations to bear in mind are: • When the onboard radar is operating, the forward hemisphere of the SPO-15LM is disabled due to limitations of this version of the MiG-29. • The threat relative elevation lights only operate when the threat signal is quite high. As such, by the time you receive relative altitude information, you may already be within threat weapon range. • It’s possible for the SPO-15LM to incorrectly classify HPRF signals as continuous wave signals. In such a case, you may see a flashing ‘X’ Type indication. This is something to keep in mind when you have both 4th generation aircraft and Hawk SAMs in a mission. • A continuous wave radar and a pulse radar along the same azimuth and mode, could be mistakenly classified as a Type C and trigger a П type indication. There are other limitations, but we suggest careful reading of the SPO-15LM White Paper for these. Let’s talk about the Fulcrums Countermeasure Dispenser System, or CMDS, that consists of up to 60 26mm chaff and flare cartridges. Naturally, flares are meant to decoy infrared-guided missiles and chaff is designed to decoy radar-guided missiles. They are stored in the two vertical stabilizer roots. The system is powered from the Aircraft System switch at the back of the right console, and readiness is indicated by the FLARE READY lamp next to the SPO-15LM power switch. From the Mission Editor, we can load: 60 flares, 60 chaff, or 30 flares and 30 chaff. This is the simple way to set up the CMDS. Let’s now look at the more detailed CMDS option in the DTC. From EDIT, select DTC Manager, and we’ll create a new program from FILE and then NEW. Select the Weapon tab, and then the CMDS tab. Below the SPO-15LM mode select option we touched on earlier are the CMDS program settings. Each activation of the dispense button, located on the throttle with the control manager Action name of Flare Dispense Button – Depress, will release two salvos – Salvo A and Salvo B. Each salvo can be programmed. Burst Count I and II determine how many countermeasures are released in each salvo. If you have both chaff and flares loaded, both will be released at the same time. There is no separate dispense option between chaff and flares. The Burst Internal determines the dispense time between each release within a burst salvo. The Salvo Interval determines the time between each salvo. The Salvo Count Air and Salvo Count Ground determine the number of salvos expended with each press of the CMDS dispense button and is based on the position of the CMDS switch on the instrument panel. Let’s talk about that now. In the center of the instrument panel is the Emergency Jettison button and the CMDS program selector switch. To jettison all countermeasures in case of an emergency, press and hold the Emergency Jettison button on the instrument panel. The CMDS program switch has three settings: Ground, Forward Hemisphere, and Rear Hemisphere. Each press of the CMDS dispense button activates two salvos by default, but the number of salvos and their characteristics are based on the program switch setting, DTC settings, the attack hemisphere, and altitude. If Ground mode is selected and you press the Fire/Launch button or the dispense button on the throttle, Salvo A and Salvo B will dispense as programmed, regardless of hemisphere and altitude. When set to Forward Hemisphere, FHS, and if your altitude is less than 6,000 meters, Salvo A and Salvo B will dispense as programmed. If, however, you are above 6,000 meters, two Salvo As will be released, and two Salvo Bs will be released. If Rear Hemisphere, RHS, is selected, and you are above 6,000 meters, four Salvo As and four Salvo Bs will be released, and if below 6,000 meters, two Salvo As and two Salvo Bs will be released. Below is the total number of remaining cartridges in groups of 20. That’s an overview of using the Fulcrum’s RWR and CMDS defensive systems. I hope you enjoyed this video, and I will see you next time. Thanks. 29-Defensive-2.pdf

Kola map Norway, south of Bodø, more than half of the region:

Fancy GBUs from old 60s aircraft

You can't deactivate the cat. You can only set it up so the aircraft launch from other cats.

Gotcha! My heart kinda stopped there for a bit when I saw that the older, I guess legacy style, of DAP ESSS wings weren't there. Are you by chance doing a stubby pylon in the new style ESSS wings that SOAR runs are you?

Hello to all ! I'm trying to understand how the SPO-15 works with the ED documentation and test it in game to be sure to well understand. But I can't explain some in game behaviour compared with what's written in the manual, let's take an exemple : First situation : ME : Mig-29A with "Stock WP" SPO-15 setting Threats: AI F-14B with radar homing continuously activated Symbology shown : At 195km from the target : "X" blinking -> It don't know if it's a Hawk radar OR an HPRF radar situated far away (mis-identified as type Х at low power levels), is that affirmation correct ? AT 60km from the target : "X" still blinking and "F" lights up steadily -> Identified as a 4th gen fighter. Second situation : ME : Mig-29A with "Automatic" SPO-15 setting Threats : AI F-14B with radar homing continuously activated Symbology shown : At 195km from the threat : "X" blinking -> Same reason than the first situation ? At 60km : "П" lights up steadily and the "X" continu to blink -> Why ? At 20km when I get the track warning, the "C" appear steadily -> Why ? For the same aircraft, already registered in the "Stock" data base, the behaviours are different between "Stock" and "Automatic" SPO configuration... The automatic configuration isn't supposed to only add more datas from the stock version ? Why change the SPO behaviours for the same threat ?

I assumed that is what the thread was about a block 30 in a ODS configuation. I figure Ideal the F-Teens modules should have had 3 maybe 4 variants . An early A, an early C (Desert Storm Configuration), and a late model C (early 2ks variant we have). I get that might not be possible to do the multipack.

Oh, that escaped me. Yes it was fixed in 2020. I guess you did the right thing - you reported it again.

It's very likely that the company that does the jet for MSFS will be the same that'll do it for DCS. See Heatblur, who develop their planes for both in parallel. The company will benefit from research and modeling (both 3D and physics) done for one when making the plane for the other. It makes no sense for ED nor HB to work on Rafale.

Replaying this campaign in the F-86F right now (already did the MiG-15 version about a year ago) and really can only agree with what others wrote here. * Storytelling is great, the whole "fly an old plane in a modern conflict" theme is fun, but also well-grounded based on the provided background * Mission scripting is superb, never had the feeling that I'm "hunting triggers", events just unfold naturally (sometimes also unexpected ones) I've now played a fair share of single player campaigns, and this one still feels like a hidden gem - really looking forward to new ones ;).

A fix on Bx1 - Bx5 act like normal navigation points (B) in that fixes made on them will affect all the other waypoints. You can see them as extra navigation points you can make fixes on, but that you maybe not want to fly over. Bx6, Bx7 and Bx9 will act as target waypoints (M) and will only affect the waypoint selected. A fix on Bx8 will move Bx8, and also Bx6, Bx7 and Bx9. Radar fix or visual fix does not change the behaviour.

This is correct. It does not matter which type of fix you perform (either RADAR or OVERFLY), a fix on a navigation point shifts the whole flight plan. Any fix on a target waypoint shifts the target waypoint, nothing more.

Hi everyone. I'd like to show you what I've come up with. But I want to redesign the throttle control panel in a Mustang style. And add a separate gear for the chassis. By the way, by switching to 24V power supplies, reducing the height of the joystick gear to 215mm, and increasing the size of the large gears to 68 teeth, I got 17 kg on the joystick with a 40 cm handle height!!! And with my old pedals, I got 40 kg!!!

This happens for me as well, from cold and dark totally repeatable the nav system resets and the game stutters when I start to taxi from the stand. I’ll upload a track when I’m next on DCS

I thought this was a livery wishlist. Sent from my SM-A536B using Tapatalk