fargo007

I went with the Crosswinds and have not looked back.

This video will take you through it. You want the LDT.

Stop it, most of us are in our 40's and 50's.

What were the conditions? Altitude? Temp? That's going to play a role there too. A big one.

This represents exactly what I posted to do on the previous page. Flare at fifty feet then use collective to cushion, and plan on a running landing. And yes, you have to go cyclic back. Either trim it or hold it there. Otherwise you won't be able to maintain RPM's which is a necessary component of any autorotation.

I think you need to maintain around 130kmh. The secret at the bottom end is to flare at 50 feet with no collective, then you pull in collective to cushion it. An auto in the gazelle will be a running landing.

Is this project still being maintained? Since 2.5.6 we have the ability in multiplayer to simulate actual cargo weight. I have added logic to introduce this into CTLD. The weights for troops are now simulated, and the "check cargo" menu item also shows the weight if the helicopter has any on board. I'd rather submit it to be merged than release it as a fork.

LOL - I'm the bomber pilot. :thumbup:

I don't think the viewpoint that CTLD is complicated to use is completely accurate. Using a script that already exists is not being in the business of scripting..... You load mist, you load CTLD, you name the helicopters and groups accordingly and you're done. Unlike the ME where the troops had to be mapped to specific helicopters to transport them, anyone can pick up any group of troops with CTLD. make a pickzone and you can load them directly into the helicopter while in that zone (like for a farp, base, etc).

Adding to the sound advice here, at the transition from ETL (anyone who doesn't know what this is should go read up) to hovering flight there's going to be a pretty decent power increase (collective) required. This is what I believe gets a lot of people in trouble. They are either not ready for it, or they underestimate the power change requirement as you come out of ETL.

The architecture of a large scale, or long-running mission matters a lot as well. What won't work is to just load the map up with the entire Opposing army. It will perform terribly. There are ways to deal with this at larger scale that involve some technique of compartmentalizing what is alive at any one time on the map. Usually in mini or subordinate missions in some kind of structure.

This. I use "SEARCH THEN ENGAGE IN ZONE."

We will get the parade together, thanks again @Chump! Even the Merkury system that is in the Su-25 would be a vast improvement, and was apparently intended for the N, so I think there's a basis of authenticity there. The dragon we are chasing here (with the changes in these mods) is a point somewhere between the functional light filters, and Merkury LLTV. Both are good points to bring up. If these are added/improved in the upcoming paid version, I'll cheerfully reassess. Those who wish to fly the Ka-50 in daytime only and insist on version-authenticity are of course free to continue doing so.

This is a big improvement! Now that I see how these values can be manipulated, I understand how this works a whole lot better. You can still launch Vikhr missiles, but you have to guide them to the target manually by slewing the targeting gate very precisely. Thank you @Chump for your quick attention and excellent quality response.

Thank you so much man. Willing to pitch in if you find a way to tune the image before the shader gets it. The issue as I find it is unique to the ka-50. None of the other MFD's in other AC were affected. The color mod was so key to our squadron it was almost de-rigueur. We would love to see it return. I mean like a parade and stuff.

As I said in the OP: We had been using this with great success prior to the ka-50 cockpit update. In the new 2.5.6 cockpit, the ka-50 shkval is so dark that it's completely unusable at night. With, or without the color mod. Try it. Apply the color mod and fly the ka-50 at night. I'd LOVE to be wrong here because many of us preferred the color mod.

I did some tweaking after coming to the realization that the new shkval is totally useless at night. The color MFD mod doesn't seem to be working anymore. The underlying image that comes into the shaders has been hopelessly darkened or gamma'd down such that it too is unusable. This is a net resolution improvement in both day and night ops for the shkval. Step 1 is to remove (back up) lensGhosts.hlsl from Bazar/shaders/PostEffects (this eliminates the reflection on the shkval of the cockpit) This mod gets applied to the main DCS installation. It affects two files.  The two files that are changed are in shaders. Back them up if you wish.(edited) WARNINGS: 1 - This is for the KA-50 only. It will likely interfere with the MFD of any other aircraft. 2 - No idea if it passes IC (because I don't care). 3 - When you enter the aircraft it will be a static white display. Max out brightness and contrast, then start dialing the brightness down. You may have to wiggle this a little bit to get the right image. 4 - HIGHLY likely this will be mooted or broken by future updates. This is intended for "the time being." If anyone finds a way to improve, or bring back the color MFD mod (owner is not maintaining anymore), please feel free to take this further. Before: After: FargoShkval.zip

This bears repeating. Thank you guys for pushing forward.

We can koopa stomp them in a helicopter........

This is called nav by "Dead Reckoning." He's absolutely right about landmarks, and getting used to looking for and using them on routes. If there are power lines that parallel your route, rivers that you will cross, valleys, draws, saddles, all of the terrain features need to become part of your plan, and features that define your waypoints. You are navigating "inside" the helicopter and need to start learning how to incorporate navigating "outside."

Why swim upstream? Align the waypoint with a zone and just use the zone.

You can see a lot of the speed/torque settings while in flight on this 360 degree video when we hired a UH-1H for a half hour. This is with ten people on board too, so I would agree with the power gap having seen it first hand.

I have this mod working with a very annoying side effect. Each time I start DCS, my pitch and roll axes are broken (dark gray) and have to be fixed by selecting "default" for each one. Anyone have any idea how to remedy that? Thanks fellas.

The above exercise in moose would look roughly like this: local _zone = ZONE:New("enemyzone") local _group = GROUP:FindByName("badguys") if _group:IsCompletelyInZone(_zone) then end MOOSE has the best documentation there is for any of this stuff. Hands down. Just ask here like you're doing, or better yet join the MOOSE discord. Plenty of people there to assist, and once you get the feel for MOOSE you start laying down sick functionality really fast.

This is excellent. Is there any advice or technique to move this functionality into an existing mission? I see there's a lua script, but also a whole bunch of triggers that seem to call functions defined in the script. If anyone's attempted that please share your experiences.