lemoen

I get that, but the pipper appears and updates so slowly that in most cases it doesn't even show up before the fight's over (mostly because my gun ammo is gone or I'm dead). Surely that range pipper should update smoothly, many times per second, if the target is hard locked?

We need the runway damage to be modeled in some way too. In a way that will make it really dangerous to try and take off in MP. Damaging a runway already stops AI from attempting it but humans are more foolhardy and don't care as long as the plane gets airborne.

Bump.

Bump. According to a fellow player on a MP server, he was using this method to drop GBU-12s and they were releasing correctly. So it looks like it is bugged for mk-82 but not for gbu-12 (maybe in MP it is not bugged at all, I have not tested this).

Thanks Ciribob!

WE'll prob be blue for the foreseeable future

Red won. Can we have a reset please?

RPM. Green. LOL.

I stand corrected.

We will,eventually. Not at the moment. Sent from my iPhone using Tapatalk

It is the same kind of thing, rocket-assisted runway penetration. I think BAP-100 is 100kg each, Durandal is 200kg, both are French designs. The same but not the same (not identical, at any rate).

The M2000C won't get Durandal anyway, the BAP-100 is its anti-runway weapon.

https://www.digitalcombatsimulator.com/en/newsletters/newsletter19052017.html

Good enough for me :D

Or learn it bit by bit. If you posted this a year ago already, you could have learned most of the A10 by now, only having an hour here and there.

Just copy your inputs folder from 1.5 (in your Saved Games folder) to 2.0. No need to redo them.

Maybe its because of my ping or maybe it is the Blue Flag server and my ping. Others on BF complain too, if the enemy dares flying perpendicular to you the lock is broken immediately and without fail. I feel that it shouldn't be this easy to break lock once you have single target tracking going. It takes about 2-3 530s to bring down an enemy. Mostly because of the lock being broken.

Also, remember another thing. Software is updated in cycles. start -> Bug report / Feature req -> Investigation -> reproduce bug / plan feature -> fix bug / implement feature -> test -> add to next update -> wait for ED to release an update -> goto start Some of these things doesn't require the developer to do anything so they have time to work on other things. Keep that in mind.

Yeah, hold on to your speed, zoom away, re-engage. Those pesky flankers and 29s with their off-bore missiles can be tricky. Also, they have loads of them. I still think the M2000 loses lock too easily. Either way, this thread is about the 530 being sucky and it works fine if you use it correctly.

Exactly. Sent from my iPhone using Tapatalk

In usually WAY above Sent from my iPhone using Tapatalk

Most targets fly below 30 000 so I'm always above. Sent from my iPhone using Tapatalk

I think the notching effect on the m2000 is a bit aggressive. The target is only inside the doppler filter for maybe a second and lock is broken. In reality I'm sure there's a memory that will allow the radar to search the space for where the target can be (can only move SO fast), and pick it up again automatically, but in the sim, the 530 is trashed and you need to fire the other one. I basically never fire as far as 18nm, on Blue Flag everyone is on Fox 1 so I know I can wait until 6 or 8nm before firing, in a head-on M2+ merge. Lock breaking is the cause of 90% of misses I would guess.

530 outrange the other Fox 1 missiles already. The only drawback it has is that radar lock issue of the M2000 which may or may not be a bug. If you want more range you need to go faster and higher. The M2000 is fast, use it to your advantage.

I select the autounhook then lower. That way the cargo is unhooked the moment it touches the ground. I had to do this part a few times because I crashed my helo later in the mission (a few times).