JG13Wulf

I don't really like either the new effect. It feel too big during day and not correctly placed. I don't remember to have seen any warbirds with flames during day. Only at night and when it's quite dark.

Don't know if it's 2.7 or my way to design mission. But I got it working. Start a mission at 6.15. Got to target at 6.30 => no shoot Turn over the area until 7.00 (heavy flak start to shoot and light AAA wake up if I turn up light / attack near them / pass extremely close to them). Fly until 7.30 and have the AAA almost completely woke up. I design the mission to have the AAA put to sleep when I'm out of area (AI off). Then AI on when I enter the area. So don't know if this make it work or if 2.7 have make some eddit on it. Still, it seems AAA wake up a bit late as the light is already quite good at 6.30/6.45. But it seems to have improved !

Hello @NineLineI'll check. But it seems before 2.7 this was not a LOD bug but a reflexion bug. This was not only limited to Ballon but to plane either. Depending on the angle I was looking to them, some appeared and disapeared. This was really obvious with large B17 formation in some situation. I'll try to make some test when I have time. But I didn't try since 2.7 is out.

Hello, Reporting here a weird behavior on our server. I created a mission for our actual campaign. The mission work well. But when loading it yesterday on our server, a lot of ground AI (flak and cars) were missing. and radar too was not working. Looking at tacview and on spectator, I notice the object were not working because they were not there ! But going back in editor, object are there. And today, laucing again the map, the mission started fine with the missing object from yesterday correcctly present. I don't know why it do this. It's I think the second time I got this trouble on 3 missions. Hope you can help me. This link contain - DCS log from server, - The mission file, - Server Track from the mission that got problem, - Server Track from my test when a restart mission today (that seems ok), - Readme that contain the information to find the loading of both the mission in the log. https://drive.google.com/file/d/1uOJbgCfHA2KAcfH2j9_Wy9HPTFkH_oOM/view?usp=sharing (Server wasn't restart between the two launch as you can see. But some mission were lauched manually / automatically) Thanks

Hello ! DCS allow to create lot of nice skin to fly with. But size of these don't allow to add a lot of them in game. After lot of research ans with lot of help, I was able to put my compressed P51 skinpack ingame. So I have a file .zip that contain my skins that is read by game. The problem I notice is that the .zip can only be read in "Mods" folder or "Coremods" folder. But in "Bazar" or "Saved Games", the .zip is ignored. My resquest is to have the game that can read .zip in Bazar and Saved games too. Thanks.

GG for the winner and to all

Manual give correct value to use with manual prop control not automatic. When using manual propeler, you can easily reach those value.

With 130 mo per P47 skin, I don't want to have tons of them too. Or ask more ED to make a system to have multiple skins sharing same files instead of 1 skins per description.lua. I requested this before multiple times. Except by "modding" a bit, there is no way to do so. Here is the post where I resquest this for the last time. I think it's a bad idea as most people but not all people have good connection. You would kill your server by using skins. If you want to play DCS, it's not in 10 - 20 - 30 minutes after Gb of skins have been downloaded.

If you can make 1 dowload link with 1 pack containing all skin you need, then it's quite possible to share this link on every platform linked to your server.

I think we should just let ED make the decision about which skin should be added or not. This is not intended to be a "multiplayer / campaign / server oriented competition". It's just a skinning competition. So skin should be designed as winner only looking on their quality. If you want to use some skin that are not designated, you can simply add them into your game. And if you run a server or a mission, it's quite easy to make a skinpack to share with other player. That's what we do on our server. Work well for everyone.

Link for my skin are added to my post (they were waiting approval). Good luck everyone.

The skin above "True story" can be used with two generic variant : First Generic : 355FS 354FG "generic blue tail" Link : https://www.digitalcombatsimulator.com/en/files/3315408/ ----------------------------------- (Forum merged the posts) Second Generic : 355FS 354FG "generic" Link : https://www.digitalcombatsimulator.com/en/files/3315409/ ----------------------------------- (Forum merged the posts) Inspired a lot but fictionnal again : 2 generic variant for the same squadron. 313FS 50FG "generic big red" : Link : https://www.digitalcombatsimulator.com/en/files/3315407/ -------------------------------------- (Forum merged posts) 313FS 50FG "generic" : Link : https://www.digitalcombatsimulator.com/en/files/3315406/

