Pikey

Easy. Your friends dont have it, you cannot play it with them. This is the absolute principle of DLC division.

To feather an engine in the Mossie you require oil pressure and electrics. An electrical boost motor increases the oil pressure to turn the screws. Often damage stops this part. You can get two types of failure, instant and progressive, so I found. If you suspect you are losing oil feather it immediately, because the aircraft becomes un landable with the drag of an unfeathered engine, I never got a landing done that wasn't unsafe. Oil leaks are simulated in the damage modelling. There's quite a bit of work to come as I understand about the finer points of the engine management so I personally am expecting changes. HTH

Computer executed your 1. before you told it what the 2. 1. script 2. moose functions were 3. What on earth are you talkign about Pay attention to script order, even if you think you made it correctly, the computer got to the first one, before the second. It's important else the computer wont know 3.

This chap hasn't been active for two years, I was ready to move the post but this was only the second time in as many years there's really a problem, so we left it as it was Discord is maintained and busy, this thread...is not

This is a sad topic all over. I've been playing DCS since before it was called such and I cant get people or find a new home. Discord broke the internet. Everyone is a member of 15 groups and plays in none of them, that's whats wrong with the communities, Discord became a disposable tool, groups of 4-5 people sit in their own friendship group talking but not contributing to the other 60 groups that some of them are each members of, but not really focusing on any of them. For every Discord person online, you get from 0 to 0.01 of their actual presence and attention. FIgures? I announced a community, put up a server with stats and saw what happened. 30 people joined. only 5 of them ever logged into the server. More people actually randomly joined the DCS server from the MP browser than contributed to the community following reading the forum post and clicking the link. After I switched it off, I joined one of the peoples friendship groups. I see the same people members of so many other Discords on my own travels. The death of the "traditional squadron" was secured with Discord, everything is join in progress because people can't commit to a time, or anonymous public, because people want to troll people as its their only fun, and so on. Fragmented is not the word for it, I say Discord has damaged online gaming as a whole. Having said that, you need to work this out first. Flying an F-16 is way simpler than understanding how social media provides any useful benefit.

Hi folks I got this reported to the ED team today, it was fairly easy to reproduce once I worked out which units caused it. In the interim, I've got a suggestion to mitigate the issue, it's something like 2 seconds per WW2 plane added to the load time. So it affects missions with large unit counts of missions. As a yardstick consider 2 seconds per plane unit. So at about 100 WW2 planes its 200 seconds on my PC. Some were more than others. There's no other issue than the waiting till its ready, after load its fine. Obviously that doesn't help dedicated servers reloading etc I dunno, the team were quiet today, they've got a lot of feedback to process, maybe that's it? I'll ask Ben to add that and refer this thread.

I should really update this with the SA5 swap and maybe desert pieces. Just been busy with Mosquito stuff

I am looking for a WW2 community that uses a planning element and flies from a fixed start time with a common goal/mission. I am not interested in a server that is JIP or PvP focused. Asymetric PvP is great (and even prefered) as long as it not the the main purpose - the PvP should be a way to disrupt the goals/protect the asset rather than "score". i.e. the goal is the destruction of a V1 site, the pvp fits around that goal as a secondary as it is in real life... rather than two sides were vaguely fighting over something they forgot about but oh look Jim got 12 kills and forgot to bomb the target. Hopefully the content will be fresh, include some original designs - "Mossie specops" comes to mind. Any day is fine, any time after 6pm UK, I have all modules except the I-16 I'm fresher on the Spit, P-47, Mossie, Bf109, Anton - I dont realy fly the P51, Dora, I prefer realism and hardcore, no labels, SRS greatly prefered etc. I bring a server and I script to a high level for DCS, if that's a selling point. If there isn't such a group in existence I'd spin up one if I can get 6 names that can fly on the same evening.

Seems right, if you landed but felt the panic turning into the dead engine then you were feathered since what happens if not feathered is spin and death. Try it. Pull the fuel stop for an engine, let it stop and try to fly without feathering. Where before you could trim and fly, with a non feathered engine the drag is horrendous. The thing with stopping th eengine im not sure about. We could kill the fuel shut off and magenetos and that thing keeps goign round most of the time.

I think there already is a giant pink pig, or there was, somewhere in the game files.

