Bankler's CASE 1 Recovery Trainer

I suspect he thinks he should fly the VVI all the way down the middle of the ICLS needles cross and at the same time pointing to the touchdown point. But that is wrong.

If that is the case? Then perhaps going back and study up on how the Hornet / NAVY lands their aircraft on Carriers is needed.

Check out this thread I put together about it all. Or at least watch

David, I refer to it as the VV because of Chuck's Guide. I like 'flight path marker' better but...

VV by craig stuard, on Flickr

Anyway, yes it is on the glide slope line or the line is within the diameter of the circle, so I am very close to correct on altitude according to that indicator ,but I constantly get the on screen comments saying I am way high. BTW, yes I am on speed in the center of the E bracket.

At this point in your approach would you expect to be told you are way high?

case 1 by craig stuard, on Flickr

Here you can see the meatball but also notice the VV is on the notch. This is how I usually look and the LSO is saying 'power, power'.

case 1 2 by craig stuard, on Flickr

Razor- yes I do think that. Got used to that doing straight in approaches because I couldn't see the ball well enough to use it. Now I have a new PC and better screen I can see it. But now I am also doing (trying) the correct pattern and I see that, until very late (wings level and on lineup) the E bracket and other crap in the hud hides the ball. So the ball is good for maybe the last 10-15 seconds only. That 10-15 seconds is the 'groove' right?

Overall this is a lot harder than I thought it would be. I have that diagram of the pattern printed and sitting next to the screen. I have watched Lex's videos twice, several other tutorials including WAGS a couple times each. Probably have done 150 traps on my own and now having discovered Bankler's excellent tool, another 100 or so . I am just trying to figure why I am getting what seems to be conflicting info. I really appreciate everyone's help.

It's not good practice to use the VV on final. Because the boat is moving away from you, if you keep the VV on the notch, your approach will get shallower/lower as you get nearer. You're low in your pic, which is why you're getting power calls.

David, I refer to it as the VV because of Chuck's Guide. I like 'flight path marker' better but...

VV by craig stuard, on Flickr

Anyway, yes it is on the glide slope line or the line is within the diameter of the circle, so I am very close to correct on altitude according to that indicator ,but I constantly get the on screen comments saying I am way high. BTW, yes I am on speed in the center of the E bracket.

At this point in your approach would you expect to be told you are way high?

case 1 by craig stuard, on Flickr

Here you can see the meatball but also notice the VV is on the notch. This is how I usually look and the LSO is saying 'power, power'.

case 1 2 by craig stuard, on Flickr

Razor- yes I do think that. Got used to that doing straight in approaches because I couldn't see the ball well enough to use it. Now I have a new PC and better screen I can see it. But now I am also doing (trying) the correct pattern and I see that, until very late (wings level and on lineup) the E bracket and other crap in the hud hides the ball. So the ball is good for maybe the last 10-15 seconds only. That 10-15 seconds is the 'groove' right?

Overall this is a lot harder than I thought it would be. I have that diagram of the pattern printed and sitting next to the screen. I have watched Lex's videos twice, several other tutorials including WAGS a couple times each. Probably have done 150 traps on my own and now having discovered Bankler's excellent tool, another 100 or so . I am just trying to figure why I am getting what seems to be conflicting info. I really appreciate everyone's help.

Sorry for the bigass quote.

