h3pilot

Clearing the mapping and rebinding didn't work, but I found that right clicking the cell and selecting reset default worked. That fixed the collective not working in the SH-60B and UH-60L mods and also the ED Mi-24 and KA-50. The red exclamation in the mapped cell went away, but there is still one in the function title cell. However, the reset default did not fix the collective in the ED KA-50 III.

I have the UH-60L v1.4 and the collective axis has stopped working. (It had previously worked, but it has been a while since I've flown it.) DCS control mapping shows the "collective" axis is still mapped to my Thrustmaster Warthog throttle, but there is a red circle with exclamation point next to the "collective" function name in the left column and also next to the mapped axis name under the throttle column of the same "collective" row. When I move the throttle lever, there is no movement of the little axis indicator line that is under the mapped axis name in the box. In the sim, the UH-60L's collective doesn't move. I also see the same behavior in the SH-60B mod. My mapped collective axis in the ED UH-1 and AH-64 are both working with my Thrustmaster throttle, so it isn't a hardware issue. I'm assuming a DCS update has broken the collective axis in the Mods? Does anyone know how to fix it?

I would LOVE to see a Solomon Islands map! And also F4U-1 and F4U-1A versions of the upcoming F4U-1D.

I'm sure someone will make a "Lucybelle" livery or perhaps "883", but technically, Boyington didn't fly a F4U-1D. VMF-214 was still flying the F4U-1A when he was shot down on 3 January 1944. The squadron ended their second combat tour five days later and was reformed in the US. The F4U-1D was introduced in April of 1944. VMF-214 was equipped with the F4U-1D when they deployed on USS Franklin on 4 Feb 1945. Unfortunately, USS Franklin was hit by two Japanese bombs on 19 March 1945. The crew heroically saved the ship, but it was the end of the war for both the ship and VMF-214.

Thanks for all the guide Nikoel!

Is there any more info on this issue? I'm seeing significant left roll when applying forward pitch on the cyclic. The control position indicator shows the cyclic is going straight forward, no left movement. I do not see a corresponding right roll with aft cyclic, though there may be a very small amount of right roll. It seems to be happening at all speeds. (Not just high speed.) Also happens with different joysticks, so not a hardware issue. I also think the yaw and roll are very unstable and have a strong tendency to oscillate. Worse than SAS off in a real helicopter.

The F4U-1D Corsairs used by the USN, USMC, and RNZAF were only painted in two basic patterns. 1) The USN/USMC started using the tri-color scheme in February of 1943, so the first F4U-1Ds would have been delivered in this scheme. - Non-Spectral Sea Blue (ANA 607) - Intermediate Blue (ANA 608) - Insignia White (ANA 601) On 28 June 1943 an ALNAV directed an Insignia Red border around the national insignia. On 29 June 1943, Army-Navy Aeronautical Specification AN-1-9a directed the same red border on all Army and Navy/Marine aircraft by 1 September 1943. This new national insignia was very short lived! Even before the directed completion date, the red border was rescinded. On 31 July 1943, Commander 3rd Fleet directed that the red border be removed from all aircraft in the South Pacific. On 14 August 1943, Army-Navy Aeronautical Specification AN-1-9b directed that the red border be replaced by an Insignia Blue (ANA 605) border on all US aircraft. RNZAF Corsairs were delivered in the same paint schemes as USN/USMC Corsairs. I'm not sure if the RNZAF national markings used the same Insignia Blue as the US. 2) Starting in Oct 1944, USN/USMC fighters were painted Gloss Sea Blue (ANA 623) overall, except a strip in front of the windscreen along the top of the fuselage and cowling, which was still Non-Spectral Sea Blue (ANA 607) to reduce glare for the pilot. There are LOTS of models, toys, and even real aircraft at airshows and on film/tv that are not accurate colors. The most common error is not using the correct Sea Blue. I have seen many cases of brighter blues being used. Some are almost Royal Blue. The correct Sea Blue is pretty dark and has a hint of green in the right light. Overall Sea Blue scheme https://www.history.navy.mil/content/history/museums/nnam/explore/collections/aircraft/f/fg-1d-corsair.html

The rules are complicated and limiting. - Can't use Bonus points for anything already on sale. - Can't use for anything released after 1 August 2019. - Limited to 20% of the price of the first two items and then an additional 5% for additional items, up to a maximum 60% if you are purchasing 9 items. A simple list of products released before 1 August 2019 would be a nice place to start, though many items are already on sale at more than 20% off.

5 November 2018, still broken in version 2.5.3.23255. This is unsatisfactory ED.

update 2.5.2.19641 deleted my Hornet joystick profile! Just did the update to 2.5.2.19641 and now my HOTAS Warthog joystick button assignments for the F/A-18C Hornet are gone. How do I get them back?

I didn't know that about the Москва! The other ships need that too. If having them movable is too much work, every ship with a landable flight deck should just be modeled with the nets and antennas down. Especially as more helicopters are being added to DCS.

Is there a way to remove the black smoke from the LHA? LHAs normally do not emit clouds of black smoke. Neither do other US Navy gas-turbine powered ships. There is normally only very faint exhaust or heat shimmer.

Is there a way to put the flight deck nets on the Oliver Hazard Perry class frigates and Ticonderoga class cruisers into the correct position for helicopter flight operations? The nets are modeled in the vertical (stowed) position. The nets should be lowered to their horizontal position during all flight operations. If the nets are not modeled to move, could the ship models please be updated to put the nets down so helicopters can be operated from the flight decks properly?

Love the F-5! I noticed that the Instant Action F-5E Cold Start mission has two floating B-1s on the east side of Nellis. Not really an F-5 bug, but a mission bug.

You need to hear the tone change before pressing the uncage button. When you hear the sidewinder tone change from the search buzz to the high pitch whine/tracking tone, that is when you press and hold the uncage button. The missile seeker will now continue to track the target through a wider area and you will continue to hear the high pitch tracking tone. I currently have a very small acquisition area, located above the pipper, where the target must be before I can get the missile tone to change from search to tracking. (I don't know how accurate this is, or if it is a bug.) However, once the tone changes, if I immediately press and hold the uncage button, the missile will continue to track the target even if it moves back outside the original tiny acquisition area.