Hi, I watched the track - I don't think its the same issue as the title of the post so I'll just explain what I found. When I watched you, you start on elevator 1. When I took the mission and played it myself from ME, I started from the six pack. When I tried to make a mission simply with player and AI following a E2 I coudlnt get it to behave the same way. When I played the mission from your track I could get the issue if I followed and waited for th Hawkeye on Cat1. But even I didnt get ATC to accept me, I dont know if I was too close, but I've submitted a track of that as a bug and I will discuss with BN. However, when I took Cat 2 everything was fine. #2 followed behind me for Cat 2 also. I could have tried a few different things but I ran out of time and will leave it as submitting a Cat1 issue. As I said, I dont think this is the same issue everyone is talkign about, esp regarding 3&4. I would bet a friendly pint of beer that the majority of the ATC issues are due to simulateously fighting with AI recovering and departing, which can mess the ATC up and is obviously not a practiced behaviour at all irl.

Anton or P47 or Mossie are sedate. For ease of switchology I think Anton. Dora is a tad twitchy with that power.

Nono, specifically avoided that. Had I a resource that gave permanent Flak instlalations I would have added it, but I have no information, so it's basically up to personal choice how much AD you stick in

WHAT IS THIS AND WHERE DO I STICK IT? Like my Syria Template this is a .stm with a lot of units on it. You go to the mission Editor and press menu Edit> STATIC TEMPLATE LOAD and browse to the file attached and add it into any mission. WHAT UNITS? Operation Crossbow NOBALL target lists and some key coastal batteries for the fun of putting down those bunkers. A NO-WHATTY? The Brits made funny names for things. This is V1, V2 and the V3 site with associated storage bunkers or manufacturing like Liquid Oxygen manufacturing. O in other words ... Mosquito food. Diver raids... HOW ACCURATE IS THIS? Good question. This is not GPS perfect stuff, there is no "samsites.kmz" Google earth can be referenced for some buildings but apart from the concrete bunkers remaining much of it has disappeared. The answer is - It varies enormously between "just finding the town!" and getting them satellite perfect. Bunkers were pretty good positionally, but the 3d objects are no good, like Wizernes, Watten, Siracourt and Mimoqueuceques. Yvrech was already placed by ED without the V1 ramp. Agenvillers I have perfect position of the ski bunkers because Google earth shows them brightly, but the launch ramp I just guessed. And things liek the Predefin Wurzberg site or Goreflos or Ailly le-haut-clocher I litterally only have evidence of the town. It gets worse... There was no naming convention. The Brits refered to V1 sites often by the nearest town. That wasnt that accurate. The French could add the specific "wood" they were in to be more specific. The Germans of course were organised and gave them numbers. The internet, however, took the first name it could find. Yes, I resolved V1 multiple sites that had multiple names in quite respectful websites. Example is Flixecourt, aka, Surcamps aka Brunehaut aka Bois du Coroy. Jeesh. What a chase that was. This was a bit of OCD pedantry i am sharing, i am not purpoting some expertise in V1 sites, just simple sharing a mad Sunday and some other hours with the community I love. REFERENCES https://en.wikipedia.org/wiki/V-1_flying_bomb_facilities http://sehet.andre.free.fr/dedetextes/boiscoroy.htm https://www.416th.com/missions/Mission_LL_And_Target_Info.html https://www.google.com/maps/d/u/0/viewer?mid=1KztEHnhAks2eFxdrI3j3bRMMByY&ll=50.24156013552968%2C1.3774708574489791&z=9 https://www.tracesofwar.com/ https://www.battlefieldsww2.com/ Google Earth/maps BUT SOME OF THESE SITES LOOK BAD! There is only so much you can do with the statics contained in the core game when trying to do a V1 site. I started to spend less time as the evening ewent on and after a bit just got silly. The important thing is you can save a lot of research time using this as a backbone for your missions. Don't judge me harshly. Please! It's free OK? CONTENTS OF THE STM Ally Le Haut Clocher V-1 Launching Site Agenvillers V-1 Launching Site Audincthun V-1 Launching Site Belmesnil V-1 Launching Site -- Duplicate of Herbouville? Bimont, Bois Rempre V-1 Launching Site Bonnières V-1 Launch site https://en.wikipedia.org/wiki/Bonni%C3%A8res,_Pas-de-Calais Flixecourt/Brunehaut/Surcamps/Domart en Ponthieu/Bois du Coroy http://sehet.andre.free.fr/dedetextes/boiscoroy.htm V-1 Launching site Domleger V-1 Storage Site Gorenflos V-1 Launching Site Huit Rues Wallon-Capelle V-1 Launching Site Groseillier V-1 Launching Site Ligescourt V-1 Launching Site Lottinghen V-1 Massive Launching Bunker Mimoyecques V-3 Massive Launching Bunker Predefin V-2 Radar Tracking Site Siracourt V-1 Massive Launching Bunker Yvrench, Bois Carre V-1 Launching Site Watten LOX Manufacturing Site Wizerne V-2 Construction Launching Site Val Ygot V-1 Launching Site Gueschart V-1 Launching Site Others sites Herbouville V1 Launch Bouillancourt-en-Sery V1 Launch Belloy-Sur-Somme V1 Launch Desvres V1 Depot Lottinghen Wurzberg - refered to...so added one. Crepy V1 Launch -- https://en.wikipedia.org/wiki/Cr%C3%A9py,_Pas-de-Calais COASTAL BATTERIES Friedrich August 1&2 Batteries Wimereux Siegfried Batteries, Audinghen Prinz Heinrich 1&2 and 3x Magazine at Sangatte Oldenburg 1&2 - Calais Battery Waldam 1&2 – Calais NOT INCLUDED (yet) Humieres V-1 Launching Site Maison Ponthieu V-1 Launching Site MaisoncelleV-1 Launching Site Renescure V-1 Storage Site Ruisseauville V-1 Launching Site Sautricourt V-1 Storage Site St. Josse V-1 Launching Site St. Remy Aux Bois V-1 Launching Site St. Lue d’ Esserent V-1 Storage Site Tammercourt V-1 Launching Site Vacqueriette V-1 Launching Site RESOLVED ISSUES WITH LISTS Nucourt V-1 Storage Site –off map Thiennes V-2 Launching Site --Cherbourg Zudausques V-1 Launching Site-- couldnt locate the launcher evidence Comette V-1 Launching Site –could not locate Croisette V-1 Launching Site --Siracourt synonym? Hesdin La Loge V-1 Launching Site – Not sure where the launchers are Beauvois V-1 Launching and Storage Site –cannot find, it's adjacent to Siracourt Roquetoire V-2 Radar Tracking Site – never operational Bergueneuse V-2 Storage Site –underground mostly Bellevue V-1 Launching Site –couldnt identify ORGANISED V-1 LIST FROM GERMAN SOURCES (was probably faster to learn German and research properly) V1 Feuerstellung Nr. 11 (IV. Abt) Flottemanville-Hague V1 Feuerstellung Nr. 12 (IV. Abt) Nouainville V1 Feuerstellung Nr. 13 (IV. Abt) Hardinvast V1 Feuerstellung Nr. 14 (IV. Abt) Tollevast V1 Feuerstellung Nr. 15 (IV. Abt) La Glacerie V1 Feuerstellung Nr. 16 (IV. Abt) Brix V1 Feuerstellung Nr. 17 (IV. Abt) Mesnil-au-Val V1 Feuerstellung Nr. 18 (IV. Abt) La Boissais V1 Feuerstellung Nr. 45 (I. Abt) Volckerinkhove V1 Feuerstellung Nr. 56 (I. Abt) Coin-Perdu V1 Feuerstellung Nr. 57 (I. Abt) Noordpeene V1 Feuerstellung Nr. 59 (I. Abt) Le Nieppe V1 Feuerstellung Nr. 61 (I. Abt) Nielles-les-Blequin V1 Feuerstellung Nr. 63 (I. Abt) Ecques V1 Feuerstellung Nr. 65 (I. Abt) Bientques V1 Feuerstellung Nr. 66 (I. Abt) Bientques V1 Feuerstellung Nr. 68 (I. Abt) Bientques V1 Feuerstellung Nr. 70 (I. Abt) Enguinegatte V1 Feuerstellung Nr. 72 (I. Abt) Erny-Saint-Julien V1 Feuerstellung Nr. 81 (I. Abt) Beaumetz-les-Aire V1 Feuerstellung Nr. 83 (I. Abt) Coupelle-Vieille V1 Feuerstellung Nr. 84 (I. Abt) Predefin V1 Feuerstellung Nr. 85 (I. Abt) Fiefs V1 Feuerstellung Nr. 88 (I. Abt) Ferfay V1 Feuerstellung Nr. 89 (I. Abt) Ambricourt V1 Feuerstellung Nr. 93 (II. Abt) Fressin V1 Feuerstellung Nr. 95 (I. Abt) Fleury V1 Feuerstellung Nr. 97 (II. Abt) La-Loge Ost V1 Feuerstellung Nr. 99 (I. Abt) Humieres V1 Feuerstellung Nr. 103 (II. Abt) Fresnoy V1 Feuerstellung Nr. 109 (II. Abt) Mouriez V1 Feuerstellung Nr. 110 (II. Abt) Bamieres V1 Feuerstellung Nr. 112 (II. Abt) Linzeux V1 Feuerstellung Nr. 113 (II. Abt) Blangermont V1 Feuerstellung Nr. 117 (II. Abt) Rapechy V1 Feuerstellung Nr. 118 (II. Abt) Rapechy V1 Feuerstellung Nr. 122 (II. Abt) Flers V1 Feuerstellung Nr. 125 (II. Abt) Ligescourt V1 Feuerstellung Nr. 128 (II. Abt) Bachimont V1 Feuerstellung Nr. 137 (II. Abt) Auxi-le-Chateau V1 Feuerstellung Nr. 138 (II. Abt) Maison Ponthieu V1 Feuerstellung Nr. 139 (II. Abt) Remaisnil V1 Feuerstellung Nr. 139 (IV. Abt) Saussemesnil V1 Feuerstellung Nr. 140 (IV. Abt) Chateau de Rochemont V1 Feuerstellung Nr. 141 (IV. Abt) Brix V1 Feuerstellung Nr. 142 (II. Abt) Prouville V1 Feuerstellung Nr. 142 (IV. Abt) Brix V1 Feuerstellung Nr. 143 (IV. Abt) Nouainville V1 Feuerstellung Nr. 144 (IV. Abt) Tonneville V1 Feuerstellung Nr. 145 (IV. Abt) Sainte-Croix-Hague V1 Feuerstellung Nr. 146 (IV. Abt) Branville-Hague V1 Feuerstellung Nr. 147 (IV. Abt) Vauvile V1 Feuerstellung Nr. 148 (IV. Abt) Saussemesnil V1 Feuerstellung Nr. 152 (II. Abt) Vignacourt V1 Feuerstellung Nr. 157 (II. Abt) La Chaussée-Tirancourt V1 Feuerstellung Nr. 161 (III. Abt) Melleville V1 Feuerstellung Nr. 165 (III. Abt) Avesnes-Chaussoy V1 Feuerstellung Nr. 170 (III. Abt) Réalcamp V1 Feuerstellung Nr. 183 (VI. Abt) Bosc-Roger V1 Feuerstellung Nr. 185 (VI. Abt) Bosc-Benard V1 Feuerstellung Nr. 197 (IV. Abt) Bertreville-Saint-Ouen V1 Feuerstellung Nr. 197 (VI. Abt) Giverville V1 Feuerstellung Nr. 198 (IV. Abt) Ablemont V1 Feuerstellung Nr. 198 (VI. Abt) Boissy-Lamberville V1 Feuerstellung Nr. 204 (VII. Abt) La Chapelle-Noiremare V1 Feuerstellung Nr. 205 (VII. Abt) Lessart-et-le-Chene V1 Feuerstellung Nr. 207 (VII. Abt) Le Pré-d'Auge V1 Feuerstellung Nr. 208 (VII. Abt) La Boissière V1 Feuerstellung Nr. 210 (IV. Abt) La Rue Giffard V1 Feuerstellung Nr. 210 (VII. Abt) Coupesarte V1 Feuerstellung Nr. 211 (IV. Abt) Saint-Germain-des-Essourts V1 Feuerstellung Nr. 212 (VII. Abt) Le Mesnil-Mauger V1 Feuerstellung Nr. 213 (VII. Abt) Berville-Ecots V1 Feuerstellung Nr. 214 (VII. Abt) Louvagny V1 Feuerstellung Nr. 215 (VII. Abt) Quesnay V1 Feuerstellung Nr. 217 (VII. Abt) Biéville-Quétiéville V1 Feuerstellung Nr. 219 (IV. Abt) Quincampoix V1 Feuerstellung Nr. 220 (VII. Abt) Émiéville V1 Feuerstellung Nr. 222 (IV. Abt) Quincampoix V1 Feuerstellung Nr. 223 (IV. Abt) Houppeville V1 Feuerstellung Nr. 224 (VIII. Abt) Houppeville V1 Feuerstellung Nr. 225 (VIII. Abt) Crosville-sur-Douve V1 Feuerstellung Nr. 226 (VIII. Abt) St Colombe Le Chateau V1 Feuerstellung Nr. 227 (VIII. Abt) Golleville Chateau du Quesnoy V1 Feuerstellung Nr. 228 (VIII. Abt) Golleville Le Chateau V1 Feuerstellung Nr. 229 (VIII. Abt) Nehou V1 Feuerstellung Nr. 230 (VIII. Abt) St Jacques de Nehou V1 Feuerstellung Nr. 231 (VIII. Abt) St Jaques de Nehou Hameau Piquet V1 Feuerstellung Nr. 232 (VIII. Abt) Yvetot Bocage V1 Feuerstellung Nr. 233 (VIII. Abt) Valognes Chateau de Beaumont V1 Feuerstellung Nr. 234 (VIII. Abt) Tamerville V1 Feuerstellung Nr. 235 (VIII. Abt) Saint-Germain-de-Tournebut V1 Feuerstellung Nr. 236 (VIII. Abt) Montaigu La Brisette V1 Feuerstellung Nr. 237 (VIII. Abt) Breuville V1 Feuerstellung Nr. 238 (VIII. Abt) Rauville le Bigot V1 Feuerstellung Nr. 239 (VIII. Abt) Rauville le Bigot Croix des Chevres V1 Feuerstellung Nr. 240 (VIII. Abt) Bricqueboscq V1 Feuerstellung Nr. 241 (VIII. Abt) Rauville la Bigot La Hectonnerie V1 Feuerstellung Nr. 242 (VIII. Abt) Grossville V1 Feuerstellung Nr. 244 (VI. Abt) Motteville V1 Feuerstellung Nr. 261 (VI. Abt) Saint-Romain-de-Colbosc V1 Feuerstellung Nr. 615 (I. Abt) Eperlecques V1 Feuerstellung Nr. 616 (I. Abt) Lostebarne V1 Feuerstellung Nr. 617 (I. Abt) Cocove V1 Feuerstellung Nr. 618 (I. Abt) Journy V1 Feuerstellung Nr. 619 (I. Abt) Cormette V1 Feuerstellung Nr. 620 (I. Abt) Zudausques - Liheuse V1 Feuerstellung Nr. 621 (I. Abt) Wisques V1 Feuerstellung Nr. 622 (I. Abt) Heuringhem V1 Feuerstellung Nr. 623 (I. Abt) Wallon-Cappel V1 Feuerstellung Nr. 624 (I. Abt) Rebecques V1 Feuerstellung Nr. 625 (I. Abt) Drionville V1 Feuerstellung Nr. 626 (I. Abt) Campagne-lès-Boulonnais V1 Feuerstellung Nr. 627 (I. Abt) Esquerdes V1 Feuerstellung Nr. 628 (I. Abt) Upen d'Aval V1 Feuerstellung Nr. 629 (I. Abt) Audincthun V1 Feuerstellung Nr. 630 (I. Abt) Herly V1 Feuerstellung Nr. 631 (II. Abt) Remortie V1 Feuerstellung Nr. 632 (II. Abt) Wicquinghem V1 Feuerstellung Nr. 633 (I. Abt) Lisbourg V1 Feuerstellung Nr. 634 (I. Abt) Febvin-Palfart V1 Feuerstellung Nr. 635 (I. Abt) Fontaine-les-Hermans V1 Feuerstellung Nr. 636 (II. Abt) Embry V1 Feuerstellung Nr. 637 (II. Abt) Rimboval V1 Feuerstellung Nr. 638 (I. Abt) Ruisseauville V1 Feuerstellung Nr. 639 (II. Abt) Maisoncelle V1 Feuerstellung Nr. 642 (II. Abt) Campagne-lès-Hesdin V1 Feuerstellung Nr. 643 (II. Abt) La-Loge West V1 Feuerstellung Nr. 644 (II. Abt) Eclimeux V1 Feuerstellung Nr. 645 (I. Abt) Croisette V1 Feuerstellung Nr. 646 (II. Abt) Saint-Josse-au-Bois V1 Feuerstellung Nr. 647 (II. Abt) Vacqueriette-Erquieres V1 Feuerstellung Nr. 648 (II. Abt) Quoeux-Haut-Mainil V1 Feuerstellung Nr. 649 (II. Abt) Montorgueil V1 Feuerstellung Nr. 650 (II. Abt) Raye-sur-Authie V1 Feuerstellung Nr. 651 (II. Abt) Gueschart V1 Feuerstellung Nr. 652 (II. Abt) Vacquerie-le-Boucq V1 Feuerstellung Nr. 654 (II. Abt) Beauvoir V1 Feuerstellung Nr. 656 (II. Abt) Maison-Ponthieu V1 Feuerstellung Nr. 657 (II. Abt) Agenvillers V1 Feuerstellung Nr. 658 (II. Abt) Yvrencheux V1 Feuerstellung Nr. 659 (II. Abt) Yvrencheux V1 Feuerstellung Nr. 660 (II. Abt) Yvrench Bois Carre V1 Feuerstellung Nr. 661 (II. Abt) Le Meillard V1 Feuerstellung Nr. 662 (III. Abt) Bienfay V1 Feuerstellung Nr. 663 (II. Abt) Ailly-le-Haut-Clocher V1 Feuerstellung Nr. 664 (II. Abt) Gorenflos V1 Feuerstellung Nr. 665 (II. Abt) Domart-en-Ponthieu V1 Feuerstellung Nr. 666 (III. Abt) Behen V1 Feuerstellung Nr. 667 (III. Abt) Limeux V1 Feuerstellung Nr. 668 (III. Abt) Longuemort V1 Feuerstellung Nr. 671 (III. Abt) Campneuseville V1 Feuerstellung Nr. 672 (III. Abt) Campneuseville V1 Feuerstellung Nr. 675 (III. Abt) Puchervin V1 Feuerstellung Nr. 679 (III. Abt) Notre-Dame-d'Aliermont V1 Feuerstellung Nr. 680 (III. Abt) Sainte-Agathe-d'Aliermont V1 Feuerstellung Nr. 681 (III. Abt) Esclavelles V1 Feuerstellung Nr. 682 (III. Abt) Les Hayons V1 Feuerstellung Nr. 684 (III. Abt) Les Petits Moraux V1 Feuerstellung Nr. 685 (III. Abt) Val Ygot V1 Feuerstellung Nr. 686 (IV. Abt) Freval V1 Feuerstellung Nr. 688 (IV. Abt) Grand-Parc V1 Feuerstellung Nr. 689 (IV. Abt) Ecalles-sur-Buchy V1 Feuerstellung Nr. 690 (IV. Abt) Bosmelet V1 Feuerstellung Nr. 691 (IV. Abt) Belmesnil V1 Feuerstellung Nr. 692 (IV. Abt) Herbouville V1 Feuerstellung Nr. 695 (IV. Abt) Bonnelot-le-Faubourg V1 Feuerstellung Nr. 698 (II. Abt) Ligescourt V1 Feuerstellung Nr. 700 (II. Abt) Radinghem V1 Versorgungsstelle 1001 Renescure V1 Versorgungsstelle 1002 Sautricourt V1 Versorgungsstelle 1003 Beauvoir V1 Versorgungsstelle 1004 Domléger-Longvillers V1 Versorgungsstelle 1007 Bosc-le-Hard V1 Versorgungsstelle 1008 Valognes V1 Versorgungsstelle 1009 Bricquebec V1 Versorgungsstelle 1011 Monterolier V1 Versorgungsstelle 1013 Saint-Riquier V1 Versorgungsstelle 1015 Ferfay V1 Versorgungsstelle 1017 Jumieges V1 FeldMuLag 1104 Theodor Ytres V1 FeldMuLag 1106 Leopold Saint-Leu-D'Esserent V1 FeldMuLag 1111 Nordpol Nucourt V1 FeldMuLag 1116 Richard Rilly-la-Montage V1 FeldMuLag 1117 Nikolaus Libermont En joy, if you need something to bomb this is your go-to list. ChannelInstallations.stm

