Foul Ole Ron

You can taxi up to the catapult, lower the launch bar and hit U to trigger the catapult being set for you. You have to get pretty close to the spot. Once you're in the right spot and hit U you'll see your plane get set up.

Make a mission yourself in the mission editor and set the Viking on a long straight flight path. You can get plenty of practice of approaching and staying connected then without having to worry about him making a turn on you. If you're not sure how to set a mission up I'll send you on a simple AAR mission I made.

Thanks Bravo - that did the trick. Seems like a bit of a bug that you have to go through 2 steps to get the required end result but it's easy to workaround I guess once you know what to look out for.

I made a quick mission for practicing AAR but getting an issue with the TACAN functionality. I added the Stennis and at waypoint 0 ordered it to activate TACAN 1X and gave it the sign CVN. I then added a S-3 tanker and ordered it to activate TACAN 99X and gave it the sign TKR. Once I started the mission I couldn't find the S-3 using 99X even though I started only 10 miles away from it. When I put the TACAN to 1X however it showed me the sign TKR on the HUD and directed me towards the S-3 and not the Stennis. I've attached the .miz file. Persian Gulf FA-18C AAR.miz

Thanks - looks like it's maybe throttle issue on my side. When using the keyboard commands after removing the throttle axis mapping the above behaviour doesn't happen. Not sure why it would work ok sometimes and sometimes not - maybe something is sticking inside the throttle when they're in the same position.

Ran into an issue when trying to move the left and right throttles to asymmetric levels. Sometimes the right engine RPM won't move until you move the left throttle a little. Then both the left and right RPM move to where they should be. To reproduce: 1. Have both left and right RPM set to e.g. 85% 2. Move only the left throttle a bit forward to 87% and both the left and right RPM will increase to that number together (I'm presuming this shouldn't be the case?) 3. Then try to move the right throttle back to idle and nothing will happen - the right RPM will stay at 87% 4. Move the left throttle forward a tiny bit and then suddenly the right engine RPM will drop back to idle I'm using an X-55 dual throttle and didn't try to reproduce yet with the keyboard commands.

Think this is a known issue that they've already confirmed as fixed in ED's internal version.

You definitely can't transfer the Harrier from Steam to standalone. There's no key to transfer and activate like before.

Steam take 30% for themselves. Given that the flight sim market is pretty niche it's better not to give them that cut. I've got plenty of games on Steam but DCS and IL-2 I always buy direct. There's really no advantages to having DCS on Steam other than it auto updates for you. If anything you're disadvantaged as new releases tend to hit Steam a bit later than the direct releases from ED.

Not remotely comparable in my experience running at 1440p. MSAA is way better but, with deferred shading on, causes a pretty severe performance hit. At 1440p I honestly could barely tell the difference switching SMAA on/off in reshade.

Would be good for somebody with Tacview to do these tests. That'll show the G forces throughout the whole flight so you can see exactly what the flight data was up to the point the wings came off.

I'd assume so. No worries - I've waited this long. I can wait a few more weeks.

Think he meant that the D model Mustang in DCS now is a model that came into service towards the end of the war. The K-14 gun sight was only starting to be a field mod around July '44 and it was October '44 before they were factory fitted in the 20-NA block. It also would've had fabric elevators around the Normandy timeframe instead of the metal elevators it currently has in game. Having said that the performance of the in game Mustang would otherwise be pretty close to the Normandy version. The same can't really be said about the 109 or 190. So really out of all the WW2 planes in DCS the only one that actually fought at Normandy was the Spit IX. But anyway it is what it is and there'll be plenty to enjoy with the new map and hopefully over time things get aligned better.

I thought it was 250 yards in the RAF? I can't see it in any official docs though. Air Chief Marshal Dowding stated: "A great deal of discussion took place before and in the early stages of the war as to the best method of harmonisation of the guns of an 8-gun fighter: that is to say the direction, in relation to the longitudinal axis of the aircraft, in which each gun should be pointed in order to get the best results. There were three schools of thought. One maintained that the lines of fire should be dispersed so that the largest possible “beaten zone” might be formed and one gun (but not more than one) would always be on the target. The second held that the guns should be left parallel and so would always cover an elongated zone corresponding with the vulnerable parts of a bomber (engines, tanks and fuselage). The third demanded concentration of the fire of all guns at a point. Arguments were produced in favour of all three methods of harmonisation, but in practice it was found that concentration of fire gave the best results. Guns were harmonised so that their lines of fire converged on a point 250 yards distant: fire was therefore effective up to about 500 yards, where the lines of fire had opened out again to their original intervals after crossing at the point of concentration." Also mentioned here and various other places: https://en.wikipedia.org/wiki/Gun_harmonisation

If it gets released tomorrow it'll probably be late afternoon Moscow time.

I think more knowledgeable people than me might have commented before that the way it's done in CLoD isn't completely realistic. Anyway as far as I know the standard harmonization that the RAF used for the Mk IX was 250 yards which is fine for general use. I would expect that we'll get whatever the standard harmonization pattern was as just about all pilots would have been expected to fly with those settings.

Hasn't been any word on adjusting the harmonization. I'd guess probably not though. The gun sight adjustments are for both range and wingspan which is related to harmonization but not exactly the same thing. From playing CLoD I never bothered too much with the range - I just set it equal to the convergence setting. Then would adjust the wingspan based on what the target was to try and hit them at the ideal range.

Here's another one - mode 2 for landing/take-off/cruising & mode 1 for A2A. I made this very early on in early access so things might have changed as haven't flown the module in a while - you might have to check some of the key commands against the current list. Some things could probably be improved too but it'll give you a base to work from I guess. DCS F-5E.rar

If ED are doing 2 different wings there'll be 2 different FMs. I don't think they would implement both wing types if it wasn't technically feasible and was just a cosmetic feature.

Flying examples aren't what Yo-Yo needs to make a flight model. He needs the detailed technical info of the plane, flight tests, etc. and it seems like this is not easily available for the P-47.

When they have a more concrete release date they usually do a pre-purchase. Right now it's probably towards the end of the year but that could shift.

2 x 20mm cannon and 4 x. 303. Not sure about bombs. I think it was able to carry a bomb load of 1 x 500lb on a centreline rack and 2 x 250lb bombs on wing racks but not sure how much this was used in practice in WWII by the RAF at least as they had other planes for ground pounding.

Yeah it's a little clunky. The communication menu is supposed to simulate you talking to the ground crew to get things going like ground power. Once I have ground power I just use the microphone button for all comms from then on out. Have it mapped to my hotas for simplicity. Think other modules like the A-10C work this way too.

You're using the control labelled "communication menu" probably on the ground? That won't work once you're in the air. You need to use the control labelled "microphone button" when in the air. Communication menu = \ Microphone button = RAlt+\

Maybe open a support ticket and see if something can be worked out privately.