71st_AH Rob

I wish I could do that when taxiing with the canopy open...

+1

It is true, however, every update the server operator needs to go back and edit every warehouse at every airfield which I can see getting old for those who have many missions in the rotation.

Really looking forward to this!

I feel that the MiG is one of the better, more complete simulations available in DCS World with the exception of the damage model which we can hope is updated after the WWII modules get the update.

One more than the Allies have, until the Centaur comes out, but it is not in the same league. The Allies could really use a Sexton and both sides could use a towed artillery piece and tractor but there are probably other items that I would prioritize over them. A British RADAR being top of the list, followed by AI aircraft appropriate for the era.

Yes, as I said, static weather is generated on the local machine not the host. As for invisible planes, as I said I've never seen it in DCS before but in other sims it seems to be a netcode issue and restarting the server seems to fix it on them.

This happens when you set up a payload that is not a current preset payload for the selected mission type. With the near infinite number of combinations that can be made with the available stores it would be hard to make all of them presets for all mission types. If it is a loadout that you use regularly, just save it and give it a name, it will speed up mission building in the future.

Static weather appears to be client side only. If you spawn at Batumi and fly to Sochi, you will see clouds for about a 60km radius* around Batumi and you will fly out of them with a noticeable demarcation line. If someone else spawned in at Sochi they would see clouds around Sochi and clear sky around Batumi. I have never seen, no pun intended, an invisible wingman in multiplayer. *this distance may actually be related to your individual preload radius, I have not thoroughly tested it. This does not apply to full overcast or fog but only to scattered clouds. This can be useful in a PvE scenario when you take off from a carrier in the middle of the Black Sea and the weather is bad and the target is clear and need to return to the carrier and land with the challenge of finding it and landing in poor conditions. Not so useful in PvP but not critical with modern jets but a real discouragement for WWII and Korean era aircraft where you can't see the guy on your six because you are in a cloud and he is in clear skies.

^Not a bug When you are inside the min firing range, if the radar is working, the sight reticle disappears. If memory serves (I am away from my library) the min range is 1200'. This is a good safety feature, you are in danger of debris being sucked into the engine intake causing damage and flame out at close range and the target is too close for the radar to track effectively. If the A-4 sight is in manual ranging mode, the min range is 600' and the reticle will cease to get bigger but should remain on the reflector glass. That being said, the A-4 sight does not quite work correctly in either manual or radar ranging mode at the moment.

This information has been given to Belsimtek in the past. Most of it can be found in this forum so is readily compiled. The only thing they did was change the M2 to the M3 browning and the ammunition type from M2 and M3 to M20. The muzzle velocity still appears to be wrong.

M20 API-T and M8 API are the rounds that the Sabre used after the upgrade from the M2 to M3 Guns and they stopped using the WWII surplus ammo. Both have a muzzle velocity of around 900m/s or 2950 fps. The Sabre had a bad initial reputation when it got to Korea, it had not been in use in winter and was armed with the M2 and using old ammunition stocks it was natural that it seemed the underdog against the Mig with three cannon. It's reputation was not helped by the fact that it took so long to get the first kill of a MiG-15 by a Sabre and it was a difficult kill. Lt Col Hinton's feat was widely reported and quoted, he used most of his ammunition to down that first MiG. Shortly thereafter the F-86A's were retrofitted with the M3 and all subsequent Sabres arriving in theater were also equipped with the M3 and newer ammunition supplies were also sent and better choices were made, now using the M8 and M20 round. Lt Col Hinton's and the experiences of other pilots early encounters with MiGs seem to have resounded with many including Belsimtek as we have rounds that are not working very well. Watch gun camera footage from Korea, note the date and you can see that later footage takes very few rounds to down a MiG, at high alt you get a lot of white vapor (fuel) and at low alt you get a fireball after a short burst or two.

GUAV. The USN and USAAF were working on them at this time, the crew bailed out before they crossed the coast. I think one of the Kennedy brothers was killed in one.

That is a VIACOM setting and not related to the mission. in the VIACOM configuration, can't remember where to turn it off

Tailsman, relax. Burning Skies choose to disable the export function for their specific needs. Your jetseat will still work with almost any other server. This is a server administrator choice, not a DCS limitation. Don't blame ED.

Clearly the world is flat, I have personally flown under the surface and my altimeter went down below 0! Much to my dismay I did not see the Great A'Tuin but equally fortunately I must have been in the void between turtles or it would have been a short visit.

Hi, we are running a 4th FG campaign with missions run on most Tuesday evenings at 2000 EST. We fly as the 334th since No. 71 became the 334th when it transferred from the RAF to the USAAF. Feel free to drop by our TS at http://www.il2aceshigh.com and have a chat. Also if there are any 190 pilots out there we have open slots for 190s.

Exactly. It makes more sense to map the manual range than the wingspan. The only time that this is required is when the radar fails. The wingspan does not normally need to be adjusted dynamically during the fight, but should be fixed to the wingspan of the target, usually the MiG-15, or if there are other targets, the most dangerous. If the radar inverter light illuminates, use the button/axis (I use the lever on the Warthog throttle) to adjust the reticle to just encompass the wingspan of the target, assuming that you have set the wingspan for the correct type of aircraft you have now given the sight computer the range information required to compute the firing solution that the radar would have given automatically when it was working.

And you wonder why they are reluctant to release WIP videos...

M20 round had a velocity of 2950 ft/s or ~900m/s

Me too, but some things are dependent on ED finishing first.

That will be perfect for the CEII!

A-10C was released what? 10 years ago? and has had a lot of development to get where it is and it was revolutionary at the time of release. It is now looking a little long in the tooth when compared with some of the new modules, though overall it has held up well. It certainly was not anywhere near bug free or complete on release, in fact it took five or six years to release the map that was promised with it. So the rant is about people throwing stones over a module not being finished that has not even been released yet.

Hopefully ED will add GDR as a country as well as W. Germany! and Albania and Czechoslovakia as well as Iceland, Luxembourg and Portugal so we can have NATO vs Warsaw Pact Cold War scenarios.

It's also very hard to hit a 109 or a MiG-15 doing this, it is not restricted to Mustang pilots.