Dolphin887

Please send your key with this message to support@leatherneck-sim.com I'll check the status with StarForce server. Thank you.

Пожалуйста, отправьте эту ошибку на LNS Mantis http://Https://leatherneck-sim.mantishub.io

Please send support request on support@leatherneck-sim.com in order to keep this thread clean from individual instructions. Let us know which DCSs you have on your PC along with Beta. You'll get your answer in minutes.

Server side needs some time to refresh the data. It's there - don't worry. Confirmed.

Curve at 13.000 is wrong by large margin. The rest of the curves comply with simulated model, precisely measured under defined conditions. I may post the charts later, in separate topic (I don't have them here).

Can you be more specific please? Under which circumstances (flight conditions) you observe excessive acceleration? Acceleration was extensively tested, it's set up according to valid curves (not all published curves are valid).

Please wait for the 2.0.5 patch. We will try to patch it next week.

This is impossible to do (literary).

Provided that the procedure is correct, you probably have more than one failed deactivation in your registry. Please delete the "Leatherneck Simulations" registry entry, and activate patched MiG in Beta. You will get one extra activation.

DSSRapidfire and zxarkov, if you are using DCS Beta, and deactivated MiG before the patch, MiG should be fine. I guess there is some procedural error here. Anyway, if you are certain you patched Beta, please delete "Leatherneck Simulations" registry entry, start DCS and activate the MiG. You'll get one extra activation (instead of 2 if the procedure was correct).

Which DCS version you are using? Please send me PM for further instructions.

Please, don't use MiG in unpatched versions (Alpha and Public) to avoid possible SF conflicts: - once you deactivated MiG in Beta, it will deactivate in all the DCSs you have, - patch the Beta, activate and use MiG in Beta. - don't attempt to activate/deactivate again in Public and Alpha: They are ready to receive new patched MiG binaries once they are released. We will attempt to arrange 2.0.5 MiG patch distribution next week. If we succeed, Public is next. We apologize for this complication; we believe things will work much better concerning the SF once we are through the process. Regards.

I understand your frustration after using MiG with wrong roll rate for so long. But this is more closer to reality then previous setup. Fact is - even with increased roll rate, roll is still intentionally decreased a bit, since the gaming equipment (joysticks) have very little movement limits compared to the real MiG stick, making the simulated plane feels "too agile". This is subjective feeling caused by the limitations of a gaming hardware (I elaborated this in details in one document I have created for ED). My recommendation is to spend some time flying the patched MiG, with whatever curves setup you see fit, you might start to like it eventually. Regards.

Not the bug. Check your roll/pitch curves, try setting them according the manual. MiG-21 have documented max. roiling speed of ~420 deg/sec. This patch actually fixes the slow roll and inertia MiG had before.

No. Once you deactivate in any version, wait for the patching. You can still use any other aircraft except MiG-21 until the patch is released. Open Beta will be patched first - you will be able to use MiG-21 very soon. We will try to arrange open Alpha patching as soon as possible.

1. We will check this at StarForce server. 2. I admit that's the worst case scenario for us. The only thing I can advise at the moment is simply not to use (try to activate/deactivate) MiG-21bis in unpatched DCS 2.0.5. You can still use all other aircraft. We will talk with TFC/ED management if it is possible to release MiG-21bis patch for 2.0.5.

We did not get your e-mails. Please write to support@leatherneck-sim.com If you are using DCS 1.5.6 please read this. Instead of activating now, I advise waiting for incoming patch (should be released this week). Whatever you decide, we are available on mentioned e-mail. Regards.

We did that - we added 2 activations for every key. Its mentioned in the documents. However, the remaining number of activations might not show correctly until the patch "sticks" to StarForce server.

Дорогой всем, Большинство из вас знают, что у нас есть проблемы с защитой StarForce для модуля MiG-21Bis. Основная жалоба заключалась в том, что защита не была достаточно гибкой для изменения аппаратного обеспечения и / или программного обеспечения пользователей. Мы относились к этому очень серьезно и посвятили свое время работе над исправлением вместе с людьми из команды StarForce. Наш патч Starforce будет распространен по следующему плану openSpeak DCS World по Eagle Dynamics, который должен быть выпущен к концу этой недели. Это важное событие для всех нас, и для успешного и правильного исполнения нам потребуется ваше сотрудничество. Короче говоря, чтобы сэкономить одну активацию для MiG-21Bis, вам придется деактивировать модуль ДО ПОЛУЧЕНИЯ патча DCS 1.5.6 на ваш ПК. Мы советуем вам сделать это в течение следующих 24 часов. Мы создали руководство с подробными инструкциями, которые помогут вам подготовиться к входящему исправлению: найдите два одинаковых документа, написанные на английском и русском языках здесь https://forums.eagle.ru/showthread.php?t=185325 Пожалуйста, не стесняйтесь распространять их среди ваших друзей, которые используют модуль МиГ-21Бис. Обратите внимание: если вы используете DCS World 2.0.5 openAlpha, вам не нужно делать это в настоящее время. Однако, когда Eagle Dynamics решит распространить патч для DCS World 2.0.5 openAlpha, мы будем распространять тот же патч StarForce; Поэтому потребуется аналогичная процедура. Мы сделаем все возможное, чтобы своевременно информировать вас. Мы искренне извиняемся за это неудобство. Наша конечная цель - ваше удовлетворение: есть вещи, которые мы должны сделать, чтобы добраться туда, и есть что-то, что мы должны сделать вместе. Мы будем оказывать помощь на этом пути, и мы надеемся, что этот переход будет успешным. Мы также надеемся, что вам понравятся исправления, которые мы подготовили в следующем патче. Если вам нужна помощь, напишите нам по адресу support@leatherneck-sim.com. Ваши преданные разработчики, LNS

Dear all, Most of you know we have issues with the StarForce protection for the MiG-21Bis module. The primary complaint was that the protection was not flexible enough for the users' hardware and/or software changes. We took this very seriously, and dedicated our time to work on the fix along with the people on the StarForce team. Our Starforce patch will be distributed along Eagle Dynamics next DCS World openBeta patch, which should be released by the end of this week. This is a major patching event for all of us, and it will require your cooperation for a proper and successful execution. In short, in order to save one activation for MiG-21Bis, you will have to deactivate the module BEFORE the DCS 1.5.6 patch is downloaded to your PC. We advise you to do this in next 24 hours. We have created a guide with detailed instructions that will help you prepare for the incoming patch: please find the attached two identical documents written in English and Russian languages. Please feel free to distribute them among your friends that are using the MiG-21Bis module. Note that if you are using DCS World 2.0.5 openAlpha, you do not have to do this at this time. However, when Eagle Dynamics decide to distribute the patch for DCS World 2.0.5 openAlpha, we will distribute the same StarForce patch; thus a simmilar procedure will be required if you do not use any other version. If you patch 1.5.6 openBeta first after doing the procedure, it is not required again for 2.0.5 openAlpha update. If there is a 2.0.5 openAlpha update and you update that first ((doing the procedure) before updating 1.5.6 openBeta), then you do not have to do it for 1.5.6 openBeta. The same as in 1.5.6 stable release. We will do our best to keep you informed in time. We sincerely appologize for this inconvinience. Our ultimate goal is your satisfaction: there are things we have to do to get there, and there are some thing we have to do together. We will provide help along the way and we hope this transition will be sucessful. We also hope you will like the fixes we prepared in the next patch. If you need any help please write us at support@leatherneck-sim.com. Your dedicated developers, LNS Important MiG-21 StarForce patch MARCH 2017 EN.pdf Important MiG-21 StarForce patch MARCH 2017 RU.pdf

The "Starter" device in MiG is actually a sequencer for proper engine start-up. Once used on the ground, it should not be turned off except in the case of unsuccessful start up (for resetting purposes). It should stay ON whole flight time, in order to enable proper engine starting in the air (if necessary). It does not consume the fuel during the flight nor on the ground (it's electrically powered).

Thank you. Just tested the mission. If you delete the MiG wingman, FPS will normalize. I attached the edited mission. It is clearly that simulation process takes CPU time if AI is next to human MiG (this is visible on FPS display, "Simulation"). I have no idea why this happens... We will have to check this with ED if they have some time. MiG-21 Cold Start.miz

Controllers are educated and trained to do this, and gain experience in time. You will probably not find any documents that cover the training and tactics, but let me say that it could be complex as you want it to be... Good controller will decide critical targets, keep you undetected, sneak-guide you behind them with your radar in stand-by, zoom you up and behind, and tell you when to turn your radar on (missiles can reach the target). Acquire the target either visually or with the radar, and shoot with either IR or SAR. Your wingman/s do the same. Hit them, split them and finish if you can, if not - dust off towards nearest AA or friendly fighter group. They might make another sneak run. Excellent controller will allocate an aircraft or two to keep the enemy busy, while you execute your plan. Bad controler will get you killed pretty soon. Machine guidance is not the best option due to lack of flexibility and creativity.

Guys, have you reported this SPS issue to our Mantis? Can some of you go there and check?

Thank you guys, no worries. We'll be here...