Michelange

Update : Same Package for BS and FC2 see link Post #1 above.

Feedback of the firts comparison between DCS 1.0.2 and FC 1.2.1 : - The directory Bazar is the same - The directory \Scripts\Database (a part Troops) is the same - The db_countries.lua is the same. What does this all mean ? It means that all new 3D models and skins are now compatible between the 2 sims.

Mainly, by copying/pasting/overlaping/changing colors of the once in game. Then adding or retouching it in image editor like Photoshop or Gimp. AND a very, very good news : the only difference between DCS-BS and FC2 is the name of the datas for the troops LOP (for FC2) / bs (for Black Shark). And that's normal the squadrons are not the same. That mean we can use this template with few modifications. Wait next update.

:megalol: At the beginning of All this, I've made a fictionnal country GROLAND well known on french speaking TV as little country with outstanding inhabitants. Yes all this is possible... :pilotfly:

Hy all Helo Pilot's, The BS patch is now out, and there are few differences between BS and FC2.0 in the file organisation. To maintain the compatibility between futur FC2 mods, i began a template for integration of new countries. NOW for BS, I will edit the same template with the DCS differences to maintain also thie compatibility between the 2 sim's. It is the same package, the difference is only in the squandon directories. If you want help to complete the troop sing's and award's please post THERE Thanks

Be careful, it's NOT a MOD at now, it's a template for moders. To have a standart. If you wish test it you have to modify db_countries.lua manualy. The other changes are writen in the Package's Readme. It is very important to respect the structure of all the files. If there is one mistake, it can cause a crash. @ MOA : I can add New Zealand but at the moment it's not my priority. I'd few free slots for other countries. What i prefer is a complete set (troops awards)

I don't Have this problem. Do you have the last package with \Config\Localizer.cfg file in ? It's this file where the Problem is. Added Croatia.

You have several solutions for this and it depends on the moder. By hand, Look into my db_countries.lua under Japan I copy/pasted the Japanees skin of Gy's F-15 cnt_unit("{CD247E45-4702-4E3A-A659-4F5E0E645D2B}", "F-15C", { color_scheme("{JASDF4fe-4c3a-4d79-b232-fd000ecJASDF}", _("JASDF F-15J 303SQ"), 9), }), - There are no limitations to add Skins, if the model is in LOM format. - There are limitations of the number of skins for the old CMD models we need new 3D models like up coming Mig-29 or F-16. To pack and add skins is another big work (I dont have time to translate my tutorials about this.) You can find cosmonaut's tutorial in english here One more point : - I didn't Assign the new countries to a default coalition it can be done in \BlackShark\data\scripts\Default_coalitions.lua - You must create à New mission to place the countries in a coalition. - I saw that some grades in FC2.0 are not correctly assigned (Example France : 2nd Lieutnan, the seen stripe is not the correct one it's the Aspirant's one.) I won't correct this by editing the stripes (delete Aspirant). The reason is that in DCS/BS its correct and it's only a problem of the coord's in db_countries. And Last point : At the moment there is a litle difference between DCS/BS and FC2.0 concerning the troops, if the coming DCS patch corrects this issue, we can use the same Package . If not it will be different. MA

No, I don't have pics and data's to complet the package :cry: I need your help for this. The Sim's limitations are : - 6 Grades (ranks) - you must use LO names First lieutenant, Captain etc... - the Callsigns : Uzi, Endfeild etc... I think it's connected to the cokpit speeking... Serbia is in the Pack as #35. ++

I've update the countries.zip. I corrected the folowing issues : - the ranks are limited to 6 and i can not use the countries names. rank('Second lieutenant', _('Second lieutenant'), 0, {0, 0, 64, 32}), rank('First lieutenant', _('First lieutenant'), 15, {0, 32, 64, 32}), rank('Captain', _('Captain'), 30, {0, 64, 64, 32}), rank('Major', _('Major'), 60, {0, 96, 64, 32}), rank('Lieutenant colonel', _('Lieutenant colonel'), 120, {0, 128, 64, 32}), rank('Colonel', _('Colonel'), 240, {0, 160, 64, 32}), If I change this it will appears in the your own contrie names for all the countries - I add Localizer.cfg, if this is not correct it will cause Sim crashes when you are flying. It is now working correctly. There is a readme inside for testers. Limitations : (in todays pack) - No Awards - No Squadrons

That's the purpose :smilewink: - Set the plane skin's in the right countries (for exemple Gys Japanees F-15) - Avoid futur MOD overlapping. - At now, i try to collect the missing Data's, Squadron's and Medals are missing and difficult to find. - For flags and all the stuff : Look in the countries.zip, most of time i was simply changing the colors, overlaping some textures (basic stuff), the only thing to respect is the format. - BUT DON'T USE THIS PACKAGE NOW : there are somme missing files, it's a moder pack to be completed.