The pitch/RPM level can be bound to a single axis for both. You can split the throttle as normal. This works just fine in the majority of cases as you don't often need to hold different RPM's, you set both the same, either max, 2850 or 2650 like the spit.

Bolder City holds many memories of our race course there

I voted an earlier german fighter - 109 G-6 1943 and the reason is based on just trying to have a game that fits a map we have, with modules we have. Yep its all great voting for literally any of this list but the vote has to made looking at what we already have, not where we want to go next in development. This is why the Me262 fanclub just infuriates me, the Axis planes live in a microcosm of its gasping breaths in 1945 on the continent mainland whilst the Spit, P47, Mossie live in different eras way before this. Where's the fight? This inconsistency keeps plaguing the multiplayer arena, you cannot have close to reasonable contests based on the most rapid technology advances the world has ever seen. Please, lets have what we need with the big picture in mind, not what we want with what we don't have either. Makes no sense, the DCS limit has always been thing sout of place and out of time. Let's not exacerbate it. Anchor on a date, make a fight, match it in pairs each side.

Well your anecdote doesn't disagree with the machine or my statements, you've simply said you found suckers to kill in another sim. The same people exist in servers in DCS, I think you might try your luck in Spit vs Dora and see who get's suckered into whose fight, because none of this is actually about the machine itself and all about the players. I don't have any data for module versus module, it sure would be interesting to see. I'm sure it's the player not the aircraft most times, but I'm still suggesting that I think the good players do not pick inferior machines mostly.

