Michelange

It works fine since one year in MP, tested and used regulary. Fell free to adjust, adapt, the mod as you like. Few knowledge in programming is necessary. Some remarks : - make sure that the server uses the mod. Should work w/o but it's better. - many times the mod is not working if you use another script who's not following this rules. I stress this point because it's the only way to make scripts compatible. TACTVIEW and LOTACT2 uses the same rules and are working together with Blinklights.lua. For the moment, G15 script, for example, is not compatibl and will inhibit the other scripts (I'd this case with a friend of mind) - As usual, the FC2 blinklights script will not pass thought "Integrity Check" as well as the other scripts, if config.lua and export.lua is checked.

@Pouga : You know the little bug, i PM'ed it to you. - The problem is when we use a new plane like in efA Mod can we assign a specific rearm list on parking ? - For now we are bloked on the file RC-Rearming-new_plane.res (like RC-Rearming-f-16a.res) and dont know how to make it visible in game, or specifically where to index this file.

Dont think, I saw a little error in the script. EDIT : - the version on page 3 #25 is working OFF and Online for FC2 - the version on page 2 #11 is for FC1.12

@diveplane : Ok I test only the US planes in the script. I've updated the script for you and I suppose that it's "A10A" for the A-10 For people who are interested in Lua programing there is a Dev tool here with Text editor

Yes, we at EVAC are using FC1.12 in our instruction because there is no way to impose MDF and HUD failures online in FC2. We use this in our lessons to practise instrumental night flight with fog for beginners of course. :pilotfly:

I must do some tests to identify the plane Names. If you want you can also do this, it's easy. - Create an empty Blinklight.log file with any text editior in /temp directory. - Edit blinklight2.lua and delete the -- (the -- are comments or not active lines) in the following lines : -- local file = io.open("./Temp/Blinklight.log", "w") -- io.output(file) -- io.write(self.plane) -- io.close() This will then write the type of your plane in the Blinklight.log file each time you start the Sim (Fly). For example US planes you should have A10 and F15 (I have to verfy the syntax). After it's easy : if self.plane then time = LoGetModelTime() -- Model Time atAir = LoGetAltitudeAboveGroundLevel()>0 -- Airborn over 3m navInfo = LoGetNavigationInfo() -- Info Hud masterMode = navInfo.SystemMode.master -- Nav mod if self.plane == "A10A" or self.plane == "F15C" then -- US plane onTime = 0.1; -- Time light on offTime = 0.2; -- Time light off else -- Russian plane onTime = 0.9; -- Time light on offTime = 1.9; -- Time light off end end thats It. Test IT, I will send the file if you dont have any result. :pilotfly: PS : - You can copy past the red lines in the Blinklight2.lua file I dont think that I've made an syntax error. :music_whistling: - The colors are there for you to understand the relations - To diveplave : Attached te lua file for test and modman pack Edit : the last version works online BlinkLight2.zip

NO, and few weapons have now new 3d models in FC2. The R77 was adapted there is a Modman Pack avalaible. I thing yes, it is easier to skin for artists.

Thank You diveplane. Love the different Time lapses in the video. :pilotfly: Question : Have You another script running in export.lua ? If yes, the scripts have to follow this rule. If not, they will not work together. You have also an errors.log in the temp folder to help you to find where the problem is. (be carefull if you have a "Null value error" it can be normal you are not always in the plane) :smilewink:

You are at the right place. Both solutions are good. Replace it or modify it. It's your choise. Make a copy of the originals if you are not sure. :pilotfly:

