All Activity

When the KC-130J comes out, can all the following be included? Obviously USMC French Air Force Kuwait Germany Luftwaffe

I tested couple of missions but wasn't able to replicate the issue. Please try the mission again and if still bugged try also skipping that one stage and fly the same mission in the next stage.

By the way ... If I call up the ground crew for external power supply, or if I call up ATC to announce 'Inbound' during the flight, the radio works fine!

Там при нажатии на карту f10 утечка памяти часто случается. Еще если от сервера к серверу подключаться так же производительность деградирует кратно.

I agree I also agree that it should be neccesary a limited power on for both weapons, it is a cheat that they can last forever, not appropriate for simulator.

It was the texture settings. As I had just installed the software on my new PC, I hadn't reviewed all Options settings. The other modules I tried were not blurred at all. It seems strange that the black shark needs a higher texture setting. All fine now, thanks to all who have responded!

Yup I’ve been flying MiG-29 with full Russian cockpit as well. The cockpit is easy enough to understand even for people who know nothing about Cyrillic writing.

According to Polish Airforce radar and computer Exploitation manual, and Soviet SPO-15LM service manual for regimental service stations(ТЭЧ), SPO is synced. It can be out of sync for two reasons: faulty electrical connections in cables, software error in the BTsVM. As for 90's manuals stating it's out of sync - it's indeed an ass covering document to cover MOD not functioning properly. Destruction on the ground by diversion and 1 case of friendly fire over own territory. Judge for yourself how it connects.

нет это я знаю, это не то как тогда делают такие кадры? или это только в VR можно?

What incidents, and how are they related to Mig-29 in DCS?

Just to add ( speed of heat has good advice ) its worth checking also flagged in your dxdiag Windows Error Reporting (WER) Your system crashes with Bluescreens. The following kernel-events have been detected: DRIVER_IRQL_NOT_LESS_OR_EQUAL,MEMORY_MANAGEMENT,KMODE_EXCEPTION_NOT_HANDLED,SYSTEM_SERVICE_EXCEPTION,HYPERVISOR_ERROR,IRQL_NOT_LESS_OR_EQUAL Remove any overclocking (including XMP)., Run SFC and DISM to check your Windows., Check for any updates of your BIOS or chipset drivers. Also make sure you have disabled hotplug in DCS controls

The BF109 deserves all the love it gets, it’s an incredible aircraft. We also want a G6 or any other earlier variant. Please.

Try turning off Windows Memory Integrity e.g. core isolation Options to optimize gaming performance in Windows 11 - Microsoft Support

Heya, lasse den server auf dem gleichen PC laufen, wo ich dann auch online fliege, im browser wird nur die IP4 angezeigt mit entsprechendem port, DCS kann IP6, wenn die IP6 im router ausschaltest sieht man weniger server in der MP Liste

Hey! I've attached both files. That option should be on main Bios Extreme Tweaker page. Asus OC profile can be used without extra-overcklocking, just with stock Pcores-5.5 and Ecores-4.3 Ghz. dcs.log DxDiag.txt

@Jarodid you tried to enlarge the MANTRACK's deadzone?

I have similar problem using easy comms, on the rest of the modules just contacting the airfield automatically changes the frequency and comms work fine, with MiG-29, easy comms work only if you set the correct frequency in ME and than in cockpit select correct preset. Still no need for push to talk but frequency must be set beforehand, otherwise no comms

Boeing 727 skin template version western1 (Civil Aircraft Mod)

An original Fighting Falcon A would be much closer to a Mig29 in regards to Systems (not the same, but closer) than a C. Probably Closer to the Mig than to the C....

External bags must be depressurized in order to be air refueled. This is done by opening the AAR door several minutes prior to refueling.

I am pretty sure I can by now quote you 3-4 documents of actual technical nature (this is user manual you are quoting) quoting that SPO gets blanked while Radar transmits. These documents and user accounts contradict each other and ED is fully aware of this. The devices you discuss now in 2025 were designed in 1970s and 1980s in Soviet Union with what was the technological base available to them. The technological base of the west at that moment was on the one magnitude higher level (we should just take a look at advances in microprocessors during late 70s and early 80s). Designing devices that meet equivalent requirements with weaker tech base did result in number of compromises. One of them is MTBF. We can take as example F-15 radar which had 250 hours, while the 29s radar is stated as 50 hours. For SPO-15 stated MTBF is 300 hours. Both Radar and SPO-15 were designed with each other in mind, and contain blanking mechanism which was designed to prevent SPO receiving own radar signals. This is how the devices left design bureau and likely the production facility with instructions to the maintenance crews: replace certain parts every XX number of flight hours. You fail to do one of those things and the combination will not work as designed. Plus a number of issues simply appear during exploitation. Surely you as aviation engineer will not fail to recognize that. When considering what went wrong, you need also to picture what happens when latest tech arrives to the unit (remember we are still talking 80s here). Both pilots and technical stuff are eager to use latest tech, but have habits and knowledge which is based on the old tech. People used to analogue technology (possibly working on it for 10-30 years) are forced to switch the latest state of the art digital tech. In real world this does not work so great. Add on top that both Soviet Union and e.g. Yugoslavia did face economic, political and military turmoil and you got all the ingredients there for things to go wrong. I personally took a great interest in SPO topics, going to the great length to find and study technical documentation, and I must say the blanking feature is certainly there. What caused it to fail, I can not tell yet. Not all of the connection and signaling diagrams are available. Also notice that video showing SPO-15LM components also shows that the device had a number of wired by-passes in additional to the regular printed circuits. Immediate questions arise: 1. Was this result of production defects, so the additional lines had to be added after a number of boards has been already produced? 2. Was this result of field repairs? 3. Was this result of modifications on the SPO, e.g. to augment it's functionality. We should also not forget that design was modular and that some sort of modification in "strobe programming" for field modifications was envisioned from the very beginning. We see that both in video and the technical design principles document for SPO. Yet we still do not know how to encode them! So to complete this "little" rant, instead of quoting user manuals that voice frustration of end users, lets take a trip to the deeper level of actual technical documentation and try to figure out what this device was truly designed to do and how it would have behaved if it was (not) properly maintained.