The sentiment is. PvP is fought under different circumstances than the seond World war was. Whilst you might say the Hawker Hurricane was undermatched it held off the defence of Britain as the backbone of the fighters. But what would the pvp crowd consider of it in DCS World? They would consider it inferior and their opinion would be pretty spot on. Does single player depend on multiplayer? That's a better question. The IJN didnt have a matched response to USN as a carrier fighter after the middle of the war, there is no historian on the planet that will counter that statement and DCS provides accurate simulation, to a point where at least good players can exploit the benefit they are given. Whilst the post quote might have hyperbole, people clamouring for a Zeke aren't willing to fly it when it really counts, they just want the idea of a matchup.

In other words you/people want access to the CPG seat in MP. I'm sure this is a popular sentiment. I don't know the level of visibility of this request but I'm behind the rationale 100%. It would be a good question for the Team.

I'd have to wait until there was some ambient lighting at night first. The only real light sources in DCS world come from your cockpit, landing lights, the sun and the moon and a couple of other things. Without the moon its very black. Without airport lighting, its really uncomfortable. Without that luminesence from the environment and light reflecting all around, you can have nights that are too dark to be useful. And we still wait for homing becons, DF, the 1155 to be fully modelled and so on. Flying at low light is OK, but the night fighting environment in DCS in undercooked. Any DCS is good, but there's some missing parts that need sorted.

