All Activity

Thanks for being right on this! I did this 4 times today, and thought I was really messing something up. It's always something with software, fix one bug create two more...

So one thing I don't like about the real life MiG-29 is that when you lock a target and you want to employ missiles, instead of like on other 4rth gen fighters (or the FC3 MiG-29s) where you would get a box, or circle, or a dot (or some other icon) highlighting the target directly on your HUD you instead have have a steering circle, and a diamond to show where the radar is pointing, and this diamond does not adjust for the roll of your aircraft if your trying to follow it. like in the picture below. This means that sometimes your not sure which target you've locked for certain, and it takes a fair bit of time and guess work to determine if the speck your looking at is the one you locked, especially if your firing into a furball environment. HOWEVER** There is a work around. You do get a circle highlighting the actual target when you pull the trigger into the first detent like if you were employing guns if you have a current radar lock, and your inside a certain distance. typically outside of 50km you will just get the gun funnel if you press the first detent. However if you close to within 30km it will flicker from the gun funnel to the circle with the locked target. Then once inside 30km you will just get the circle around the locked target like in the picture below: This is currently handy if you want to actually know where on the hud is the actual target that you locked up is. Now I'm not sure if this is a current bug, and the ranges are way off for this to appear, or if this is something that actually was possible with the system, and could be used as a work around. Interested to see.

It is just unfinished and all effected by range scales Normally cursor is 8 degrees wide 5 km long With TWS is 8 degrees wide and 10 km With scales changing from 50-150 km. You can see what happens

you're not looking close enough - put it in combat relative bearing he manuevers, turns further than the gimbal permits -- missile still tracks

good call, if you turn it off, how does it show up on the kneeboard then ?

CrazyGman that is an interesting explanation Off to go try again.

That helps with the FFB forces being applied wrong, but not with this issue. This happens when you are trying to cold start the aircraft and you do the BIT for the autopilot. The game detects joystick inputs and fails because in the real aircraft you can't move the stick during this process. The only way to get it through the Autopilot BIT successfully is to erase the axis assignments for the joystick then remap it when it's done.

Any chance of getting the updated Apache manual?

Ahh…OK. Well one one hand poo - on the other I guess then I have a surprise in store. Looking forward to finding out. DCS really does helos well.

Para los que no tengáis la versión: v250921-1, bajaros esa versión ya que es la que tiene un control de versiones y os avisará en caso de que meta algún cambio. Edito iré poniendo la última versión en el primer mensaje, ya que voy encontrando errores y arreglándolos, y lleva mucho curro. slds.

А ничего что эти процессы как раз и отслеживаются СОС?

Just put english hud at options and see what it means, you can revert it when you want. But it says pause in "Rusky", so I think it displays this word when you are not able to fire . You can find the description at page 8-7 in the ka50-3 manual : "‘PAUSE’ cue - cooling cycle of the laser range-finder in the Target Marker (“ПМ”) targeting mode "

Ever since the stated 2.9.19.13478 changelog quoted above by Actium - HARMs are able to hit a radar even when it's been completely turned off. @BIGNEWY @NineLine

Слушайте, я не говорил что СОС управляет положением закрылков в выпущенном состоянии. Прочтите пару страниц выше с моими постами то. Там пружина этим делом занимается. Про то как работает СОС я же текст не из головы придумал. В другом посте ещё одну страничку привёл, коротко: СОС определяет по углам атаки и скорости когда вываливать механизацию и толкать РУС. Просто прочтите ещё раз мой пост где приведено две странички. Я вообще не понимаю почему вы пытаетесь спорить со мной опровергая литературу из библиотеки МАИ по этому ЛА,

I will note that the NASA AIM-54 is simulated as none we fired by NASA and the Mach 5 numbers are only for a significantly lightened missile (-250lbs) fired at 45 degrees, Mach 1.2, 45000ft with no guidance and locked fins. The current missile matches pretty closely to the NASA flight profile and speed for a typical Phoenix load.

I cannot find description of this in the manual or chuck's guide, or searching internet. What does this word on the HUD mean? null

I noticed this as well.

