Charlie_01

Sorry, I've forgotten that we are talking about an F-16"A" livery and that the A's liveries work differently from C's ones. To put the canopy skin into the livery's folder and calling it with the command "false" is enough for C's liveries only (I've tested it). For the A ones you have instead to place the modded canopy skin (either with empty low half or with different numbers there) directly into the "...\Bazar\TempTextures" subfolder of the game directory (it seems not enough to put it into "TempTextures" of the Saved Games directory, but I'm not completely sure about that because some tests are still on the run...).

Hey usctaylor, maybe you can check this out at F-16.net... You can simply Googling F-16.net xxxxx (where xxxx is each tail number listed into the Sierra99's post above). As well you don't need to make a fixed number for each skin because the large numbers are the dynamical ones you can set in ME. You only need to add either a canopy skin along with the appropriate little numbers (AF with the pair of numbers below: see attachment) into each livery's folder plus the appropriate line into the related description.lua file (just like i'm doing with my customized canopies, for instance: {"texture F-16.tga f2 g0",0,"f-16-glassmix_num-w2.tga",false}; ). That's all... Hope this could help. :thumbup:

I think you're right... Most of the canopy files' names ends *.tga.dds. This should mean they were exported to .tga format before to be converted to the final .dds skin. To be precise I've found some of them ending *.bmp.dds too. Anyway your suggestion should be good for my purpose. Thx mate!

Hello folks, I need to create a custom canopy skin using Gimp, but I'm not able to maintain the transparency as I try to export the layered .xcf file to the .bmp one (before to convert the latter into the final .dds skin). The .bmp file I can make looks as the attached so the final .dds file does the same. Anyway I saw a lot of custom skins out there containing files of transparent canopy so there should be a way to do that... :mad: Is there someone can help me with this? :helpsmilie: Thx in advance. P.S. Sorry for the inaccurate header: at first I was thinking to ask about a different but related issue. So the answer for the asked one should be useful to make empty transparent skin too... :) my_f-16-glass.bmp.bmp

Hey usctaylor, I've just solved the issue of the USAF insigna duplication in F-16A's skins!! Wanna post here the solution for your and general knowledge, just in case someone would need it in the future... You said you hadn't this issue... I guess you have 4 skin files from an old bl.52 skin into your TempTextures folder, haven't you? I've just found out one of them is named just like the USAF insignia skin as and another like the canopy glass one (the latter is shared with the sign "AF89" too). When they are into "TempTexture" replace the originals but they are EMPTY!! This way the sim STILL thinks to put another "dynamic" USAF insigna over the custom livery's "permanent" one. However it actually overwrites there... NOTHING! :D :smilewink: :thumbup: And that's all... :)

Duplicazione - RISOLTO Ho risolto!! Ho trovato una vecchia skin per l'F-16 in cui ci sono dei file da inserire nella cartella Bazar/TempTextures che hanno i nomi dei file da cui vengono prese le insegne nazionali ed i numeri "dinamici" e che però sono immagini... vuote, per cui il programma aggiunge non altre insegne sopra quelle "fisse", bensì... nulla! ;) Grazie cmq per l'aiuto.

Questo lo so bene, ma non ho ancora provato a lasciarla vuota. Però ho provato a mettere l'indicazione di un'altra nazionalità e in quel caso la livrea non è neppure disponibile se la nazionalità non è selezionata per la specifica missione. Considerato questo, lasciando la nazionalità in bianco la livrea non dovrebbe risultare altrettanto indisponibile e questa volta senza possibilità d'inserire la nuova nazione (mancando del tutto) nella missione per poter così usare la skin?

Salve, ho un problema con delle skin per l' F-16 AI. Nel relativo sottoforum (mods & apps -> liveries/skinning -> AI Aircraft) ho trovato numerose livree per l'F-16A create soprattutto per il mod flyable, ma che a me servono soprattutto per aerei AI per il Mission Editor. Il problema è che molte delle skin hanno delle proprie insegne nazionali "fisse" che vengono duplicate con quelle dinamiche create dal ME. Alla mia richiesta di aiuto il creatore delle skin ha risposto che lui non ha duplicazioni. Appresso la struttura del file description.lua di una delle skin con il relativo screenshot in allegato. Sto eseguendo dei test per cercare di risolvere il problema, ma sono ancora in alto mare. Se qualcuno avesse qualche dritta gliene sarei veramente grato. Grazie in anticipo.

Ehmmm... And what about TempTextures? Under Saved Games\DCS directly too or in this case under Saved...\DCS\Bazar?

Thx again mate! You're very kind!! :) Would you please tell me if are you using the jabog32's F-16 template from FC 1.12 ( http://www.virtual-jabog32.de/index.php?section=downloads&subcat=13&file=636 ) and uboats' "Extractor for EDM files" ( https://www.digitalcombatsimulator.com/en/files/1744284/ ) for making all these skins? If not, get a look at them: could be very useful for you in case... :smilewink:

Well, could you make me anyway a skin without either right-wing upper and left-wing bottom roundel? Not too complicated if you have template with markings layers... Please... :worthy:

Yep... the test has just said you're right! That's a good news for me because I have so maaaaany skins and they are too heavy for a fast activation by JSGME, not to mention the duplication of filled HD space when activated. Now I've to test also if the mod worked for real or something else was running instead... :huh: Anyway thx a lot. :thumbup: Cheers!

Sorry but the fixing skin still has roundels on either upper and lower surface of both wings just like the original skin had... :(

Excuse me, but I've created the folder "Liveries" as "Bazar's" subfolder with a path as the following: {C:\Users\myUserName\Saved Games\DCS\Bazar\Liveries\F-16a} Do you mean I shold put "Liveires" directly under "DCS"?! :huh: I've put a modded .dds file into the ShipTexturesBMP.zip that is into {C:\Users\myUserName\Saved Games\DCS\Bazar\World\textures\} and it seems to work even with that more complex path (in JSGME-style like)... Are you really sure I shouldn't place "Liveries" under "DCS" instead into "Bazar" and the latter under "DCS"?? :dunno: Well... not hard to run a test however... :joystick:

Well, it seems the 2nd condiction only is true: liveries seem not working if stored into Saved Games\DCS... :(

The mods stored into ...Users\userID\Saved Games\DCS\ subfolders should work as well as those added directly into the Game subdirectories... They also should be safe from the updates of the game there and one shouldn't need neither to overwrite nor to backup original files. Is that true for liveries too? :helpsmilie:

Wow!! Thx again!! :thumbup:

Thx mate! And don't worry... I've already noticed the different gray tones between some of your liveries (it was easy for me to see that because I used either to build and paint aircraft models when I was young 8) :smartass:) so will be careful about that. :thumbup: Anyway I've one more fix to ask you... As one can see on the pics the Netherlands AF too has the USAF-style country markings on the F-16s' wings. At least this is true for the operational liveries (on particular liveries at airshows is not... see ff). https://ukdjstatic-b4d.kxcdn.com/wp-content/uploads/2015/09/Dutch_F-16.jpg https://s-media-cache-ak0.pinimg.com/originals/63/32/3a/63323a610c3ae31cc3369ee8a5d72c3e.jpg https://i.ytimg.com/vi/fbvRrgqJpe8/maxresdefault.jpg http://www.richard-seaman.com/Wallpaper/Aircraft/Displays/OtherTeams/TeamworkF16ClimbingVertically.jpg IMO for a more realistic skin you should delete either the roundel on the upper surface of the right wing and the other on the bottom of the left one... ;)

Well, I have DCSW 1.5.6 and I've set the planes as AI (uncontrolled) just for skins testing purpose. I'm working on them trying to fix for personal use. I've started from your similar skins made for bl.52d that work fine for me instead. However I wonder how you can get no usaf marking at all on the planes showed in your pics. :huh: Having the "USA" as country in description.lua should allow the stars to be dynamically displayed. When there are fixed country markings into the template the dynamic superimpose the latter. By chance did you change the country name into description.lua? The F-16A is not allowed for EU countries (they have mainly F-16MLU or bl.50) so swapping "USA" with, for instance, "ITA" prevents the usaf markings to be displayed. Unfortunately that also prevents the whole skin to be listed if you choose Italy as country in ME just by the reason as above. The following F-16's skins are still working fine for NATO countries, even if they are outdated: https://www.digitalcombatsimulator.com/en/files/665655/?sphrase_id=6522746 Anyway I'm continuing with tests and maybe something will come out eventually... Greetings.

Your skins are very nice, but I had some issues with country markings duplication on almost all of these liveries. You can check up the related screenshots that are into the attached zip file (there are some mistakes with some folders' names too). The one into the red box is the paint scheme's name you can see in plane customization window of mission editor. Could you please fix them as soon as you'll have a bit of free time? :helpsmilie: Thx in advance fellow pilot... :thumbup: ScreenShots.zip

I've just found out I can't add greek planes in DCS 1.5 Misson Editor because Greece isn't listed in drop-down menu although it is into the countries db of the game. Why is that?

But is there some issue with FC3 if I want to install the module anyway?

Thx

It's written I don't need to BUY the A-10A module if I'm a FC3 owner, but do I need to download the module however or I don't too?

After I updated online to 1.2.5 I can't no more run the sim. If I don't go wrong I had the same issue with update to 1.2.4 and that time I read somewhere I could fix it with manual installation of dcsw and all modules downloaded from ED's archive. Can you confirm that about 1.2.5 too? I don't remember: before to install have I either to uninstall the presently installed 1.2.5 or can I only overwrite it?