You fly instruments until the 90°, you can use the VV to a limited amount while getting into the groove. Once in the groove, you fly the ball, like others have said (technically, ball and line-up until in close, when you can't do much about lineup).

When the LSO says "power", it doesn't necessarily mean you are too low. It may also mean you are approaching glideslope from above and your sinkrate is going to put you below the glideslope if you don't fix your power setting. Take the call literally, adjust your power to arrest your sinkrate and then see what happens to your glideslope. Also, bankler's script is super strict and will start calling you out for minor deviations, it feels like.

Last thing, if you post screenies, post high res pictures. I can't read anything on your hud. :)

Slant, I just realized I screwed that up. Those pics are 1-from Chucks guide and 2&3- from the video that David posted. I tried to snap a screen shot of my own approach but haven't got the process down yet. Unfortunately I am on a slow satelite web connection so I have to run youtube videos at 480 resolution. I think you may be right, Bankler is strict. I have always felt that as long as the VV circle is touching the ICLS cross hairs that is close enough that it's correctable. I guess Bankler's margin of allowable error is smaller than mine.

Flamin, that is a very good point. I have noticed that my lineup may start fine right as the wings come level but gets worse as I get closer. I think it is the same thing you mention regarding altitude but on a 90 degree different plain. The boat is constantly moving; 1- away which affects planes altitude/glide slope, and 2- to the plane's right so I end up coming onto the deck at an angle.

I just need a couple hundred more traps and maybe I will be reasonably proficient.

Putting your velocity vector on the ICSL glideslope is not a bad move per say. Just be aware that in the turn you have a much slower descent (since your vector to the carrier is offset by your lateral movement, ie. you're not pointing at the carrier as if you were flying a true glideslope on glidepath).

Once you are in the groove, your descent rate would be slightly higher than while in the turn. You need to adjust your glideslope accordingly. And of course, like everyone else says, you need to fly the ball (and line-up with centerline, most people don't mention this, but it is important).

This is EXACTLY the tool I needed to help with my traps. I can get on the boat most times but Jester almost always complains it's a bolter and I know it's not pretty and this helps me know the many things I need to correct. Which is helping me learn to properly trim on the break and downwind especially.

GREAT stuff. Kudos.

Can you do one for aerial refueling??

What would be the proper feedback parameter about refueling?

"don't shoot me!"

I had a few questions as to how Pattern mode works. Do you not lower the hook? To engage it do I call up the map page? After I bolter do you stay dirty and fly a 600 ft pattern?

I love this tool it is beyond words the amount of help this has been I have a long way to go but it's fun watching my score sometime jump a little. Thanks

Where should this be placed?

in your saved games dcs missions directory

WOW that was simple. Thanx. I need my coffee

Anyone else having issues using the mission since the latest patch?

hangs for me !

it seems there is a series of bugs caused by the change in the scripting engine, as this a pretty heavily scripted mission im guessing it breaks

For me it dies on loading during "Terrain Preload: 100, Stage 38"

Investigating.

Some progress here. The KC-130 is bugged. It's invisible. And if that aircraft is shown as the preview aircraft when selecting slot, the mission won't even load.

I will post a fixed mission in short.

Problem solved!

New version, compatible with new patch is out:

5.1.0

* You can now use the F10 radio menu to Reactivate TACAN in case the "random TACAN death" bug should happen.

* Replaced the KC-130 with a KC-135MPRS as a workaround as the bugged KC-130 stopped the mission from loading.

* Changed the tanker route into using a race track waypoint.

Download 5.1.0 on first page. Keeping 5.0.0 available for a while just in case. But this new version should work even if you have rolled back.

Love this mission btw. You're a hero.

Thanks for the update Bankler. It's working again :thumbup:

I did however notice, that the KC-135 also vanished at some point.

18nm to ±3nm distance = visual contact

±3nm to 0.7nm KC-135 disappeared

<0.7nm = ah, there it is again :P

ED has some serious work to do before they roll out 2.5.6 to stable :music_whistling:

Hi Bankler - Thanks for making this awesome mission - it has really improved my flying around the boat!

Unfortunately, since this latest version "DCS Openbeta 2.5.6.43872", I am now getting error messages and no scoring/text of any kind.

The messages are "Mission Script Error"s - the first one is "string DleayedMissionStart", and the subsequent errors are "String Init: attempt to call global init". None of that means anything to me - perhaps it makes sense toy you!

I have tried your missions versions 04-02 (I changed the KC-130 to a C-130 so it would work), and the latest 05-10. Both were working with the big update earlier this week "DCS World open beta 2.5.6.43453", but neither work with today's update "43872".

Assuming this is not just on my install, I wanted to give you a heads-up.

Thanks again for the great work!

I got lots of script error doing the latest version today.

I could still fly the aircraft when I click OK after the error windows but no monitoring of positions and scores.

I'm not able to choose aircraft after the latest update and I had to switch to standalone.

It just places a spectator camera behind the KC-130, with no option for "Select Role" in the Escape menu.

Have I done something wrong during the switch to standalone, or is this because of the update?