Kazansky222

in BF I've tried M1 M4 and M6 IFF modes and for some reason, almost randomly friendly F-14 will sometimes show as bandits, and friendly F-16 will also sometimes show as hostile. And for some reason DL contacts that are friendly will also sometimes show as hostile. I've had many F-14 on DL show as hostile, and sometimes even friendly AWACS shows as hostile. This is all multiplayer on Blue Flag PG. Today I even had a friendly JF-17 show as friendly, then hostile, then unknown, then back to friendly all within about 30 seconds.

So when I'm in INTERCEPTOR mode doing BVR and select a CM program and choose chaff or flare or both, my change weapons bind on hotas/throttle no long functions. I have to leave INTERCEPTOR mode go back into INTERCEPTOR mode and then switch weapons, then re-enable CM. Pretty sure its a bug. :pilotfly:

Radar elevation is extremely hard to control unless you bind it to an axis. When bound to just a button the slew rate is incredibly fast, too fast to have good control over the antenna elevation.

You might also want to consider the Harrier, its a fun ground pounder, and you can do some fun vtol shenanigans.

I love a J-10 to get my Lavi on ;)

I agree, I really hope they have somebody like IASTAGG write up a nice whitepaper on the missile like HB did.

Thanks for the reply Chizh. The 3 point navigation method for some systems such as Tunguska, are you describing a guidance law that is basically PN with known distance or time to go added to the basic PN equation? Also I'm curious about the ED APN equation, is is more similar to a PN style system with known distance or is it more like Predictive Guidance (PG) with zero effort miss & time to go taken into consideration to find most optimal flight path? I made / borrowed from some academic pages a basic PG script which seems to work pretty well for finding optimal paths, I haven't tried to add anything to it such as kalman filters or anything yet, it does seem to take a bit more cpu then I would have hoped but I think I can slow down the interval of the script a little bit to ease the cpu load while not slowing it down soo much to break the navigation.

I've taken it past mach 1.7 with 2 120s at 45-50k feet.

I'd love a Mig-29SMT or Mig-29K or any modernized Mig-29, or Flanker, or Mig-25 or Mig-31 literally annything.....

I personally hope DL is low on the priority list, would much rather have a SAM that doesn't spike a target and the drag/thrust looked at.

Something happened in a recent update, like the pitch dampener is not online, even though the light is on saying that is it online. But it is flying exactly like it did if you didn't wait for the pitch dampener to come online.

For some reason the Mig-29 feels very twitchy now, its flying as it the pitch dampener is not online, but it is.... But yes that is exactly how it feels now, like the pitch dampener is offline.