A litle Test to assign a plane. There is on problem left, the correct stripes are not shown for the new countries.

OK I do

Hi all, Some people of the moder communauty are working on integration of new countries. I need help to complet Awards and Squadrons of the "Template Package" for the following countries : SWEDEN, 18 HUNGARY, 19 CZECH, 20 AFGHANISTAN, 21 AUSTRALIA, 22 CHINA, 23 GREECE, 24 INDIA, 25 IRAN, 26 IRAQ, 27 ITALY, 28 PAKISTAN, 29 POLAND, 30 TAJIKISTAN, 31 TURKMENISTAN, 32 UZBEKISTAN, 33 JAPAN, 34 SERBIA, 35 CROATIA, 36 --- Done by Shark LITHUANIA, 37 NEW_ZEALAND, 38 PORTUGAL, 39 ROMANIA, 40 ALBANIA, 41 AZERBAIDJAN, 42 BULGARIA, 43 ESTONIA, 44 FINLAND, 45 LATVIA, 46 SLOVAKIA, 47 SLOVENIA, 48 MACEDONIA, 49 ARMENIA, 50 AUSTRIA, 51 IRELAND, 52 KAZAKHSTAN, 53 KYRGYZSTAN, 54 SWITZERLAND, 55 Most is done but i'm searching mainly Squadron badges and medals of those countries. If you have pictures you can post it there. The purpose of this is to have common Keys CLSID and also ID's for each countrie. The choise was done with Pink_tigrou (for his Grippen Mod), Batou (for his afganistan terrain). The new coutries are not in the standart ED's coalitions (this is my choise), you can choose it when you create a new mission, you can also change this by editing Default_coalitions.lua in \BlackShark\data\scripts. WARNING : - The Add a country.rar is not a MOD, don't install it, open and look inside it's the tempate for moder's. Thanks Edit 15/05/2010 : - Correction of the ranks and limitation to 6 ranks due to ED's specs - Working version NOT a modman Pack. - No Awards and Squadrons. - Assigned Gy's Valery's Japanees F-15 to Japan for test - Add Serbia - Add Croatia - Add a template to complete the missing pictures for Squadrons and Awards Edit 16/05/2010 : - Little text correction orthography of Afghanistan was false - The only difference between BS1.0.2 and FC1.2.1 now are the troops Edit 17/05/2010 : - Little update of : Add a Country - Template for BS or FC2.rar - Update : Countries.rar : Now common with DCS BS1.0.2 the only difference is in the Squadon directories (for BS troops /bs folder, for FC2 /LOP folder) - Next updates are only saqdron pictures and assignement in the above quoted folders. Edit 30/05/2010 : - Update : Countries.rar : add some countries, flags and stripes done - Macedonian stripes are not the corect one's didn't find it at now. Edit 06/06/2010 : - Last Update of countries. - Began to populate Awards and Squadrons Edit 06/07/2010 : - ground troops are done - Added some medals and squadrons for the logbook. Edit 27/11/2010 : - Added Switzerland You can also use this template to add your own countries but then give us an update. Important : - The last country Number is 55, if you create a new country you must increase this number, but befor this, verify in the forum that threre is no other addon with another number. Very important : - If you uninstall the mod. Befor doing this, go to the Logbook and choose a countrie from Ed's original list. The logbook informations are stored after each change and may cause errors if the stored data are not in accordance with the game's data after uninstallation. - To make an addon for one country use the Add a Country - Template for BS or FC2.rar - You can use this now to : - Change the place of a plane like Valery's Gy's Japanees F-15. - Add your own skins dont forget to declare it in the correct Plane.lua and Plane.skins files. You moders know how do. - Define your countries units (mostly a copy/past of existing units from the original db_countries.lua) Add a Country - Template for BS or FC2.rar Countries.zip

What I'm trying to say is : Moders, please take care off several things. There are also some rules to test a Mod. - Install the MOD, créate a mission with the mod's and ask a non moded user to join your mission and verify together what you see. - Install the MOD, créate a mission without the mod's (sample use Ed's standart slots for a skin) and ask a non moded user to join your mission and verify together what you see. - Same for the Non Moded User, créate a mission (with the changed planes for example) and ask a moded user to join your mission and verify together what you see. I give you few examples : - A-10 SimMod for FC2.0 : Did you see, as me, that some weapons aren't attached on the pylons ? The Minox's Mod is solving this issue by correcting the coordinates. - The F4-E & Harrier by Mitch and Tomcat's : The skins don't have the same position as in ED's standart for the first once. That mean if you are using this mod on a server mission, there is a big chance that the F4-E is not visible for non Moded players. - And so on... To the moder's : try to respect as mutch as possible ED's spec's. If it is not possible the User must be warned. MA