In this case it was the usage that changed, not the aircraft, which they didn't foresee. Considering US air doctrine is based on air superiority, it makes the long loiter time of the A-10C fit even better to what it became than what it was designed for. That's the hard thing to swallow, how the arguments are even stronger now than they were, for a slow COIN ops loiterer with cheap(er) hourly cost (than the fast jets). There was an assumption way back that swing/multirole was the thing that costed the least by unification of the airframe counts, so that engineering, parts and support were condensed into one, but it never really counted in on station time to the equation - how many other airframes can go back to station, loiter for an hour and return to the same firefight a bit later? That's two missions for everyone else. We don't know what the future holds, but it's difficult to imagine support of ground troops in a permissive airspace just disappearing. I'd like to see Navies manage to get closer to the A-10 mindset. The one place you need a good loiter time is in a force projection scenario on a carrier.

what do you mean by "if this South Atlantic Map will be going ahead"? Building terrain is not a spectator sport or one that you get weekly updates on, its simply arduos, time consuming, very boring and extremely slow. They take years. Updates are not interesting. But you will know when its done because they'll sell it. Not very much before. Plus the terrain isnt the only thing being made for that DLC so there are interconnecting tasks.

Hello I have updated the OP. Firstly I've added a sample miz and script. This was because someone helpfully copied out my event handlers from the video and this was never intended. Subsequently people went through that code and identified some weaknesses which it then fell upon me to fix. This was however a valid excercise and important. Therefore I've set a sample that avoids the first ones shortfalls. --added function repl(dirty) local text = dirty:gsub("&", ""):gsub('"', ""):gsub("|", " "):gsub("'", ""):gsub("%%", ""):gsub("/", ""):gsub("\\", ""):gsub(">", "") local clean = text:gsub("<", "") return clean end function BotSay(msg) local message=repl(msg)--added string replacement for some DOS escape characters local text='C:\\Webhook\\DiscordSendWebhook.exe -m "'..message..'" -w "https://discord.com/api/webhooks/832742644517830667/blahblahblah" ' os.execute(text) end