Dolphin887

See manual thread. There will be something, but not in next few days, still WIP. In the meantime, here is one short final for all: (Ignore the FPS, my PC is a dinosaur)

No without specific Leatherneck permission. Even in the test version there are many things that are still WIP, but not so much important for the internal tests (liveries, damage model, manuals finalization). Those things will be fixed along the way in next week or so, and the test mod will update daily. Besides, since Mig-21bis is pretty different than other aircraft it would take at least a week of learning, flying, considerations and the passion to settle down so that experienced player give his impression about the mod. Nick added: "But you will be seeing an increase in promotional material in the coming days for sure, from various sources."

About planned release date /June 2014/ A lot of question concerning the release date spread all over the forum - so here is the updated information about our release procedure and plans. We informed the Eagle management we want to release later this month, which was well received. In order to do so, we need to pass internal quality checks with the Eagle. This is in all parties interest: ensure mod quality, integration stability and players satisfaction. The module will be available for the Eagle internal tests tomorrow (09. June). We don't know how much time the Eagle will need for their tests - but I assume anything up to 10-15 days (could be much less). Note that the Eagle needs to check the level of integration of 21 to DCS core, and perhaps extend their code to fully support it. On the other side, they might send some feedback or implementation requests which we need to implement. In such case, we will provide updated mod for further tests in very short time; we usually patch the mod in max 12-24 hours, usually much less. If all goes according to our plans, we will be ready at the end of this month (anywhere from ~20. June +). There are things we can't anticipate. This is our plan, and we will try hard to follow it. Mod should be initially available on the DCS site for download. If all goes well, we might go for the Steam later.

... This is what we have after 18 straight hours of protection work. You'll get it today. Good luck there.

You caught my attention with your post. We will have to think about it from the patching perspective, StarForce protection and Eagle management opinion. As for the 21 release, if it would be an utter necessity - it could be released in 2-3 days. However, we want to wrap it up properly, and we want Eagle green light. Bottom line is - the development is finished, we are adding features and polishing things.

Yes. Differences are not significant. However, few things should be clear concerning the available (real) charts: 1. Some data are obsolete, never corrected/updated, and many are not publicly available. 2. Principle when it comes to data presentation is to always present data with great safety margin, mostly for average flying technique and average pilot. I believe this is the case for most aircraft, it surely is for all that I was/am flying. Possible, no promises. Im not sure we will focus on that after release, we will have lot of things to do mostly of administrative nature (e.g. backers, huge job) and user support in sense of additional features and bugfixing. But players can have a lot of fun researching and creating their own data-tables and charts, comparing them, testing... That is interesting aspect of gaming, at the end. Not everything need to be a fight.

No. We have no time to create more complex telemetry tools for data extraction (we have it for the real time tests). Original charts could be used for some references. Note that all simulated aircraft deviate more or less from the real aircraft, it is normal and can't be avoided. I really tried to diminish the differences, but I had to compromise also.

True. I attached the (early) theater setup I'm using for last 6 days for the campaign in English. No too many options, but still. Pink circle is the combat range for 21 from Kobuleti (takeoff - rush to the edge on ~MIL POW- stay there 5-15min - get back). Very difficult terrain, complex for helicopters units simulation (forward FARPs, just 2-3 mountain passages), ground units possible to simulate in later stages. Limited options for NAVY, especially reciprocal. This theater will change as the campaign develops. I hope I'll have enough time to do campaign on Russian, for the other side.

You might be right, it could be, depending on which definition someone is using for classification. I have never found a common, officially accepted definition of mil jet aircraft generations. Early 21 surely belongs to 2nd while later to 3rd generation (to some extent). Maybe the compromise would be to classify 21BIS as early third generation.

That is possible, however, it's a huge project: not only that many guidance algorithms have to be created (which is pretty complex task since we are talking about 3D vectors along with 3D objects orientation of each object), but that also require voice messages recordings (at least 2, Russian and English) and voice support implementation. Extension of radio messages menu also. It could be done as a separate project, and development would last at least few months. Software can change in whichever direction. Problem is to define priorities. Changes (even small) cause domino effect: things are connected. Thus, anything new has to be incrementally introduced. Players are often forgetting that other units in the DCS have their own "intelligence" and sensors/weapons definitions which are tailored for a modern battle theater. Aircraft sensors and maneuverability are usually better than in reality, and this was necessary in order to support a game-play. For example F-4 and F-5 are very agile, most notably on low speeds along the longitudinal axis (roll); radars are at max efficiency all the time within their FOV. Awareness of the AI is also very high. But this is a game and it is normal. Reality is much different. To change everything in DCS would require rebuilding many things. With MiG-21BIS players will have opportunity to see how it really was to sit in a 2nd/3rd generation tactical fighter. It will be hard, that is for sure.