Inspired a lot but fictionnal : 355FS 354FG "TrueStory" Link : https://www.digitalcombatsimulator.com/en/files/3315410/ Reworked template and reworked letters and number.

On a flight back to England, I look at Dover and see the Ballon I placed. But turning the head, I notice some of them appear and disapear. Seems on some angle, the ballon may not appear.

Recap mission 0 (mission test). La campagne commencera début Mars !

As requested, I post it here. I'm working on a first skin but since I got the template (previous one) I can't figure out where the "mobile" propeller is in the template. I didn't found it in any of the 4 file. In those picture I tired to modify the "engine" file too. But I don't know where it is. EDIT : Change picture for better understanding of the problem

I can add I saw this for almost all warbirds (P47, P51 and Spit too). Most of time it happen when the AI get shot in vertical. It loose speed and then go backward in strait line to the ground. I thought it was an AI bad behavior that arrived because AI got updated but not finished.

Maybe not rearming screen but a setting in mission editor and / or Special setting at least

Seems to be corrected for some ship but not all. I tried LS Samuel Chase : OK Then LST MK II : Ok But for Schnellboat : Still the bug. I tried to put a brand new one, I didn't edit the one in the mission.

Thanks ! Yes it help Nice work you did there. Still I think that could be simpler if ED used their description.lua a better way. But this will allow to lower the weight for the moment ! Big thanks !

Yes, c'est possible. Pour la musique en boucle, il y a moyen de faire ca via un soft externe (ce qui permet facilement de changer la musique). Sinon, dans les trigger, il y a moyen d'ajouter un son (audible tout le temps et partout). Ou d'ajouter une transmission radio (donc audible seulement si la radio est allumé et sur la bonne fréquence. Lorsque tu fais les paramétrages dans la mission, il te propose quel fichiers tu veux. Pour jouer un son, je pense que c'est plus compliqué pour le faire jouer en boucle. Pour la transmission radio, c'est en boucle tant que la condition stop (autre trigger) n'est pas activé.

