some1

Use the standard comms menu shortcut (default '/' key).

BTW, Casmo said in one of his videos, that he and most other pilots he knows always flew with force trim off. They only used force trim on the ground to prevent cyclic from flailing around. Tutorials are in, more than a dozen. No voiceover I think, text instructions only.

ILS does not transmit bearing to station, only localizer and glideslope deviation. So the bearing needle won't show the direction when tuned to ILS frequency. It may keep showing bearing to TACAN depending on how the aircraft is wired. ILS also does not transmit DME by itself, but most real world installations combine it with DME beacon. But last time I checked, DCS still does not simulate ILS/DME stations so you won't get DME on ILS frequency either.

The landing light cone magically shines through the nose and lights up the rain above the horizon line, in front of the cockpit. It produces a massive "warp speed" effect on approach. It should be oriented more like the green line here. It doesn't happen in F-16 or A-10, either because different light effect is used, or the light intensity is lower.

A follow up on this topic, here's another set of missions this time testing AI climb performance. Again, you are on his wing, push the throttle full foward and try to keep up. The climb is not extreme, 25-40 degrees depending on the aircraft. It can be adjusted in waypoint options, aerobatics task. From what I can see: - AI doesn't slow down as quickly as the player - AI can keep climbing and maintain level wings at speeds that cause the player to stall and fall down. - AI doesn't overheat (Mosquito) These are the first four aircraft I've tried and they all have the same issues. You're free to check other AI aircraft, I don't expect them to be any better. zAIclimb_Mig15.miz zAIclimb_Mig21.miz zAIclimb_Mosq.miz zAIclimb_Su25.miz

Is that not enough? https://forum.dcs.world/topic/326798-ai-turn-performance-impossible-for-a-human-aircraft/#comment-5226532 You have a mission to test mig21 fm there. Have fun following him pulling 7-8 g.

As posted in the other thread, ED has no intention to take over and continue development of 3rd party module if the original developer ceases the support. Chizh and other ED team memebers made it pretty clear on the Russian forum. Regardless of whether Razbam issue gets resolved or not, that seems to be the current stance about all 3rd parties and it's not much different to how it works with MSFS, Xplane or even Steam itself. Translation: https://forum-dcs-world.translate.goog/topic/317495-dcs-f-15e-strike-eagle-ot-razbam/page/30/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_hist=true

With the new fuzing menus, CBUs default to 300 meters burst, while Mk20 bursts almost immediately after leaving the wing. These are very impractical fuzing settings. This basically breaks all existing missions using these weapons until you go over the payload and manually change the fusing for each bomb.

Checked several 3rd party modules, and the bombs fusing options are not available for bombs connected to ejector racks. Only bombs connected directly to pylon can be customised in the mission editor. The issue is in F14, F15E, AV8, M2000 and JF17.

In the current Dcs version Mk 20 only has timed fuze options, so it bursts after a fixed time, not at fixed altitude. Default fusing options cause the weapon to burst almost immediately. That's rather awkward.

Just watched Kiowa startup video where Casmo explains that he never used force trim and most of the guys he knows didn't either. They only turned it on when on the ground, to prevent the cyclic from accidentally moving around. Turns out you can fly in combat with a cyclic that is "wet noodle" (his words). https://www.youtube.com/watch?v=r-hITMf5FxI&t=618s Spring, friction, damper, inertia are different kinds of force feedback effects that you can implement using electric motors with directX API. All work within the budget allowed by your stick motors, but differently. Trim effects are implemented with spring, not friction. Dampening and friction are two different things. Weight is not friction, etc. You use these words interchangeably. https://learn.microsoft.com/en-us/previous-versions/windows/desktop/ee416335(v=vs.85)

Maybe from here? https://www.reddit.com/r/Helicopters/comments/12d4lj9/question_about_force_trim/ Worth a read. There's even an UH-1 pilot there commenting that he flew OH58 and UH1 with force trim off most of the time, including manoeuvring. Now imagine a fixed wing aircraft, not a helicopter. I've already wrote an example in the previous post. Also, I'm talking about the centering (spring) forces, especially peak forces when pulling high gs, not the relatively constant friction or damping, don't mix the two. The controls are displacement based, so the precision depends only on how small are the movements that you can make with the stick, not how much force you have to apply. Of course having some force resisting your inputs is better, building muscle memory and better feel of what the aircraft is doing. But you certainly don't need 10 kg+ forces to fly with precision in the simulator.