Originaly it was done for FC1.12 and it is working in local as well as online. There is only one line différent. To avoid problems I've attached the FC1.12 version below. There is a readme.txt inside for the installation procedure. You can not turn OFF the lights in NAV (1) mod it's permanant. You can use it like this : - At parking : turn the nav lights ON (Ctrl + l). The lights will not blink. - After Take off the lights are blinking. - You recive the ordre to FENCE IN, change your mode to BVR (2) or other mode depending of what you've briefed (Air/Groud, BORE etc...) - Verify in what state are the Nav Lights, if they are on (pull it off CTRL + L). The state (on/off) of the lights is depending on witch moment you've changed NAV to BVR. It is due to this conditions : if atAir and masterMode == "NAV" and self.plane ~= "su25" - atAir is over 3m you can change this but, be carefull if you change it to 50 m the condition is changing under 50m (in low flight it's peraps not what you want). I've no found an other solution to have the airborn information. - masterMode == "NAV" the other values are "BVR" "CAC" "LNG" "A2G" "OFF" look in export.lua - self.plane ~= "su25" this is to exclude Su-25 an Su-25T from the script, you can also excude other planes. This is not possible there is no LUA command avalaible in lockon to get keyboard state information. There is another LUA Blinklights script on Lockonfiles who's using a external soft to do this but for me it was not the best solution. All the commands avalaible are listed in Export.lua. In fact Export.lua is a big (poor commented), list of Lockon's exchange routines. In the original file there is no active line, all the file is a big comment ( -- text or --[[ several lines of text ]] are comments in LUA) BlinkLightFC1.12.rar

I've reuploaded the script. Yes, edit the script BlinkLight2.lua you will fint this line : atAir = LoGetAltitudeAboveGroundLevel()>3 -- Airborn over 3m You can change the conditions or delete this but then you have also to remove it from this line if atAir and masterMode == "NAV" and self.plane ~= "su25" then - No, this command LoSetCommand(175) concerns all the lights there is no command for red or green light. - The only solution is to do this in animation of a new 3DModel (ADA mod Les mirages is using this for exemple) Not sure, but if I refer to Tacview and Lotact you must extract all the planes ID from LoGetWorldObjects() then use the routine (sorry, I'm not programmer but some people may help you) Yes, you are not alowed to get some informations (cheating) LoGetSelfData() is passing the check but LoGetModelTime(), LoGetAltitudeAboveGroundLevel(), LoGetNavigationInfo() are perhaps not alowed and there are no other solutions. The best solution for me is to include this as animation in the 3D model in LOM format and only the owners of the original 3DSMAX can do that try to contact them. Best regards

Hi, This is my Blinklight mod, it works after take off and only in NAV mod (Su-25 and Su-25T are not inclued they have this in game) This is only working for flyable planes. It is not possible to do this with AI the only solution is to have a new 3D model with animation of the flash light. Hope this is what you are searching BlinkLight2.rar

Batou is working on it: Afghanistan WIP I Work in parallel with him to populate the army's, countries and some skins for planes. For Su-25 there are some in Kazakhstan, Uzbekistan, Iran and Iraq, it would be interesting to have some skins. Here some shemes

This script will not work together with Tactview or Lotact, it's not following this rules : Myfonction = { Start=function(self) -- Place your code here end, AfterNextFrame=function(self) -- Place your code here end, Stop=function(self) -- Place your code here end, } -- ========================================= -- Overload you can see this in tactview.lua or Lotact.lua -- ========================================= -- Works once just before mission start. do local PrevLuaExportStart=LuaExportStart; LuaExportStart=function() Myfonction:Start(); if PrevLuaExportStart then PrevLuaExportStart(); end end end -- Works just after every simulation frame. do local PrevLuaExportAfterNextFrame=LuaExportAfterNextFram e; LuaExportAfterNextFrame=function() Myfonction:AfterNextFrame(); if PrevLuaExportAfterNextFrame then PrevLuaExportAfterNextFrame(); end end end -- Works once just after mission stop. do local PrevLuaExportStop=LuaExportStop; LuaExportStop=function() Myfonction:Stop(); if PrevLuaExportStop then PrevLuaExportStop(); end end end cheers

We use it for Both :pilotfly:

Hi, Very beautiful :thumbup: It, would be interseting to make some skins for this countries (to populate the Mod) I'm Working on it : This is for Uzbekistan :smilewink:

Salut, Génial tout ça comme d'habitude. Merci

The pack has now 33 new countries : - 90% of ISAF (Singapoor is not in) - 90% of EUFOR (miss Ireland, Austria and Cyprus) - 90% of the region Black Sea / Caspian Sea (miss Kazakhstan & Kyrgyzstan) I can add these last ones, your opignon ?

Normaly Not. It may cause other issues if a player join a server and don't have this mod, like invisible planes. If you build a mission and use the standart coalitions, then there should not be any problem. All this is to test.