Yes. See attachment. No. See attachment. This is a description I wrote few years ago, to explain the RP-22 to Eagle, for implementation and support, in gaming purposes. This document was presented in locked 21 forum, in one of the Laszlo Becz posts in this thread http://forums.eagle.ru/showthread.php?t=97314. MiG21BIS radar RP-22SM basic description.zip

No, generally you need to be below the target. EW gives you BRAA. Where will you fly depends on you. That will certanly be impossible for many. Same as previous. You are right. "GCI" became a common term for many things here. I allready explained the source of this confusion. MiG-21BIS will be unique in many ways: most people will find it very complex to master, and difficult to manage. It can't be compared to the fighters that players used to fly in FC/X. When it comes to aircraft use in combat, players will discover their own tactics, like they did for any other aircraft so far.

MiG-21BIS is using the Eagle implementation of interception control. My opinion is that the implementation is very good at current DCS development stage. I would only add option for dedicated controller for each fighter group. The only purpose of this is to reduce the radio chatter when there are many fighters airborne, and improve the CI response time to user inquires. But this is not necessary since all units in the DCS can have dedicated radio channels. Presented image is from the actual mission. The data given by interception controller are sufficient. In this particular mission some 60 aircraft are airborne at the same time, about 70% are fighters. Once again: the whole confusion concerning the "GCI implementation" was caused by Laszlo Becz statement the he "implemented" GCI. He did not implemented it - he only created a template EW unit which could be used on BLUE (generally Western) coalition, since it lacks the EW radars (thus, GCI). Process of templates creation is explained in DCS User manual and future MiG-21BIS manual. This was already mentioned in some other thread/s.

First post in this thread updated.

"GCI implementation" was inaccurate statement. There is nothing to implement. When it comes to avionics, LAZUR ("the gauge") is not part of current cockpit (it conflicts with RSBN/PRMG), but this will not prevent players from CGI support, regardless of the coalition/country they select. Player can create any custom unit/group as a template in the Mission editor, and use it for any coalition/country. For example, player can create EW radar unit comprised of RUS EW radar and other ground units. This group/unit can be used from templates list in any mission, as a group/unit assigned to any side/country. This process is well described in DCS User manual, in "Create unit template" chapter, page 210. Because of this confusion, GCI creation process is described and illustrated in 21 Manual. We can only see if we can ship a template with the 21 installation. I'm not sure about this however, since it will conflict with local files, so no promises.

I apologize, we can't release TOC at the moment. Content have to be approved, at least to some extent, before it become public. I am not writing any other version except the English (core). Language-organized teams will have to do that. Personally, I will be happy with every added translation of this or any other mod for DCS, therefore, I honestly hope there will be translations to south-Slavic languages.

It has English cockpit, including hints. It's just that some screens are taken with RUS cockpit.

Some update Although there were no images of the manual so far since it was a draft version, and manual images posted on Cobra's update are unfortunately from obsolete manual version (draft 1.83), here are few current images (draft 2.00). Manual is in finalization phase. Currently adding description of custom GCI unit creation, custom options and other features not directly connected with aircraft/systems handling. Once I'm done with the manual Ill have to compile/create Quick start guide, which will also consume few days. Apart from the manual, I have created 15 interactive training missions in last two weeks. I will create several single/multiplayer missions. I don't think we have the time for the campaign creation unless specifically requested by Eagle/TFC. Note: All interested in translating the M and QST will be noticed on time, no worries. However, you will have to work hard to deliver. At the moment, M have 170 A4 pages.

Guys, you all have right to be disappointed. Pretty much how we felt just a months ago, for two months. The whole project was at stake, and situation was serious. Bottom line is we received support from legal parties included in this project, most importantly TFC and Eagle Dynamics, finally resulting in granted licence from ED, for which we are thankful. On the other side, we lost two months and we knew we have to rebuild our reputation not from the scratch but from negative initial position. Very hard and unpleasant, but necessary and normal. We won't meet the given release date, we admitted that and we are not hiding it. You will get your long waited aircraft; we simply need time to finish mostly boring and administrative things (tutorials, missions, campaign, manual, promo things etc.). We are extremely sorry for this, and there is nothing we can do to accelerate this process except to stay focused and continue to work. If MiG-21Bis lost some of you along the way it was just it's destiny. We are doing our best, and want you to have it. At the end, it is 21 last chance to ever be re-created. I honestly don't think that aircraft will ever be done at this level for any home or military class flight simulator. My personal thanks to people who understand our situation. Once we release, our common troubles will be forgotten.