Hy all, Concerning the futur Mod's for FC2.0 and DCS, it think that it will be important to have some common rules. The countries : The integration of new countries will cause the problem of the overlaying (Same ID for 2 different Mods). Example : - I know that Pink_Tigrou's Sweden has the ID=18 - In \BlackShark\data\images\Countries\flags-1.png you have all the flags : Sweden, will be at the end of this list - The corresponding line in \Scripts\Database\db_countries.lua to assign the flag is {0,510,64,30} that's Pink_Tigrou's Sweden. I think, if each new country has it's own ID, we will prevent futur problems. The skin's There is a problem of transparency In FC2 and BS if you change or move the ID's, for that all mod's should respect the given ID's of the skin's. If you add some skin's after the common one's don't use it on server missions. DCS KA-50 What will be the game play if add a new plane in FC2.0 and don't have the mod in DCS ? You have to think about this ! Are they other rules ? MA

You can add a new plane with one of the FM in game : Try this. At now, adding a new FM is not possible. We have to search.

Adding a countrie is not a problem. At the end of this tutorial you will find 2 templates. One for FC2.0 the other for Blackshark. At now, there à little différences between the tow sim's. If you are taking a look in the /Blackshark directory, you will find pictures of flags from countries who are not in the sim.

OK this is how to add a new F-16 BLK 60 in FC2.0 In Names.lua add this line to have the FM of the F-16C : laTypes["{082D2561-FB8B-11d5-9190-00A0249B6F01}"] = F_16;-- = 7; -- F-16 Fighting Falcon This is a copy/past of the original line with CLSID+1 In db_units_planes.lua add at the end : plane_file("planes\\F-16C-3.lua"); In db_countries.lua add under cnt_unit("{082D2561-FB8B-11d5-9190-00A0249B6F00}", "F-16C bl.52d", { color_scheme("{eeaab67f-6f15-4a5d-9b74-1c08ee971e9b}", "USAFE 555th FS (AV) Aviano AFB"), color_scheme("{189e0024-e439-494c-8b7e-817a2884ab85}", "PACAF 14th FS (MJ) Misawa AFB"), color_scheme("{65a85d13-351d-450d-84f9-c5cc528228cf}", "PACAF 35th FW (WW) Misawa AFB"), color_scheme("{89c5ff57-d84c-4950-8109-dafd18e40143}", "USAF 77th FS (SW) Shaw AFB"), color_scheme("{356613e0-28af-4ca1-ac5d-1c590bb213c6}", "USAFE 22nd FS (SP) Spangdahlem AFB"), color_scheme("{382e7a6a-b29f-4881-9c28-d9ea192bc4c6}", "USAF 414th CTS (WA) Nellis AFB"), color_scheme("{924ed5b8-c371-4315-b29f-c0be4ecb188d}", "USAF 412th TW (ED) Edwards AFB"), color_scheme("{d00a836b-6c9c-40f9-a8c5-39501ae3a178}", "USAF 147th FIG (EF) Ellington AFB"), }), this files : cnt_unit("{082D2561-FB8B-11d5-9190-00A0249B6F01}", "F-16C bl.60", { color_scheme("{eeaab67f-6f15-4a5d-9b74-1c08ee971e9b}", "USAFE 555th FS (AV) Aviano AFB"), Its only a copy past with CLSID+1 Now in directory \Scripts\Database\planes : copy / past and rename F-16C-2.lua to F-16C-3.lua you must also edit the first line : return plane("{082D2561-FB8B-11d5-9190-00A0249B6F01}", "F-16C bl.60", _("F-16C bl.60"), I've added also in wsTypesTree.lua this line ["F-16C bl.60"] = F_16, under [wsType_Fighter] = { but i think this it is not necessary. That's It You have now a new IA with the FM of the F-16C that will open all the doors to add the 3D models of the planes we have. The rest of the issues are details to adjust but the principle is there. Sorry, but it's to difficult for me to translate all the moding stuff I've explained there. :smilewink:

Yep, I think also that it's possible to add New objects. Now I'm exploring this way. For exemple : wsTypes.lua wsType_Air = 1 wsType_Airplane = 1 wsType_Fighter = 1 F_4E = 45; -- Is that the FM of the F4 ? I saw in this file 57 planes ID and ..... that : LastPlaneType = 150; !!! In WSTypesTree.lua -- That's only à tree ? [wsType_Air] = { [wsType_Airplane] = { [wsType_Fighter] = { ["F-4E"] = F_4E, In Types.lua planes_types[45 ]= {wsType_Air, wsType_Airplane, wsType_Fighter,F_4E} -- array of the wsTypes data In Names.lua laTypes["{4B75FEBA-9997-4D34-A0D6-0DB061350951}"] = F_4E; -- assygn the CLSID ? And in F-4E.lua -- the definition of the plane return plane("{4B75FEBA-9997-4D34-A0D6-0DB061350951}", "F-4E", _("F-4E"), I want test this : - If I change in wsTypes.lua the line F_4E = 3; -- 3 = Su-27 what's happen ? -Or if I add : In Types.lua : planes_types[58 ]= {wsType_Air, wsType_Airplane, wsType_Fighter,F_4E} In Names.lua : laTypes["{new CLSID}"] = F_4E; In Mirage-F1.lua : return plane("{new CLSID}", "Mirage F1", _("Mirage F1"), Do I have than a new IA Plane with the F_4E FM ? Grimes : the only thing is to find where or how the FM is assigned to the model, all the other things is done in the models.lua files in \Scripts\Database\planes for the planes. :music_whistling:

Depending of the server integrity check defined by the server in his file Config/network.cfg The original : integrity_check = {"Config/Weapons"} should pass, if not you need to change this line. There is a discution about this in the forum.

Bonjour, je ne sais pas si ce problème à déjà été reporté. Je n'ai rien vu à ce sujet et je ne sais pas si c'est aussi le cas dans BS. Vu qu'on a la possibilité de rajouter des skins aux modèles 3D.Lom en modifiant les fichiers .skins correspondant et en rajoutant des clés dans db_contries et a-10A.lua par exemple, certaines personnes se retrouvent avec FC2.0 modé et d'autres avec la version originale. Lorsqu'en réseau, un avion avec une skin complémentaire est utilisée (et que cette skin a été choisie), la personne se connectant avec FC2.0 original, ne voit pas l'avion... (ce n'était pas le cas dans FC1.12, il voyait dans ce cas la première skin du slot). Exemple (les valeurs sont à titre d'exemple): - J'ai 10 skins originales pour le Su-27 (numéro 1 à10) - J'en rajoute quelques unes pour le plaisir des yeux (numéro 11 à15) - Je créer une mission avec la skin 12 - Si quelqu'un se connecte à ma mission et n'a que le jeu 1 à 10 d'installé, il ne voit pas l'avion. - Dans FC1.12, il avait la skin 1 à la place. Je tiens à précise que je sais de quoi je parle, qu'il n'y a pas eu d'erreur de manipulation et que les personnes qui ont constaté cela avec moi ont aussi de l'expérience dans ce domaine. A+ MA

For french readers look there : Nouveau réarmement Now, you have to edit 3 files : 1°- Assign à new key in Scripts\Input\WingmenCommandPlane.lua WC['RearmingPlanes'] = { keyCommands = { {combos = {{key = 'F1'}}, down = 4501}, {combos = {{key = 'F2'}}, down = 4502}, {combos = {{key = 'F3'}}, down = 4503}, {combos = {{key = 'F4'}}, down = 4504}, {combos = {{key = 'F5'}}, down = 4505}, {combos = {{key = 'F6'}}, down = 4506}, {combos = {{key = 'F7'}}, down = 4507}, {combos = {{key = 'F8'}}, down = 4508}, {combos = {{key = 'F9'}}, down = 4509}, {combos = {{key = 'F10'}}, down = 4510}, {combos = {{key = '1'}}, down = 4511}, --> for key the new rearm in n° 4511 {combos = {{key = 'F11'}}, down = wsRepHumanBack}, {combos = {{key = 'F12'}}, down = wsRepHumanAbort}} } 2°- Créate the new list in the game : In \FUI\Resources edit the folowing files depending on witch plane you need a new rearm list RC-Rearming-su-27.res RC-Rearming-su-33.res RC-Rearming-F-15C.res etc... \dialog \begin \tag{-1} \upright \coord{-387,5,-5,280} --> add 20 each time you add a new key (for 1 more key 300) \caption{Select preset...} \musthavecursor{0} \drawitself{1} \color{0, 0, 0, 50} \layer{100} \end ... Blabla... ... At the end of the file add \static \begin \tag{14} \font{2} \coord{12,265,387,285} -- New line \caption{Key 1 -New rearm} -- New text description \end NB : You can also place the F11 et F12 keys at the end of the list but dont forget to change the value of row position. 3° - Creat the payload : Edit Rearm.lua in \Scripts\Aircrafts\_Common Search the [4010] value of the plane you need to add a payload ex: rearm_payloads[su_33] [4510] = { blabla... } Add at the end the new payload : ex : 2 s-13 on pilon 3 et 7 [4511] = { { Pylon = 3, LauncherCLSID = "{FC56DF80-9B09-44C5-8976-DCFAFF219062}",--B-13L - 5 S-13 OF LauncherCategory = "11", }, { Pylon = 7, LauncherCLSID = "{FC56DF80-9B09-44C5-8976-DCFAFF219062}", LauncherCategory = "11", }, } that's it.