All Activity

If I’m intercepting a formation from long range often the radar can’t distinguish between contacts if they are in a close formation (understandable). so say I launch a phoenix from around 40nm and then say I want to launch another pheonix at 25nm, the radar jester is controlling won’t let me launch another pheonix at this time because all he can see is a single contact which I have already launched at. I know a workaround to this which is switching to the back seat then pressing key command Next Launch. Then I can return to the front seat and resume my pilot role. What I would like to know is if there’s a way to ask Jester to do this without leaving the front seat? I’ve looked at the Jester commands under the pilot controls and can’t see anything like it.

Guess I should get to work on a default QF-4 skin for us to include, I think I already had some of the masks created for the hi-vis paint, just need to make a very faded and weather worn Hill scheme.

Thanks for the response. I have a Rhino too. When you pull through it, what do you see the virtual stick does? Follow your stick movements, or stay below the limiter visually?

Ага, к ним. А то заказать-то я заказал, но я ж никогда не носил ничего для коррекции зрения, так что несколько волнительно - а как оно будет. Так что твой опыт важен )

I don’t believe the AH-64 uses that to land on a ship if it did. Does it?

Ich war jahrelang Intel Nutzer. Habe nun aber vor geraumer Zeit auch auf AMD gewechselt und nutze nun einen 9800X3D und bin sehr zufrieden mit.

I'm not sure if I'm interpreting the question correctly, but with my VPForce Rhino, there's the high AoA buffet (from the TelemFFB software), then a very clear and deliberate 'stick push' forward from DCS itself, which you can pull through. Obviously the Rhino can't generate 17kg, but with the stick force set to max it's pretty vigorous nonetheless (I don't keep it at max though). I have mine mounted to the floor with an extension, topped by a Virpil Mongoose T50. It worked with zero issues from day one with the AFC self test, which was a bonus. I think it's doing what you describe properly?

2. Так и должно быть.

Nein ist er nicht, stimmlich kommt es dem Nahe, aber laut dessen Insta-Profil, ist er es nicht.

@AeriaGloria I will check your video as well, I've just seen it after posting.

Is there any news or update on this?

what upcoming Normandy 2 revamp? I haven't heard of that.

Тонкая синяя линия XD

You can use the search option in the russian part of the forum, check the popularity of the word fulcrum

True, this same technique applies to "short landings", and is similar to the night landing technique when assessing height is difficult. For most aircraft, the main landing gear can sustain the Vz of a standard 3° slope impact without flare (at normal weight).

I have just bought the Apache in the sale, first helo and proving challenging after fixed wing! In Wags video the FLOLS overlay is in the top right corner, I have this enabled in Supercarrier SPECIAL but it doesn't show in the Apache?

1. Налёт на МиГ-29А идёт только в общий налёт. В налёте по типу не учитывается. 2. Закрылки выпускаются только в посадочное положение как по кнопке "Взлёт", так и по кнопке "Посадка".

In addition to checking the "module specific FFF" option, also make sure you have the force strength sliders both set to zero. FFB won't work otherwise.

Energy saving mechanism on E-Cores on modern CPUs that some applications are somehow unable to "unlock" inducing processing latency, from what I understood so far. Here is a tutorial to make disable it in Windows and to forget about it after:

Excellent stuff: the only proviso I'd make is that 'aiming at, or short of the threshold' will only apply if you intend to flare. If you're in an F-14 or F/A-18, and intend to land hard, carrier-style, your velocity vector wants to be on your intended landing spot so you stay on AoA, and on the intended glide path, until impact.

Его действительно больше стало после последних обновлений DCS.

@Reezo_200 Thank you for the update. The discord link works properly. Mike Force Team

Hi, First of all, I want to thank ED team for this clean and well appreciated release. The Fulcrum is awesome. Now concerning this topic. I also noticed some inconsistency during radar usage but : at this moment we don't really know how ED team plans to design this radar model. So it is hard to say if something is a bug or not. In the first release of the manual there is no sufficient informations to juge wether or not everything is correct or bugged. Based on what I read in DCS forums or heard from well documented DCS members I made with hexcalidraw a "fulcrum radar workflow". It would be appreciated to have a feedback from ED team and from you guys to have a clear view on : - What we should expect from the radar (in terms of performance etc) - What is implemented or not at this moment - What will be implemented or not in the future - How to correctly operate this radar (it might change depending on DCS tactics or historical doctrines) - Correct this diagram and maybe give an accurate one for the future manual versions if it helps community With that, I think we could have more tools to understand what we are doing, what might be a bug or not and save a lot of time for everyone I guess. PS : I won't debate on open source data or anything else external from DCS forums since I had problems with moderation in the past, so I will rely only on your advice and hopefully on ED team' feedback. Have a good day !

That’s so cool!

Thanks but this i dont understand! What are parked cores?