No one states that MiG-29 is the explorer of the worlds. However, stating that it has short legs is stretching it, because it can go respectably far, for an otherwise insanely versatile airframe. F1 is a cruiser, but a horrible dogfighter. Again, it was built for a particular job, but not it's not a one to rule them all. Mirage 2000 (more appropriate in function and time aspect) is surprisingly versatile, but as a delta, doesn't have the power to maintain it's maximum turn rate and even stated sustained (given higher altitudes). It also has very high landing speeds (you cannot land it anywhere unless you always use the chute) and it's engine will potentially give you a catastrophic failiure given, at times, light to medium abuse. For comparison, MiG-29 didn't have a section on engine limitations because there were none in the envelope it was designed to operate in. That alone, is a first for the history books, and highly regarded by combat pilots, as I've heard. It seems to me that the MiG-29 might just not be for you.

This never even crossed my mind. I did not know they did that based on coalition! I assumed it would stay with the selected 'general settings' measurement system. I do not fly much as red except for the Hind so I guess I've never noticed the change before! Thanks! Please close!

So I was trying to place an AI F9F Panther to land on the Essex carrier in mission editor and I was able to place the second waypoint on the carrier so that the mod can land on it but once I select it to land, it just gone back to being a turning point when I click on the aircraft again

Would any professionals or experts know what the parameters in the configuration files for A2A and A2G missiles signify? I've recently tried to create an A2A missile, but it's clearly unsuccessful. At the start, the missile climbs excessively, then performs meaningless maneuvers at the highest point, and finally, there's no turning or guidance at all when approaching the target. The G-force remains unchanged, even when the target isn't making any maneuvers and is just flying straight toward me.

You are comparing! I mentioned F-16 as anecdotal and MiG's natural counterpart. I cannot comment on your performance as a pilot, as I haven't seen you fly, but 2000ft is a very low altitude for these engines. They are efficient up high, but down low, you pay a massive penalty for carrying the power. Still, they are different designs, so treat them as such. On the other hand, F-16 isn't underpowered, but MiG-29 - it is not. If you want to fly at 2000ft, then I'll be straight forward with you - accept what you got, or else the MiG-29 is not for you. The moment you wish to travel further, is the moment you have to accept that "high" has to be incorporated into your flight plan. It's that simple. Even though emergency drops for fuel/weapon stores exist in the aircraft, doesn't mean that a mission relies on them being used. It is in the name - an emergency. Remember, that you might be caught very quickly in an uneven fight (WVR/BVR) and be forced into a defensive (high-G) position. There are pre-requisites when using emergency drop. It's not something you can do in the majority of the flight envelope due to the hazard of hitting your own aircraft/other potential self-threatening situations (partial jettison/uneven jettison/etc...). Hence, you cannot rely on it as a be all saver. I'll tell you this though: the sheer simplicity/ruggedness/automatization in MiG-29 won't be truly appreciated until we get more realistic damage modelling in DCS. Razbam did a fantastic job here with e.g. F-15E, to show how quickly you will bend the airframe (and ruin it) by running down low and fast (a typical on quake servers). When, due to bad piloting, you'll be able to cause a critical failiure to an airframe among all aircraft, you'll finally realize what was so revolutionary about these aircraft. Flaming Cliffs has given a bad perspective of that so far, because everything is stupidly simple and effects not simulated. It's much the same with e.g. helicopters, where you won't truly grasp where the value of co-axial lies, until absolutely all effects get simulated (including tail rotor vortex ring state). Only then, will you finally start to respect which way wind blows, and focus like you never have in your life, when transitioning to a hover. Until now, many people in this community have the wrong sensation that the AP and co-ax is trying to kill them, while IRL, nothing could be further from the truth. Not to divert the discussion, but you seem hung up on a particular with the MiG-28, which I told you that you can mitigate with altitude and lower average thrust, yet you somehow have made up your mind that you want to fly it low and do Magellan across continents. It's no different than trying to use a Sa342 with Mistral as a dedicated dogfighting platform, be cause you want it to... That's my point. It's the wrong mentality.

I'm really enjoying the MiG-29, but I think some people need to realize that there are still a few missing features when it comes to the IRST, radar, and helmet-mounted sight. Currently, the COOP switch in the MiG-29 is non-functional. With it enabled, the two sensors are supposed to work together: depending on which sensor you’re using, the other will automatically slave to it. This means you should be able to lock a target with the IRST, and then have the radar lock as well, without needing to manually switch sensors and relock the target. As for the helmet-mounted sight, right now you need to achieve a target lock first, and only then will your IR missiles slave to it. However, according to the manual, by using the helmet-mounted sight and holding the lock-on button, the missiles should be able to target directly, irrespective of whether a lock has been achieved through the optical locator laser station or the radar.