This is a turbofan engine, so it has two independently turning sections. High pressure (Core) that burns fuel and Low pressure which uses the power produced by the Core to turn the Fan at the front. https://en.wikipedia.org/wiki/Turbofan#/media/File:Turbofan_operation.svg The pilot mostly uses the Fan speed (N1 in other engines), as this is the part that produces most thrust of the engine. The core speed (N2) is important for startup and abnormal situations. But the startup process in the A-10 is automated, so for most of the time there is not much need to look at it in the sim.

True, helicopters require lots of precision yet they have the lightest controls, and the pilot can remove all centering with a press of the trim button on the stick, leaving only the damping in place. Flight simmers often forget that flying aerobatics in a real aircraft is a very taxing physical task due to g-forces, and the controls have to be tailored accordingly. Your arm weights around 5% or your body, so, let's say 4kg. At 8g that's 32 kg, and a large portion of that is added to the force acting on the stick, even with zero muscle effort from the pilot. The stick has to be heavy enough to oppose that, through the strong centering, bobweights etc. The worst thing to happen is if the pilot pulls the stick, g-force increases, he inadvertently pulls more, g-force increases even more, and we end up in a positive feedback loop that can even result in pilot blackout and aircraft destruction. Because of the above, the point where simulated force equals the real is not realistic at all In real life g-force "helps" the pilot pull more with less effort. But we have none of it in desktop simulators playing in 1 g environment. By the way, you want precision in the sim, you can remove the spring completely and fly very accurately based on stick displacement only. You can't do that in a real aircraft that makes even meagre 2-3 g maneuvers, you won't be able to hold your hand still. The requirements of real environment are vastly different to the requirements of our simulators, even the hardcore motion platform sims can't fully replicate that. No one makes them requiring 30 kg force either. F-16 stick requires maximum 7,5 kg in roll 13,5 kg force in pitch (that's for the absolute max of 10.86g, requires less for 9g), Airbus stick requires 10 kg force in pitch, 2-3 kg in roll (it's assymetric). That's enough to avoid PIO and unwanted activation due to forces acting on the pilot in flight, without unnecessary workout.

From what I've checked during the weekend, the sight is quite accurate with radar lock. Even seems better than F-14.

The range ring looks good now. Not sure about sight accuracy, it seems a bit off (too little lead), but maybe it's just the sight imperfection.

Sounds like you need to invert FFB axes in DCS settings. For reference, on the ground you should feel a normal centering in roll axis, but no forces on the pitch axis until you gain speed.

In the context of the game, you have some advantage, but not enough to mindlessly lit the burners and extend in every situation. That's what I get from people posting in this thread. In the context of real world comparisons, they usually don't talk about MiG-21bis in particular.

Isn't that what we're doing in this thread already?

Lock first, then switch weapons.

Keyword: in real life. Anyway, the Phantom doesn't get much more thrust from being 70's variant, on the other hand it may have more drag and weight than earlier models.

Usually when you hear such statements in real life, people don't say it in comparison to the 21bis, but older aircraft. 21bis is the latest version of the Fishbed, it only began service in 1972 and it wasn't an adversary for the F-4 in real conflicts for most of its career. The bis was delivered to other countries like Iraq or Syria only in the late 70's and early '80s.

Yes, I noticed the same issue and was about to make a bug report too The problem is that FFB spring force is initially set at lower value on mission start (around 50% I think), while it should be at 100% on airstart when the aircraft is flying at high speed. It seems that the joystick spring force gets updated only when the internal FFB calculations drop from 100%. Until then you're flying with half the force on the stick while internally F-4 thinks you're already at 100% so it doesn't send new FFB numbers. When you slow down or start agressive manoeuvres the new FFB spring values will be finally received, and that's what you feel as sudden force increase, because your stick goes from 50% to 99%, 98% etc. It's more noticeable with high pitch gain settings in special options, because then the Phantom FFB stays at 100% spring in most of the speed range.

You can try this little challenge to verify that. Just load the mig21 mission and stay on his tail in another mig21. https://forum.dcs.world/topic/326798-ai-turn-performance-impossible-for-a-human-aircraft/#comment-5226532 How "flying very precisely" allows AI to sustain 7g at 1000 km/h is anyone's guess.

Easier to tell jester to go back to search mode by double clicking jester action button.