All Activity

MiG-29A had look down shoot down. We know that if target is above horizon makes more sense since it gives radar better picture and no struggle to process terrain, when it comes to ranges less than 25km with this radar N019 it makes no difference except in HPRF mode which is worst for close range combat, but as in modes such AUTO and P it makes no sense to break lock depending on where target is, above or under horizon, giving a fact that target is closing fast, even with his crank to side i did same in his direction of nose so i don't lose closure speed. My personal opinion it makes no sense since i know for sure how radar works in PRF modes. Please take this as reason to take a good look in details more and do tests by yourself, thanks.

The "gorka" command is generally understood to mean a hi-rate change in flight altitude, usually upward. However, in the context of the MiG-29 manual, it can also mean downward. These are safety maneuvers to reduce the risk of collision with a target or target debris.

Install latest, as it is in the code of the version you are using. ( the menu handler was not removed after aircraft selection in older versions ) Latest removed this behavior ( and the menu handler is disabled after aircraft is selected ) By the way , i'm just about to release a new version to get rid off console and command line options. This should be easier for new users. (forces dcsbios config before start , etc .. )

Hi everyone! This is a small mod, just one file handling the animation of the fire proceeding the crash of a vehicle in land. This animation as far as I know has always been broken. And a couple of enhanced resolution files (4) for flipbooks used in the animation. OvGME for installation is preferred, if not, you have to overwrite the system file located in the main installation: ... \DCS World\Bazar\shaders\ParticleSystem2\smoke.fx ... \DCS World\Bazar\Effects\ParticleSystem2\xxxx.dds This is my first mod so bear with me, I would like to see if this is working on your end. Inside the file there are a lot of modifiers defined with comments to experiment and find all kind of combinations. I will always leave the comments for some tinkering people if you want to take a look and experiment. Fly safe! Moran_ENHANCED_fire_v1.zip

i have this profile. I will test it RAVEN, thanks a lot for your detailed answer. I used to have a rhino before the FFbeast, so I will try to compare profiles, and see which setting is causing the issue.- Tshark, let me know if you figure it out. My profiles are highly tweaked to produce a lot of AoA/stall effects and such. so i'd like to keep using them while finding whats creating the issue.

Please see the thread link below

hello. i updated on 9/17 and got 90+ dl speeds. attach your autoupdate_log.txt maybe some clues.

Well said! I’m having a ton of fun with this module as well and I’m very excited for the rest of the capabilities to be released (especially IFF lol). I didn’t know the COOP switch was unfunctional, my dumbass has been flipping it on during fence-in every flight.

We don't. 1200km (650NM) on internal fuel with high altitude cruise (say FL400) is an abysmal range. We also just established that the range-indication is a slot-machine, not taking wind into account. Sure. But we're talking about a tactical jet over here. That means employing the jet not in some kind of arbitrary "the designer wanted you to do this"-mission, but in an actual tactical engagement with requirements dictated by the sitaution at hand. Under those circumstances, we'll have to see what the jet can do, rather than what it could do if we'de be sticking to some ideal design mission dreamt up by some higher echelon staff officer. The jet can loiter at low speed and high altitude for a bit. But it not anywhere near outperforms the opposition. It just can't carry enough internal fuel to cash in on the airframe's good properties. Leaving out the rough-field intake louvers and taking more gas instead would have been the better design choice. That's pretty much the direction they later took - which is kinda weird if they'd thought they had "enough range" before.

Tbf in reality pilots apparently lowered the volume to almost minimum as well, because it just gave so many warnings.

Just watch the warnings. You'll see emitters jumping around on both azimuth, distance and type. It may well be a very realistic depiction of the SPO15. I'm not knowledgeable enough to argue for our against. But I know for a fact that it is as useless as the SPO10. I fly the Fulcrum like I do the 21: without SPO.

Thank you for reply. The problem is, i even do not know what to change in the registry. Because I do not know where to begin when trying to follow your advice I searcherd for the registry keys but did not find under HKCU\Software\Eagle Dynamics\DCS World OpenBeta\Path and HKCU\Software\Eagle Dynamics\DCS World\ Before I did transfer the STEAM installlation it was under "Steam" on D and now it is named " SteamLibrary" on E I assumed, it might have something to do with this? However, before migrating to Drive E it did copy the files from the STEAM installation to the stand alone. Or maybe this feature does not work anymore an it was only by incident I migrated at the same time?

Это известно. Будут править.

Раритет первых серий. С гребнями под килями и без блоков выброса ловушек.

More informative error messages would certainly help. Same applies to the Error 500 issue. It shouldn't be too difficult to add human-readable error messages to the popup and the dcs.log, so users are not left absolutely clueless as to what is going on. I've even detailed a straightforward way to implement that. Should be feasible in a day's work.

Thank you so much brother. I appreciate your hard work!

Фото старое и не моё. А я там уже 3-4 года не появлялся. Так что всё возможно. ...Вот тоже не моё но уникальное точно.

Btw is it actually false warning? I thought it was more like the 21s RWR, where it just picks up radar from the entire battlefield but cant seperate them effectively. Outside of the own radar interference, that sounds pretty troubling.

347

Вот тут с 8.40 наглядно. При выборе пушки при захвате маркер именно на цели лежит.

Which page is this?

And youre not wrong with that. Maybe im bad at communicating it, but I think the difference isnt quite as big as people sometimes think. For example, is an F4 more suitable for solo operation than a Mig-21 in DCS? Sure! Yet if the Mig-21 gets AWACS support (like EWRS mod), it will immediately dominate the F4 in terms of SA. Give it real soviet style GCI and its not even funny anymore. I would assume the Mig-29 has better SA than the F4 tho, aside from the RWR. Its radar is superior and so is the view out of the cockpit. Aerodynamics/thrust also helps navigating and reacting to dangerous situations. The SPO15 is a weakpoint, but it can see SARH launches I 'think', which the F4 cant.

Overall, I agree with you, except for the missiles. The missiles in DCS are the best in any simulator. I've been following their development for many years. Also, ED guys wrote that the MiG-29 radar is completely based on the new physics and is currently the best in the simulator. Give it a try. We also got the completely new SPO, implemented as closely as possible to the original, and now I hope all future developments will be just as good.

Это баг или фича? по-моему у 29 не показывает (т.е в привычном для нас понимании) маркер на цель, показывает только отклонение антенны. Или я не прав?

From the changelog: With every update of the mod packs, I remove the assets that are now in DCS core.