Jump to content

Renato71

Members
  • Posts

    808
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Renato71

  1. POPCORNS! POPCORNS! PEANUTS AND LOLLIPOPS!
  2. No problem, glad to help. BTW, in case I forget to intervene later on, here is the fix for CroAF, using your YU numbers: skin { value = 0.9; material = {"Mig-21_texture001", "standart", "mig21bis_001_CRO_01.bmp"}; material = {"Mig-21_texture001_2side", "standart", "mig21bis_001_CRO_01.bmp"}; material = {"Mig-21_texture002", "standart", "mig21bis_002_CRO_01.bmp"}; material = {"Mig-21_texture003", "standart", "mig21bis_003_CRO_01.bmp"}; material = {"Mig-21_texture004", "standart", "mig21bis_004_ALL.bmp"}; material = {"Mig-21_texture004_1side", "standart", "mig21bis_004_ALL.bmp"}; material = {"Mig-21_texture005", "standart", "mig21bis_005_ALL.bmp"}; material = {"Mig-21_texture006", "standart", "mig21bis_006_CRO_01.bmp"}; material = {"Mig-21_cockpitnight", "standart", "mig21bis_007_CRO_01.bmp"}; material = {"Mig-21_bis_damage", "standart", "mig21bis_damage.tga"}; material = {"Mig-21_Nomera", "standart", "mig21bis_YUG_Numbers.tga"}; material = {"Mig-21_Nomera_fix1", "standart", "Empty_NOMERA_Mig21_fix_1st.tga"}; material = {"Mig-21_Nomera_fix2", "standart", "mig21bis_YUG_Numbers_12_Fix.tga"}; material = {"Mig-21_texture001_antenne", "standart", "mig21bis_001_antenna.tga"}; } Also, while playing with this, I've made a short tutorial on how to do this on your own. Will post later on...
  3. @Kuky: Great work on ex-YU skin and numbers! Those number work on CroAF just fine. Just one thing: in F-16A.skins you should have: material = {"Mig-21_Nomera", "standart", "mig21bis_YUG_Numbers.tga"}; instead of: material = {"Mig-21_Nomera", "standart", "Empty_NOMERA_Mig21.tga"}; The former one does not display last digit at all. Also, there should be a note that bort numbers in mission editor should be entered as 10, 20, 30, 40... instead of 11, 12, 13, 14... cos only the tens are displayed on the aircraft, second digit from editor is transparent. If I explained that correctly :) Unless I'm doing something wrong?
  4. Yes, I remember you talking here about such issues. In fact, later on after I asked about this, I've realized that it may be more complicated then I initially thought, however, I see that you were able to do it! CONGRATS! I'll inform my friends and will get back to you about that! PS - could you please confirm that in BVR mode [3], TD box on HUD can be moved only up and down, and it cannot be moved to the left or right.
  5. Again, no :) I mean, to turn it off, to make it not visible at all, to disable it in full, not to be shown in any way. Just the blank "radar screen". About 6dof, I know about those instructions, thanks, but that method is not preferable to all players. As for "not realistic", I mean - it does not display realistic data in realistic way. Hence, many players voiced to remove such MFD in full, as that rather have blank radar screen. As for "players", I mean buddies of mine that are spending quite a lot of a time with this mod, and does not represent other players of this mod in any way.
  6. I said MFD, the one that overlays radar display in the instrument panel, not HUD :)
  7. I need one confirmation: In BVR mode [3], TD box on HUD can be moved only up and down, and it cannot be moved to the left or right. Question: Any way to disable MFD? Some friends of mine are complaining that it does not look realistic, especially as it moves over the panel while you maneuver the aircraft (due to head movement bob). thnx!
  8. Not quite. They are just slightly upgraded BIS with parts of the Lancer package. Like that antenna below nose. Primarly, its just comm and nav equipment up to NATO requirements (Croatia is a NATO member). At the time of that "modernization", due to political reasons (sold to public as financial probs, but there is more to it...), Air Force and government could not make up their mind whether they want full upgrade to Lancer standard, some other package (21-93, Israel...), limited modernization, or to purchase a new aircraft, which one, and how many (F-16, M2000, and Grippen were discussed). So, the cheapest option was chosen in hope that within few year a final decision will be made. That backfired in the form of lack of funds later then, that led to numerous problems, resulting in recent accident (mid-air collision during a2g training). Air Force is expensive, and politicians rather commit funds into things that are more familiar to them, like bureaucracy, then try to wrap their minds around concepts like flying. Some people, when they do not understand physics and natural phenomenons, invent religion. Others turn to politics. On subject, main factor for such decision was a visit by Russian experts prior to that decision, which evaluated airframes as "too old and too used to fly at all", and recommended to "throw them into trash". On topic, looking forward to see ANY future version of MIG-21 :)
  9. The problem with Lancer is that is both externally and internally quite different. Many things are added to the outside (antennas under nose, on each side of nose, on tail, chaff dispenser under tail, and many more, subjected to a new topic), and the cockpit is significantly different. Adding Lancer skin to this MiG-21bis model is more like a stop-gap measure. Best approach is completely new model, in addition to BIS.
  10. Croatian Air Force patches There is a problem with these patches, as there was very little official about them during early period of CroAF - the one to which two-tone cammo is related. Pilots had patches of their own, ground crew different patches, and since MiG-21 was based at two Air bases, each airbase had a patch of their own. Each pilot, ground crew or any other person working at the base (and NOT related to aircraft) tend to display those patches in various ways, regarding position, design, layout. On top of that, same thing happened to CroAF (general) patch, Croatian flags, crests and any other patch. And, cos CroAF was established during the peak of Croatian Independence War, there was a lot of bureaucratic disorganization and confusion regarding correct numbering, names and layouts. For example, 21st FS patch displays number "1", and so on... In short, there were TWO squadrons, and the best options are: 21. ELZ - Eskadrila lovačkih zrakoplova (21st Fighter Squadron), stationed at 91st AB Pleso, Zagreb 22. ELZ - Eskadrila lovačkih zrakoplova (22nd Fighter Squadron), stationed at 92nd AB Pula
  11. Thanks for the info :) Pity about effect limitations. Still, after having some fun with it, honestly I do not think that I'll use it too often. Oh, I was only referring to H-N cyrillic-latin in video title. Ruskie is 244H, latin is 244N. Back to MiG-21... sweet, sweet, sweet, sweet....
  12. I does not look as powerful as one may expect from a 5kt weapon. Many vehicles lasted way too long. And, I have to admit that I've expected them flying trough the air on a wake of the blast :) BTW, isn't milit designation for "8U69", and factory only 244N (not H)?
  13. Looking better and better! Regarding cockpit lights, could you link them to navigation and/or taxi lights? For example, on take off you have taxi on, and nav on. And, if cockpit is on max, then it means that you can use one command for both, no? And, when lowest cockpit setting is needed, after takeoff, well thats about when taxi light are turned off, no?
  14. NEVERENDING AMAZING! As for HUD/gunsight... Can you disable it using LUA scripts? Like, when mission starts and/or player chooses some of the HUD modes, it will be automatically switched to fixed gunsight reticle SETKA? And also to fix HDD (radar display in this case) in the same manner to show only in the shortest range? I know none of the above will be authentic, but will be much more closer to the original then HUD/HDD from Su-27/MiG-29.
  15. Oh my! Brought tear to my eyes! THAT is the real thing worth admiring! I'll take it any time over mountain of candies and dozens of cockpits for iHog-10 shotgun hairdryer or any other Wii-wonder and its zillions of flight manual pages :D
  16. AMA-ZZZZING-G-G-G !!! I'm going to pop a bear to celebrate those videos! One thing to ask - will you be able to fix that "must have 2-engines" code? I'm sure it must be a significant problem, cos all FC/DCS flyables are 2-engined.
  17. I rather fly FC1 with fixed AI and dynamic campaign, then FC-XX with copy/paste/paste/paste/paste AI.
  18. Amazing! Tell us, about possible "movable" stuff around cockpit, not clickable, just that moves. Dial switches, toggles? Will you be able to make radar display work?
  19. Ayeh, I've did that but some pop-up come up with some ladies :) Then I though "porni" means in Romanian about the same as in English :) No luck in Opera, but it did start after several attempts i FF. Thanks for explanation!
  20. And I have to click what/where/how? Sorry, I do not speak Romanian :)
  21. Looking forward into reading your text. And especially looking forward into looking into this pit :)
  22. Well, something like step-by-step? I know that there are plenty of tutorial around the web, but it would be much easier to follow (and adapt) an actual effort. Currently, its all about reading and comparing some dozens of various tutorials and forum threads. There is nothing comprehensive, all in one place. As far as I have noticed, sorry if I missed anything :)
  23. Amazing work! Just one, slightly off topic request: While you are working on the cockpit, could you be so kind to keep the notes about your work and release them as some sort of tutorial?
×
×
  • Create New...