Hello, below you will see a few links, the main link is for a PDF on a mod I helped with a long time ago. Along with a couple support links from the PDF's author to help better explain everything, In the PDF please scroll down the the section on Homing laws. After you have done that please discuss what you think? Does anyone know the math behind DCS's implementation of PN and APN? How similar or dissimilar is it to these equations? Links: https://drive.google.com/file/d/1krnJxq4zk2peUGI1K9ZXj9N_xDFsgeXI/view?usp=sharing https://www.moddb.com/members/blahdy...igation-part-i https://www.moddb.com/members/blahdy/blogs Here's an excerpt from the Homing laws portion of the PDF PROPORTIONAL NAVIGATION Also known as Collision Homing or a form of ‘lead-pursuit’, Proportional Navigation (PN) is simple to implement and very effective, where: Acceleration = Closing Velocity * LOS Rotation Rate * NC NC = Navigation Constant (typically 3 to 5) • PN forces the missile to “lead” its target, without having to know anything about the target’s speed, or range to target. • Very effective and simple to implement on any missile, even on heat- seeking missiles that don’t have a radar. Missile always leads the target no matter what. • PN means that as you are chasing your target, your running-path rotation rate is faster than the LOS rotation rate by a constant multiplier – the Navigation Constant (NC). • Higher the NC, the faster you correct your path early in the flight, and less corrections are needed near the end. • Under PN guidance, the missile and the target appear to be on a mid-air collision course, where both objects appear to look “frozen” in state as they merge closer. Simple PN as described earlier assumes constant air speed. Under maneuvering or accelerating situations, lead is ineffective. • Even against non-maneuvering target, a non-maneuvering target still has an upward sensible acceleration of 1G. To produce a more efficient intercept trajectory, the PN equation in FLINT engine is modified by an additional term: Acceleration = Closing Velocity * LOS Rotation Rate * NC + ( NC / 2 ) * at • This is also known as Augmented Proportional Navigation (APN) • Under APN, the missile violently wiggles to align itself on the LOS to target, immediately after launch. Corrections in flight are minimal as it approaches closer to target. The missile collides onto the target in a near straight line. PREDICTIVE GUIDANCE Predictive Guidance (PG) can be argued as an advanced derivative of Proportional Navigation (PN), typically used by radar-guided missiles (i.e. AIM-120C, AGM-114L, MIM-104, PAC-3, etc). • Real world versions of these missiles use similar in concept, but much more advanced forms of PG, though actual details are classified. • We use a simpler elementary form of PG that is publicly known, but very effective for game presentation. Proportional Navigation (PN) works without knowing the range to target, nor any kinematics data. Predictive Guidance augments PN by taking kinematics parameters and range into consideration. Zero Effort Miss (ZEM) In deriving homing guidance laws, it’s useful to know what the miss distance would be if the missile and the target did nothing but continue on their current courses. This is called Zero Effort Miss or ZEM. The logic behind ZEM is that if we know how far a missile will miss its target without effort, an acceleration command can be applied to reduce that miss. A homing guidance law can then be deriving using ZEM by repeating the following process: 1. Find ZEM 2. Compute missile acceleration to reduce ZEM 3. Repeat until ZEM becomes zero. ZEM is closely related to the LOS Rotation Rate (LOSr), which we used earlier for Proportional Navigation guidance. ZEM’s relationship to LOS rate (LOSr) can be presented as follows: LOSr = ZEM / ( LOS * Tgo 2 ) Alternatively, ZEM = LOS * Tgo 2 * LOSr • LOS Rotation Rate is easy to derive, as missile seeker itself can measure the change in angular rate of sightline (as all PN-guided missiles do). • Tgo represents Time to Go (estimated time to intercept), which can be calculated from the missile’s radar range to target and its velocity measured by IMU. Knowing the ZEM and Time to Go, which accounts for missile’s range to the target, the acceleration command should be proportional to the Zero Effort Miss and inversely proportional to the square of Time to Go until intercept as: Acceleration = NC * ZEM / Tgo 2 + ( NC / 2 ) * at • Predictive Guidance (PG) produces one of the most efficient collision-lead intercept trajectory, by combining the concept of Proportional Navigation (PN) and LOS rotation rate, with engagement geometry and kinematics data (Time to Go). • Time to Go estimation can be augmented with various forms as seen fit, using range to target and kinematics parameters. • Missiles using PG produce a straight-line intercept flight path, where the target appears to be being smacked by a meteor.

I think its great, been flying it in multiplayer since launch day, kill stuff, and not dieing. The implementation of IFF was what it needed to be use-able imo, Everything else is just icing on the cake.

Looking forward to that, what kind of "self protection behavior" ideas were you thinking as far as when ARMs are in play?

NVG's with the Pimax is a little wierd, double visiony on normal FoV. Also I would love to be able to use the VR zoom, without getting double vision with it, and yes parallel projection fixes it, and it also cuts my performance by 40%.

Yea you have to be at no to very low stick input at release point, it just takes a little experimenting to get it just right. Also try pulling into the climb a little earlier like 40 seconds or so, the timing depends on your speed.

Great information, I wonder if these figures match the information ED is using for the radar simulation.

I just tgp the target area, then get low increase to maximum speed and then about 30-35 seconds from release pull up into a 40-45 degree climb, and hold down weapon release, then either oblique split S away or pull over the top and back the way you came If you time it just right it works well against radar sites, and keeps you out of deadly manpads range.

I just had this problem for the first time today, I was around mach 1 low with 500lbs of fuel, and had fired all my weapons, just had empty pylons, and it began to oscillate in pitch, and it got so bad that my pilot blacked out and then I crashed into the ground. I'll check the tacview with here in a bit but I'm almost 100% sure I wasn't hit by anything. *edit* yea just checked tacview, I wasn't hit, oscillations start at low altitude around mach 1, I decreased speed to try to recover, but it got worse and around 0.83 mach my pilot blacked out from the oscillations and soon after crashed into the ground.

I got this weird problem today happen, I was on a multiplayer server, I had just fired my final a2a weapon and was clean except for pylons running at low altitude around mach 1, low on fuel about 500lbs and the plane just started to oscillate by itself, uncontrollably, until my pilot blacked out and crashed into the ground. *edit and I'm pretty much certain I wasn't hit by anything as I was being guided by GCI and nothing was within weapon parameters, but I'll check the tacview when it becomes available.*

I am super interested, I'm running the FSSB R3 Lightning right now, best piece of simulator hardware I've ever touched.

I usually make a kneeboard cheat sheet with information like that on it.

I'm still getting kills just fine with them. In fact the shortest range kill I got yesterday was 20 or 25nm

I've wondered about that as well, like if it was working as intended or should it be just 1 release on the press.