This is the actual list country:add('RUSSIA', 0) country:add('UKRAINE', 1) country:add('USA', 2) country:add('TURKEY', 3) country:add('UK', 4) country:add('FRANCE', 5) country:add('GERMANY', 6) country:add('CANADA', 8 ) country:add('SPAIN', 9) country:add('THE_NETHERLANDS', 10) country:add('BELGIUM', 11) country:add('NORWAY', 12) country:add('DENMARK', 13) country:add('ISRAEL', 15) country:add('GEORGIA', 16) country:add('INSURGENTS', 17) country:add('SWEDEN', 18 ) country:add('HUNGARY', 19) country:add('CZECH', 20) country:add('AFGHANISTAN', 21) country:add('AUSTRALIA', 22) country:add('CHINA', 23) country:add('GREECE', 24) country:add('INDIA', 25) country:add('IRAN', 26) country:add('IRAQ', 27) country:add('ITALY', 28 ) country:add('PAKISTAN', 29) country:add('POLAND', 30) country:add('TAJIKISTAN', 31) country:add('TURKMENISTAN', 32) country:add('UZBEKISTAN', 33) country:add('JAPAN', 34) country:add('SERBIA', 35) country:add('CROATIA', 36) -- From here there are no Flags and stripes avalaible for the moment country:add('LITHUANIA', 37) country:add('NEW_ZEALAND', 38 ) country:add('PORTUGAL', 39) country:add('ROMANIA', 40) country:add('ALBANIA', 41) country:add('AZERBAIDJAN', 42) country:add('BULGARIA', 43) country:add('ESTONIA', 44) country:add('FINLAND', 45) country:add('LATVIA', 46) country:add('SLOVAKIA', 47) country:add('SLOVENIA', 48 ) country:add('MACEDONIA', 49)

Hi, you can begin to search there Wiki, for color shemes look here and here. The list of countries will also continue to grow. Take à look here on greg765 list. At the moment i'm to busy in other moding stuff (FC2 adaptations) to continue myself this work befor end June. If you want help you're welcom.

Yes would be interesting to know if we can add a new plane with FM and 3D.

Yes we found some solutions, but impossible to add à new FM. There is also a solution to add new planes but we must overlay the 3D models. That's usefull for single/two seeters for example (Pink_Tigrou's Gripen, Futur Mig-29 ?)

Download this Pack for Su-25T You can install it with Modman or manualy. 1°- Look into Script\Database\Planes\Su-25T.lua you will find a list of new skins return plane("{31E68806-0891-4e12-9573-D1CFEA8C96F8}", "Su-25T", _("Su-25T"), .... ------------------------------------------------------------------------- -- New skins ------------------------------------------------------------------------- .... color_scheme("{433CEED3-8098-4962-865A-6925E639D978}", _("Su-25T Hungary"), 29), -- this is the last of the list for Hungary 2°- Now go to Script\Database\db_contries.lua and open it. Search Hungary ------------------------------------------------------------------------- Hungary -- Saab Mod sides ------------------------------------------------------------------------- country("{EDFC0F44-58FB-11DF-B840-25F7DFD72085}", _("Hungary"), "Hungary", "HUN", "Hungary.png", 19, { Planes = { CATID = "{C168A850-3C0B-436a-95B5-C4A015552560}", Plane = { -- Place your planes here cnt_unit("{31E68806-0891-4e12-9573-D1CFEA8C96F8}", "Su-25T", { color_scheme("{433CEED3-8098-4962-865A-6925E639D978}", "Su-25T Hungary"), }), - You can do this from number 14 to 29. - It's a self made skin pack from several Su-25T skin found on LockonFiles. - I prefer a packed CDDS as all the skins in Temptextures, it loads faster. All moders should do this. - If you are looking in the different files in the pack you will understand the relation between CDDS packs (there is a CDDS viewer in modman)-> .skins files -> Plane_file.lua -> db_countries.lua PS : -The last 2 skins declared in Su-25T.lua, number 50 and 51 are not in the pack (our school skins not public), delete this lines. If you do not this, you will see it listed in the editor but not accessible. - Open also all \Bazar\World\Shapes\SU-25T.xxx.Skins files and delete skin { value = 5.0; -- this values are not usable for you .... } skin { value = 5.1; .... } Be carefull dont delete the last }, If you read french, see my signature Try it

No, and it's now totaly the same as FC2.0. The only difference is in the declaration of the CDDS files : graphics.cfg for FC2.0 bs_graphics.cfg for BS1.02 And that should be managed by Modman by selecting your Sim.