About the manual Lot of people asked similar questions: will it be available in their language, how does it relate to original 21 manual, is it near completion etc. Since we are making 21Bis mod for DCSW, there are differences between simulated 21Bis and real 21Bis (as you must have noted so far). Therefore, the only relevant document for DCS MiG-21Bis will be its manual. This does not prevent you from using any other document you might have, but DCSW MiG-21Bis will be what’s written in its manual. Manual is near completion, still, I have to write and illustrate missing parts concerning recently added features, most notably new weapon use and complex navigation subsection (e.g. radials interception with RSBN). Note that manual can be finished after we finish everything else (e.g we need finished internal/external model and textures for manual illustrations). Before we conclude it (“lock” it), it has to be approved by Eagle. Manual in your language? Absolutely. Once concluded in English, manual will be available for translation to anything community can provide. Document containing the detailed “call for translators” will be presented here on time. Translations that satisfy required standards, quality and are delivered in time will be included in official release. Other translations (rejected, late, partial etc.) can still be presented to community here or elsewhere to support local players, but will not be included in release. **************************************************************************** Leatherneck Simulations is in need of volunteers for MiG-21BiS flight manual and other materials translation. 1. RESPONSIBILITIES - Provide a translation of material given to the English language, in exact form as provided, on time as required, - Change (update) translated material if original material changes, within given timeframe, - All produced materials must be internationally compatible with word processing tools so they can be opened and further processed on machines other than translator’s (E.g. Chinese translation must open and appear exactly the same as on translators’ machines). - All original material that translators receive must stay classified even after publishing. 2. REQUIREMENTS - Language of translation must be a candidate’s mother tongue, - High English language proficiency, - High level of literacy, excellent knowledge of translating language grammar, spelling and language writing style, - Good knowledge of word processing software (use free Kingsoft Office Suite, not MS Word or other commercial office tools), - Good typing skills (fast typing rate), - Good experience with Eagle Dynamics products line, with focus on DCS World, - Good or average technical and military aviation knowledge, - “Team Player”, - Responsible, Honest and Confidential person, - Age 23 or higher preferred. 3. JOB DESCRIPTION - Translation of ~180 A4 pages written in English (lots of illustrations, so it’s not text only), - Translation of a “Quick start guide” or similar additional material if required, - Translation (“Localization”) of coded training missions or interface such are hint messages appearing on mouse-hover in cockpit, - Expect that you will have to translate minimum 5 pages per day per person. - Expect that you will have maximum four weeks to complete and cross-check translation. - Expect that your team will have to translate minimum 10 pages each day, - Expect that you will have maximum four weeks to complete and cross-check translation. 4. BENEFITS - Credits for translation you provide as complete and accepted translation; credits will be stated in the Manual. - You will get one digital copy of the DCS: MiG-21BIS upon release, per person in a team, for accepted translation. - No credits for partial/incomplete/low quality translations. We will not use those - they will be rejected and not included in the release. - You are volunteering for this task, so understand that we can’t provide any money (we don’t have any funds). 5. PROCEDURE Although this list might look imposing to you, please note that we are looking for quality and reliable personnel, thus the strict requirements. You will have to work in team with at least one person speaking your mother tongue (translation target language). Primary reason for this is because the material is demanding, and you will need to split the workload. Furthermore, this will help you mutually support and supervise each other. You will encounter some difficult concepts and unknown aircraft systems for which you will have to provide explanation based on existing explanation in English, which can be difficult. Procedure: - Find few friends to work with. Selecting the right people is critical for success, otherwise you wont make it alone. Optimum is 2 - 4 persons. - NOTE: No more than 4 persons per team. - Calculate translation time: if you have 3 persons in a team, divide 180 with 3 and than with 21 -> this gives you 3 pages per day per person (9 pages daily, minimum). If you think that the workload is too high - don’t apply, you won’t make it. Last 5-7 days use to cross check the Manual and send it. - Download attached CV form and fill it up. Save the document in .xls format (not anything else). - One person in your team will have to send me an PM containing filled CV form for your team. Insert “Translation application LLLLL ” in e-mail subject, where LLLLL is target language. Example “Translation application Spanish”. Don’t send your application before Sunday, 27. April 2014. This job offer will close next Wednesday (30. April 2014.) in 24:00 UTC. Further steps will be announced. ************************************************************************** ************************* UPDATE 04. July 2014. ****************************** ************************************************************************** Here are some information that can answer many questions in this and possibly other threads. - Manual text and core illustrations (text related) are finished according to my criteria as an author. Art and Appendixes are WIP, and they will be concluded before the release (artistic illustrations, legal things, "special thanks", "contributors list" etc.). - Following translators teams were accepted for translating the manual to their languages: Russian Serbian /Cyrillic/ German - All gentleman in translating teams put considerable effort to meet the deadline, for which they have my sincere admiration. Their names are included in all versions of the manual, and they will be honored according to our agreement. No less, and possibly more. - Following translation satisfy the quality criteria at the moment: Russian Serbian - German manual is currently missing translation for a dozen+ pages. Since there are still some time, I sincerely hope the team will dedicate some free time to finish it. It would be a great misfortune not to have it in the release, since it is around 80-90% done at the moment. - As you know, MiG-21 need to pass internal TFC/ED Q testing procedure, so will the manual/s. All of them - no matter of the present translation state - are shipped with the aircraft and are available to testers as a references. From the point of the manual, this means that things might be changed, altered, deleted, or additional content requested. Aircraft might still change in complexity and features - so will the manual. Therefore, there is no point of releasing the manual before the aircraft is "locked"and cleared for the release. I as an author don't want to publish non-confirmed, possibly partially-relevant, partially-obsolete document. At the end, I will have to ask you to use this thread for all manual related posts. It is hard to track the posts and discussion if they are under the different topic, thank you. Leatherneck Application Form Translators.zip

