Jump to content

beczl

Members
  • Posts

    1293
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by beczl

  1. See attached docs. How to use and assign Point Helper for your 3D Model.zip
  2. It has a dynamic materials same typa as P-51 has. It's only a modelviewer preview that doens't show too much bro. Not with this skin. All other non unique skin has a dynamic bort-numbers as well.
  3. I'm not 100% sure what you want to ask.
  4. Thanks for the info. I already know this plane. I sent a mail to you.
  5. Georgia and Argentin skin.
  6. New skin finished:
  7. That's a famous skin.:-) It used in several books as an Ukrainian MiG-21. But after some photoshop of course.
  8. The first two skin are finished. :-) The others in progress.
  9. I know this site. Some of them are not fictional. For example Botswana skin based on the Ex Egypt "Chrocodile" skin as well.
  10. You're right. I have a wrong sidenumbers assigned to this plane. I'll change it. Thanks for to report this issue. :thumbup:
  11. It doesn't interfere with any other part of the development. Sometimes the coding and math things caused too much headache so I often do an other task especially create skins. Also it's quite easy due I created a good photoshop templates. Anyway thanks guys the new request. I'll check all of them and start to creating them.
  12. You can post here your camo request for MiG-21Bis. I try to create as many user requested skin as I can. Rules: - I accept only MiG-21Bis skins requests that based on the real example (e.g. the skin must be exist in real life) - In cases if your AF operate other variant of MiG-21 (MF, SMT, M, MT) I accept other subtype skins as well. - Fictional skins allowed only the countries that doesn't operate MiG-21. (e.g. USA, Canada, France, etc...) - Post as many good resolution of pics or link about the requested skin as you can. You can also send me a mail, PM about skin examples. The following skins are already done for DCS:MiG-21Bis: British finctional #1 British finctional #2 Bulgarian camo Croatia camo Cuba camo Czech metal (based on MF) Egypt camo Egypt crocodile Finnish camo East-German camo German camo (after reunion) Hungarian gray Hungarian metal Hungarian camo Hungarian "Capeti" Indian gray Iraqi camo Iranian camo Namibian camo Polish gray Russian camo (Afghanistan) Russian Sokol Russian metal Russian camo #1 Russian camo #2 Serbian gray Slovakian gray (based on MF) Ukrainian camo USA fictional (based on US PF skin) Vietnam metal Yugoslavian gray
  13. It's just a "connection". You have to develop your own FM and connect to your developed AC as well.
  14. In real life the usage of the flashlight is the worst option that the pilot can do at night. Because if the pilot use any high lightsource (for example flashlight) it can be cause a temporary visual loss. Also without electricity the plane systems doesn't run most cases and most instruments are not working also. So the pilot have only one option = eject.
  15. Which EDM material type selected? Try to set it to Mirror. Also set it all unused Map amount from 100 to 0!!!!
  16. Yes it's a separated mod that need to be installed over the standard DCS:World.
  17. Yes and served in many country. Vietnam, Africa, Afghanistan, Warsaw pact, end so on... Also thousands of S-60 was build in Hungary between 1969-1980 as well. Well it's under discussion with myself. :-)
  18. The P-18 is planned for SA-2 due this was also in use the other systems as well.
  19. Yes absolutely. :pilotfly:
  20. Some new WIP and test pics. The S-60 57mm AA gun and ZSU-57-2 SPAAG is finished. Now I'm working on the Puazo optical fire controller and SA-2F complex. The missile launcher pad, V-750V 11D missile and SA-75M radar is WIP.
  21. Sorry my fault. It's an early morning. :-)
  22. Should need to be insert the following before function update due the sensor_data declaration is required.. local sensor_data = get_base_data() make_default_activity(0.05) --20 time per secondSo the code looks like this: local sensor_data = get_base_data() make_default_activity(0.05) --20 time per second local m_max = get_param_handle("Max_Mach") local auto_ext = get_param_handle("AutoExtended") function post_initialize() auto_ext:set(0) m_max:set(0) print("post_initialize called in BrakeController.lua") end function update() local spdbrkpos = sensor_data.getSpeedBrakePos() local mach = sensor_data.getMachNumber() if mach>0.78 then m_max:set(1) else m_max:set(0) end if mach>0.78 and spdbrkpos==0 then --BRAKES OUT LoSetCommand(147) -- Air brake on auto_ext:set(1) elseif mach<0.75 and spdbrkpos==1 and auto_ext==1 then --BRAKES IN LoSetCommand(148) -- Air brake off auto_ext:set(0) end end need_to_be_closed = true -- close lua state after initialization
  23. Try to use "cycled" parameter for your 1000 and 100m needle. Like this: --1000 ft needle Altimeter_1000m_Gauge = CreateGauge("cycled") Altimeter_1000m_Gauge.cycle_value = 1000 Altimeter_1000m_Gauge.arg_number = 53 Altimeter_1000m_Gauge.input = {0.0, 1000} Altimeter_1000m_Gauge.output = {0.0, 1.0} Altimeter_1000m_Gauge.controller = controllers.base_gauge_BarometricAltitude --100 ft needle Altimeter_100m_Gauge = CreateGauge("cycled") Altimeter_100m_Gauge.cycle_value = 100 Altimeter_100m_Gauge.arg_number = 51 Altimeter_100m_Gauge.input = {0.0, 100} Altimeter_100m_Gauge.output = {0.0, 1.0} Altimeter_100m_Gauge.controller = controllers.base_gauge_BarometricAltitude And no alt100 and 1000 variable need to Altimeter.lua
  24. You have to use the exact names that available in Damage.lua.
×
×
  • Create New...