Yes, if I understand correctly, it's similar to what I look for. I looked about how to do that. But didn't find anyone that did this. I see they talk about F86F. Is it moded variant of F86 ? I'm going to try to make make something work the way he do for one of his pack. Would be nice if it's already possible to have something that describe clearly how to make this. (If I make it work, I'll do it) EDIT : Ok no, I understood a bit more. It's like he created a moded variant of the F86, the F86F that have another texture folder to look for. I will try if it break or not the integrity check (with ou version). This is something that can be done. But it's not the way I was looking to do it. I was more looking for a methode that don't need to "mod". I'll try.

Salut à tous, Je passe rappeler que la campagne WW2 Fortitude que nous organisons commencera dans un mois (fin février / début mars). Pour tester une dernière fois le serveur avant le début, nous proposons une mission 0 (test) le 4 février sur la Template de la campagne ! Si cela vous intéresse, inscrivez-vous à l'aide de notre Tableau des vols : https://forums.gtac-sim.fr/app.php/tutoriel-tdv (Accessible une fois connecté sur le forum, tout est expliqué dans ce tuto). La mission test ainsi que les missions de la campagne seront toutes sur la map Channel (+Asset pack) avec tous les warbirds SAUF le Fw 190D9 et le I16. Nos missions s'organiseront de la sorte : - Inscription via le tableau des vols, - Rendez-vous le soir du vol sur le Teamspeak 3 (démarrage serveur 21h00 donc arrivez un brin avant si possible), - Briefings disponibles sur demande et via notre Discord (canaux privés) https://discord.gtac-sim.fr/ J'en profite également pour rappeler que nous organisons des entrainements Warbirds publics tous les jeudis jusqu'au début de la campagne pour vous permettre de prendre en mains les appareils (inscription également via le Tableau des Vols). Photos par JP57 ! Bons vols !

As we use an automatic updater, it didn't compress to not update whole skin when only 1 file is modified in one skin of our team skin pack. So we don't compress them before sending. But even if we can improve the download, the size at the end on the user's computer is still huge. I download this one from your user files (I think) to see if there is a difference : https://www.digitalcombatsimulator.com/en/files/3314346/ (nice one by the way) You have a 40 mo archive and like me a 130 mo skin. Except if I miss something, I'm not able to use the archive directly in game. I have to unzip in correct folder to see it in game. If I get a 130mo skin on my SSD. For 1 it's not a problem. But when you start to have multiple skins, only 8 bring you to 1Go. It's nice to have details. I don't want to have less quality. But in some case, ED can optimize the way skins are handling without a lot of work. If I take your skin as an example. I see the fuselage is specific to a particular plane (marking, bombs decals, ...). But wings seems to be quite common. Imagine you want to make another plane to go with this particular P47 (Edit : I just notice you did a lot of friends for him). For the moment, we need to have a complete new skins with all new files + description.lua. If ED allow the possitility to make multiple skins per description.lua. You could easily make a second skins using the same wings files as this one but new fuselages files. This would make 2 skins for the price of 1 and a half. Imagine then you want to make 2 more the same way, you get 4 skins for the price of 1 complete + 3 half (so 2 and a half instead of 4). We therefore have (estimate) 325mo instead 520 mo. 130+65+65+65 = 325 130+130+130+130 = 520. If I compare further, I need 15 skins the reach the 1Go (130 + 14x65) with this solution instead of 8 with what we have now. Note that the win is not a lot for plane with "4 pieces template". But would make things better for more detailled plane/more bigger plane. (I imagine mosquito will use more than 4 files for skins) And If you take the solution 2 of my first post, the size win is even greater as you would be able to keep all the files of the plane and then just make a bunch of small decals that can be put on the skins with a bit more line in the description.lua. As all the tools are there to make this happen, I think the bit of work to adapt is worth the price so people will be able to use more skins in their game for same size. And even it would increase performance as shared files would be load 1 time and not multiple time by computer.

Hello, I'm requesting a modification about how skins are read by the game (again). I started working on the P47 yesterday and I saw that 1 skin of P47 is about 128 mo ! Looking at ww2 picture, we can see most of plane of a same squadron share similar paint but vary because or personalisation (noseart, killmark, ...). So for 2 skins of a same squadron (only few details that differ), we need to download and put on the SSD 2x 128 mo. For lot of people, this is not possible to use lot of skins. And it's not motivating to create new one as people might not be able to use them. So I'm requesting a modification about how skins are handle by the game to reduce the size of skins by sharing common files between groups of skins (base, serial numbers, numbers, ...) To do so, it would only need 1 thing : a description.lua able to share multiple skins This would allow to share multiple files between skins. For example, if I make 2 or 3 P47 that only differ on their nose art, it means that the wings and the tails files could be shared (and not copied in multiple folders). So we would have a larger folder because of the 2 or 3 front section that differ. But the size/skins is reduced a lot for plane that differ only a bit ! Now a second solution to combine with the previous one to even reduce more the skin size (maybe more complex). During WW2, one squadron had multiple plane with (almost) exact same squadron marking. As DCS skins work in layer, it would be nice to have the possibility to create a new layer that could be set on top of a skin part with coordinate. I mean that a nose art is only paint that is placed at a particular position. If we are able to generate a basic skin and then to generate a small nose art files that fit on this skin and that we can place using coordinate, then we would have even smaller size/skins. => we could genrate a nose art files that is maybe 400x400 pixels that would fit perfectly at (x,y) coordinate.. So if we have multiple skins/description.lua. We make a base and then we add lines to have multiple skins that use different nose art files (and their specific roughmet). With this, we would therefore have multiple skins for a small cost. If at least we can have the multiple skins per description.lua (or multiple description.lua in a folder), we could save a lot of space. Skins are maybe details for some. But they are details that bring live to a game and show how beautifull and wide it is. Having colorfull and various aircraft skins is one of the most iconic part of WW2 air war. Thanks