71st_AH Rob

Not released yet. No date announced

That is a bug that was reported about two years ago if I remember correctly and no word on when it will be fixed.

The cut off is not a mixture control. Earlier Spitfires with a manual mixture control, like the Mk I, II and early V and IX all had a manual mixture control and a Slow Running Cutout that served different purposes. Some Mk V had a Slow Running Cutout and an Automatic Mixture Control. The slow running cutout was generally a knob or ring pulled out to choke the engine causing it to stop. The Idle cut off fills the same purpose but does it differently, controlling fuel flow at the carburettors. Mixture control is separate and automatic on our Mk IX

Not to mention the LST Mk. II and the LS Samuel Chase

If anything the impression I get of the Spitfire is that it is too heavy. Watch one take off in person and it takes of like a startled cat, the tail in in the air in a few feet and the aircraft is airborne far sooner than I can get it off the ground safely on the Normandy map.

Yes, if we could have the Grass Fields concept that was promised. We would need flat areas where the airfields were and the "scenery remove objects zone" to work in MP. Then we could place an airfield like a FARP today. Instead of a place on the map being an airfield with special properties, we could have placeable runways etc or take off from grass. Vehs or buildings could have the properties for refueling or rearming. Say a hanger that you could taxi inside or within a close radius for repairs, or a veh that was close to you that was a repair veh. Or you run out of fuel on the taxi way, jump into combined arms and drive the fuel truck over to refuel your aircraft and get back to the rearming truck.

oops, caps.. it is DCS.openbeta_server Although, I have found through experimentation that I can keep DCE in my DCS folder for my editor and run it using the dedicated server and it will generate the mission results when I stop the mission using the web portal and generate the next mission when I accept the results.

Thats great news, will it also work with DCS.Openbeta_Server? I was running multiplayer campaigns for my squadron before and would love to do it easier in the future.

Will they change Hawkinge as well? I don't understand their marketing at all, why even announce the map let alone a release date if you haven't nailed down an era? How much earlier would it be? We only have one aircraft from early 1943. The Fw-190A-8 would be next at mid-1944. The rest are late 1944 and 1945 aircraft except for the I-16 which is irrelevant to a discussion of WWII on the Channel front.

There is no need to do anything, the Open Beta will create a directory of its own: c:/users/User Name/Saved Games/DCS.openbeta

I hope they don't get distracted and whatever we get will be more in line with the current maps and existing aircraft. A 110 or a Ju-87 would not make a lot of sense for Normandy or Channel map based in 1944. A Tempest V, Typhoon Ib, Spitfire XIV, B-26 would all make sense and the Typhoon and B-26 are already on the roadmap. The P-47 in any Razorback configuration would be logical as would a Mustang III and both would be modifications of existing flyable aircraft. A 410 and a 109G-6 would be relevant and the G-6 is already on the roadmap. the F-8 is a logical addition since it is a modification of an existing a/c.

Today GMT = UTC +/-0.00 Always. UTC +1 = BST always. In 1944 GMT = GMT Always. For military time zones GMT = ZULU...Always. UTC did not exist until the 60's and reading historical documents can be confusing, particularly for amateur historians making sense of differing accounts of a battle. In the 19th C even Calendars were reckoned differently never mind time on such a small scale as hours. The times on the Normandy Map are correct for local time in Normandy in June 1944. The problem for allied mission designers is the same as it is for historians, convert Allied accounts to local time!

You will need to opt into the beta on steam in the same manner as other games. Then you will be able to only see those server which also use open beta.

Beautiful!

If you have it mapped to your HOTAS it will be start in the position of your switches unless you un-check the option "synchronize with HOTAS at start"

It would seem logical that, like the recent inclusion of the V1 as a static model only, that the planned assets be added first as static models and incrementally updated to their final planned status. For example the Mosquito could be added as a Static Model in the next update. When the AI flight model (SFM) is ready update the Asset Pack to include the AI Mosquito, then when the cockpit and basic features are complete, offer it for sale in EA, then complete it and sell at full price as a complete released module. The OF 3.7 inch AA Gun could be added as a static as soon as it is ready, updated to a working AI asset once the AI logic is figured out and finally could be given Combined Arms access once it is finished. History tells a different story. The Ju-88A-4 model was shown to us two years ago but did not show up as a Static Model until it was added as a full AI asset in the recent update. I suspect that this will be the more likely path and we will not see the C-47/DC-3 this year and the Bf-109G-6 and Typhoon Ib are a long way off. Hopefully we will one day see them as full modules.

Just like trains

Just like the trains then.

Agreed.

First start of the day and warm up would be done by the ground crew in wartime conditions.

Or you can opt into the Open Beta. I do not recommend this unless you are prepared to deal with the bugs but it is fairly simple. There are two factors driving people to the Open Beta One, the Dedicated Server is only available on Open Beta at the moment and much of the MP audience is on Open Beta as a result, not because they want to participate in finding bugs. Two, the last major update, from 2.5 to 2.6 was significant and did not go as ... smoothly as hoped, resulting in a longer than normal time between Open Beta being released and being promoted to Stable Release. This has resulted in more new features in the Open Beta than normal. A case of greener grass envy really. you have to balance more new cool bells and whistles against stability and play ability. I normally recommend to my squadron members that if they only have room for one version, make it the Stable Release, only install the Open Beta if you can have both.

All updates are released first to Open Beta for testing before they go to the stable release, it has been this way for several years. The change log for the update is quite specific about the version it works on.

They've been delayed..

^This. If you look at the TACVIEW file you recorded it will of course show only your a/c since export is turned off to improve performance and prevent unethical use of TACVIEW. If you download the server version as Mike_Romeo suggests, you will not only see all the aircraft but you get the entire session and can download any from the last few days.

Nice work! Thanks I will make use of this