OK, it's late, I'm still awake, just finished few things with Mike /Rudel/. I have few minutes for update - not a fancy one /I have low-end PC, no fancy screens.../. In latest set of weapons tests, Roland and I implemented 3 pods available for RU planes: GUV-7800 G, GUV-7800 M and UPK-23-250. Note that I have never saw 21Bis with any of these. Most integrated weapon is UPK-23-250. Really impressive thing and closest to MiG-21Bis weapon system. I really recommend that one instead of 7800M. It has 2xGsh 23mm guns /which is the same gun 21 have/ and can pack serious punch. Besides, it fits the ASP natively. Pure Eagle weapon, no tweaks or "guessed" stuff. UPK will come with 21 for sure, well see about other things /more integration and tests needed... time?/. I have no screens at the moment, sorry. Mike might fire few rounds for you if he has some time tomorrow. As for the Kh-66, it's done also. You will have difficulties with this weapon, although it is a fun and a challenge to use it. Ill tell you just one thing that will create a lot of problems: asymmetric load after one missile is fired. Asymmetric load for heavy payload is not allowed on 21. However, once you get in the cockpit it will be your problem. At the moment it is ours. You'll have to discover other problems and realize why weapon development went the other way. We only need to integrate new Kh control box although it could be used even without it. (Note: screens here are 3 days old, that's all I have at the moment.)

Bit more explanations: The image you see in this thread contains weapons 3D models. That does not mean that the weapon was ever implemented properly. What you have seen in some videos were mostly external visual effects (GUV for example). That is still very far from proper implementation and integration of particular weapon into the simulated world. Every weapon has it's aerodynamic, ballistic and energy features, some more complex than others. For rare weapons and for weapons that did not see wide usage it is almost impossible to find those data, making the implementation very time consuming with problematic results. When I started testing all previously declared weapons, I found out that big part of it was incorrectly defined, some working wrong, and some not integrated /properly implemented/ at all. I wasted several days redefining and integrating all declared weapons; some of them were significantly improved, but I also found out that some can't be integrated at the moment. On the other side, some weapons (mostly bombs) are just a bit changed copies of original Eagle weapons - which is very well defined and integrated. I temporarily ruled out "low-quality implementation" weapons for different reasons. I never said I'm not interested in implementing GUV and 66 for example; it was scheduled for more screening in next several days after we tune up smoke containers and perform some other tests concerning ASP operation in A-A mode. I cant promise you anything at the moment, but we will dedicate more time to currently disabled weapons /as we planned/, and you can rest assure we will do our best to enable weapons that satisfy our requirements.

Hello Aginor, let me answer your question briefly. The list you presented here is the list of 3D models that Laszlo Becz developed previously. Some of the weapons from that list can't be /properly/ integrated into DCSW at the moment, most notable examples are flammable/incendiary containers/bombs. Some weapons is not included since it proved useless during testing (e.g. small bombs, GUV due to small caliber intended for use against infantry not effective against tough targets, some drag bombs (difficult declaration, problematic aiming and behavior)), or impossible to aim with ASP sight (-6.5 degrees limit). Grayed entries on the list are excluded /I might have made mistake or two since Im not on my PC at the moment/. Some original ED weapons are included and are not on this list. Launchers ( APU-13MT APU-13MI (U) APU-7 APU-60-II APU-60) UB-32M2 UB-16UM S-5M R-3R R-3S R-13M R-13M1 R-60M R-55 RS-2US S-24A/B H-66 ZB-500SKS ZB-360 SPRD-99 JATO SF-4 Light Flare Chuted for SAB-250-200 SAB-250-200 Candle Bomb OFAB-500SR Chuted FAB-500SR Chuted ODAB-500PM Chuted PTAB-500S Rocket/Chuted FAB-500TA High Speed BETAB-500 FAB-500SL Chuted FAB-500M54TU Retarded FAB-500M54 ZAB-500-400 Incendiary FAB-250M54TU Retarded FAB-250M54 OFAB-100-120 Retarded ASO-2V Flare/Chute dispensers SPS-141-100 ECM Jammer & Flare/Chaff dispensers IAB-500 "nuke" GUV-8700 Gun Pod (9A669), 1x AGS-17 30mm automatic grenade launcher GUV-8700 Gun Pod (9A624) 2x GshG 7.62mm & 1x Yak-B 12.7mm Fuel Droptank 490l W Fuel Droptank 800l Fuel Droptank 490l C

LUA script v2.0 for the Beczl's MiG-21bis Please download and overwrite the old mig21.lua script with this improved and debugged version (2.0). This is the LUA script for Beczl's Mig-21 for improved realism; the script has been tested both in single-player and multiplayer games. Here is the list of implemented improvements: *************************************************************************** FLIGHT DYNAMICS REALISM IMPROVEMENTS 1. The script correctly recognizes the MiG-21bis plane and activates only if the pilot chooses MiG-21bis. It will not interfere with other plane types. 2. If you put an orange smoke generator on pylon 8, the script will turn smoke generation on/off depending on the throttle settings (<75% off, >75% and <95% on, >95% off). You will be able to see the simulated exhaust smokes. 3. The script will generate “shaking view” effect in following conditions: - throttle >80% AND - altitude AG <300m OR g load > 5.5 In order to actually see this effect, you need to have cockpit mouse instruction set to CockpitMouse = true in View.lua file located in \Ubisoft\Eagle Dynamics\Lock On\Config\View folder 4. The engine maximal power setting is limited to closely match MiG-21bis engine performance. With this script, afterburner won't fire at full power, it will fire only for limited time and with minimal thrust. 5. If you have fuselage fuel tank, you won’t be able to extend the air-brakes until you jettison the tank. 6. If the pilot pulls more than 5.8g with the fuselage fuel tank installed, the tank will drop-off. Unfortunately, due to LO code this can only happen if the wings are in near level position (e.g. entering the loop). 7. Maximal AoA is limited to 28 degrees. For very short time pilot can go beyond 28 degrees but with some difficulties in airplane control. 8. Maximal G-load is limited to 7.7g. In reality, max. allowed G load is 8, but in LO 7.7 is closer reality match. Like in 3. the pilot can go beyond 7.7 for short time. 9. The script calculates the engine stress: the engine is stressed if - the pilot force the engine beyond it's limit for >10 seconds, - the pilot flies the plane beyond IAS or Ma limits for >10 seconds, - the pilot flies with the negative g (e.g. inverted) for >10 seconds, - the pilot forces the plane to climb beyond certain altitude (21.000m / 64.000 ft) In case of the engine stress, the engine will shut-down. The script then calculates the time needed to recover the engine and enable the restart. The more pilot insist on stressing the engine, the more time will be needed for the engine to recover. 10. The script will sense following hard-limits: - maximum altitude 21.000m (if exceeded the engine will shut-down), - maximum IAS and Ma (if exceeded the engine will try to decrease power first, and after some time - if speed is not reduced - it will shut down). 11. Script is able to sense landing and give instruction for drogue-chute to be released. However, this doesn't work due to LO code. 12. The script will collect some data during the flight which will be written in a MiG21bis.log file at the mission exit (the log file is located in \Ubisoft\Eagle Dynamics\Lock On\Temp folder): - type of the plane - if it is not MiG-21bis the script will write "Main aircraft is not MiG-21bis - attempting to confirm this..." - Highest IAS (km/h) - Highest Ma - Highest altitude (m) - Highest G - Highest Alpha (AoA) - *** FINAL REMARKS on exit *** - IAS (on exit) - Altitude above ground level (on exit) ************************************************************************ WEAPON SECTION OF THE SCRIPT - I will try to implement some real limitations but this is going to be hard since LUA interface is not supporting much of the weaponry functionalities. *********************************************************************** Regards. THE SCRIPT: mig21bis.zip